Multi-Region Failover with Route 53 Health Checks
A regional web application for a inventory service must fail over automatically to a secondary Region if the primary endpoint becomes unhealthy. Which two services or features are required? The team wants the control to be enforceable during normal operations.
Quick Answer
The answer is a deployed standby application stack in the secondary Region combined with Route 53 failover routing and health checks. This works because Route 53 health checks continuously monitor the primary endpoint’s availability, and when a failure is detected, the failover routing policy automatically updates the DNS record to direct traffic to the standby stack in the secondary Region. On the SAA-C03 exam, this scenario tests your understanding of multi-region failover with Route 53 health checks, often appearing as a question where you must distinguish between active-passive and active-active architectures. A common trap is confusing Route 53 failover routing with simple load balancing—remember that failover routing is specifically for disaster recovery, not traffic distribution. Memory tip: think “primary gets pinged, secondary gets traffic” to recall that health checks drive the DNS switch.
⚠ Common exam trap
Watch out — candidates often think DNS-level failover alone is sufficient, forgetting that a fully deployed standby stack in the secondary Region is required to actually serve traffic after failover.
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
✓
Route 53 failover routing with health checks
Route 53 failover routing with health checks is correct because it enables automatic DNS-level failover to a secondary Region when the primary endpoint is unhealthy. Route 53 health checks monitor the primary endpoint's health, and if they detect a failure, the DNS record is updated to route traffic to the secondary Region's endpoint. This provides enforceable control during normal operations by allowing you to define routing policies that are active at all times.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Route 53 failover routing with health checks
Why this is correct
Route 53 can monitor endpoint health and return the standby endpoint when the primary is unhealthy.
- ✗
S3 Transfer Acceleration
Why it's wrong here
Transfer Acceleration improves upload paths to S3 but does not provide application failover.
- ✓
A deployed standby application stack in the secondary Region
Why this is correct
DNS failover requires a working target in the secondary Region.
- ✗
AWS Organizations service control policies
Why it's wrong here
SCPs enforce permissions and do not provide regional failover.
Visual reference
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 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. An internal-facing application is available in two AWS regions (Region 1 and Region 2). Each region has its own Application Load Balancer (ALB) and target group. The company uses an AWS Route 53 private hosted zone to route clients to Region 1 by default, but it must automatically fail over to Region 2 when Region 1’s ALB is unhealthy. Which Route 53 design best meets this requirement?
medium- A.Use latency-based routing with two alias records; Route 53 will automatically shift traffic away from the unhealthy region.
- B.Use weighted routing with weights 100/0 and update weights manually after detecting failures.
- ✓ C.Use failover routing with two alias A records for the same name: one PRIMARY and one SECONDARY, both pointing to each region’s ALB; attach the health check to the PRIMARY record.
- D.Use geolocation routing with a single alias record for Region 1, and enable EDNS Client Subnet to detect unhealthy endpoints.
Why C: Route 53 failover routing with a PRIMARY and SECONDARY alias record allows automatic failover when the health check attached to the PRIMARY record fails. The health check monitors Region 1's ALB, and upon failure, Route 53 returns the SECONDARY record's IP (Region 2's ALB) to clients. This design meets the requirement for automatic failover without manual intervention.
Variation 2. A company hosts an internal API behind an Application Load Balancer (ALB) in two AWS Regions. They want Amazon Route 53 to automatically fail over to the secondary Region when the primary Region’s ALB is unhealthy. Health checks for the primary ALB are already configured, but the DNS record currently uses a latency-based routing policy. Which Route 53 configuration most directly provides automatic failover based on health status?
medium- A.Keep latency-based routing, and set the weights so the secondary Region rarely receives traffic unless manual changes are made.
- ✓ B.Use a Route 53 failover routing policy: configure two alias records for the ALBs where the primary record is marked PRIMARY, the secondary is marked SECONDARY, and each record has an associated health check.
- C.Use an alias A record that returns both ALBs simultaneously so clients automatically load balance across Regions during outages.
- D.Use geolocation routing to route users to the primary Region and rely on ALB health checks to shift requests between Regions.
Why B: Route 53 failover routing policy is specifically designed to automatically route traffic away from an unhealthy resource to a healthy one. By creating two alias records (one PRIMARY with an associated health check for the primary ALB, and one SECONDARY for the secondary ALB), Route 53 will automatically fail over to the secondary record when the primary health check fails. This directly meets the requirement for automatic failover based on health status, unlike latency-based routing which only optimizes for response time.
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.