A company has a VPC with multiple private subnets that host multiple applications. The applications must not be accessible to the internet. However, the applications need to access multiple AWS…

Question

Options

• AConfigure interface VPC endpoints for the required AWS services. Route traffic from the private
• BDeploy a NAT gateway in each private subnet. Route traffic from the private subnets through the
• CDeploy internet gateways in each private subnet. Route traffic from the private subnets through
• DSet up an AWS Direct Connect connection between the private subnets. Route traffic from the

• A
  73% (40)
• B
  4% (2)
• C
  9% (5)
• D
  15% (8)

Explanation

AWS VPC endpoints (interface and gateway) allow private connectivity from VPC resources to AWS services without requiring public IP addresses or internet gateways. This ensures applications remain isolated in private subnets while securely accessing AWS services. NAT gateways (B) would allow internet access, which does not meet the security requirement. Internet gateways (C) directly expose traffic to the internet, which violates the isolation requirement. Direct Connect (D) connects on- premises environments to AWS but does not provide service access from private subnets. Therefore, option A - using interface VPC endpoints - is the correct solution.

No community discussion yet for this question.