You created an Internet Gateway and attached it to your VPC, but instances in the public subnet still cannot access the internet. What is the most likely misconfiguration?

medium📝 Debug Q6 of 15

AWS - VPC Fundamentals

AThe subnet does not have a security group.

BThe Internet Gateway is not attached to the subnet.

CThe VPC does not have an Elastic IP.

DThe route table for the subnet does not have a route to the Internet Gateway.

Step-by-Step Solution

Solution:

Step 1: Check Internet Gateway attachment
The IGW is attached to the VPC, so that is correct.
Step 2: Verify route table configuration
If the route table lacks a route to the IGW, traffic won't reach the internet.
Final Answer:
The route table for the subnet does not have a route to the Internet Gateway. -> Option D
Quick Check:
Route table must route to IGW for internet access [OK]

Quick Trick: Route table must include IGW route for internet access [OK]

Common Mistakes:

MISTAKES

Thinking IGW attaches to subnet directly
Assuming Elastic IP is required for VPC

Master "VPC Fundamentals" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You created an Internet Gateway and attached it to your VPC, but instances in the public subnet still cannot access the internet. What is the most likely misconfiguration?

Step 1: Check Internet Gateway attachment

Step 2: Verify route table configuration

Final Answer:

Quick Check:

Want More Practice?