AWS Certified Solutions Architect – Associate (SAA-C03) — Question 324

A company serves a dynamic website from a fleet of Amazon EC2 instances behind an Application Load Balancer (ALB). The website needs to support multiple languages to serve customers around the world. The website’s architecture is running in the us-west-1 Region and is exhibiting high request latency for users that are located in other parts of the world.

The website needs to serve requests quickly and efficiently regardless of a user’s location. However, the company does not want to recreate the existing architecture across multiple Regions.

What should a solutions architect do to meet these requirements?

Answer options

• A. Replace the existing architecture with a website that is served from an Amazon S3 bucket. Configure an Amazon CloudFront distribution with the S3 bucket as the origin. Set the cache behavior settings to cache based on the Accept-Language request header.
• B. Configure an Amazon CloudFront distribution with the ALB as the origin. Set the cache behavior settings to cache based on the Accept-Language request header.
• C. Create an Amazon API Gateway API that is integrated with the ALB. Configure the API to use the HTTP integration type. Set up an API Gateway stage to enable the API cache based on the Accept-Language request header.
• D. Launch an EC2 instance in each additional Region and configure NGINX to act as a cache server for that Region. Put all the EC2 instances and the ALB behind an Amazon Route 53 record set with a geolocation routing policy.

Correct answer: B

Explanation

Amazon CloudFront can use an Application Load Balancer (ALB) as a custom origin to cache dynamic content at edge locations globally, which significantly reduces latency without duplicating the infrastructure. Configuring the CloudFront cache behavior to cache based on the Accept-Language request header ensures that users receive the correct localized version of the website. Other options either require static hosting (S3), violate the constraint of avoiding multi-region deployments (EC2 with NGINX), or add unnecessary complexity (API Gateway).