Which AWS construct helps manage IP addressing across multiple VPCs and accounts?

• A. VPC Peering
• B. AWS Transit Gateway
• C. Direct Connect
• D. Route 53

Answer: (B)

A centralized hub for inter-VPC routing is what this item measures. AWS Transit Gateway acts as a single hub that connects many VPCs (even across different AWS accounts) and other networks through attachments, creating a hub-and-spoke network. This setup makes IP addressing and routing across multiple VPCs much simpler because you manage traffic between VPCs through one place, using route tables associated with the transit gateway and its attachments. It scales as you add more VPCs and accounts, and it avoids the complexity of maintaining many point-to-point connections.

VPC peering would require individual connections between pairs of VPCs and doesn’t scale well when you have many VPCs or cross-account setups. Direct Connect is for establishing a dedicated physical link between on-premises networks and AWS, not for inter-VPC IP management across multiple VPCs. Route 53 is a DNS service and isn’t used for routing IP traffic between VPCs.