A cloud engineer needs to expand the primary IPv4 CIDR range of an existing custom-mode Virtual Private Cloud (VPC) subnet in Google Cloud to accommodate new virtual machines without causing service disruption. What is the correct sequence of steps to plan and execute this subnet expansion?
- 1Inspect the existing subnet IP range and verify that the contiguous adjacent IP space does not overlap with existing subnets, custom routes, or connected networks.
- 2Select a broader subnet prefix length (such as expanding from /24 to /23) that contains the starting IP address of the current primary range.
- 3Run the `gcloud compute networks subnets expand-ip-range` command, passing the `--prefix-length` parameter with the targeted netmask value.
- 4Validate the expanded subnet configuration by describing the subnet resource to ensure the new primary IPv4 range is active.
Cevap
The correct sequence for expanding a custom-mode VPC primary subnet range is: 1) Verify that adjacent contiguous IP space is free of conflicts, 2) Select a broader prefix length encompassing the original base IP address, 3) Execute `gcloud compute networks subnets expand-ip-range` with the desired prefix length, and 4) Verify the expanded primary range in the subnet resource configuration.
Proper planning and execution of a GCP custom-mode VPC subnet primary range expansion requires checking for non-overlapping contiguous IP space, calculating a valid expanded prefix length, executing `gcloud compute networks subnets expand-ip-range`, and verifying the updated subnet status.
Adım Adım Çözüm
Anahtar Kavram
VPC Subnet Primary Range Expansion Procedure