A company runs a dynamic web application on EC2 instances behind an Application Load Balancer (ALB) with DNS managed by Route 53. A static S3 website must serve as an automated backup if the app fails. Which combination of steps will implement fully automated failover to the S3 site? (Choose two.)

To implement automated failover using Route 53, you need to configure failover routing policies. The first correct step is to create a primary failover Route 53 record that points to the ALB and associate it with a Route 53 health check. This health check monitors the ALB's availability. If the health check fails, Route 53 automatically routes traffic to the secondary record. The second correct step is to create a secondary failover Route 53 record that points to the static S3 website. This record does not need its own health check because it acts as the backup destination when the primary fails. The incorrect option "Create a primary failover Route 53 record that points to the ALB" is incomplete because it omits the crucial health check association. Without a health check, Route 53 cannot automatically detect a failure and initiate failover. The option "Write a Lambda function that switches DNS from the primary site to the backup when a health check fails" is an overly complex and unnecessary solution; Route 53's built-in failover routing policy handles this automatically. The option "Create a secondary failover Route 53 record that points to the static S3 website and associate that record with a Route 53 health check" is incorrect because the secondary record in a simple failover setup typically doesn't require a health check; it's the fallback.