AWS - VPC Fundamentals
You have an active VPC peering connection between two VPCs, but instances cannot communicate. Which of the following is the most probable cause?
You have an active VPC peering connection between two VPCs, but instances cannot communicate. Which of the following is the most probable cause?
medium📝 Predict Output Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Verify peering connection status
The connection is active, so acceptance is confirmed.Step 2: Check CIDR blocks
Overlapping CIDR blocks prevent peering creation, so this is unlikely.Step 3: Confirm route tables
Without proper routes in route tables, traffic cannot flow between VPCs despite active peering.Final Answer:
Route tables in one or both VPCs do not have routes for the peered VPC's CIDR block -> Option CQuick Check:
Active peering needs route table updates [OK]
Quick Trick: Active peering requires route table entries for communication [OK]
Common Mistakes:
MISTAKES- Assuming acceptance is automatic
- Ignoring route table configuration
- Confusing subnet type with peering issues
Master "VPC Fundamentals" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes