ANS-C01 Question 58
Select 2An e-commerce company is designing a high-traffic web application hosted in multiple AWS Regions. The application must meet the following requirements:
- Automatically distribute incoming traffic across multiple backend instances in multiple Regions to handle surges in demand.
- Provide a secure interface to handle SSL/TLS termination.
- Route traffic based on the geographic location of users to reduce latency.
Which solution design meets these requirements?
- A
Use AWS Global Accelerator with ALBs in each Region to distribute traffic and enable SSL termination.
- B
Use Amazon Route 53 with geolocation routing policies and ALBs in each Region for SSL termination.
- C
Use an Application Load Balancer (ALB) in a single Region with cross-zone load balancing enabled and geolocation routing.
- D
Deploy Elastic Load Balancers (ELBs) in each Region and use Route 53 for geographic routing and SSL integration.
- E
Use a Network Load Balancer (NLB) with AWS Global Accelerator for multi-Region traffic distribution and SSL termination.
Show answer and explanation
Correct answers: B, D
Explanation
To meet the requirements of high availability, scalability, and security, the solution must distribute traffic across multiple Regions, handle SSL termination, and route traffic based on geographic location. Amazon Route 53 with geolocation routing policies, combined with ALBs or ELBs in each Region, fulfills all these criteria. AWS Global Accelerator and NLBs provide robust performance improvements but lack native geolocation routing capabilities.
- A. Incorrect.
AWS Global Accelerator improves performance by routing traffic to the optimal endpoint but does not provide native geolocation-based routing. While it supports SSL termination, it doesn't fully meet the requirement of geolocation routing.
- B. Correct.
Amazon Route 53 supports geolocation routing policies, which can direct traffic based on user location. When combined with ALBs in multiple Regions, it enables SSL termination and distributes traffic effectively.
- C. Incorrect.
An ALB in a single Region cannot handle traffic distribution across multiple Regions or meet the geolocation routing requirement. Cross-zone load balancing is limited to balancing traffic within a single Region.
- D. Correct.
Elastic Load Balancers (ELBs) in each Region can be integrated with Route 53 geolocation routing policies to distribute traffic based on geographic location. ELBs also support SSL termination, making this a valid solution.
- E. Incorrect.
Network Load Balancers (NLBs) are optimized for ultra-low latency and high throughput but do not support geolocation routing natively. AWS Global Accelerator does not compensate for this limitation in this scenario.