ANS-C01 Question 386
Single answerYour company runs a global e-commerce platform hosted on AWS. Customers report intermittent latency issues when accessing the application, especially from regions distant from the primary deployment in us-east-1. The architecture currently uses an Application Load Balancer (ALB) in us-east-1, with backend Amazon EC2 instances. The company wants to reduce latency for global users while minimizing costs. Which solution would you recommend?
- A
Deploy Amazon CloudFront with the ALB as the origin to cache content closer to users globally.
- B
Use AWS Global Accelerator to provide low-latency routing to the ALB from global regions.
- C
Replicate the entire application stack in multiple AWS Regions and use Route 53 latency-based routing.
- D
Migrate the application to AWS Fargate to simplify management and improve latency.
Show answer and explanation
Correct answer: A
Explanation
Using Amazon CloudFront with the ALB as the origin is the optimal solution in this scenario because it reduces latency for global users by caching content at edge locations. It is also cost-effective as it minimizes repeated data transfers and does not require replicating the application stack across multiple Regions. Other solutions either increase costs or fail to address the specific latency problem effectively.
- A. Correct.
This option is correct as Amazon CloudFront caches content at edge locations around the world, minimizing latency for global users while being cost-effective. The ALB can act as the CloudFront origin, making this solution easy to implement.
- B. Incorrect.
While AWS Global Accelerator can improve latency by routing traffic to the ALB using AWS's global network, it is more expensive compared to CloudFront and does not provide caching capabilities to reduce repeated data transfer costs.
- C. Incorrect.
Replicating the application stack across multiple Regions and using Route 53 latency-based routing can reduce latency but is significantly more complex and expensive compared to using CloudFront for caching.
- D. Incorrect.
Migrating to AWS Fargate simplifies container management but does not inherently address the latency issue for global users, as it doesn't optimize network performance or provide caching.