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 4 Question 22 Discussion

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

A development team is building a new web application in the AWS Cloud. The main company domain, example.com. is currently hosted in an Amazon Route 53 public hosted zone in one of the company's production AWS accounts.

The developers want to test the web application in the company's staging AWS account by using publicly resolvable subdomains under the example.com domain with the ability to create and delete DNS records as needed. Developers have full access to Route 53 hosted zones within the staging account, but they are prohibited from accessing resources in any of the production AWS accounts.

Which combination of steps should a network engineer take to allow the developers to create records under the example.com domain? (Select TWO.)

Show Suggested Answer Hide Answer
Suggested Answer: C

The correct solution is to use an S3 interface endpoint and an on-premises DNS resolver. An S3 interface endpoint allows you to access Amazon S3 using private IP addresses within your VPC. An on-premises DNS resolver can be configured to forward the DNS queries for the S3 domain names to the S3 interface endpoint, so that the on-premises workloads can access Amazon S3 privately over the VPN connection. This solution is operationally efficient, as it does not require any additional infrastructure or changes to the existing workloads. The VPC workloads can continue to use the S3 gateway endpoint, which provides lower latency and higher throughput than the S3 interface endpoint.


Contribute your Thoughts:

0/2000 characters
Apolonia
3 months ago
I think a private hosted zone might be better for security.
upvoted 0 times
...
Glennis
3 months ago
B is definitely a solid choice too!
upvoted 0 times
...
Felix
3 months ago
Wait, can they really manage DNS records without access to production?
upvoted 0 times
...
Jettie
4 months ago
Totally agree, that’s the way to go!
upvoted 0 times
...
Michal
4 months ago
Just create a public hosted zone for staging.example.com, right?
upvoted 0 times
...
Pansy
4 months ago
I feel like option E makes sense since it allows the staging account to manage its own subdomain, but I'm not completely confident about the NS records part.
upvoted 0 times
...
Shoshana
4 months ago
I practiced a similar question where we had to set up DNS records, but I can't recall if we should create a public hosted zone or just use the existing one.
upvoted 0 times
...
Abel
4 months ago
I think we might need to create an NS record for staging.example.com in the main example.com domain to delegate the DNS management.
upvoted 0 times
...
Theola
5 months ago
I remember something about creating subdomains, but I'm not sure if we need a public or private hosted zone for staging.example.com.
upvoted 0 times
...
Darci
5 months ago
Based on the requirements, I think the best approach is to go with options A and E. Creating a public hosted zone for staging.example.com in the staging account, and then letting the developers manage DNS records there, seems like the cleanest solution.
upvoted 0 times
...
Claribel
5 months ago
I'm a bit confused about the requirement to use the example.com domain in the staging account. Wouldn't it be simpler to just create a new domain for the staging environment? Options C and D don't seem to address the core issue.
upvoted 0 times
...
Arlette
5 months ago
I think the key here is to create a subdomain in the staging account that can be used for testing, without modifying the production domain. Options A and E seem like the best approach to achieve that.
upvoted 0 times
...
Refugia
5 months ago
Hmm, this is a tricky one. I'm leaning towards options A and B - creating a public hosted zone for the subdomain in the staging account, and then setting up an NS record to point to it from the production domain. That way, the developers can manage the subdomain independently.
upvoted 0 times
...
Patrick
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the debug output and compare the configuration settings on both routers.
upvoted 0 times
...
Shanda
5 months ago
I think the key here is to make sure the operands are the same data type. If the Balance field is a string, I'll need to convert it to a number before comparing it.
upvoted 0 times
...
Loise
5 months ago
Wait, what's the default runlevel again? I'm drawing a blank on that detail. I better review my study materials quickly before answering.
upvoted 0 times
...
Maryann
9 months ago
Okay, let's think this through step-by-step. I think B and E are the right combination, but I'm curious to see what the other candidates come up with.
upvoted 0 times
...
Rhea
9 months ago
Haha, I'm just imagining the developers trying to remember which DNS records they created and where. Maybe they should just use a separate domain for the staging environment.
upvoted 0 times
...
Fausto
10 months ago
Hmm, I think the key here is to create a subdomain in the staging account and link it back to the production domain. Option B seems like the way to go.
upvoted 0 times
Elinore
8 months ago
Let's go with Option B and create the staging.example.com NS record in the example.com domain.
upvoted 0 times
...
Ena
8 months ago
Creating a public hosted zone for example.com in the staging account and setting up the NS record for staging.example.com makes sense.
upvoted 0 times
...
Tonette
8 months ago
I agree, Option B seems like the best choice to link the subdomain back to the production domain.
upvoted 0 times
...
...
Desire
11 months ago
Wait, so we can't access the production account, but we need to create records in the production domain? This sounds like a recipe for disaster.
upvoted 0 times
Ardella
10 months ago
B) Create a staging.example.com NS record in the example.com domain. Populate the value with the name servers from the staging.example.com domain. Set the routing policy type to simple routing.
upvoted 0 times
...
Brunilda
10 months ago
A) Create a public hosted zone for example.com in the staging account.
upvoted 0 times
...
...
Malcom
11 months ago
I'm not sure about that. Maybe we should create a private hosted zone for staging.example.com instead.
upvoted 0 times
...
Deandrea
11 months ago
I agree with Stefan. We also need to create a staging.example.com NS record in the example.com domain.
upvoted 0 times
...
Stefan
11 months ago
I think we should create a public hosted zone for example.com in the staging account.
upvoted 0 times
...

Save Cancel