DOP-C02 Resilient Cloud Solutions Practice Question
A company uses Amazon Route 53 for DNS. They want to ensure that if their primary website endpoint fails, traffic is automatically routed to a secondary endpoint in a different Region. Which routing policy should be used?
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
Failover routing policy allows you to configure an active-passive failover setup.
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 routing
Why it's wrong here
Latency-based routing selects the region that responds fastest to the user's resolver by referencing network latency measurements between user networks and AWS endpoints. Its decision criterion is performance, not endpoint health; a failed resource can still be returned as the lowest-latency target. Therefore, latency routing alone doesn't satisfy an availability or failover requirement.
- ✗
Simple routing
Why it's wrong here
Simple routing is the most basic policy where one record set maps a name to a single value, and Route 53 has no built-in health checking or active/passive endpoint awareness. If the target becomes unavailable, the DNS response remains unchanged, so clients continue to be pointed at the down resource. In short, simple routing provides no automatic recovery, making it unsuitable for failover.
- ✓
Failover routing
Why this is correct
Failover routing is the correct choice because it explicitly pairs a primary record with a secondary record and uses Route 53 health checks to decide which to return. When the health check for the primary endpoint fails, Route 53 automatically returns the secondary record's value. This works in an active-passive configuration and gives the deterministic failover behavior the company requires.
- ✗
Weighted routing
Why it's wrong here
Weighted routing distributes traffic across multiple records according to assigned weights, for example 80% to one endpoint and 20% to another. Although you can attach health checks to weighted records, its purpose is load balancing and traffic control, not deterministic failover; an unhealthy record is excluded while healthy weighted records share traffic, but it lacks the primary/secondary relationship of failover routing. Thus, weighted routing doesn't meet the stated availability goal.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DOP-C02 question from scratch — 1,013 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DOP-C02 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 DOP-C02 exam.