SAA-C03 · Domain 1: Design Resilient Architectures

Enterprise Multi-VPC Peering: Non-Transitive Routing & Route 53 Private Hosted Zone Fallacy

Client Profile: Multi-business unit enterprise operates three VPCs: VPC A (Frontend Web, 10.10.0.0/16), VPC B (Shared Services Hub, 10.20.0.0/16), and VPC C (Backend Database & Ledger, 10.30.0.0/16). Problem: The infrastructure team peered A-to-B and B-to-C, expecting Web workers in VPC A to reach the database in VPC C through the intermediate Shared Services VPC. All transactions from A to C timeout because VPC Peering does not support transitive routing, and database hostnames fail to resolve because VPC C was never associated with the Route 53 Private Hosted Zone.

Launch Interactive Lab in Browser → Browse All 56 AWS Labs

Lab Objective

Establish a direct VPC Peering connection between VPC A and VPC C, update route tables with non-overlapping routes, and associate the Route 53 Private Hosted Zone with VPC C.

Exam Track & Type

Solutions Architect Associate (SAA) (SAA-C03) · Live Outage Troubleshooting Drill

FinOps & Cost Impact

Establishing direct VPC Peering between A and C costs $0.00/hour and charges low intra-region data transfer ($0.01/GB), avoiding intermediate hop latency and redundant compute proxy appliances.

AWS Services Involved

VPC Cheatsheet → SUBNET Cheatsheet → EC2 Cheatsheet → RDS Cheatsheet → VPC-PEERING TRANSIT-GATEWAY Cheatsheet → ROUTE53 Cheatsheet → RTB Cheatsheet →

Verification Success Criteria

Diagnostic Starting Point (Spoiler-Free Hint)

Why cannot packets hop transitively through intermediate VPC B when VPC A is peered with VPC B and VPC B is peered with VPC C? What non-transitive routing rule governs AWS VPC Peering, and how do Route 53 Private Hosted Zones resolve internal hostnames across peered VPCs?

Real Solutions Architect Interview Question

Explain why AWS VPC Peering is non-transitive, how Route 53 Private Hosted Zones handle cross-VPC DNS resolution, and at what scale an enterprise should migrate from a VPC peering mesh to an AWS Transit Gateway hub.

Frequently Asked Questions

How do I troubleshoot "Enterprise Multi-VPC Peering: Non-Transitive Routing & Route 53 Private Hosted Zone Fallacy" in AWS?

Why cannot packets hop transitively through intermediate VPC B when VPC A is peered with VPC B and VPC B is peered with VPC C? What non-transitive routing rule governs AWS VPC Peering, and how do Route 53 Private Hosted Zones resolve internal hostnames across peered VPCs?

Which AWS certification exam covers this architecture scenario?

This interactive lab maps directly to SAA-C03 (Solutions Architect Associate (SAA)) under Domain 1: Design Resilient Architectures.

Do I need an AWS account or credit card to practice this lab?

No. CloudTracer runs a stateful VPC packet engine locally in your browser so you can debug Route Tables, Security Groups, NACLs, and target groups with $0 AWS cloud spend.

Related SAA-C03 Troubleshooting Labs

CLF-01

Missing Internet Gateway Route

Attach or route default outbound traffic 0.0.0.0/0 to the Internet Gateway in the public route table.…

CLF-04

Single Point of Failure (Single-AZ)

Add a secondary subnet in us-east-1b and front instances with an Application Load Balancer across both Availability…

CLF-06

Tight Coupling in Transaction Processing

Decouple the architecture by placing an Amazon SQS queue between the producer and consumer.…

SAA-01

FinTech Payment Ledger: $6,750 NAT Gateway S3 Cost Surge

Add an S3 prefix-list destination route in the private route table targeting the S3 Gateway Endpoint.…

SAA-02

HealthTech EMR Backend: Asymmetric Outbound NAT Routing

Re-point the private route table default route pointing to NAT (0.0.0.0/0 -> nat-xxx) in the public subnet.…

SAA-03

Retail Banking PCI Audit: Stateless NACL Ephemeral Drop

Add an outbound NACL rule permitting return ephemeral traffic (TCP 1024-65535) to 0.0.0.0/0.…