You are implementing Route 53 failover for an on-premises website that has an active primary server and a passive secondary server. The primary should receive traffic only when its health check returns HTTP 2xx or 3xx responses; otherwise all traffic must go to the secondary. The failover routing and set IDs are already configured for both records. What is the next configuration step?

The correct answer is to create an A record for each server and associate each record with a Route 53 HTTP health check. For failover routing with on-premises resources, you must use standard A records (or AAAA records for IPv6) and associate them with Route 53 health checks. Route 53 health checks monitor the endpoint's health. Since the requirement specifies HTTP 2xx or 3xx responses, an HTTP health check is appropriate. Incorrect options: Using a TCP health check would only verify if the port is open, not if the web server is responding correctly with HTTP status codes. Alias records are used to map DNS names to AWS resources like ELBs, CloudFront distributions, or S3 buckets, not directly to on-premises IP addresses for failover. While evaluate target health is a feature of alias records, it's not applicable here because the targets are on-premises, not AWS resources.