Route 53 Latency-Based Routing for High Performance

SAA-C03 By islever Editorial Last updated

Determine high-performing and/or scalable network architectures.

Short answer

A Create an A record with a latency policy.

Question

A company is deploying an application in three AWS Regions using an Application Load Balancer. Amazon Route 53 will be used to distribute traffic between these Regions. Which Route 53 configuration should a solutions architect use to provide the MOST high-performing experience?
  1. Create an A record with a latency policy. Correct Answer
  2. Create an A record with a geolocation policy.
  3. Create a CNAME record with a failover policy.
  4. Create a CNAME record with a geoproximity policy.

Key Takeaways

The question tests the distinction between latency-based and geolocation-based routing, with the common trap being the assumption that geographic proximity always equals network latency.

This page explains how to use Amazon Route 53 latency-based routing policies to direct traffic to the AWS region providing the lowest latency, ensuring the highest performance experience for global users.

Common mistake: Many learners choose Geolocation (B) or Geoproximity (D), mistakenly believing that physical distance is the primary factor in network performance, ignoring actual network path latency.

Expert Analysis

Why the Answer Is Correct

Latency-based routing is specifically designed to route traffic to the resource that provides the lowest latency, which directly addresses the requirement for the 'MOST high-performing experience.' By measuring real-time network conditions from various locations to each endpoint, Route 53 ensures users are directed to the fastest available region, making Option A the correct choice.

Why the Other Options Are Wrong

Geolocation (B) routes based on user location but does not account for current network congestion or latency variations, potentially leading to suboptimal performance. Failover (C) is intended for disaster recovery scenarios rather than optimizing active traffic performance. Geoproximity (D) allows biasing based on location but is more complex and still relies on geographic data rather than pure latency metrics, and CNAME records are generally less optimal than Alias records for ALBs.

Community Comment Notes

As noted by Kezuko and h0ng97_spare_002, official AWS documentation confirms that latency-based routing is the appropriate policy for improving application performance for a global audience. User sandordini highlighted that while CNAMEs can point to DNS names, Alias records are preferred for ALBs, though the key differentiator here is the routing policy itself. User mohammadthainat correctly pointed out that geographic location does not always correlate with the absolute lowest latency, reinforcing why Geoproximity is not the best answer for pure performance optimization.

Official Reference

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

This link opens the official vendor documentation in a new tab.

Exam Strategy

When asked about 'high performance' or 'lowest latency' in multi-region deployments, always select Latency-Based Routing. Distinguish this from 'disaster recovery' (Failover) or 'compliance/localization' (Geolocation). Remember that Alias records are typically used with ALBs, but the routing policy is the deciding factor in these questions.

Frequently Asked Questions

Why not use Geoproximity for better performance?

Geoproximity uses geographic location and can apply biases, but it doesn't measure real-time network latency. Latency-based routing directly optimizes for the fastest response time.

Should I use CNAME or Alias for ALB?

While the question options use A/CNAME, AWS recommends using Alias records for Application Load Balancers because they are free and resolve to IP addresses dynamically. However, the routing policy is the key exam concept here.

More SAA-C03 FAQ →

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 13 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 13

  1. Kezuko 👍 6 Answered A
    https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html
  2. sandordini 👍 4 Answered A
    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.
  3. mohammadthainat 👍 4 Answered A
    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.
  4. 1Alpha1 👍 3 Answered A
    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/
  5. haci 👍 3 Answered A
    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.
Show 8 more comments
  1. cedser8 👍 3 Answered D
    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.
  2. osmk 👍 2
    A https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-latency.html
  3. bodakrishna 👍 1
    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.
  4. LeonSauveterre 👍 1 Answered A
    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.
  5. Cali182 👍 1 Answered B
    Why would you use a CNAME record?? Most suitable seems to be option B
  6. TruthWS 👍 3
    A is true
  7. Andy_09 👍 2
    D looks correct.
  8. Andy_09 👍 1
    Sorry changing to B.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide