ANS-C01 Question 420
Select 2Your company is running a web application hosted on Amazon EC2 instances behind an Application Load Balancer (ALB) in a single AWS Region. The traffic to your application has increased significantly, and you notice that users in different geographic locations are experiencing higher latency when accessing the application. To address this, you want to implement a solution to improve performance by distributing traffic based on the geographic location of users. Which combination of steps should you take to achieve this?
- A
Configure a Route 53 Geolocation routing policy to route traffic to multiple ALBs deployed in different Regions.
- B
Deploy additional Application Load Balancers (ALBs) in multiple AWS Regions closer to your users.
- C
Enable cross-zone load balancing on the existing Application Load Balancer (ALB).
- D
Configure a Route 53 Weighted routing policy to distribute traffic across multiple ALBs.
- E
Use AWS Global Accelerator to route traffic to the closest ALB based on latency.
Show answer and explanation
Correct answers: A, B
Explanation
To reduce latency for users in different geographic locations, you must deploy additional ALBs in Regions closer to those users and use Route 53 Geolocation routing to direct traffic based on their location. This solution ensures that users are routed to the nearest Region, improving overall application performance. Cross-zone load balancing and Weighted routing are not suitable in this scenario as they do not address geographic distribution. While AWS Global Accelerator is latency-focused, the requirement specifically calls for geolocation-based traffic distribution.
- A. Correct.
Correct: Route 53 Geolocation routing allows you to route traffic to different endpoints based on the geographic location of the users, addressing the latency issue for users in different regions.
- B. Correct.
Correct: Deploying additional ALBs in multiple AWS Regions closer to your users ensures that traffic is routed to the nearest Region, reducing latency and improving application performance.
- C. Incorrect.
Incorrect: Cross-zone load balancing improves load distribution across Availability Zones within a Region but does not address latency for users in different geographic locations.
- D. Incorrect.
Incorrect: Route 53 Weighted routing distributes traffic based on assigned weights and does not consider geographic location, so it is not suitable for addressing regional latency issues.
- E. Incorrect.
Incorrect: AWS Global Accelerator routes traffic based on latency but does not use geolocation to route traffic. In this scenario, geolocation-based routing is specifically required.