Bird
0
0

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

medium📝 Debug Q14 of 15
AWS - VPC Fundamentals
You created an Internet Gateway and attached it to your VPC, but your EC2 instance in the public subnet still cannot access the internet. What is the most likely cause?
AThe Internet Gateway is not attached to the VPC
BThe EC2 instance is stopped
CThe route table for the subnet does not have a route to the Internet Gateway
DThe security group allows all traffic
Step-by-Step Solution
Solution:
  1. Step 1: Confirm Internet Gateway attachment

    The question states the Internet Gateway is attached to the VPC, so this is not the issue.
  2. Step 2: Check route table configuration

    For internet access, the subnet's route table must have a route directing 0.0.0.0/0 traffic to the Internet Gateway. Missing this route blocks internet access.
  3. Final Answer:

    The route table for the subnet does not have a route to the Internet Gateway -> Option C
  4. Quick Check:

    Route table missing IGW route = no internet [OK]
Quick Trick: Check route table for 0.0.0.0/0 route to IGW [OK]
Common Mistakes:
MISTAKES
  • Ignoring route table routes
  • Assuming attachment alone grants internet
  • Confusing security group rules with routing

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes