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

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

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

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

1. Given the chance >always use Alias over a Cname< 2. Latency-based routing is for user experience. (low latency) Failover is for DR, Geolocation for local restrictions/rights/language/currency, and geo-proximity is a more complex, biased location-based routing, not part of the SA Associate exam.

Geoproximity Policy routing users to resources based on their geographic location, routing based on geographic location may not always be the absolute lowest latency. latency-based routing prioritizes user experience.

Based on previous questions, I believe A is correct. Because; the closest geolocated server doesn't necessarily provide the best performance. Geolocated load balancing is mostly used for serving location-specific content.

Q. What is Amazon Route 53's Latency Based Routing (LBR) feature? LBR (Latency Based Routing) is a new feature for Amazon Route 53 that helps you improve your application’s performance for a global audience. You can run applications in multiple AWS regions and Amazon Route 53, using dozens of edge locations worldwide, will route end users to the AWS region that provides the lowest latency. https://aws.amazon.com/route53/faqs/

The correct is D, the question says "using an Application Load Balancer" the ALB has a DNS name assigned not an IP. A type A record will only allow you to point to an IPv4. If I'm wrong, happy to be corrected.

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.

A is true

D looks correct.

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

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.

But generally speaking it's not a bad idea. But yes A record alias name can point to it. and i don't think it's B cause even if it's geolocation it may not always result in a high-performing exp.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html To provide the MOST high-performing experience, the Latency-based routing policy is the most appropriate. It ensures requests are routed to the AWS Region that provides the fastest response times based on real-world network conditions.

three AWS Regions using an Application Load Balancer?? I think they meant to say three AZs. ALBs do not span regions.

ChatGPT: The most high-performing experience in this scenario would be achieved by using: D. Create a CNAME record with a geoproximity policy. Geoproximity routing allows you to route traffic based on the geographic location of your users and your resources. This would distribute traffic to the AWS Region that is closest to the user, optimizing performance by reducing latency. It's particularly useful when deploying applications across multiple regions to ensure users are directed to the closest region, minimizing network latency and providing the best user experience.

Sorry changing to B.

Why would you use a CNAME record?? Most suitable seems to be option B