Discuss Amazon ANS-C01 Exam Topic 1 Question 49

A company has expanded its network to the AWS Cloud by using a hybrid architecture with multiple AWS accounts. The company has set up a shared AWS account for the connection to its on-premises data centers and the company offices. The workloads consist of private web-based services for internal use. These services run in different AWS accounts. Office-based employees consume these services by using a DNS name in an on-premises DNS zone that is named example.internal.

The process to register a new service that runs on AWS requires a manual and complicated change request to the internal DNS. The process involves many teams.

The company wants to update the DNS registration process by giving the service creators access that will allow them to register their DNS records. A network engineer must design a solution that will achieve this goal. The solution must maximize cost-effectiveness and must require the least possible number of configuration changes.

Which combination of steps should the network engineer take to meet these requirements? (Choose three.)

ACreate a record for each service in its local private hosted zone (serviceA.account1.aws.example.internal). Provide this DNS record to the employees who need access.

BCreate an Amazon Route 53 Resolver inbound endpoint in the shared account VPC. Create a conditional forwarder for a domain named aws.example.internal on the on-premises DNS servers. Set the forwarding IP addresses to the inbound endpoint's IP addresses that were created.

CCreate an Amazon Route 53 Resolver rule to forward any queries made to onprem.example.internal to the on-premises DNS servers.

DCreate an Amazon Route 53 private hosted zone named aws.example.internal in the shared AWS account to resolve queries for this domain.

ELaunch two Amazon EC2 instances in the shared AWS account. Install BIND on each instance. Create a DNS conditional forwarder on each BIND server to forward queries for each subdomain under aws.example.internal to the appropriate private hosted zone in each AWS account. Create a conditional forwarder for a domain named aws.example.internal on the on-premises DNS servers. Set the forwarding IP addresses to the IP addresses of the BIND servers.

FCreate a private hosted zone in the shared AWS account for each account that runs the service. Configure the private hosted zone to contain aws.example.internal in the domain (account1.aws.example.internal). Associate the private hosted zone with the VPC that runs the service and the shared account VPC.

Suggested Answer: A, B, D

To meet the requirements of updating the DNS registration process while maximizing cost-effectiveness and minimizing configuration changes, the network engineer should take the following steps:

Create an Amazon Route 53 Resolver inbound endpoint in the shared account VPC. Create a conditional forwarder for a domain named aws.example.internal on the on-premises DNS servers. Set the forwarding IP addresses to the inbound endpoint's IP addresses that were created (Option B).

Create an Amazon Route 53 private hosted zone named aws.example.internal in the shared AWS account to resolve queries for this domain (Option D).

Create a record for each service in its local private hosted zone (serviceA.account1.aws.example.internal). Provide this DNS record to the employees who need access (Option A).

These steps will allow service creators to register their DNS records while keeping costs low and minimizing configuration changes.

Get Premium ANS-C01 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

29 comments · newest first

Ramonita 10 months ago

Not sure why they wouldn't just use a private hosted zone.

Margot 10 months ago

I think option B is the best choice here!

Harris 10 months ago

Sounds like a complex setup with multiple accounts.

Tegan 11 months ago

Surprised they haven't automated the DNS process yet!

Lucina 11 months ago

I disagree, option E seems way too complicated for this.

Tawanna 11 months ago

I’m a bit confused about whether we need to create a record for each service or just set up a conditional forwarder. I wish I had reviewed that part more thoroughly!

Olga 11 months ago

I practiced a similar question where we had to minimize changes, and I feel like creating a private hosted zone in the shared account might be the right approach.

Carri 11 months ago

I think option B sounds familiar; setting up a Route 53 Resolver inbound endpoint could help with the DNS queries, but I’m not entirely confident about the details.

Deja 12 months ago

I remember we discussed the importance of using Route 53 for DNS management, but I'm not sure if creating a private hosted zone is the best option here.

Leonida 12 months ago

This is a tricky one. I'm not sure which combination of steps is the best approach. I'll need to review the details carefully and think through the trade-offs of each option.

Herschel 1 year ago

I'm feeling pretty confident about this. I think a combination of B, D, and F would meet the requirements nicely. The private hosted zones and conditional forwarding should do the trick.

Charlene 1 year ago

Option B seems like a good starting point - using Route 53 Resolver to forward queries to the on-premises DNS servers. That could help simplify the overall architecture.

Tiffiny 1 year ago

I'm a bit confused by all the different options. I need to carefully read through each one and make sure I understand how they work before deciding.

Lavonne 1 year ago

This looks like a complex networking question, but I think I have a good strategy. I'll focus on the key requirements of cost-effectiveness and minimal configuration changes.

Kip 1 year ago

Hmm, Option F with the private hosted zones in the shared account could work, but it might get a bit complex to manage all those zones. I'd try to keep things as simple as possible.

Dorothy 1 year ago

Option E with the BIND servers sounds a bit overkill. Why not just use the built-in Route 53 features in Options B and D? That seems simpler and more efficient.

Elin 1 year ago

↳ replying to Dorothy

I think sticking with the built-in Route 53 features will definitely be more cost-effective and require fewer configuration changes.

Carman 1 year ago

↳ replying to Dorothy

Yeah, setting up BIND servers in Option E does seem like a lot of extra work.

Hollis 1 year ago

↳ replying to Dorothy

I agree, using Route 53 features in Options B and D seems like a more straightforward solution.

Yolando 1 year ago

Option C is a bit of a head-scratcher. Forwarding queries to on-premises servers when the goal is to move to the cloud? I think we can do better than that.

Lon 1 year ago

↳ replying to Yolando

A: That sounds like a more efficient approach. It would simplify the process for service creators to register their DNS records.

Ashton 1 year ago

↳ replying to Yolando

B: I agree. Maybe we should consider options that involve creating private hosted zones in the shared AWS account for each service.

Ma 1 year ago

↳ replying to Yolando

A: Option C does seem counterintuitive. We should focus on solutions that align with moving to the cloud.

Mila 2 years ago

I'm not sure about option A. I think option E might be more cost-effective in the long run.

Callie 2 years ago

Haha, Option E with the BIND servers sounds like a job for the DNS wizard themselves. I hope they have their robe and wand ready!

Denae 1 year ago

↳ replying to Callie

User 2: Definitely! Those BIND servers seem like they will do some magic.

Shalon 1 year ago

↳ replying to Callie

User 1: Haha, Option E does sound like a job for a DNS wizard!

Fallon 2 years ago

I agree with you, Clarinda. Option A seems like the most straightforward solution.

Clarinda 2 years ago

I think option A is a good choice. It allows service creators to register their DNS records.

Amazon ANS-C01 Exam - Topic 1 Question 49 Discussion