A company has an AWS account that contains three VPCs (Dev, Test, and Prod) in the same region. There is a requirement to ensure that instances in the Development and Test VPC`s can access resources in the Production VPC. There should be minimal efforts with minimal administrative overhead. Which of the following would be the ideal way to get this in place?

Answer options:

A.Create an AWS Direct Connect connection between the Development, Test VPC to the Production VPC.B.Create a separate VPC peering connection from Development to Production and from Test to the Production VPC.C.Create a VPN connection between the Development, Test VPC to the Production VPC.D.Create a VPC peering connection between the Development to the Production VPC and from Development to the Test VPC.

Answer – B
Options A and C are incorrect since these options will NOT involve minimal efforts or minimal overhead. Hence you need to choose VPC peering.
Options D is incorrect since the VPC Peering configuration mentioned would be invalid. We need access from Production to Test and NOT from "Development to Test" as given in the option
You need VPC Peering Configuration between Dev to Prod and Test to Prod.
"A VPC peering connection is a networking connection between two VPCs that enable you to route traffic between them using private IPv4 addresses or IPv6 addresses. Instances in either VPC can communicate with each other as if they are within the same network. You can create a VPC peering connection between your own VPCs, or with a VPC in another AWS account. The VPCs can be in different regions (also known as an inter-region VPC peering connection)."
For more information on VPC peering, please visit the URL-
https://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/Welcome.html