0/16 localWhat should be added to the private subnet’s route table in order to address this issue, given the information provided?
0.0.0.0/0 IGW
0.0.0.0/0 NAT
10.0.1.0/24 IGW
10.0.1.0/24 NAT
Explanations:
An Internet Gateway (IGW) cannot be used in a private subnet route table. The IGW is associated with the public subnet and allows resources in the public subnet to access the internet directly. Private subnets cannot use IGW for routing internet traffic.
Adding a route for0.0.0.0/0to target the NAT Gateway allows instances in the private subnet to send traffic to the internet while keeping them inaccessible from the public internet. The NAT Gateway enables outbound internet access for resources in the private subnet, allowing them to download patches.
The route10.0.1.0/24 IGWdoes not enable internet access for the private subnet. This route points to a public subnet’s IGW, which is not valid for a private subnet. Instances in the private subnet require a NAT Gateway for internet connectivity.
The route10.0.1.0/24 NATdoes not make sense as it implies routing traffic to a NAT Gateway within the same CIDR block of the public subnet, which is not how routing works. Instances in the private subnet should route0.0.0.0/0to the NAT Gateway for outbound internet access, not to a specific subnet.