A company has a VPC with a public subnet and a private subnet. An EC2 instance in the public subnet is configured as a NAT instance. The company wants to replace the NAT instance with a NAT gateway for better availability and maintenance. After creating a NAT gateway in the public subnet and updating the route table of the private subnet, traffic from the private subnet cannot reach the internet. What is the MOST likely cause?
A NAT gateway requires an Elastic IP for outbound traffic.
Why this answer
A NAT gateway requires an Elastic IP address to function as a gateway for outbound internet traffic. Without an Elastic IP, the NAT gateway cannot perform source network address translation (SNAT), so instances in the private subnet cannot reach the internet. This is the most likely cause given that the route table update was already performed.
Exam trap
The trap here is that candidates may assume a NAT gateway can function without an Elastic IP, similar to a NAT instance, or they may incorrectly focus on route table misconfigurations when the route table was already updated.
How to eliminate wrong answers
Option A is wrong because the public subnet's route table does not affect traffic from the private subnet; the private subnet's route table controls its outbound traffic. Option B is wrong because NAT gateways do not use security groups; they use network ACLs at the subnet level, and security groups are not applicable to NAT gateways. Option C is wrong because the question states the route table was updated to point to the NAT gateway, so a lingering route to the NAT instance would be a configuration error that contradicts the given scenario.