Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - 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's VPC has Amazon EC2 instances that are communicating with AWS services over the public internet. The company needs to change the connectivity so that the communication

does not occur over the public intemet.

The company deploys AWS PrivateLink endpoints in the VPC. After the deployment of the PrivateLink endpoints, the EC2 instances can no longer communicate at all with the required AWS

services.

Which combination of steps should a network engineer take to restore communication with the AWS services? (Select TWO.)

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:

Taryn
3 months ago
Ah, the joys of AWS networking. Gotta love it! Okay, let's see... Add a route in the VPC table, make sure the DNS is set up right, and check that VPC endpoint policy. Easy peasy, right? Just don't forget to bring your problem-solving hat!
upvoted 0 times
...
Nieves
3 months ago
Haha, yeah, that public hosted zone option is like trying to sneak through the front door when you've got a secret tunnel out back. Not the way to go, my friend!
upvoted 0 times
...
Shakira
4 months ago
Wait, hold up... Did someone say 'public hosted zone'? I thought we were trying to avoid the public internet here! Gotta keep those AWS services on the down-low, am I right?
upvoted 0 times
Hershel
3 months ago
C: And make sure the VPC endpoint policy allows communication.
upvoted 0 times
...
Long
3 months ago
D: Definitely, we don't want to create a public hosted zone for all services. Let's keep it private.
upvoted 0 times
...
Maricela
3 months ago
B: We should add a route in the VPC route table for the PrivateLink endpoints.
upvoted 0 times
...
Laurena
3 months ago
C: And we need to check that the VPC endpoint policy allows communication.
upvoted 0 times
...
Louvenia
3 months ago
A: Yeah, we need to make sure the communication doesn't go over the public internet.
upvoted 0 times
...
Ryan
3 months ago
B: I think we should add a route in the VPC route table for the PrivateLink endpoints.
upvoted 0 times
...
Winfred
3 months ago
A: Yeah, we need to make sure the communication doesn't go over the public internet.
upvoted 0 times
...
...
Bernardine
4 months ago
I agree with both of those steps. We need to make sure the enableDnsSupport attribute is set to True for the VPC as well.
upvoted 0 times
...
Ashanti
4 months ago
Yes, that sounds like a good idea. We also need to ensure that the VPC endpoint policy allows communication.
upvoted 0 times
...
Clorinda
4 months ago
I think we should add a route in the VPC route table with PrivateLink endpoints as the destination.
upvoted 0 times
...
Evangelina
4 months ago
Hmm, I think the key here is to ensure the PrivateLink endpoints have proper DNS support and the VPC endpoint policy is configured correctly. That should do the trick.
upvoted 0 times
Claudio
4 months ago
A) In the VPC route table, add a route that has the PrivateLink endpoints as the destination.
upvoted 0 times
...
Corrie
4 months ago
C) Ensure that the VPC endpoint policy allows communication.
upvoted 0 times
...
Minna
4 months ago
B) Ensure that the enableDnsSupport attribute is set to True for the VPC. Ensure that each VPC endpoint has DNS support enabled.
upvoted 0 times
...
Chaya
4 months ago
A) In the VPC route table, add a route that has the PrivateLink endpoints as the destination.
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