Learn the correct steps to create a subdomain in another AWS account using Amazon Route 53, and avoid common mistakes that can cause errors or delays.
Table of Contents
Question
A company uses Amazon Route 53 to register a public domain, example.com, in an AWS account. A central services group manages the account. The company wants to create a subdomain, test.example.com, in another AWS account to offer name services for Amazon EC2 instances that are hosted in the account. The company does not want to migrate the parent domain to the subdomain account.
A network engineer creates a new Route 53 hosted zone for the subdomain in the second account.
Which combination of steps must the network engineer take to complete the task? (Choose two.)
A. Add records for the hosts of the new subdomain to the new Route 53 hosted zone.
B. Update the DNS service for the parent domain by adding name server (NS) records for the subdomain.
C. Update the DNS service for the subdomain by adding name server (NS) records for the parent domain.
D. Create an alias record from the parent domain that points to the hosted zone for the subdomain in the second account.
E. Add a start of authority (SOA) record in the parent domain for the subdomain.
Answer
A. Add records for the hosts of the new subdomain to the new Route 53 hosted zone.
B. Update the DNS service for the parent domain by adding name server (NS) records for the subdomain.
Explanation
The correct combination of steps to create a subdomain in another AWS account using Amazon Route 53 is A and B.
A. Add records for the hosts of the new subdomain to the new Route 53 hosted zone.
This step is necessary to define how to route traffic for the subdomain and its subdomains, such as test.example.com and backend.test.example.com. You can create records using either the Route 53 console or the Route 53 API.
B. Update the DNS service for the parent domain by adding name server (NS) records for the subdomain.
This step is necessary to delegate responsibility for the subdomain to the new hosted zone in the second account. You need to get the name servers that Route 53 assigned to the new hosted zone and add them as NS records in the hosted zone for the parent domain.
C. Update the DNS service for the subdomain by adding name server (NS) records for the parent domain.
This step is incorrect because it is not required to add NS records for the parent domain in the subdomain hosted zone. The NS records for the parent domain are already defined in the root domain hosted zone.
D. Create an alias record from the parent domain that points to the hosted zone for the subdomain in the second account.
This step is incorrect because an alias record is used to route traffic to a specific AWS resource, such as an ELB load balancer or an S3 bucket, not to a hosted zone. An alias record cannot point to another domain name or subdomain name.
E. Add a start of authority (SOA) record in the parent domain for the subdomain.
This step is incorrect because it is not necessary to create an additional SOA record in the parent domain for the subdomain. The SOA record is automatically created by Route 53 when you create a hosted zone, and it contains information about the zone, such as the primary name server and the serial number. You should not create or delete SOA records in Route 53.
AWS Certified Advanced Networking – Specialty ANS-C01 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the AWS Certified Advanced Networking – Specialty ANS-C01 exam and earn AWS Certified Advanced Networking – Specialty ANS-C01 certification.