Which two security characteristics are related to the use of VPC peering to connect two VPC networks? (Choose two.)

Question

Options

• ACentral management of routes, firewalls, and VPNs for peered networks
• BNon-transitive peered networks; where only directly peered networks can communicate
• CAbility to peer networks that belong to different Google Cloud Platform organizations
• DFirewall rules that can be created with a tag from one peered network to another peered network
• EAbility to share specific subnets across peered networks

• A
  2% (1)
• B
  87% (54)
• D
  8% (5)
• E
  3% (2)

Explanation

VPC peering has two key security-relevant characteristics addressed here: (B) VPC peering is non-transitive - if VPC A peers with VPC B and VPC B peers with VPC C, A and C cannot communicate through B; only directly peered networks can exchange traffic. (C) VPC peering supports cross-organization peering, meaning two VPCs from completely separate GCP organizations can be peered. Option A is incorrect - each peered VPC independently manages its own routes, firewalls, and VPNs; there is no centralized management. Option D is incorrect - firewall rules in one VPC cannot reference network tags from a peered VPC. Option E is incorrect - VPC peering peers entire VPCs, not specific subnets; subnet-level sharing is the domain of Shared VPC.

No community discussion yet for this question.