SAA-C03 Question #561: Real Exam Question with Answer & Explanation

Question

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?

Options

• ACreate an Amazon Route 53 public hosted zone for the domain name. Import the zone file
• BCreate an Amazon Route 53 private hosted zone for the domain name. Import the zone file
• CCreate a Simple AD directory in AWS. Enable zone transfer between the DNS provider and AWS
• DCreate an Amazon Route 53 Resolver inbound endpoint in the VPC. Specify the IP addresses

Explanation

Amazon Route 53 is a highly available and scalable authoritative DNS service. To move a public domain, you create a public hosted zone, import or recreate the zone records, and then update the registrar to use the Route 53 name servers assigned to the zone. Route 53 is globally distributed and designed for rapid propagation and resilience, and supports features such as health checks and routing policies. A private hosted zone (Option B) is resolvable only by VPCs that are associated with it and is not for public internet DNS. Directory Service and zone transfers (Option C) are unrelated to Route 53 public DNS hosting. Route 53 Resolver inbound endpoints (Option D) provide hybrid DNS forwarding for VPC workloads, not authoritative public hosting. Therefore, the fastest AWS-native migration path to a resilient managed DNS is to create a Route 53 public hosted zone and import the existing zone file.

No community discussion yet for this question.