ANS-C01 Question 396
Single answerYour company has multiple VPCs, each representing a different environment (e.g., production, development, and testing) within the same AWS Region. The production VPC has shared services, such as a central database and logging systems, that need to be accessed by the other environments. The network design must simplify management and scale as new VPCs are added. Which connectivity option is most appropriate for this scenario?
- A
Use VPC peering to connect each environment's VPC with the production VPC.
- B
Set up a Transit Gateway to connect all VPCs, allowing centralized routing and management.
- C
Use an Internet Gateway to allow traffic between the VPCs.
- D
Deploy a VPN connection between each VPC to enable inter-VPC communication.
Show answer and explanation
Correct answer: B
Explanation
A Transit Gateway is the most appropriate solution for this scenario because it allows centralized management of routing between multiple VPCs. It is highly scalable and simplifies connectivity as new VPCs are added. VPC peering, while functional, becomes difficult to scale in environments with more than a few VPCs. Internet Gateways and VPNs are not designed for inter-VPC communication and do not meet the requirements of this use case.
- A. Incorrect.
Using VPC peering for multiple VPCs becomes complex as the number of VPCs grows. It does not scale well because it requires managing numerous peering connections and routing tables.
- B. Correct.
A Transit Gateway is the best solution for connecting multiple VPCs in a scalable, centralized manner. It simplifies management and routing, making it ideal for environments with shared services and multiple environments.
- C. Incorrect.
An Internet Gateway is used for external internet access and cannot be used for direct communication between VPCs.
- D. Incorrect.
A VPN connection is typically used for secure communication between on-premises networks and AWS. It is not suitable for inter-VPC communication as it adds unnecessary complexity and cost.