Topic 1 Question 191

AWS Certified Advanced Networking - Specialty

Topic 1 Question 191
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 internet.

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?

2 つ選択
- In the VPC route table, add a route that has the PrivateLink endpoints as the destination.
- Ensure that the enableDnsSupport attribute is set to True for the VPC. Ensure that each VPC endpoint has DNS support enabled.
- Ensure that the VPC endpoint policy allows communication.
- Create an Amazon Route 53 public hosted zone for all services.
- Create an Amazon Route 53 private hosted zone that includes a custom name for each service.
ユーザの投票
コメント(3)
- 正解だと思う選択肢: BC
  A. This is not a VPC Gateway Endpoint. B. You need to use AmazonProvidedDNS, so this is doable option. C. VPC endpoint policy might block the connection, so possible cause. D & E. You don't need to use the R53 Hosted Zone for this scenario.
  
  👍 3
  seochan2024/05/29
- 正解だと思う選択肢: BC
  The most effective steps are B and C. Ensuring that DNS support is enabled for both the VPC and the PrivateLink endpoints, along with verifying that the VPC endpoint policy permits the required access, will restore the necessary communication between the EC2 instances and the AWS services over the private network. These steps ensure that the services are correctly resolved and accessible while maintaining security and privacy through the AWS network.
  
  👍 2
  Akshay04032024/07/23
- 正解だと思う選択肢: BC
  A is incorrect: Adding routes to the PrivateLink endpoints in the route table is not necessary for endpoint communication D is incorrect: Creating a public hosted zone is not the right approach for private connectivity E is incorrect: While private hosted zones can be useful, they are not directly required to restore PrivateLink endpoint communication
  
  👍 1
  woorkim2024/12/10
シャッフルモード

ユーザの投票

コメント(3)