ANS-C01 Question 397
Single answerYour organization has three VPCs in the same AWS Region: VPC-A, VPC-B, and VPC-C. VPC-A needs to communicate with VPC-B and VPC-C. The communication is bidirectional and high-volume. VPC-B and VPC-C do not need to communicate with each other. Which architecture is the most cost-effective and operationally efficient for this scenario?
- A
Set up individual VPC peering connections between VPC-A and VPC-B, and between VPC-A and VPC-C.
- B
Use a Transit Gateway to connect all three VPCs.
- C
Establish a Transit Gateway and create separate route tables to isolate communication between VPC-B and VPC-C.
- D
Create a shared VPC and migrate all workloads from VPC-B and VPC-C into VPC-A.
Show answer and explanation
Correct answer: A
Explanation
VPC peering is ideal for scenarios where a few VPCs need direct, low-latency, and high-throughput communication. Since the connectivity requirements are limited to VPC-A communicating with VPC-B and VPC-C, and there is no need for VPC-B and VPC-C to communicate with each other, VPC peering is the most cost-effective and efficient solution. A Transit Gateway would be better suited for more complex scenarios involving many-to-many connectivity or dynamic routing requirements.
- A. Correct.
This is the correct answer. VPC peering is cost-effective and operationally efficient because only VPC-A needs to communicate with VPC-B and VPC-C. There is no need for a Transit Gateway since VPC-B and VPC-C do not require connectivity to each other.
- B. Incorrect.
This is incorrect. While a Transit Gateway could connect all three VPCs, it introduces higher costs and complexity, which is unnecessary since VPC-B and VPC-C do not need to communicate with each other.
- C. Incorrect.
This is incorrect. Isolating traffic using route tables with a Transit Gateway is not required because VPC-B and VPC-C don't need to communicate. A simpler peering solution is sufficient.
- D. Incorrect.
This is incorrect. Migrating workloads into a shared VPC would introduce significant operational overhead and potential downtime, which is not necessary to resolve the connectivity requirements in this scenario.