Question

Which statements regarding VPC Peering are accurate? Select TWO.

A) Two VPCs in different AWS Regions and under separate AWS Accounts can share traffic between each other.
B) In order for VPC Peering to work, each VPC should have a public subnet.
C) In VPC Peering, it is possible for traffic from one VPC to traverse through a transit VPC in order to reach a third VPC.
D) Traffic between VPC peers in different AWS Regions is not encrypted by default.
E) VPC Peering can be used to replicate data to geographically distinct locations for fault-tolerance, disaster recovery, and redundancy.

Answer 1

D) Traffic between VPC peers in different AWS Regions is not encrypted by default.The two accurate statements regarding VPC Peering are that VPCs in different AWS Regions and accounts can share traffic,

Step-by-step explanation:

Among the statements provided regarding VPC Peering, two are accurate:

• A) Two VPCs in different AWS Regions and under separate AWS Accounts can share traffic between each other. This is true because VPC Peering supports inter-region (cross-region) VPC Peering connections, allowing VPCs to communicate with each other across different regions and AWS accounts.
• E) VPC Peering can be used to replicate data to geographically distinct locations for fault-tolerance, disaster recovery, and redundancy. Replicating data across peered VPCs in different regions can be part of a comprehensive disaster recovery plan, leveraging the infrastructure's redundancy for increased fault tolerance.

Options B and C are incorrect. VPC Peering does not require public subnets; it can connect private subnets in different VPCs. Additionally, VPC Peering is a one-to-one networking connection between two VPCs and does not support transitive peering, so one VPC cannot act as a transit hub for others (Option C).

Lastly, Option D is inaccurate because AWS encrypts all traffic between VPCs when using VPC Peering, regardless of the regions involved.