A company has configured an active-passive disaster recovery strategy for its web application across two AWS Regions. They use Amazon Route 53 with failover routing policies to direct traffic. During a disaster recovery simulation, the primary region's application server is shut down, but Route 53 continues to resolve DNS queries to the primary region's load balancer. Which of the following is the most likely cause of this behavior?
- AThe Route 53 Private Hosted Zone is not associated with the Virtual Private Cloud (VPC) in the secondary region.
- BThe primary region's Application Load Balancer is pointing to a single non-redundant NAT Gateway.
- The failover routing record for the primary region is not associated with a Route 53 health check.Cevap
- DThe disaster recovery strategy is configured as pilot light instead of active-active replication.
Cevap
The failover routing record for the primary region is not associated with a Route 53 health check.
The correct answer is that the failover routing record for the primary region is not associated with a Route 53 health check. Route 53 requires a health check to be associated with a record to determine when to fail over. Without a health check, Route 53 considers the endpoint healthy by default and continues to route traffic to the primary region.
Adım Adım Çözüm
Anahtar Kavram
Amazon Route 53 DNS Failover and Health Checks
Tahmini Süre:1m 0s