Question 802 of 1,040
Design Resilient ArchitecturesmediumMultiple ChoiceObjective-mapped

Configuring Route 53 Failover Routing for Automatic Regional Failover

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.

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

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

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

Option C is correct because Route 53 failover routing allows you to create a primary record with an associated health check for Region A and a secondary record for Region B. When the health check for Region A fails, Route 53 automatically returns the secondary record's IP address, directing traffic to Region B. This directly meets the requirement for automatic failover based on application reachability.

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.

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

    Why it's wrong here

    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.

    When this WOULD be correct

    You need to route users to the region with the lowest latency for better performance, and you have health checks to exclude unhealthy endpoints. Latency-based routing with health checks would be correct.

  • Geolocation routing using country-based routing policies.

    Why it's wrong here

    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.

    When this WOULD be correct

    A company needs to route users to the nearest regional endpoint based on their country for compliance or content localization, and failover is not required. Geolocation routing would be correct if the requirement is to direct traffic from specific countries to specific regions.

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

    Why this is correct

    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.

    Related concept

    Read the scenario before looking for a memorised answer.

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

    Why it's wrong here

    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.

    When this WOULD be correct

    A scenario where you want to gradually shift traffic from one region to another (e.g., for blue/green deployment or load balancing) without automatic failover. For example, you want to send 10% of traffic to a new region and 90% to the old region, adjusting weights manually over time.

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.

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

Why this is correct

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.

Latency-based routing with regional aliases to split traffic based on measured latency.Wrong answer — click to see why

Why this is wrong here

Latency-based routing directs traffic based on lowest latency, not health status. It cannot automatically fail over to Region B when Region A is unhealthy because it lacks health check integration.

★ When this WOULD be the correct answer

You need to route users to the region with the lowest latency for better performance, and you have health checks to exclude unhealthy endpoints. Latency-based routing with health checks would be correct.

Why candidates choose this

Candidates may confuse latency-based routing with failover, thinking that routing to the lowest latency region inherently provides failover, but it does not consider health unless health checks are explicitly used.

Geolocation routing using country-based routing policies.Wrong answer — click to see why

Why this is wrong here

Geolocation routing directs traffic based on the geographic location of the user, not on the health of the endpoint. It cannot automatically failover from Region A to Region B when Region A becomes unhealthy.

★ When this WOULD be the correct answer

A company needs to route users to the nearest regional endpoint based on their country for compliance or content localization, and failover is not required. Geolocation routing would be correct if the requirement is to direct traffic from specific countries to specific regions.

Why candidates choose this

Candidates may confuse geolocation routing with failover routing because both involve multiple regions, but geolocation focuses on user location rather than endpoint health.

Weighted routing with weights set to 100 for Region A and 0 for Region B.Wrong answer — click to see why

Why this is wrong here

Weighted routing with 100/0 weights does not provide automatic failover; it simply sends all traffic to Region A until you manually change weights. It lacks health checks to trigger failover when Region A becomes unhealthy.

★ When this WOULD be the correct answer

A scenario where you want to gradually shift traffic from one region to another (e.g., for blue/green deployment or load balancing) without automatic failover. For example, you want to send 10% of traffic to a new region and 90% to the old region, adjusting weights manually over time.

Why candidates choose this

Candidates may think setting weights to 100/0 is a simple way to direct all traffic to Region A, and assume failover can be achieved by manually changing weights to 0/100 when Region A fails, overlooking the requirement for automatic failover based on health checks.

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 failover routing with weighted routing, mistakenly thinking that setting weights to 100/0 will achieve failover, but weighted routing does not automatically adjust weights based on health checks.

Detailed technical explanation

How to think about this question

Route 53 failover routing works by associating a health check with the primary record; the health check monitors the endpoint via HTTP/HTTPS/TCP or can be a calculated health check. When the health check fails, Route 53 removes the primary record from DNS responses and returns the secondary record's value, with a TTL typically set low (e.g., 60 seconds) to speed up failover. In a real-world scenario, you might combine failover routing with an Application Load Balancer in each region, where the health check targets the ALB's DNS name or IP, ensuring traffic shifts only when the entire regional stack is down.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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.

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.

Practice this exam

Start a free SAA-C03 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

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: Failover routing using a primary record with an associated health check for Region A and a secondary record for Region B. — Option C is correct because Route 53 failover routing allows you to create a primary record with an associated health check for Region A and a secondary record for Region B. When the health check for Region A fails, Route 53 automatically returns the secondary record's IP address, directing traffic to Region B. This directly meets the requirement for automatic failover based on application reachability.

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.

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 →

How Courseiva writes practice questions · Editorial policy

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 regional web application for a content publishing system must fail over automatically to a secondary Region if the primary endpoint becomes unhealthy. Which two services or features are required?

hard
  • A.AWS Organizations service control policies
  • B.Route 53 failover routing with health checks
  • C.S3 Transfer Acceleration
  • D.A deployed standby application stack in the secondary Region

Why B: Route 53 failover routing with health checks (B) is required because it continuously monitors the health of the primary endpoint and automatically reroutes traffic to a secondary Region when the primary becomes unhealthy. This is achieved by configuring a primary and secondary failover record set in Route 53, where the health check is associated with the primary record. When the health check fails, Route 53 returns the secondary record's IP address, enabling automatic failover at the DNS level.

Variation 2. A regional web application for a content publishing system must fail over automatically to a secondary Region if the primary endpoint becomes unhealthy. Which two services or features are required? The design must avoid adding custom operational scripts.

hard
  • A.AWS Organizations service control policies
  • B.Route 53 failover routing with health checks
  • C.S3 Transfer Acceleration
  • D.A deployed standby application stack in the secondary Region

Why B: Route 53 failover routing with health checks is required because it automatically directs traffic away from an unhealthy primary endpoint to a secondary endpoint, enabling cross-region failover without custom scripts. A deployed standby application stack in the secondary Region is necessary to serve traffic when the primary fails, as Route 53 can only route to healthy endpoints that are actually running.

Variation 3. A regional web application for a content publishing system must fail over automatically to a secondary Region if the primary endpoint becomes unhealthy. Which two services or features are required? The architecture review board prefers a managed AWS-native control.

hard
  • A.AWS Organizations service control policies
  • B.Route 53 failover routing with health checks
  • C.S3 Transfer Acceleration
  • D.A deployed standby application stack in the secondary Region

Why B: Route 53 failover routing with health checks (Option B) is required because it monitors the primary endpoint's health and automatically reroutes traffic to a secondary Region when the primary becomes unhealthy. This is the managed AWS-native control for DNS-based failover, meeting the architecture review board's preference.

Keep practising

More SAA-C03 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.