Google Professional Cloud Network Engineer Question 231
Select 3Google Cloud PlatformYour organization uses a private Google Cloud VPC network with a subnet that has a CIDR range of 10.0.0.0/24. Due to increased demand, you need to expand the subnet range to accommodate more IP addresses. What steps must you take to successfully expand the subnet's CIDR range?
- A
Update the subnet's CIDR range in the Google Cloud Console or gcloud CLI to a larger prefix, such as 10.0.0.0/22.
- B
Ensure no IP addresses in the new range overlap with other subnets in the VPC.
- C
Delete and recreate the subnet with the new CIDR range.
- D
Verify that the expanded range does not overlap with any connected on-premises networks or peered VPCs.
- E
Expand the subnet range only during a maintenance window because doing so will cause downtime for existing resources.
Show answer and explanation
Correct answers: A, B, D
Explanation
To expand a VPC subnet range, you must ensure the new CIDR range does not overlap with existing subnets, connected on-premises networks, or peered VPCs. The expansion can be performed directly using the Google Cloud Console or gcloud CLI without causing downtime for existing resources. Deleting and recreating the subnet is unnecessary, as Google Cloud supports live subnet range expansion.
- A. Correct.
This is correct. Subnet CIDR ranges can be expanded using the Google Cloud Console or gcloud CLI by specifying a larger range. For example, increasing from /24 to /22 allows for more IP addresses.
- B. Correct.
This is correct. Ensuring no overlap with other subnets in the VPC is essential to maintain network integrity and avoid IP conflicts.
- C. Incorrect.
This is incorrect. Subnets in Google Cloud can be expanded without needing to delete and recreate them, provided the new range is valid and non-overlapping.
- D. Correct.
This is correct. It’s important to verify that the expanded range does not conflict with IP ranges in connected on-premises networks or peered VPCs to prevent routing issues.
- E. Incorrect.
This is incorrect. Expanding a subnet range does not cause downtime for existing resources. It is a live operation in Google Cloud.