ANS-C01 Question 289
Select 2You are managing a global application hosted on AWS that needs to direct users to the nearest application endpoint based on latency. Additionally, in certain scenarios, you need to distribute traffic evenly across endpoints regardless of location. Which combination of methods would you use to achieve this requirement?
- A
Use Route 53 with a Geolocation routing policy for latency-based traffic distribution.
- B
Use Route 53 with a Latency routing policy to route users to the endpoint with the lowest latency.
- C
Use Route 53 with a Weighted routing policy to evenly distribute traffic across endpoints.
- D
Use Application Load Balancer's target groups to route traffic based on geography.
- E
Use Route 53 Failover routing policy to select endpoints based on latency.
Show answer and explanation
Correct answers: B, C
Explanation
To meet the requirements of routing traffic based on latency and evenly distributing traffic across endpoints, you need to use a combination of Route 53 Latency routing and Weighted routing policies. Latency routing ensures users are directed to the nearest endpoint with the least latency, while Weighted routing allows for even traffic distribution across all endpoints.
- A. Incorrect.
Geolocation routing in Route 53 is used to route traffic based on the user's geographic location, not latency. This does not meet the requirement for latency-based routing.
- B. Correct.
Latency routing in Route 53 directs users to the endpoint with the lowest latency, addressing the requirement for latency-based traffic distribution.
- C. Correct.
Weighted routing in Route 53 allows you to distribute traffic evenly or in specific proportions across endpoints, fulfilling the requirement for equal distribution regardless of location.
- D. Incorrect.
Application Load Balancer’s target groups are not designed to route traffic based on geography. This option does not satisfy the requirements in the scenario.
- E. Incorrect.
Failover routing in Route 53 is used to route traffic to a backup endpoint when the primary one becomes unavailable. It does not consider latency.