A cloud engineer is preparing to integrate a Google Cloud environment with an on-premises network via Cloud VPN. The current GCP deployment uses an auto-mode Virtual Private Cloud (VPC) network. To prevent future IP CIDR collisions with on-premises subnets and gain control over subnet creation, the engineer must convert the auto-mode VPC to a custom-mode VPC and provision a new subnet in a new region. What is the correct sequence of steps to execute this migration safely?
- 1Audit the existing on-premises IP address space and verify that currently deployed auto-mode subnets do not conflict with remote routes.
- 2Switch the VPC network mode from auto to custom using the gcloud command-line tool or Google Cloud Console.
- 3Plan and define a unique primary CIDR block for the target expansion region that does not overlap with any existing GCP or on-premises subnets.
- 4Create the new custom subnet in the target region within the converted VPC network using the allocated non-overlapping CIDR block.
Cevap
The correct sequence begins with auditing existing network IP space for conflicts, followed by converting the VPC network from auto to custom mode, then planning a unique non-overlapping CIDR block for the target region, and finally creating the new custom subnet.
To safely transition a GCP VPC for hybrid connectivity, an engineer must first audit existing IP allocations against on-premises routes to identify potential conflicts. Next, the VPC network mode must be converted from auto to custom mode, which retains existing subnets while granting administrative control over future subnet creation. After conversion, the engineer plans a distinct, non-overlapping CIDR block for the new region, and finally provisions the new custom subnet using that range.
Adım Adım Çözüm
Anahtar Kavram
Converting Auto-Mode VPC to Custom-Mode VPC for Hybrid Network Planning