Question

Difficulty: MediumPlanning Virtual Private Cloud (VPC) Networks and Subnets

A cloud infrastructure engineer is designing a Google Cloud Virtual Private Cloud (VPC) network for a workload deployed across 22 specific regions: `us-central1` and `europe-west1`. Corporate policy mandates full control over IP address range allocations to prevent collisions with existing corporate networks, and strictly prohibits provisioning subnets in any unused regions. Which VPC creation method and configuration should the engineer implement?

  1. Create a custom-mode VPC network and manually define subnets only in `us-central1` and `europe-west1` with non-overlapping CIDR ranges.Answer
  2. B
    Create an auto-mode VPC network and select `us-central1` and `europe-west1` as the designated subnet regions during creation.
  3. C
    Create an auto-mode VPC network and delete the automatically generated subnets in all regions except `us-central1` and `europe-west1`.
  4. D
    Create a custom-mode VPC network with the automatic subnet allocation flag enabled specifically for `us-central1` and `europe-west1`.

Answer

Create a custom-mode VPC network and manually define subnets only in `us-central1` and `europe-west1` with non-overlapping CIDR ranges.
Creating a custom-mode VPC network allows full architectural control because no subnets are created automatically. The network engineer can manually define subnets only in the required regions (`us-central1` and `europe-west1`) and assign specific, non-overlapping IP address ranges that conform to corporate IP governance policies.

Step-by-Step Solution

1
Evaluate the requirements for subnet provisioning and IP address control.
The requirement specifies provisioning subnets in only two regions while preventing IP range collisions with existing corporate networks.
Enterprise hybrid environments require strict IP management to avoid routing issues and IP address overlaps.
2
Compare Google Cloud VPC network modes (Auto-mode vs. Custom-mode).
Auto-mode automatically creates a subnet in every GCP region using predefined set ranges (10.128.0.0/910.128.0.0/9). Custom-mode creates zero subnets upon creation, giving full manual control over subnet regions and CIDR blocks.
Auto-mode violates the constraint against provisioning subnets in unused regions and risks IP overlap with corporate networks.
3
Select the correct VPC deployment pattern.
Custom-mode VPC network creation allows manual specification of subnets exclusively in `us-central1` and `europe-west1`.
This fulfills all security and enterprise IP governance requirements.

Key Concept

Custom-mode vs. Auto-mode VPC Network Planning
Rate this question