Route 53 Routing for Closest EC2 Instances Globally

SAA-C03 By islever Editorial Last updated

Determine high-performing and/or scalable network architectures. Design highly available and/or fault-tolerant architectures.

Short answer

B Use Amazon Route 53 geoproximity routing with an internet-facing Network Load Balancer to send each user to the closest EC2 instances across Regions.

Question

A company is implementing a new application on AWS. The company will run the application on multiple Amazon EC2 instances across multiple Availability Zones within multiple AWS Regions. The application will be available through the internet. Users will access the application from around the world. The company wants to ensure that each user who accesses the application is sent to the EC2 instances that are closest to the user’s location. Which solution will meet these requirements?
  1. Implement an Amazon Route 53 geolocation routing policy. Use an internet-facing Application Load Balancer to distribute the traffic across all Availability Zones within the same Region.
  2. Implement an Amazon Route 53 geoproximity routing policy. Use an internet-facing Network Load Balancer to distribute the traffic across all Availability Zones within the same Region. Correct Answer
  3. Implement an Amazon Route 53 multivalue answer routing policy. Use an internet-facing Application Load Balancer to distribute the traffic across all Availability Zones within the same Region.
  4. Implement an Amazon Route 53 weighted routing policy. Use an internet-facing Network Load Balancer to distribute the traffic across all Availability Zones within the same Region.

Key Takeaways

Tested: distinguishing geoproximity from geolocation; the trap is assuming geolocation always routes to the physically closest region.

This question tests Amazon Route 53 routing policies for directing global users to the closest EC2 instances across multiple AWS Regions. The correct answer (B) uses geoproximity routing with an internet-facing Network Load Balancer to distribute traffic across Availability Zones.

Common mistake: Many candidates choose A (geolocation) because it also routes based on user location, but geolocation maps users by country or continent rather than calculating true geographic proximity to resources.

Expert Analysis

Why the Answer Is Correct

Geoproximity routing in Amazon Route 53 is designed to route traffic based on the geographic location of both users and resources, which directly satisfies the requirement to send each user to the closest EC2 instances. By using an internet-facing Network Load Balancer, the application can distribute incoming traffic across all Availability Zones within a Region, even though NLB operates at layer 4. The combination of geoproximity routing and a NLB provides a scalable, low-latency solution for a global user base. The question emphasizes "closest to the user's location," a phrase that aligns with geoproximity rather than geolocation. Therefore, option B is the correct solution.

Why the Other Options Are Wrong

Option A uses geolocation routing, which routes users based on their country or continent rather than true proximity; it cannot guarantee the closest EC2 instances. Option C uses multivalue answer routing, which simply returns multiple healthy records and does not consider user location. Option D uses weighted routing, which distributes traffic according to predefined weights, not geographic proximity. Although option A includes an Application Load Balancer, the routing policy is the critical differentiator and is incorrect.

Community Comment Notes

As dhewa noted, geoproximity routing "directs traffic based on the geographic location of your users and your resources." LeonSauveterre argued that "geoproximity is better for ensuring actual closeness" even if it adds complexity. Bwhizzy claimed "you can't use a network load balancer for internet traffic," but this is incorrect because NLB supports internet-facing workloads. The majority vote for B reflects the correct understanding that geoproximity is the policy for proximity-based routing.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When a question emphasizes 'closest' or 'proximity' to users, prioritize Route 53 geoproximity over geolocation. Also, don't reject a solution solely because it uses an NLB; both ALB and NLB can be internet-facing, and the question's primary focus is the routing policy.

Frequently Asked Questions

Why is geolocation routing not the best choice for routing to the closest EC2 instances?

Geolocation routes based on the user's country or continent, not true geographic proximity. It cannot dynamically calculate the closest region as geoproximity does.

Can a Network Load Balancer be used for an internet-facing application?

Yes, NLB supports internet-facing traffic and can distribute across Availability Zones, though ALB is often used for HTTP/HTTPS-specific features.

More SAA-C03 FAQ →

Community Votes

B
65%
A
35%

65% of anonymous learners picked answer B. 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. dhewa 👍 9 Answered B
    Keyword closest. Amazon Route 53 Geoproximity Routing: This routing policy directs traffic based on the geographic location of your users and your resources, ensuring that users are routed to the closest EC2 instances.
  2. nebajp 👍 8 Answered A
    Correct answer is A Geo location is based on users location GeoProximity is based on the AWS services used by users.
  3. LeonSauveterre 👍 4 Answered B
    A - "geolocation" is simple and effective, but it might not always direct users to the physically closest Region. It’s more about their geographic "label" (country/region). B - "geoproximity" is better for ensuring actual closeness but adds a bit more complexity. Then, I don't think ALB or NLB should be an argument here. NLBs are generally preferred for applications that require high throughput and low latency, especially if they are not using HTTP/HTTPS. NLBs operate at Layer 4 (TCP/UDP), so suitable for a wider range of applications than ALBs (Layer 7, HTTP/HTTPS). Even if the application does use HTTP/HTTPS, NLBs can still be used if you don't need the advanced features of an ALB (like content-based routing or host-based routing). Then again, the question haven't explicitly stated the protocol so oh well, I'm gonna go with B.
  4. [Removed] 👍 4 Answered B
    Geolocation Routing Policy - Routes traffic based on the geographic location of the users. Geoproximity Routing Policy - Routes traffic based on the geographic proximity of the user to AWS resources.
  5. Bwhizzy 👍 4 Answered A
    The answer is A. routing traffic to the user region. Also, it can't be B. It says using a Network Load Balancer. you can't use a network load balancer for internet traffic
Show 8 more comments
  1. blehbleh 👍 3 Answered B
    It is B: Geolocation: Primarily focuses on the user's location, allowing you to serve different content based on their geographic region. Geoproximity: Considers both the user's location and the location of your resources, dynamically choosing the closest option based on network latency.
  2. Salilgen 👍 2 Answered B
    https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-geoproximity.html
  3. dragossky 👍 1 Answered B
    Which AWS Route 53 routing policy should be used to route traffic based on users' location? Geoproximity routing Geoproximity routing lets Amazon Route 53 route traffic to your resources based on the geographic location of your users and your resources.
  4. deacon967 👍 1 Answered A
    You can argue geolocation vs geoproximity all day but why would one use a NLB for an internet based app? The is the perfect use case for an ALB. A is the correct answer.
  5. komorebi 👍 5 Answered B
    Answer is B
  6. b3b5fdd 👍 4 Answered B
    Correct answer is B!
  7. kbgsgsgs 👍 2 Answered A
    Correct answer is A
  8. 8621a7c 👍 2 Answered A
    Go with A

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