Bird
0
0

After establishing a VPC peering connection, you notice traffic is blocked despite correct routes and security groups. What could be the issue?

medium📝 Debug Q7 of 15
AWS - VPC Fundamentals
After establishing a VPC peering connection, you notice traffic is blocked despite correct routes and security groups. What could be the issue?
AInstances are in different availability zones
BVPC peering connection is in pending state
CElastic Load Balancer is misconfigured
DNetwork ACLs are blocking traffic between VPCs
Step-by-Step Solution
Solution:
  1. Step 1: Confirm peering and routes

    Peering is established and routes are correct, so these are not the issue.
  2. Step 2: Check Network ACLs

    Network ACLs can block traffic at subnet level even if routes and security groups allow it.
  3. Final Answer:

    Network ACLs are blocking traffic between VPCs -> Option D
  4. Quick Check:

    Network ACLs can block traffic despite routes [OK]
Quick Trick: Check Network ACLs if traffic blocked after routes and SGs [OK]
Common Mistakes:
MISTAKES
  • Ignoring Network ACLs in troubleshooting
  • Assuming availability zones affect peering
  • Blaming unrelated ELB configuration

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes