How to Configure Route 53 Failover Routing for Active-Passive Setup
Exhibit
DNS design notes: Primary Region: us-east-1 Primary ALB: alb-prod-east-1.example.internal Secondary Region: us-west-2 Secondary ALB: alb-prod-west-2.example.internal Health check results: /health on us-east-1 returns HTTP 503 /health on us-west-2 returns HTTP 200 Requirement: Clients should use the primary endpoint during normal operations and switch automatically only on primary failure
Based on the exhibit, which Route 53 configuration should be used so traffic automatically returns to the secondary Region only when the primary Region becomes unhealthy?
Quick Answer
The answer is failover routing with a primary alias record, a secondary alias record, and a Route 53 health check on the primary target. This configuration is correct because Route 53 failover routing is specifically designed for active-passive setups, where the primary resource handles all traffic until a health check failure triggers an automatic shift to the secondary resource. In this scenario, the health check monitors the primary Region’s ALB; only when that check reports unhealthy does Route 53 return traffic to the secondary Region, ensuring traffic does not split or route to the passive site during normal operation. On the SAA-C03 exam, this tests your understanding of how to implement disaster recovery with minimal manual intervention—a common trap is confusing failover routing with weighted or latency routing, which would distribute traffic incorrectly. Remember the key distinction: failover routing is binary, not balanced. Memory tip: “Failover = one active, one passive; health check is the trigger, not the traffic splitter.”
⚠ Common exam trap
Watch out — candidates often confuse failover routing with latency-based or geolocation routing, assuming that 'closest' or 'fastest' automatically implies health awareness, but Route 53 health checks must be explicitly associated with failover records to trigger automatic traffic redirection.
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 failover routing with a primary alias record, a secondary alias record, and a Route 53 health check on the primary target.
Failover routing in Amazon Route 53 is designed for active-passive configurations. By creating a primary alias record pointing to the ALB in the primary Region and a secondary alias record pointing to the ALB in the secondary Region, and attaching a Route 53 health check to the primary target, traffic automatically fails over to the secondary Region only when the health check detects the primary as unhealthy. This meets the requirement of returning traffic to the secondary Region only upon primary failure.
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 latency-based routing with both ALB records enabled.
Why it's wrong here
Latency-based routing chooses the Region with the lowest latency, not a designated primary/secondary pair. It does not provide the explicit health-based failover behavior required here.
- ✓
Use failover routing with a primary alias record, a secondary alias record, and a Route 53 health check on the primary target.
Why this is correct
Failover routing is designed for this pattern: Route 53 returns the primary alias while the primary endpoint is healthy, and switches to the secondary alias when the primary health check fails. Alias records integrate cleanly with ALB targets, and the health check provides the signal that drives the failover decision.
- ✗
Use geolocation routing so users are always sent to the closest Region.
Why it's wrong here
Geolocation routing is based on client location, not the health of the primary Region. It can still direct users to an unhealthy endpoint if that Region matches the location rule.
- ✗
Use a CNAME record that points to both ALBs so DNS can round-robin between Regions.
Why it's wrong here
A single DNS record cannot provide health-aware active failover to two targets in that manner. Round-robin behavior also does not guarantee that traffic will move away from a failed primary only when the primary becomes unhealthy.
Go deeper
Related to this question
About these practice questions
One of 302 original SAA-C03 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 →
Same concept, more angles
3 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company hosts a public API using two AWS regions behind a single custom domain. Route 53 is configured with latency-based routing and health checks. During a regional outage, application metrics confirm the primary API is unhealthy, but clients still resolve to the primary region for most requests. Which DNS configuration change will most directly ensure automatic failover to the secondary region when the primary fails?
medium- A.Change the record type to A/AAAA alias with an active-active routing policy so both regions always receive equal traffic.
- ✓ B.Switch to Route 53 failover routing: configure the primary record with the primary health check and the secondary record with the secondary failover health check.
- C.Keep latency-based routing but shorten the health check interval to 5 seconds.
- D.Use geolocation routing so requests from each country route to the nearest region.
Why B: Route 53 failover routing with health checks explicitly directs traffic to the secondary region when the primary health check fails. This ensures automatic failover at the DNS level, whereas latency-based routing does not guarantee failover even with health checks—it only reduces latency and may still return unhealthy records if no healthier alternative exists.
Variation 2. An internal API is hosted in two AWS Regions behind Route 53. Under normal conditions, clients should use the primary region. If the primary endpoint becomes unhealthy, traffic must automatically switch to the secondary region. Which Route 53 setup best meets this requirement?
easy- A.Use latency-based routing with one record per region and no health checks.
- ✓ B.Use failover routing policy: create two alias records for the same name (primary and failover) and associate health checks with the primary record.
- C.Use weighted routing and manually change the weights during incidents.
- D.Create a single alias record only for the primary region and rely on client-side DNS retries.
Why B: Route 53 failover routing policy is designed for active-passive failover scenarios. By creating two alias records (primary and secondary) for the same DNS name and associating a health check with the primary record, Route 53 automatically directs traffic to the secondary region if the primary health check fails. This meets the requirement of automatic failover without manual intervention.
Variation 3. Based on the exhibit, DNS still sends traffic to the primary Region even though Route 53 health checks show the primary endpoint is unhealthy. What is the best change to make failover work as intended?
hard- A.Change both records to weighted routing with a 50/50 split so Route 53 can shift traffic gradually.
- ✓ B.Use a failover routing policy with a primary record and a secondary record, and attach the health check to the primary record.
- C.Switch to latency-based routing so users are always directed to the lowest-latency Region.
- D.Use geolocation routing so clients in one Region are sent to the healthier endpoint.
Why B: A failover routing policy with a health check attached to the primary record is the only configuration that allows Route 53 to automatically stop sending traffic to an unhealthy primary endpoint and redirect it to the secondary endpoint. Without the health check attached to the primary record, Route 53 has no mechanism to detect the failure and will continue routing traffic to the primary Region, even if the health check status shows unhealthy.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 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 SAA-C03 exam.