Question

Difficulty: EasyConfiguring Network Topology and VPC Infrastructure

An organization needs to establish direct, low-latency private IP connectivity between two VPC networks (vpc-a and vpc-b) in Google Cloud without traversing the public internet or deploying hybrid VPN gateways. Which GCP networking configuration should be implemented to enable internal communication between resources in both VPCs?

  1. Establish a VPC Network Peering connection directly between vpc-a and vpc-b.Answer
  2. B
    Peer vpc-a and vpc-b to a central transit VPC network to rely on transitive routing between them.
  3. C
    Deploy a Dedicated Interconnect connection between vpc-a and vpc-b.
  4. D
    Create a VPC Service Controls perimeter encompassing both VPC networks to automatically enable inter-VPC IP routing.

Answer

Establish a VPC Network Peering connection directly between vpc-a and vpc-b.
Establishing a direct VPC Network Peering connection enables private RFC 1918 network connectivity between both VPC networks over Google's internal network backbone without public IP routing or VPN infrastructure.

Step-by-Step Solution

1
Identify the primary networking requirement
The requirement calls for direct, private RFC 1918 communication between two Google Cloud VPC networks without public internet routing or VPN overhead.
Google Cloud VPC Network Peering allows private IP address connectivity across distinct VPC networks using Google's internal network infrastructure.
2
Evaluate inter-VPC connectivity features
Direct VPC Network Peering provides full internal IP reachability with low latency and high bandwidth.
Direct VPC Peering is the simplest and most efficient mechanism for linking two separate VPC networks within Google Cloud.

Key Concept

VPC Network Peering capabilities and non-transitive routing behavior
Rate this question