[Solved] You associated a route table with a subnet that has a route:- Destination: 0.0.0.0/0, Target: igw-xyz789Instances still cannot access the internet. What is the most probable cause? | AWS

AWS - VPC Fundamentals

You associated a route table with a subnet that has a route:
- Destination: 0.0.0.0/0, Target: igw-xyz789
Instances still cannot access the internet. What is the most probable cause?

AThe instances lack public IP addresses

BThe route table is not associated with the subnet

CThe subnet's network ACL blocks outbound traffic

DThe Internet Gateway is detached from the VPC

Step-by-Step Solution

Solution:

Step 1: Confirm route table association
The question states the route table is associated.
Step 2: Check Internet Gateway attachment
Assuming igw-xyz789 is attached; otherwise, route wouldn't work.
Step 3: Consider instance IP addressing
Instances need public IPs to access internet via IGW.
Final Answer:
Instances lack public IP addresses -> Option A
Quick Check:
Public IP required for IGW internet access [OK]

Quick Trick: Instances need public IPs for IGW internet access [OK]

Common Mistakes:

MISTAKES

Ignoring instance IP assignment
Assuming route table association is missing

Master "VPC Fundamentals" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More AWS Quizzes

You associated a route table with a subnet that has a route:

Step 1: Confirm route table association

Step 2: Check Internet Gateway attachment

Step 3: Consider instance IP addressing

Final Answer:

Quick Check:

Want More Practice?