A company registers the public domain example.com in a central AWS account using Amazon Route 53. The company wants to host a subdomain, test.example.com, in a different AWS account to provide name resolution for EC2 instances in that account, without transferring the parent domain. An engineer creates a new Route 53 hosted zone for the subdomain in the second account. Which steps must the engineer perform to finish the setup? (Choose two.)

To delegate a subdomain to a separate AWS account, two key steps are required. First, you must create the necessary DNS records (like A, CNAME, etc.) for the hosts within the test.example.com subdomain inside the new Route 53 hosted zone in the second account. This makes the subdomain resolvable. Second, the parent domain's hosted zone (example.com) in the central account needs NS records that delegate authority for test.example.com to the name servers of the new hosted zone. This tells DNS resolvers where to find information for the subdomain. Updating the subdomain's DNS with NS records pointing back to the parent is incorrect; the delegation flows from parent to child. Creating an alias record in the parent domain pointing to the subdomain's hosted zone is not the standard or correct way to delegate a subdomain; NS records are used for delegation. Adding an SOA record in the parent domain for the subdomain is unnecessary; the SOA record for the subdomain resides within its own hosted zone.