A solutions architect is configuring an active-passive disaster recovery strategy in Amazon Route 53. The primary application runs on an Application Load Balancer (ALB), and the backup site is a static website hosted on Amazon S3. Which of the following Route 53 record configurations must the solutions architect create to implement this failover mechanism? (Select TWO.)
- A Failover record pointing to the Application Load Balancer with the Failover Record Type set to Primary and Evaluate Target Health set to YesCevap
- A Failover record pointing to the Amazon S3 bucket website endpoint with the Failover Record Type set to SecondaryCevap
- CA Latency routing record pointing to the Application Load Balancer to act as the primary failover target
- DA Failover record pointing directly to an Amazon RDS Read Replica as the primary target
- EA Warm Standby routing record to manage the automatic scaling of the primary and backup resources
Cevap
The correct configurations are creating a Failover record pointing to the Application Load Balancer with the Failover Record Type set to Primary and Evaluate Target Health set to Yes, and creating a Failover record pointing to the Amazon S3 bucket website endpoint with the Failover Record Type set to Secondary.
To set up active-passive failover in Route 53, you must create a Primary record using the Failover routing policy pointing to the active resource (the ALB) and enable 'Evaluate Target Health'. You must also create a Secondary record using the Failover routing policy pointing to the standby resource (the S3 bucket website endpoint). When the primary resource is determined to be unhealthy, Route 53 automatically shifts DNS traffic to the secondary resource.
Adım Adım Çözüm
Anahtar Kavram
Route 53 active-passive DNS failover configurations use Failover routing policies with defined Primary and Secondary records, where the Primary record evaluates the target's health to determine when to route traffic to the Secondary record.