You need to establish network connectivity between three Virtual Private Cloud networks, Sales, Marketing, and Finance, so that users can access resources in all three VPCs.
You configure VPC peering between the Sales VPC and the Finance VPC.
You also configure VPC peering between the Marketing VPC and the Finance VPC.
After you complete the configuration, some users cannot connect to resources in the Sales VPC and the Marketing VPC.
You want to resolve the problem.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
In this scenario, the goal is to establish network connectivity between three Virtual Private Cloud networks (VPCs) - Sales, Marketing, and Finance - so that users can access resources in all three VPCs. The first step taken was to configure VPC peering between the Sales VPC and the Finance VPC, and also between the Marketing VPC and the Finance VPC. However, after completing the configuration, some users are unable to connect to resources in the Sales VPC and the Marketing VPC.
To resolve this issue, there are a few potential solutions:
A. Configure VPC peering in a full mesh: In a full mesh topology, each VPC is peered with every other VPC. This approach ensures that all VPCs can communicate with each other, regardless of the specific peering relationship. However, this can be complex to manage and may not scale well as the number of VPCs increases.
B. Alter the routing table to resolve the asymmetric route: When VPC peering is established between two VPCs, the routing tables in each VPC are updated to include the CIDR block of the other VPC. However, if the routing tables are not updated properly or there is an asymmetric route, it can result in connectivity issues. To resolve this, the routing table may need to be altered to ensure proper routing between the VPCs.
C. Create network tags to allow connectivity between all three VPCs: Network tags can be used to identify resources that need to communicate with each other, regardless of their location in the VPC. By tagging resources in all three VPCs with a common tag, they can be allowed to communicate with each other. However, this approach may not provide granular control over which resources can communicate with each other.
D. Delete the legacy network and recreate it to allow transitive peering: Transitive peering allows for communication between VPCs that are not directly peered with each other. However, this feature is not supported by all cloud providers, and may not be the most efficient solution.
Overall, the best solution will depend on the specific requirements of the organization and the resources available. However, altering the routing table to resolve any asymmetric routes is often the first step in troubleshooting VPC peering connectivity issues.