ANS-C01 AWS Global Accelerator Practice Question
A company is designing a multi-Region active-active application using Application Load Balancers (ALBs) in us-east-1 and eu-west-1, with Route 53 latency-based routing. Users report that after a failover, existing connections fail. What should the company implement to ensure seamless failover?
⚠ Common exam trap
The trap is to think that sticky sessions (session affinity) on ALBs can provide cross-region session persistence. In reality, ALB sticky session cookies are region-specific and not shared across regions; a cookie from one ALB is meaningless to another, so existing connections will still fail after a DNS failover. Global Accelerator maintains a constant anycast IP to avoid connection drops.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a Global Accelerator instead of Route 53
AWS Global Accelerator provides a static anycast IP address that remains constant during failover. Clients connect to the same IP, and the accelerator directs traffic to the healthy regional endpoint without breaking existing connections. Route 53 latency-based routing relies on DNS, which changes the resolved IP on failover, causing existing TCP connections to fail. Sticky sessions (session affinity) on ALBs only persist within a single ALB and do not help when traffic is redirected to a different region. Therefore, Global Accelerator ensures seamless failover for existing connections.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use a Global Accelerator instead of Route 53
Why this is correct
Correct. Global Accelerator provides a static anycast IP that does not change on failover, allowing clients to continue using the same IP and maintain existing connections. It also offers health checks and traffic shifting without breaking connections.
- ✗
Enable client IP affinity on the ALBs
Why it's wrong here
Incorrect. Client IP affinity on ALBs targets requests from the same client IP to the same target within a single ALB, but it does not work across regions and does not preserve connections when DNS changes redirect traffic to another region.
- ✗
Use Amazon Route 53 geolocation routing instead of latency
Why it's wrong here
Incorrect. Geolocation routing bases routing on the client's geographic location, but like latency routing, it uses DNS and changes the IP on failover, causing existing connections to fail.
- ✗
Enable sticky sessions (session affinity) on the ALBs with a cookie duration
Why it's wrong here
Incorrect. Sticky sessions (session affinity) only ensure that requests from a client during a session are routed to the same target within a single ALB. They do not provide cross-region session persistence, so existing connections will still fail when traffic is redirected to a different region via DNS.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,621 original ANS-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ANS-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ANS-C01 exam.