SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Route 53 record set
Name: app.example.com
Type: A (Alias)
Routing policy: Simple
Alias target: alb-primary-123.us-east-1.elb.amazonaws.com
TTL: 60 seconds
Health check
ID: hc-44
Status: Inactive
Secondary environment
ALB target exists in us-west-2: alb-secondary-456.us-west-2.elb.amazonaws.com
Operational note
A Region outage should shift users to the secondary ALB without manual DNS changes.
Based on the exhibit, the company wants DNS traffic to fail over automatically from the primary Region to a secondary Region when the primary endpoint is unhealthy. Which Route 53 change is best?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "primary"
Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
Exhibit
Route 53 record set
Name: app.example.com
Type: A (Alias)
Routing policy: Simple
Alias target: alb-primary-123.us-east-1.elb.amazonaws.com
TTL: 60 seconds
Health check
ID: hc-44
Status: Inactive
Secondary environment
ALB target exists in us-west-2: alb-secondary-456.us-west-2.elb.amazonaws.com
Operational note
A Region outage should shift users to the secondary ALB without manual DNS changes.
A
Keep simple routing and lower the TTL to 10 seconds.
Why wrong: A lower TTL can make clients refresh cached answers sooner, but simple routing still returns only one endpoint and does not provide primary/secondary failover behavior. It does not automatically switch traffic to the standby Region when the primary becomes unhealthy.
B
Use weighted routing with equal weights for both ALBs.
Why wrong: Weighted routing is useful for traffic splitting or gradual migration, but it is not the same as health-based disaster recovery. Equal weights do not create a primary endpoint with an automatic standby that is used only on failure.
C
Use geolocation routing so users in each continent reach a closer ALB.
Why wrong: Geolocation routing makes decisions based on user location, not on endpoint health or Regional disaster recovery. It is not designed to shift all traffic away from an unhealthy primary Region.
D
Create Route 53 failover records with health checks for the primary and secondary ALBs.
Failover routing is the Route 53 policy intended for this use case. Route 53 returns the primary record while its health check passes, and automatically serves the secondary record when the primary health check fails. That provides DNS-based Regional failover without manual intervention.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create Route 53 failover records with health checks for the primary and secondary ALBs.
Route 53 failover routing with health checks is the only option that automatically directs DNS traffic away from an unhealthy primary endpoint to a healthy secondary endpoint. When the health check for the primary ALB fails, Route 53 returns the secondary ALB's IP address in DNS responses, providing automatic failover across regions. Simple, weighted, and geolocation routing do not natively support automatic failover based on endpoint health.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Keep simple routing and lower the TTL to 10 seconds.
Why it's wrong here
A lower TTL can make clients refresh cached answers sooner, but simple routing still returns only one endpoint and does not provide primary/secondary failover behavior. It does not automatically switch traffic to the standby Region when the primary becomes unhealthy.
When this WOULD be correct
When the requirement is to distribute traffic evenly across multiple healthy endpoints without health-based failover, and the application can tolerate brief downtime during DNS propagation. For example, a static website hosted on multiple servers where manual failover is acceptable.
✗
Use weighted routing with equal weights for both ALBs.
Why it's wrong here
Weighted routing is useful for traffic splitting or gradual migration, but it is not the same as health-based disaster recovery. Equal weights do not create a primary endpoint with an automatic standby that is used only on failure.
When this WOULD be correct
When you need to distribute traffic across multiple endpoints with a specified ratio (e.g., 10% to one ALB and 90% to another) for A/B testing or gradual migration, and health checks are not required for automatic failover.
✗
Use geolocation routing so users in each continent reach a closer ALB.
Why it's wrong here
Geolocation routing makes decisions based on user location, not on endpoint health or Regional disaster recovery. It is not designed to shift all traffic away from an unhealthy primary Region.
When this WOULD be correct
A company wants to direct users to the nearest application endpoint based on their geographic location to reduce latency, and each region's endpoint is stateless and can serve all users. In that case, geolocation routing is appropriate.
✓
Create Route 53 failover records with health checks for the primary and secondary ALBs.
Why this is correct
Failover routing is the Route 53 policy intended for this use case. Route 53 returns the primary record while its health check passes, and automatically serves the secondary record when the primary health check fails. That provides DNS-based Regional failover without manual intervention.
Clue confirmation
The clue word "primary" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Create Route 53 failover records with health checks for the primary and secondary ALBs.Correct answer▾
Why this is correct
Failover routing is the Route 53 policy intended for this use case. Route 53 returns the primary record while its health check passes, and automatically serves the secondary record when the primary health check fails. That provides DNS-based Regional failover without manual intervention.
✗Keep simple routing and lower the TTL to 10 seconds.Wrong answer — click to see why▾
Why this is wrong here
Simple routing does not support health checks or automatic failover; lowering TTL only speeds up DNS propagation but does not enable failover to a secondary endpoint when the primary is unhealthy.
★ When this WOULD be the correct answer
When the requirement is to distribute traffic evenly across multiple healthy endpoints without health-based failover, and the application can tolerate brief downtime during DNS propagation. For example, a static website hosted on multiple servers where manual failover is acceptable.
Why candidates choose this
Candidates may think that a low TTL combined with simple routing can achieve fast failover by quickly updating DNS records, but they overlook that simple routing lacks health checks and automatic record switching.
✗Use weighted routing with equal weights for both ALBs.Wrong answer — click to see why▾
Why this is wrong here
Weighted routing distributes traffic based on weights, not health; it does not automatically failover to a healthy endpoint when the primary is unhealthy.
★ When this WOULD be the correct answer
When you need to distribute traffic across multiple endpoints with a specified ratio (e.g., 10% to one ALB and 90% to another) for A/B testing or gradual migration, and health checks are not required for automatic failover.
Why candidates choose this
Candidates may think equal weights provide load balancing and failover, but weighted routing lacks health-based automatic failover; it only splits traffic proportionally.
✗Use geolocation routing so users in each continent reach a closer ALB.Wrong answer — click to see why▾
Why this is wrong here
Geolocation routing directs traffic based on the user's geographic location, not health. It does not automatically failover to a secondary region when the primary endpoint is unhealthy; it would continue sending traffic from that region to the unhealthy endpoint.
★ When this WOULD be the correct answer
A company wants to direct users to the nearest application endpoint based on their geographic location to reduce latency, and each region's endpoint is stateless and can serve all users. In that case, geolocation routing is appropriate.
Why candidates choose this
Candidates may think geolocation routing can provide failover by routing users away from an unhealthy region, but it lacks health-based automatic failover and is designed for latency reduction, not disaster recovery.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse weighted routing with failover, assuming equal weights will somehow cause automatic failover, but weighted routing does not consider health status and requires manual intervention to shift traffic.
Detailed technical explanation
How to think about this question
Route 53 failover records work by associating each record with a health check that monitors the endpoint (e.g., ALB). When the primary record's health check fails, Route 53 removes that record from DNS responses and returns only the secondary record's value. The health check interval and failure threshold (e.g., 30 seconds with 3 consecutive failures) determine failover speed, and you can use a 'primary' and 'secondary' set with the same DNS name to achieve active-passive failover across regions.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design Resilient Architectures — This question tests Design Resilient Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create Route 53 failover records with health checks for the primary and secondary ALBs. — Route 53 failover routing with health checks is the only option that automatically directs DNS traffic away from an unhealthy primary endpoint to a healthy secondary endpoint. When the health check for the primary ALB fails, Route 53 returns the secondary ALB's IP address in DNS responses, providing automatic failover across regions. Simple, weighted, and geolocation routing do not natively support automatic failover based on endpoint health.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "primary". Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.