Failover routing for disaster recovery in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Failover Routing Behavior

In AWS Route 53, failover routing is used to route traffic to a primary resource and switch to a secondary resource if the primary becomes unhealthy.

What happens when the health check for the primary resource fails?

A Route 53 stops routing traffic to both primary and secondary resources until manual intervention.

B Traffic continues to be routed to the primary resource regardless of health check status.

C Traffic is automatically routed to the secondary resource configured in the failover routing policy.

D Traffic is routed randomly between primary and secondary resources.

💡 Hint

Think about what failover means in disaster recovery.

Failover routing automatically directs traffic to the secondary resource when the primary fails health checks, ensuring availability.

❓ Configuration

intermediate

Configuring Health Checks for Failover Routing

You want to configure failover routing in AWS Route 53 to switch traffic to a backup server if the primary server is down.

Which of the following is a required step to enable failover routing?

A Configure a weighted routing policy instead of failover routing.

B Create a health check for the secondary resource only.

C Disable health checks and rely on DNS TTL for failover.

D Create a health check for the primary resource and associate it with the primary record set.

💡 Hint

Failover routing depends on health checks to detect failures.

Failover routing requires a health check on the primary resource to detect when it is unhealthy and trigger failover.

❓ Architecture

advanced

Designing a Multi-Region Failover Architecture

You are designing a disaster recovery solution using AWS Route 53 failover routing between two regions.

Which architecture best supports automatic failover with minimal downtime?

A Primary region hosts the application with a health check; secondary region is standby with identical setup and DNS failover configured.

B Both regions serve traffic simultaneously with weighted routing and no health checks.

C Secondary region hosts the application; primary region is used only for backups.

D Primary region only, with manual DNS update to secondary region during failure.

💡 Hint

Failover routing requires health checks and a standby resource ready to serve traffic.

Automatic failover requires a primary region with health checks and a secondary region ready to take over, configured in Route 53 failover routing.

❓ security

advanced

Security Considerations in Failover Routing

When implementing failover routing for disaster recovery, which security practice is most important to protect DNS failover configurations?

A Restrict Route 53 console access using IAM policies to authorized personnel only.

B Use public IP addresses only for all resources to simplify routing.

C Disable health checks to prevent false failover triggers.

D Allow all users to modify DNS records for faster recovery.

💡 Hint

Think about who should control DNS settings in a disaster recovery setup.

Restricting access to Route 53 configurations prevents unauthorized changes that could disrupt failover routing and cause downtime.

❓ service_behavior

expert

Analyzing Failover Routing Behavior with Health Check Flapping

In AWS Route 53 failover routing, if the primary resource's health check status rapidly changes between healthy and unhealthy (flapping), what is the expected behavior?

A Route 53 immediately switches traffic to secondary resource on any unhealthy status without delay.

B Route 53 uses a configurable evaluation period to stabilize health check status before switching traffic, preventing rapid failover toggling.

C Route 53 disables failover routing until manual reset is performed.

D Route 53 routes traffic to both primary and secondary resources simultaneously during flapping.

💡 Hint

Consider how health checks are evaluated over time to avoid instability.

Route 53 health checks have evaluation intervals and thresholds to avoid rapid failover toggling caused by transient failures.

Practice

1. What is the main purpose of failover routing in disaster recovery?

easy

A. To block all traffic during maintenance

B. To increase the speed of the primary server

C. To reduce the cost of cloud services

D. To automatically send users to a backup server if the main server fails

Solution

1. Step 1: Understand failover routing purpose

   Failover routing is designed to keep services available by switching traffic to a backup if the main server fails.

2. Step 2: Eliminate unrelated options

   Options about speed, cost, or blocking traffic do not describe failover routing's main goal.

3. Final Answer:

   To automatically send users to a backup server if the main server fails -> Option D

4. Quick Check:

   Failover routing = automatic backup switch [OK]

Hint: Failover means switch to backup when main fails [OK]

Common Mistakes:

• Confusing failover with performance improvement
• Thinking failover blocks traffic
• Assuming failover reduces costs

2. Which AWS Route 53 routing policy is used to implement failover routing?

easy

A. Geolocation routing policy

B. Latency routing policy

C. Failover routing policy

D. Weighted routing policy

Solution

1. Step 1: Identify routing policies in Route 53

   Route 53 offers several routing policies, including latency, geolocation, weighted, and failover.

2. Step 2: Match failover routing policy to disaster recovery

   Failover routing policy is specifically designed to route traffic to a backup when the primary fails.

3. Final Answer:

   Failover routing policy -> Option C

4. Quick Check:

   Failover routing policy = failover setup [OK]

Hint: Failover routing policy is named for failover use [OK]

Common Mistakes:

• Choosing latency or weighted policies for failover
• Confusing geolocation with failover
• Not knowing Route 53 routing policy names

3. Given this Route 53 failover setup: Primary health check fails, what happens to user traffic?
Primary: IP 10.0.0.1 (health check enabled)
Secondary: IP 10.0.0.2 (backup)

medium

A. Traffic switches to secondary IP 10.0.0.2

B. Traffic is split evenly between primary and secondary

C. Traffic is blocked until primary recovers

D. Traffic continues to primary IP 10.0.0.1

Solution

1. Step 1: Understand health check failure effect

   If the primary health check fails, Route 53 detects the primary is unhealthy.

2. Step 2: Apply failover routing behavior

   Failover routing sends traffic to the secondary (backup) IP when primary is unhealthy.

3. Final Answer:

   Traffic switches to secondary IP 10.0.0.2 -> Option A

4. Quick Check:

   Primary down = traffic to backup [OK]

Hint: Failover sends traffic to backup if primary fails health check [OK]

Common Mistakes:

• Assuming traffic stays on primary despite failure
• Thinking traffic is blocked during failover
• Believing traffic splits evenly without weighting

4. You configured failover routing but traffic never switches to the backup server during primary failure. What is the most likely cause?

medium

A. Latency routing policy is used instead of failover

B. Health check is not associated with the primary record

C. Backup server IP address is incorrect

D. TTL value is set to zero

Solution

1. Step 1: Check health check association

   Failover routing requires the primary record to have a health check to detect failure.

2. Step 2: Understand impact of missing health check

   If the health check is missing or not linked, Route 53 never detects primary failure, so no failover occurs.

3. Final Answer:

   Health check is not associated with the primary record -> Option B

4. Quick Check:

   Failover needs health check linked to primary [OK]

Hint: Failover needs health check linked to primary record [OK]

Common Mistakes:

• Ignoring health check association
• Blaming backup IP without checking health check
• Confusing routing policies
• Misunderstanding TTL effects

5. You want to design a disaster recovery setup using Route 53 failover routing with two regions: primary in us-east-1 and backup in us-west-2. Which configuration ensures automatic failover with minimal downtime?

hard

A. Create two records with failover routing; primary record with health check in us-east-1, secondary record without health check in us-west-2

B. Create two records with weighted routing; assign 100% weight to primary and 0% to backup

C. Create two records with geolocation routing; route us-east traffic to primary and us-west traffic to backup

D. Create two records with latency routing; primary in us-east-1 and backup in us-west-2

Solution

1. Step 1: Understand failover routing setup

   Failover routing requires a primary record with a health check and a secondary record without a health check as backup.

2. Step 2: Evaluate options for disaster recovery

   Create two records with failover routing; primary record with health check in us-east-1, secondary record without health check in us-west-2 correctly sets primary with health check and backup without health check, enabling automatic failover.

3. Step 3: Eliminate other options

   Weighted routing does not provide automatic failover; geolocation routes by location, not health; latency routing routes by speed, not failure.

4. Final Answer:

   Create two records with failover routing; primary record with health check in us-east-1, secondary record without health check in us-west-2 -> Option A

5. Quick Check:

   Failover needs primary health check and backup record [OK]

Hint: Primary needs health check; backup record no health check [OK]

Common Mistakes:

• Using weighted routing instead of failover
• Assigning health check to backup record
• Confusing geolocation with failover
• Expecting latency routing to handle failover