A company must migrate both its DNS registrar and DNS hosting to Amazon Route 53 without any downtime. The current DNS provider cannot handle the website traffic. What migration plan allows the company to switch quickly with zero interruption?

The correct approach for a zero-downtime migration involves first setting up Route 53 as the authoritative DNS server. By copying all existing DNS records to a new Route 53 public hosted zone and then updating the name servers at the current registrar to point to Route 53's name servers, the DNS resolution process switches to Route 53 without changing the domain registrar. This ensures continuous service. Once propagation is complete and Route 53 is handling all DNS queries, the domain name transfer to Route 53 can be performed without impact. Incorrect options: Creating a private hosted zone is incorrect because it's used for DNS resolution within a VPC, not for public internet traffic. Transferring the domain before setting up Route 53 as the authoritative DNS server risks downtime if the new DNS records aren't fully propagated or correctly configured. Setting TTL to 1 second is not necessary for a smooth migration and can increase DNS query load. The primary goal is to switch authoritative DNS first, then transfer the domain.