Why Do Users Experience Timeouts During Regional Failure with Route 53 Latency Routing?
A company is running a multi-tier web application across two AWS Regions (us-east-1 and eu-west-1) for disaster recovery. The application uses an Application Load Balancer (ALB) in each Region. The company uses Amazon Route 53 with latency-based routing to direct traffic to the closest Region. Recently, during a regional failure in us-east-1, users experienced timeouts instead of being redirected to eu-west-1. The DNS TTL is set to 60 seconds. The Route 53 health checks for the us-east-1 ALB are configured to check the HTTP endpoint every 30 seconds with 3 consecutive failures required to mark it unhealthy. The eu-west-1 ALB is healthy. The company's network design includes a VPC in each Region with public and private subnets. The ALBs are internet-facing and have proper security groups. The Route 53 records are configured correctly. What is the MOST likely cause of the timeout?
Quick Answer
The answer is the combined delay from the health check failure detection and DNS caching. Route 53 health checks are configured to test every 30 seconds and require three consecutive failures to mark an endpoint unhealthy, creating a 90-second detection window. During this time, Route 53 continues returning the us-east-1 ALB IP, and client DNS resolvers cache that IP for the 60-second TTL, so even after the failure is detected, cached records cause continued timeouts. This question tests your understanding of how health check intervals, failure thresholds, and DNS TTLs interact during regional failover scenarios on the ANS-C01 exam. A common trap is assuming latency routing instantly redirects traffic, but the real bottleneck is the time needed to mark the endpoint unhealthy plus the lingering DNS cache. Remember the 3-30-60 rule: three failures at 30-second intervals plus a 60-second TTL means over two minutes of potential timeout before traffic shifts.
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
✓
The health check interval and failure threshold cause a delay in detecting the failure, and DNS caching causes clients to still resolve to the unhealthy endpoint.
The most likely cause is that the health check interval and failure threshold create a delay in detection, and DNS caching causes clients to still resolve to the unhealthy endpoint. Route 53 health checks check the endpoint every 30 seconds and require 3 consecutive failures to mark it unhealthy, resulting in up to 90 seconds (3 * 30s) before the health check fails. Additionally, DNS resolvers cache the resolved IP address for the TTL of 60 seconds. Therefore, even after the health check marks the endpoint unhealthy, some clients may still have the cached IP and attempt to connect to the failed us-east-1 ALB, causing timeouts. Option A is incorrect because latency-based routing does fail over when health checks fail; the issue is the delay. Option B is incorrect because cross-zone load balancing is irrelevant to multi-region failover. Option D is incorrect because Route 53 health checks are global and can reach any region.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The latency-based routing policy does not fail over to the other region when a health check fails.
Why it's wrong here
Latency-based routing with health checks does fail over to healthy endpoints.
- ✗
The ALB in us-east-1 is not configured to be cross-zone load balancing, causing it to fail.
Why it's wrong here
Cross-zone load balancing is irrelevant to regional failure.
- ✓
The health check interval and failure threshold cause a delay in detecting the failure, and DNS caching causes clients to still resolve to the unhealthy endpoint.
Why this is correct
The health check takes up to 90 seconds to mark unhealthy, and DNS TTL of 60 seconds extends the impact.
- ✗
The Route 53 health check is not able to reach the ALB in us-east-1 from eu-west-1 due to network ACLs.
Why it's wrong here
Health checks come from Route 53 health checkers, which are allowed by default.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,621 original ANS-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on ANS-C01
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 company is deploying a critical application across three AWS Regions using an active-active architecture with Amazon Route 53 latency-based routing. Each region has an Application Load Balancer (ALB) as the endpoint. The application health checks are configured to check the /health endpoint every 10 seconds. During a regional failure, some users experience timeouts while others are redirected correctly. What is the most likely cause?
hard- ✓ A.Route 53 health checkers take multiple intervals to detect failure, and timeouts occur before failover completes.
- B.The ALB health check is misconfigured and returns a non-200 status code during normal operation.
- C.The TTL on the Route 53 record is set too low, causing stale DNS responses.
- D.Users have cached DNS records from the failed region, and Route 53 does not return healthy endpoints.
Why A: Route 53 health checkers operate from multiple global locations and evaluate the /health endpoint every 10 seconds. However, to declare an endpoint unhealthy, Route 53 requires a configurable number of consecutive failures (default is 3), meaning it can take 30 seconds or more before the DNS record is updated to remove the failed region. During this detection window, some users whose DNS queries are answered by Route 53 before the failure is fully propagated may receive the IP of the failing ALB, leading to timeouts, while others who query after the failover complete successfully.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ANS-C01 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 ANS-C01 exam.