A solutions architect is configuring a VPC that has public subnets and private subnets. The VPC and subnets use IPv4 CIDR blocks. There is one public subnet and one private subnet in each of three Ava

Question

Options

• ACreate a NAT gateway in one of the public subnets. Update the route tables that are attached to
• BCreate three NAT instances in each private subnet. Create a private route table for each
• CAttach an egress-only internet gateway in the VPC. Update the route tables of the private subnets
• DCreate a NAT gateway in one of the private subnets. Update the route tables that are attached to

• A
  86% (12)
• B
  7% (1)
• C
  7% (1)

Explanation

Private subnets require outbound internet access to download updates, but they must not have public IPs or direct inbound access. The recommended AWS solution is to create a NAT gateway in a public subnet. Private subnet route tables are updated to route internet-bound traffic (0.0.0.0/0) to the NAT gateway. The NAT gateway then uses the internet gateway attached to the VPC to communicate with the internet. Option B (NAT instances) is an older approach and less scalable/maintainable than NAT Option C (egress-only internet gateway) is for IPv6 outbound-only traffic, not IPv4. Option D is invalid because NAT gateways must be deployed in public subnets.

No community discussion yet for this question.