SAA-C03 · Question #53
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…
The correct answer is A. Implement an Amazon Route 53 geolocation routing policy. Use an internet-facing Application. The requirement is to route users to the nearest AWS Region where the application is deployed. The best solution is to use Amazon Route 53 with a geolocation routing policy, which routes traffic based on the geographic location of the user making the request. Geolocation…
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?
Options
- AImplement an Amazon Route 53 geolocation routing policy. Use an internet-facing Application
- BImplement an Amazon Route 53 geoproximity routing policy. Use an internet-facing Network Load
- CImplement an Amazon Route 53 multivalue answer routing policy Use an internet-facing
- DImplement an Amazon Route 53 weighted routing policy. Use an internet-facing Network Load
How the community answered
(45 responses)- A76% (34)
- B4% (2)
- C7% (3)
- D13% (6)
Explanation
The requirement is to route users to the nearest AWS Region where the application is deployed. The best solution is to use Amazon Route 53 with a geolocation routing policy, which routes traffic based on the geographic location of the user making the request. Geolocation Routing: This routing policy ensures that users are directed to the resources (in this case, EC2 instances) that are geographically closest to them, thereby reducing latency and improving the user Application Load Balancer (ALB): Within each Region, an internet-facing Application Load Balancer (ALB) is used to distribute incoming traffic across multiple EC2 instances in different Availability Zones. ALBs are designed to handle HTTP/HTTPS traffic and provide advanced features like content- based routing, SSL termination, and user authentication. Why Not Other Options?: Option B (Geoproximity + NLB): Geoproximity routing is similar but more complex as it requires fine- tuning the proximity settings. A Network Load Balancer (NLB) is better suited for TCP/UDP traffic rather than HTTP/HTTPS. Option C (Multivalue Answer Routing + ALB): Multivalue answer routing does not direct traffic based on user location but rather returns multiple values and lets the client choose. This does not meet the requirement for geographically routing users. Option D (Weighted Routing + NLB): Weighted routing splits traffic based on predefined weights and does not consider the user's geographic location. NLB is not ideal for this scenario due to its focus on lower-level protocols.
Community Discussion
No community discussion yet for this question.