AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A multinational SaaS provider runs a latency-sensitive REST API in two AWS Regions (us-east-1 and ap-southeast-1). Each Region hosts identical Amazon EC2 instances behind an internet-facing Application Load Balancer (ALB). Latency-based records in Amazon Route 53 direct users to the nearest ALB, and Route 53 health checks confirm both ALBs are healthy.
During periods of public-internet congestion, customers in Europe and South America observe large variations in TLS handshake time and time-to-first-byte-often more than 300 ms-even when the local Region remains healthy. The engineering team wants to lower latency variation for all users without adding a caching layer or changing the existing Regional infrastructure. They also want to avoid exposing multiple Regional DNS names or IP addresses to customers.
Which change will MOST effectively meet these requirements?
Replace each ALB with a Network Load Balancer and enable HTTP/3 (QUIC) on the listeners to reduce connection-setup time across the internet.
Lower the TTL of the Route 53 latency records to 30 seconds and switch to weighted routing. Use an AWS Lambda function to adjust weights dynamically based on CloudWatch latency metrics.
Create an AWS Global Accelerator with two endpoint groups, each containing one Regional ALB, and instruct clients to connect to the accelerator's static Anycast IP addresses.
Deploy an Amazon CloudFront distribution with both ALBs configured as origins and enable origin failover. Update the API endpoint to use the distribution's domain name.
AWS Global Accelerator places static Anycast IP addresses at AWS edge locations. Client traffic enters the AWS global network close to the user, where Global Accelerator terminates the TCP connection, then forwards it across the congestion-free AWS backbone to the optimal healthy ALB endpoint. This design typically reduces average latency and jitter and hides Regional endpoints behind a single, unchanging address, satisfying all of the company's goals.
Amazon CloudFront can improve performance, but its primary function is as a caching layer, which the team explicitly wants to avoid. While it can proxy dynamic requests, it is primarily optimized for HTTP content delivery, whereas Global Accelerator is designed to accelerate dynamic and non-HTTP workloads by optimizing the network path.
Altering Route 53 TTL values or weights still relies on public-internet routing and DNS caching, so it cannot mitigate mid-path congestion. Network Load Balancers operate at Layer 4 and do not provide native termination for HTTP/3 (QUIC); more importantly, changing protocols or load balancer types would not address the fundamental internet-routing problem. Therefore, integrating AWS Global Accelerator is the most appropriate managed-service enhancement for consistent global performance.
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 AWS Global Accelerator and how does it reduce latency?
Open an interactive chat with Bash
Why is AWS Global Accelerator better for dynamic workloads compared to Amazon CloudFront?
Open an interactive chat with Bash
What role does Anycast play in AWS Global Accelerator's performance?
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