The Networking Team Has Created a VPC in an AWS

Multiple Choice

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?

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.