Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 692 discussion

Alias?! "A record" is NOT an Alias record; it's an ADDRESS RECORD. There's a difference in between an address record (A record) & an Alias. An Address record will map to 1 or more IP addresses. An Alias record will map to another name like a CNAME does. We eliminate C&D bc we need an IP address that will give us the best performance; we distribute traffic to a certain IP address based on policy. geolocation policy is defined by where the request comes from. latency policy is defined by how fast (performance) we can reply.

Answer A is correct. Route53 uses an internal record type called ALIAS, but from a DNS point of view it's still an A record. Just try it yourself, create an ALB and create a DNS record in Route53. While you can technically use a CNAME (for subdomains, see below), the wizard will guide you to use an A ALIAS record, which also makes the most sense. The problem with CNAME records is that it's not possible to create them at the root level of the domain. Let's say your domain is somedomain.com - you can't create a CNAME for the apex of the domain (mydomain.com), only for subdomains (subdomain.mydomain.com). https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html

And, exactly, this is the reason why you should not rely on a LANGUAGE MODEL when you need a solution architect's advice .

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-latency.html

Not really sure but ALBs do not have a static ip address they have domains assigned to them and also an Elastic ip can't be attached to an ALB. So mainly a cname would be preferred here.