A company's DNS provider is experiencing outages that disrupt a website hosted on AWS. The company wants to migrate quickly to a more resilient managed DNS service running on AWS. What should a solutions architect do to rapidly migrate DNS hosting?

Creating an Amazon Route 53 public hosted zone is the correct approach for migrating a public-facing website's DNS. Route 53 is a highly available and scalable managed DNS service. Importing the existing zone file ensures a rapid and accurate transfer of all domain records (A, CNAME, MX, etc.) from the previous provider, minimizing manual configuration and potential errors. A private hosted zone is incorrect because it's used for DNS resolution within a VPC, not for public internet traffic. Creating a Simple AD directory is irrelevant as it's an identity and access management service, not a public DNS hosting solution. Route 53 Resolver inbound endpoints are used for hybrid DNS architectures, allowing on-premises DNS to resolve AWS resources, not for migrating public domain hosting.