A company hosts its primary web application behind an Application Load Balancer (ALB) in the us-east-1 Region. The company wants to set up a simple disaster recovery strategy where public DNS traffic is automatically redirected to a static error page hosted on an Amazon S3 bucket in the us-west-2 Region if the primary application becomes unavailable. Which Amazon Route 53 routing configuration should a solutions architect implement to meet these requirements?
- Configure Route 53 failover routing. Create a primary failover record pointing to the ALB with health checks enabled, and a secondary failover record pointing to the S3 bucket endpoint.Cevap
- BConfigure Route 53 latency routing records pointing to both the ALB and the S3 bucket endpoint, relying on Route 53 to automatically route all traffic to the S3 bucket during a primary region outage.
- CConfigure a Route 53 database failover policy that monitors the application's RDS read replica in us-west-2 and automatically redirects all client web traffic to that replica when the primary database fails.
- DConfigure Route 53 with a pilot light routing record that keeps the S3 bucket endpoint inactive and scale-up the bucket's resources only after a CloudWatch alarm triggers a failover event.
Cevap
Configure Route 53 failover routing by creating a primary failover record pointing to the ALB with health checks enabled, and a secondary failover record pointing to the S3 bucket endpoint.
The correct answer correctly identifies that a failover routing policy should be used for active-passive disaster recovery. By setting the Application Load Balancer as the primary endpoint and enabling health checks, Route 53 will route traffic to the primary endpoint as long as it is healthy. If the health checks fail, Route 53 automatically redirects incoming DNS queries to the secondary endpoint, which is the Amazon S3 static website.
Adım Adım Çözüm
Anahtar Kavram
Amazon Route 53 DNS Failover with Active-Passive Architecture