Q3 — AWS SAA-C03 Ch.12

Question 3 of 100 | ← Chapter 12

Q803. The DNS provider that hosts a company's domain name records is experiencing outages that cause service disruption for a website running on AWS. The company needs to migrate to a more resilient managed DNS service and wants the service to run on AWS.What should a solutions architect do to rapidly migrate the DNS hosting service?

• A. Create an Amazon Route 53 public hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider. ✓
• B. Create an Amazon Route 53 private hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider.
• C. Create a Simple AD directory in AWS. Enable zone transfer between the DNS provider and AWS Directory Service for Microsoft Active Directory for the domain records.
• D. Create an Amazon Route 53 Resolver inbound endpoint in the VPC. Specify the IP addresses that the provider's DNS will forward DNS queries to. Configure the provider's DNS to forward DNS queries for the domain to the IP addresses that are specified in the inbound endpoint.

Correct Answer: A. Create an Amazon Route 53 public hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider.

Explanation

To rapidly migrate the DNS hosting service to a more resilient managed DNS service running on AWS, the recommended solution is:A. Create an Amazon Route 53 public hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider.Option A allows for a rapid migration of the DNS hosting service using Amazon Route 53:\1. Creating an Amazon Route 53 public hosted zone provides a managed DNS service on AWS.\2. Importing the zone file containing the domain records hosted by the previous provider allows for a seamless transition of the DNS records to Route 53.By following this approach, the company can quickly migrate the DNS hosting service to a more resilient managed DNS service running on AWS.Here's why the other options are not the best fit for the given scenario:B. Creating an Amazon Route 53 private hosted zone: Private hosted zones are used for managing DNS within a VPC and are not suitable for hosting public domain name records.C. Creating a Simple AD directory and enabling zone transfer: This option is not necessary for migrating the DNS hosting service. It involves setting up an Active Directory and configuring zone transfers, which is not the primary requirement for the scenario.D. Creating an Amazon Route 53 Resolver inbound endpoint: This option involves configuring DNS resolution within a VPC and is not directly related to migrating the DNS hosting service to a more resilient managed DNS service.Therefore, the recommended solution for rapidly migrating the DNS hosting service to a more resilient managed DNS service running on AWS is:A. Create an Amazon Route 53 public hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider.