VPC peering connections allow instances in one VPC to communicate with instances in another VPC. Peering is a one-to-one relationship between two VPCs.
Transit Routing Limitation:
AWS VPC peering connections do not support transitive peering. This means that a packet originating in VPC B cannot be routed through VPC A to reach VPC C. Each pair of VPCs must have its own peering connection.
Routing Table Configuration:
Even if you add a route in the VPC A routing table for the 192.168.0.0/16 network, it won't allow VPC B to communicate with VPC C because of the non-transitive nature of VPC peering.
Comparison with Other Options:
Option A is incorrect because adding a route in VPC A does not overcome the limitation of non-transitive peering.
Option C is incorrect because associating pcx-23232323 with VPC B is not how VPC peering works.
Option D is incorrect because you can create a separate peering connection between VPC B and VPC C, which is the required approach for communication between these VPCs.
References:
AWS VPC Peering Guide:VPC Peering
Limitations of VPC Peering:AWS VPC Peering Limitations
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit