What should a solutions architect do to automate the failover process?
Enable an ALB health check
Enable an Amazon Route 53 health check.
Crate an CNAME record on Amazon Route 53 pointing to the ALB endpoint.
Create conditional forwarding rules on Amazon Route 53 pointing to an internal BIND DNS server.
Explanations:
Enabling an ALB health check only checks the health of the targets behind the ALB in the same Region. It does not automate the failover process to a secondary ALB in another Region.
Enabling an Amazon Route 53 health check allows Route 53 to monitor the health of the primary ALB. If the health check fails, Route 53 can automatically route traffic to the secondary ALB in another Region, automating the failover process.
Creating a CNAME record pointing to the ALB endpoint does not automate failover. It simply establishes a static mapping to the ALB, which does not respond to changes in availability.
Conditional forwarding rules for an internal BIND DNS server do not provide a solution for automated failover between Regions. This option involves manual configurations and does not leverage Route 53’s health checks or failover capabilities.
From what I’ve seen, the answer is:
Enable an Amazon Route 53 health check.