A county application team proposes peering every microservice VPC to every other microservice VPC. The architect must recommend a scalable alternative for multi-VPC connectivity. What should the architect recommend?
Select an answer to reveal the explanation.
Short Explanation
Full-mesh peering is like drawing a string between every house in the county—fine for three homes, nonsense for thirty. Transit Gateway gives you a hub: one attachment style, central route control. That is the grown-up multi-VPC answer.
Full Explanation
VPC peering is point-to-point and does not support transitive routing, so a full mesh grows poorly as microservice VPCs multiply and hits practical operational and quota limits. AWS Transit Gateway centralizes attachments and routing for hub-and-spoke (and controlled spoke patterns), which is the scalable multi-VPC recommendation. Collapsing all services into one subnet or exposing east-west traffic publicly trades isolation and security for temporary simplicity.