Amazon ANS-C01 Exam - Topic 5 Question 33 Discussion

Actual exam question for Amazon's ANS-C01 exam

Question #: 33
Topic #: 5

A company has a VPC in the AWS Cloud. The company recently acquired a competitor that also has a VPC in the AWS Cloud. A network engineer discovers an IP address overlap between the two VPCs. Both VPCs require access to an AWS Marketplace partner service.

Which solution will ensure interoperability among the VPC hosted services and the AWS Marketplace partner service?

AConfigure VPC peering with static routing between the VPCs. Configure an AWS Site-to-Site VPN connection with static routing to the partner service.

BConfigure a NAT gateway in the VPCs. Configure default routes in each VPC to point to the local NAT gateway. Attach each NAT gateway to a transit gateway. Configure an AWS Site-to-Site VPN connection with static routing to the partner service.

CConfigure AWS PrivateLink to facilitate connectivity between the VPCs and the partner service. Use the DNS name that is created with the associated interface endpoints to route traffic between the VPCs and the partner service.

DConfigure a NAT instance in the VPCs. Configure default routes in each VPC to point to the local NAT instance. Configure an interface endpoint in each VPC to connect to the partner service. Use the DNS name that is created with the associated interface endpoints to route traffic between the VPCs and the partner service.

Show Suggested Answer

Suggested Answer: B, C

To use AWS PrivateLink, you need to create interface type VPC endpoints for the services that you want to access privately from your VPC1. These endpoints appear as elastic network interfaces (ENIs) with private IPs in your subnets2. To enable DNS resolution for these endpoints, you need to set the enableDnsSupport attribute to True for your VPC, and enable DNS support for each endpoint3. You also need to ensure that the VPC endpoint policy allows communication between your VPC and the service4. You do not need to create any route table entries or Route 53 hosted zones for the endpoints, as they are not required for PrivateLink5.

AWS PrivateLink FAQs -- Amazon Web Services 2: AWS PrivateLink and service endpoint - Amazon EC2 Overview and Networking Introduction for Telecom Companies 3: VPC Endpoints: Secure and Direct Access to AWS Services 4: AWS PrivateLink and service endpoint - Amazon EC2 Overview and Networking Introduction for Telecom Companies 5: AWS Private Link vs VPC Endpoint - Stack Overflow

by Ozell at Aug 02, 2024, 07:18 AM

Limited Time Offer

25%

Off

Get Premium ANS-C01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Gilma

3 months ago

I think peering might work too, but C looks cleaner.

upvoted 0 times

...

Georgeanna

3 months ago

Wait, are we really sure about the IP overlap issue?

upvoted 0 times

...

Cristal

3 months ago

Not sure about that, NAT gateways can add complexity.

upvoted 0 times

...

Vilma

4 months ago

I agree, PrivateLink is a solid solution!

upvoted 0 times

...

Lucia

4 months ago

Option C seems like the best choice for VPC connectivity.

upvoted 0 times

...

Dion

4 months ago

I feel like using a NAT instance might be outdated compared to newer solutions like PrivateLink. I wonder if that's the right choice here.

upvoted 0 times

...

Viola

4 months ago

I practiced a similar question about NAT gateways, but I can't recall if they work well with overlapping IPs.

upvoted 0 times

...

Marla

4 months ago

I think AWS PrivateLink could be a good option here. It seems like it would solve the connectivity issue without needing to change the IPs.

upvoted 0 times

...

Maryann

5 months ago

I remember studying VPC peering, but I'm not sure if static routing is the best way to handle IP overlaps.

upvoted 0 times

...

Shannan

5 months ago

Based on the information provided, I believe Option C is the most appropriate solution. Using AWS PrivateLink to facilitate connectivity between the VPCs and the partner service seems like the cleanest way to address the IP address overlap.

upvoted 0 times

...

Cecily

5 months ago

I'm a bit confused by the different routing options presented. I'll need to review the details of each approach to determine which one best fits the requirements.

upvoted 0 times

...

Arminda

5 months ago

I think the key here is finding a solution that can handle the IP address overlap and provide secure connectivity to the partner service. Option C with AWS PrivateLink seems like the most elegant solution.

upvoted 0 times

...

Leah

5 months ago

Okay, let's think this through step-by-step. We have two VPCs with IP address overlap, and we need to connect them to an AWS Marketplace partner service. Hmm, this could get tricky.

upvoted 0 times

...

Kayleigh

5 months ago

This question seems straightforward, but I want to make sure I understand the requirements correctly before choosing an answer.

upvoted 0 times

...

Claudia

5 months ago

I'm a bit confused by the "Stop" profile. Does that mean the other profiles won't be applied? Or will the user still get everything except the "Stop" profile? I'll need to think this through carefully.

upvoted 0 times

...

Grover

5 months ago

This looks like a pretty straightforward question. I'll go through the options carefully and try to identify the key elements of a valid arrest.

upvoted 0 times

...

Kaitlyn

10 months ago

I'm with Jacinta on this one. Putting a NAT instance in each VPC? That's like using a rotary phone to call your grandma. Option C is the clear winner here.

upvoted 0 times

Makeda

8 months ago

Yeah, setting up VPC peering with static routing seems like a hassle compared to using AWS PrivateLink.

upvoted 0 times

...

Willard

9 months ago

I agree, using AWS PrivateLink makes the most sense in this scenario.

upvoted 0 times

...

Dell

9 months ago

Option C is definitely the way to go. It's the most modern and efficient solution.

upvoted 0 times

...

Jacinta

10 months ago

Haha, a NAT instance? What is this, the 90s? Option D is way too clunky. PrivateLink is the future, baby!

upvoted 0 times

Vonda

9 months ago

Yeah, NAT instance seems like a step back in time compared to PrivateLink.

upvoted 0 times

...

Merilyn

9 months ago

I agree, PrivateLink is definitely the more modern and efficient solution.

upvoted 0 times

...

Zana

9 months ago

Option D is outdated, PrivateLink is the way to go!

upvoted 0 times

...

Marge

10 months ago

I'm not a fan of using a transit gateway in this scenario. It adds an unnecessary layer of complexity. Option C is the way to go for sure.

upvoted 0 times

Benton

9 months ago

Let's go with Option C then. It's the most efficient choice.

upvoted 0 times

...

Gwen

9 months ago

Yeah, AWS PrivateLink simplifies the connectivity between VPCs and the partner service.

upvoted 0 times

...

Stefan

9 months ago

I think Option C with AWS PrivateLink is the most straightforward solution.

upvoted 0 times

...

Graham

10 months ago

I agree, using a transit gateway does seem like overkill.

upvoted 0 times

...

Jerry

10 months ago

Option C seems like the most straightforward and scalable solution. Using PrivateLink to connect the VPCs and the partner service is a clean and efficient way to handle the IP address overlap.

upvoted 0 times