Answer-first summary for fast verification
Answer: Configure VPC peering in a full mesh.
VPC peering in Google Cloud does not support transitive peering, meaning that if VPC A is peered with VPC B, and VPC B is peered with VPC C, VPC A cannot communicate with VPC C through VPC B. To enable full connectivity between the Sales, Marketing, and Finance VPCs, a full mesh peering configuration is required. This means each VPC must be directly peered with every other VPC. In this scenario, since Sales is peered with Finance and Marketing is peered with Finance, but Sales is not peered with Marketing, users cannot connect between Sales and Marketing. Configuring a full mesh peering (option A) would resolve this issue by establishing direct peering between Sales and Marketing, ensuring all VPCs can communicate with each other. Options B, C, and D do not address the root cause of the connectivity issue, which is the lack of direct peering between Sales and Marketing.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
To enable full network connectivity between the Sales, Marketing, and Finance VPCs where users can access resources across all three, you have configured VPC peering between Sales-Finance and Marketing-Finance. However, some users cannot connect to resources in the Sales and Marketing VPCs.
What steps should you take to resolve this connectivity issue?
A
Configure VPC peering in a full mesh.
B
Alter the routing table to resolve the asymmetric route.
C
Create network tags to allow connectivity between all three VPCs.
D
Delete the legacy network and recreate it to allow transitive peering.