Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam ANS-C01 Topic 5 Question 33 Discussion

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

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?

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


Contribute your Thoughts:

Kaitlyn
1 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
2 days ago
Yeah, setting up VPC peering with static routing seems like a hassle compared to using AWS PrivateLink.
upvoted 0 times
...
Willard
9 days ago
I agree, using AWS PrivateLink makes the most sense in this scenario.
upvoted 0 times
...
Dell
1 months ago
Option C is definitely the way to go. It's the most modern and efficient solution.
upvoted 0 times
...
...
Jacinta
2 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
24 days ago
Yeah, NAT instance seems like a step back in time compared to PrivateLink.
upvoted 0 times
...
Merilyn
29 days ago
I agree, PrivateLink is definitely the more modern and efficient solution.
upvoted 0 times
...
Zana
1 months ago
Option D is outdated, PrivateLink is the way to go!
upvoted 0 times
...
...
Marge
2 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
13 days ago
Let's go with Option C then. It's the most efficient choice.
upvoted 0 times
...
Gwen
17 days ago
Yeah, AWS PrivateLink simplifies the connectivity between VPCs and the partner service.
upvoted 0 times
...
Stefan
1 months ago
I think Option C with AWS PrivateLink is the most straightforward solution.
upvoted 0 times
...
Graham
1 months ago
I agree, using a transit gateway does seem like overkill.
upvoted 0 times
...
...
Jerry
2 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
Kirby
1 months ago
A
upvoted 0 times
...
Almeta
2 months ago
C
upvoted 0 times
...
...
Telma
2 months ago
But wouldn't using NAT gateways and transit gateways provide better connectivity?
upvoted 0 times
...
Carolynn
2 months ago
I disagree, I believe configuring AWS PrivateLink is the way to go for interoperability.
upvoted 0 times
...
Telma
2 months ago
I think the best solution is to configure VPC peering with static routing between the VPCs.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77