AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A global SaaS provider deploys identical micro-service stacks in two AWS Regions (us-east-1 primary, us-west-2 secondary). Each Region exposes an Application Load Balancer (ALB). Amazon Route 53 uses a weighted routing policy (100:0) with a TTL of 300 seconds and health checks so that all client traffic goes to the primary Region. During a recent Regional outage the primary ALB became unreachable; some customers experienced about 10 minutes of failed requests before traffic shifted to the secondary Region. The reliability team must redesign cross-Region traffic management so that any future Regional failure causes no more than 60 seconds of disruption and does not require clients to change DNS names or application configuration. Operational overhead should be kept to a minimum.
Which solution best meets these requirements?
Replace the ALBs with Network Load Balancers in each Region, enable cross-zone load balancing, and advertise the NLB IP addresses over AWS Direct Connect using BGP.
Provision AWS Global Accelerator and add the two Regional ALB endpoints to separate endpoint groups so that the accelerator's static anycast IP addresses automatically route traffic to the healthy Region.
Deploy edge-optimized Amazon API Gateway endpoints in both Regions, front them with Amazon CloudFront, and modify the application to retry against both endpoints.
Lower the Route 53 record TTL to 30 seconds and switch to an active-passive failover routing policy that continues to use health checks on the primary ALB.
AWS Global Accelerator provides two anycast static IP addresses that clients use instead of Region-specific DNS names. The service continuously performs health checks on each configured endpoint and redirects traffic away from an unhealthy endpoint-typically within about 30 seconds-without waiting for DNS TTLs to expire. Because failover happens at the edge and the IP addresses remain constant, clients are unaware of Regional outages and no DNS propagation delay occurs. Reducing Route 53 TTL values still relies on DNS caches and cannot guarantee sub-minute failover for all resolvers. Network Load Balancers with cross-zone load balancing improve Availability Zone resilience, not cross-Region reliability, and Direct Connect/BGP adds significant operational complexity. Edge-optimized API Gateway and CloudFront require clients to reference a new hostname or incorporate custom retry logic, so they do not fully satisfy the requirement.
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 improve cross-region traffic management?
Open an interactive chat with Bash
Why is DNS TTL insufficient for guaranteeing sub-minute failover during regional outages?
Open an interactive chat with Bash
How does Global Accelerator differ from Route 53's routing policies in managing traffic failover?
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