VPC Peering Connection
Question
Your company has a set of VPC's.
There is now a requirement to establish communication across the Instances in the VPC's.
Your supervisor has asked you to implement the VPC peering connection.
Which of the following considerations would you keep in mind for VPC peering? Choose 2 answers from the options below.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Sure, I'd be happy to help!
VPC peering is a feature that allows you to connect two VPCs together so that instances in one VPC can communicate directly with instances in the other VPC. This can be useful in a variety of situations, such as when you want to set up a hub-and-spoke network topology or when you want to share resources between VPCs.
Now let's take a look at the considerations for VPC peering:
A. Ensuring that the VPCs don't have overlapping CIDR blocks: This is a very important consideration for VPC peering. CIDR (Classless Inter-Domain Routing) blocks are used to assign IP addresses to resources in your VPC. If the CIDR blocks of the two VPCs overlap, it can cause IP address conflicts and prevent the VPC peering from functioning correctly. Therefore, it's important to ensure that the CIDR blocks of the VPCs don't overlap before creating a VPC peering connection.
B. The transitive peering is not supported: This is another important consideration for VPC peering. Transitive peering is a scenario where VPC A is peered with VPC B and VPC B is peered with VPC C, but VPC A is not directly peered with VPC C. In other words, VPC peering does not support transitive relationships. If you need to connect multiple VPCs, you'll need to create a separate VPC peering connection between each pair of VPCs that need to communicate.
C. Ensuring that the VPCs only have public subnets for communication: This is not a requirement for VPC peering. VPC peering allows communication between instances in private subnets as well as public subnets. However, it's important to note that communication between private subnets across VPC peering connections requires additional configuration, such as setting up route tables and network address translation (NAT).
D. Ensuring that the VPCs are created in the same region: This is a requirement for VPC peering. VPC peering connections can only be created between VPCs in the same region. If you need to connect VPCs in different regions, you'll need to use a different solution, such as VPN or AWS Direct Connect.
So, the correct answers for this question are A and B. You need to ensure that the VPCs don't have overlapping CIDR blocks and that transitive peering is not supported.
