AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A global e-commerce company hosts its single-page application on EC2 instances behind an Application Load Balancer (ALB) in the us-east-1 Region. The application serves static assets from the path /static and makes personalized API calls at /api. Customers outside North America report first-page load times above 3 seconds, and analysis shows that 70 percent of the requests for /static originate outside the United States, accounting for most of the ALB's peak throughput. The architecture team must reduce end-to-end latency for worldwide users, decrease the load on the origin, keep TLS termination as close to viewers as possible, and ensure that user-specific API responses are never cached. No code or DNS changes to existing URLs are allowed. Which strategy best meets these requirements?
Provision AWS Global Accelerator with the ALB as the only endpoint and enable HTTP/2 to improve global TCP performance.
Deploy identical EC2 application stacks behind ALBs in multiple Regions and use Amazon Route 53 latency-based routing to direct users to the nearest Region.
Enable S3 Transfer Acceleration on a new S3 bucket, migrate all static assets to the bucket, and update the application to reference the new bucket while continuing to access /api through the ALB.
Create an Amazon CloudFront distribution in front of the ALB, add a cache behavior for /static/* that uses an optimized cache policy with compression, add a cache behavior for /api/* that uses the CachingDisabled managed policy and forwards all headers, and enable Origin Shield for the ALB origin.
Placing Amazon CloudFront in front of the ALB provides edge termination of TLS and a global network of edge locations that shorten round-trip times for viewers. Creating a cache behavior for /static/* with an optimized cache policy and compression lets CloudFront cache and compress static files, greatly reducing origin traffic. Configuring a second behavior for /api/* that uses the CachingDisabled managed policy (TTL 0) and forwards all headers prevents CloudFront from caching personalized API responses. Enabling Origin Shield adds an extra regional cache layer that further consolidates requests, improving cache hit ratio and offloading the ALB. Global Accelerator accelerates TCP handshakes but cannot cache content, S3 Transfer Acceleration requires rewriting URLs, and multi-region replication with Route 53 adds significant complexity and does not offload static traffic from a single origin.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Amazon CloudFront, and why is it suitable for this scenario?
Open an interactive chat with Bash
What is Origin Shield in CloudFront, and how does it enhance caching efficiency?
Open an interactive chat with Bash
Why is the 'CachingDisabled' managed policy used for /api/*, and what headers need to be forwarded?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Continuous Improvement for Existing Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access