Your company has many VPCs, one for Development, one for Staging, one for Production and one for Management VPC. It is required for traffic to flow from the other VPCs to the Management VPCs. The VPCs should also be traversable via the on-premises infrastructure. How would you architect the solution with the least amount of effort?

Answer options:

A.Create a VPC peering connection between the VPCs. Create an AWS VPN connection between the Management VPC and the on-premises environment.
B.Create a VPC peering connection between the Management and the other VPCs. Create an AWS VPN connection between all the VPCs and the on-premises environment.
C.Create a Virtual Private gateway connection between all of the VPCs. Create an AWS VPN connection between the Management VPC and the on-premises environment.
D.Create an AWS VPN connection between the Management VPC and all other VPCs. Create an AWS VPN connection between the Management VPC and the on-premises environment.

Answer – B
This is an example of a shared services VPC. The below snippet from the AWS Documentation shows the architecture around this.
Option A is incorrect because the on-premises resources cannot traverse the other VPCs via the Peering connection.
Option C is incorrect because of the incorrect use of the Virtual Private gateway.
Option D is incorrect because of the overall maintenance for the activities being performed.
For more information on VPC and VPN connection sharing, please refer to the below URL
https://aws.amazon.com/answers/networking/aws-multiple-vpc-vpn-connection-sharing/