ANS-C01 Network Management and Operations Practice Question
A global company is designing a multi-region Active-Active application using Amazon Route 53 latency-based routing. Each region has an Application Load Balancer (ALB) fronting Auto Scaling groups. The application requires sticky sessions based on the user's source IP. The network team notices that users are frequently switched to a different region mid-session, causing errors. What should the team do to resolve this issue?
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
✓
Switch to geolocation routing policy with a bias to maintain sessions
The issue is that latency-based routing can change the selected region mid-session due to fluctuating latency, breaking sticky sessions. Geolocation routing policy routes users to a region based on their source IP address, ensuring that the same user always reaches the same region, thus maintaining session stickiness. Using a bias allows fine-tuning to adjust routing for specific locations. Option C is not valid because Route 53 latency-based routing does not support custom origin headers; this is not a feature available in AWS. Option A only affects health checks and does not influence session persistence. Option B enables stickiness within a region but does not prevent Route 53 from switching regions. Therefore, switching to geolocation routing is the correct solution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure Route 53 health checks with a low threshold to quickly detect failures
Why it's wrong here
This is incorrect. Configuring Route 53 health checks with a low threshold helps detect failures quickly but does not provide sticky sessions. It does not prevent Route 53 from switching regions mid-session.
- ✗
Enable stickiness on each ALB using a cookie generated by the ALB
Why it's wrong here
This is incorrect. Enabling stickiness on each ALB maintains sessions within that ALB, but Route 53 latency-based routing can still send subsequent requests from the same user to a different region if latency changes, breaking stickiness across regions.
- ✗
Use a custom origin header in the Route 53 latency policy to route based on the user's IP address and enable ALB stickiness
Why it's wrong here
This option is invalid because Route 53's latency-based routing policy does not support custom origin headers. The described solution is not possible in AWS. Enabling ALB stickiness alone does not prevent Route 53 from redirecting users to a different region based on latency changes.
- ✓
Switch to geolocation routing policy with a bias to maintain sessions
Why this is correct
Geolocation routing policy routes traffic based on the geographic location of the user's IP address, ensuring that users consistently reach the same region. This maintains session stickiness. A bias can be added to adjust routing for specific locations or to handle edge cases. This is the correct approach to prevent mid-session region switches.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every ANS-C01 question from scratch — 1,621 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.