The networking team has created a VPC in an AWS account. The application team has asked for access to resources in another VPC in the same AWS account. The SysOps Administrator has created the VPC peering connection between both the accounts, but the resources in one VPC cannot communicate with the resources in the other VPC. What could be causing this issue?

by totorovn at Feb. 21, 2025, 3:31 am

A. One of the VPCs is not sized correctly for peering.
B. There is no public subnet in one of the VPCs.
C. The route tables have not been updated.
D. One VPC has disabled the peering flag.

- Awsexamhub website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Join the Discussion

You must be logged in to post a comment.

Suggested Answer:

Share this post

Join the Discussion