Discover how to leverage Amazon Route 53’s latency routing policy to automatically route user traffic to the Application Load Balancer endpoint with the lowest latency, ensuring optimal performance without changing the URL.
Table of Contents
Question
A company has an application that runs behind an Application Load Balancer (ALB) in the us-west-2 Region. An Amazon Route 53 record set contains an alias record for app.anycompany.com that references the ALB in us-west-2 and uses a simple routing policy. The application is experiencing an increase in users from other locations in the world. These users are experiencing high latency.
Most of the new users are close to the ap-southeast-2 Region. The company deploys a copy of the application to ap-southeast-2. A SysOps administrator must implement a solution that automatically routes requests to the lowest latency endpoint for users without changing the URL.
Which solution will meet these requirements?
A. Add a new value to the existing alias record for app.anycompany.com with the DNS name of the new ALB in ap-southeast-2.
B. Change the existing alias record to use a geolocation routing policy. Create two geolocation records, one record that references each ALSelect the location that is closest to each Region.
C. Change the existing alias record to use a latency routing policy. Create two latency records, one record that references each ALB.
D. Change the existing alias record to use a multivalue routing policy Add the DNS name of each ALB to the record.
Answer
C. Change the existing alias record to use a latency routing policy. Create two latency records, one record that references each ALB.
Explanation
- The latency routing policy in Amazon Route 53 is designed to route traffic to the resource that provides the lowest latency for the end-user’s location.
- To implement this solution, the SysOps administrator should change the existing alias record for app.anycompany.com from a simple routing policy to a latency routing policy.
- Under the latency routing policy, two latency records should be created, one for each Application Load Balancer (ALB) endpoint:
- The first latency record should reference the DNS name of the ALB in the us-west-2 Region.
- The second latency record should reference the DNS name of the newly deployed ALB in the ap-southeast-2 Region.
- When a user accesses app.anycompany.com, Route 53 will automatically route the request to the ALB endpoint that provides the lowest latency based on the user’s geographic location.
- This solution ensures that users are directed to the nearest endpoint without the need to change the URL, providing a seamless and low-latency experience.
The other options are incorrect because:
A. Adding a new value to the existing alias record with the DNS name of the new ALB would create a multivalue answer, which does not consider latency and may not route users to the nearest endpoint. B. Using a geolocation routing policy would require manually defining geographic regions and assigning them to specific endpoints, which may not accurately reflect the lowest latency for all locations. D. A multivalue routing policy distributes traffic randomly across the specified resources, which does not consider latency and may lead to suboptimal performance for users.
Amazon AWS Certified SysOps Administrator – Associate certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Amazon AWS Certified SysOps Administrator – Associate exam and earn Amazon AWS Certified SysOps Administrator – Associate certification.