A county needs separate VPCs for assessor, courts, and public works that must reach a central shared-services VPC for Active Directory and logging without creating a full mesh of VPC peerings. Which connectivity design best meets this requirement?
Select an answer to reveal the explanation.
Short Explanation
Think of Transit Gateway like a county road hub instead of paving a driveway from every building to every other building. Each VPC attaches once, shared services sit in the middle, and route tables decide who can talk to whom. Full-mesh peering gets ugly fast as departments multiply.
Full Explanation
For multi-VPC municipal designs, AWS Transit Gateway provides scalable hub-and-spoke connectivity without the N-squared cost of VPC peering. Attach assessor, courts, public works, and shared-services VPCs to the Transit Gateway, then use separate Transit Gateway route tables so spokes can reach shared services without unrestricted transitive spoke-to-spoke paths unless explicitly required. Peering alone does not scale for many department VPCs, collapsing into one VPC weakens blast-radius isolation, and public internet fronting for directory and logging violates typical private shared-services requirements.