A company wants to direct users to a backup static error page if the primary website is unavailable. The primary website's DNS is hosted in Amazon Route 53 and points to an Application Load Balancer (ALB). The solution should minimize changes and infrastructure overhead. Which solution meets these requirements?

The correct answer is to set up a Route 53 active-passive failover configuration. This approach uses Route 53 health checks to monitor the primary ALB endpoint. If the health check fails, Route 53 automatically routes traffic to the secondary endpoint, which in this case is a static error page hosted in an Amazon S3 bucket. This minimizes changes and infrastructure overhead because S3 is a cost-effective and highly available service for static content, and Route 53 handles the failover automatically. Latency routing (option 1) directs traffic to the endpoint with the lowest latency, not based on health, and wouldn't guarantee failover to the error page. Active-active configuration (option 3) with an EC2 instance adds unnecessary infrastructure and complexity compared to S3 for a static page. Multivalue answer routing (option 4) returns multiple healthy records and relies on the client to choose, which isn't suitable for automatic failover to a specific error page upon primary site failure.