ANS-C01 Question 394
Select 2Your company has multiple VPCs across two AWS Regions. Some VPCs require low-latency, high-bandwidth connectivity between them, while others need to communicate with a centralized shared service VPC that hosts security and monitoring tools. Additionally, you want a solution that minimizes management overhead and scales as new VPCs are added. Which combination of networking approaches is most appropriate for this scenario?
- A
Use VPC peering for VPCs requiring low-latency, high-bandwidth communication within the same region.
- B
Use VPC peering between VPCs across regions for all communication needs.
- C
Use a transit gateway for centralized communication to the shared service VPC.
- D
Use a transit gateway for all communication, including low-latency, high-bandwidth scenarios.
- E
Use AWS Direct Connect to connect all VPCs together.
Show answer and explanation
Correct answers: A, C
Explanation
The combination of VPC peering and a transit gateway provides the best solution for the scenario. VPC peering is ideal for low-latency, high-bandwidth communication between VPCs within the same region, while a transit gateway simplifies and scales centralized communication with a shared service VPC. Using both ensures efficient and scalable networking while minimizing management overhead.
- A. Correct.
This is correct because VPC peering is a cost-effective and efficient solution for low-latency, high-bandwidth communication between VPCs in the same region. It provides direct connectivity without the need for a transit gateway.
- B. Incorrect.
This is incorrect because VPC peering is not as scalable and can become challenging to manage when connecting multiple VPCs across regions. Additionally, it lacks centralized routing capabilities.
- C. Correct.
This is correct because a transit gateway simplifies connectivity to a shared service VPC by providing a central hub for routing traffic. It scales well as new VPCs are added.
- D. Incorrect.
This is incorrect because while a transit gateway is scalable, it introduces additional latency and cost, making it less suitable for low-latency, high-bandwidth scenarios that are better handled with VPC peering.
- E. Incorrect.
This is incorrect because AWS Direct Connect is used for connecting on-premises environments to AWS, not for interconnecting VPCs within or across regions.