New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon ANS-C01 Exam - Topic 1 Question 49 Discussion

Actual exam question for Amazon's ANS-C01 exam
Question #: 49
Topic #: 1
[All ANS-C01 Questions]

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.)

Show Suggested Answer Hide Answer
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.


Contribute your Thoughts:

0/2000 characters
Ramonita
2 months ago
Not sure why they wouldn't just use a private hosted zone.
upvoted 0 times
...
Margot
2 months ago
I think option B is the best choice here!
upvoted 0 times
...
Harris
2 months ago
Sounds like a complex setup with multiple accounts.
upvoted 0 times
...
Tegan
3 months ago
Surprised they haven't automated the DNS process yet!
upvoted 0 times
...
Lucina
3 months ago
I disagree, option E seems way too complicated for this.
upvoted 0 times
...
Tawanna
3 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!
upvoted 0 times
...
Olga
3 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.
upvoted 0 times
...
Carri
4 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.
upvoted 0 times
...
Deja
4 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.
upvoted 0 times
...
Leonida
4 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.
upvoted 0 times
...
Herschel
4 months 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.
upvoted 0 times
...
Charlene
4 months 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.
upvoted 0 times
...
Tiffiny
5 months 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.
upvoted 0 times
...
Lavonne
5 months 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.
upvoted 0 times
...
Kip
10 months 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.
upvoted 0 times
...
Dorothy
10 months 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.
upvoted 0 times
Elin
9 months ago
I think sticking with the built-in Route 53 features will definitely be more cost-effective and require fewer configuration changes.
upvoted 0 times
...
Carman
9 months ago
Yeah, setting up BIND servers in Option E does seem like a lot of extra work.
upvoted 0 times
...
Hollis
9 months ago
I agree, using Route 53 features in Options B and D seems like a more straightforward solution.
upvoted 0 times
...
...
Yolando
10 months 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.
upvoted 0 times
Lon
9 months ago
A: That sounds like a more efficient approach. It would simplify the process for service creators to register their DNS records.
upvoted 0 times
...
Ashton
9 months ago
B: I agree. Maybe we should consider options that involve creating private hosted zones in the shared AWS account for each service.
upvoted 0 times
...
Ma
9 months ago
A: Option C does seem counterintuitive. We should focus on solutions that align with moving to the cloud.
upvoted 0 times
...
...
Mila
10 months ago
I'm not sure about option A. I think option E might be more cost-effective in the long run.
upvoted 0 times
...
Callie
10 months 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!
upvoted 0 times
Denae
9 months ago
User 2: Definitely! Those BIND servers seem like they will do some magic.
upvoted 0 times
...
Shalon
9 months ago
User 1: Haha, Option E does sound like a job for a DNS wizard!
upvoted 0 times
...
...
Fallon
11 months ago
I agree with you, Clarinda. Option A seems like the most straightforward solution.
upvoted 0 times
...
Clarinda
11 months ago
I think option A is a good choice. It allows service creators to register their DNS records.
upvoted 0 times
...

Save Cancel