mediummultiple choiceObjective-mapped

Your web application is deployed in two AWS Regions (Region A and Region B). You want Route 53 to automatically fail over DNS traffic from Region A to Region B when Region A is unhealthy.

The failover decision must be based on health checks that verify whether the application in Region A is reachable.

Which Route 53 routing configuration best meets these requirements?

Question 1mediummultiple choice
Full question →

Your web application is deployed in two AWS Regions (Region A and Region B). You want Route 53 to automatically fail over DNS traffic from Region A to Region B when Region A is unhealthy.

The failover decision must be based on health checks that verify whether the application in Region A is reachable.

Which Route 53 routing configuration best meets these requirements?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Latency-based routing with regional aliases to split traffic based on measured latency.

Latency-based routing selects answers based on request latency, not on health check status. If Region A becomes unhealthy, Route 53 does not automatically switch all traffic to Region B based solely on latency.

B

Distractor review

Geolocation routing using country-based routing policies.

Geolocation routing chooses records based on the geography of the client. It does not use health checks to determine which region to return during an outage.

C

Best answer

Failover routing using a primary record with an associated health check for Region A and a secondary record for Region B.

Route 53 failover routing is designed for active/standby patterns. You configure the Region A record as primary with a health check. When that health check fails, Route 53 automatically returns the Region B (secondary) record, enabling health-check-driven regional failover.

D

Distractor review

Weighted routing with weights set to 100 for Region A and 0 for Region B.

Weighted routing splits traffic based on configured weights, but it does not automatically change weights in response to health checks. You would still need external automation to detect failure and update weights.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Failover routing using a primary record with an associated health check for Region A and a secondary record for Region B. — Route 53 failover routing ties DNS responses directly to health check results. Configure the Region A record as the primary with a health check that validates reachability in Region A, and configure the Region B record as the secondary. When Region A fails the health check, Route 53 automatically returns the Region B record for failover. Why others are wrong: Latency and geolocation routing depend on request attributes (performance or client location), not the health state of the endpoints. Weighted routing distributes traffic by static weight unless you update it, so it does not inherently perform automatic failover based on health checks.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.