Google Professional Cloud Network Engineer Question 230
Select 3Google Cloud PlatformYou are managing a Virtual Private Cloud (VPC) in Google Cloud and need to expand the range of an existing subnet to accommodate additional IP addresses. Which of the following steps and considerations are correct when expanding the subnet range?
- A
The new subnet IP range must remain within the same CIDR block as the original VPC range.
- B
You can expand the IP range of a subnet to overlap with another existing subnet in the same VPC.
- C
Expanding the subnet range does not cause any downtime for existing resources in the subnet.
- D
The new IP range must not overlap with any existing routes or peered VPC networks.
- E
You can only expand a subnet range if it was created as a custom mode VPC.
Show answer and explanation
Correct answers: A, C, D
Explanation
When expanding a VPC subnet range, it is essential to ensure the new range is within the VPC's CIDR block, does not overlap with other subnets or routes, and adheres to network peering constraints. Expanding a subnet range is non-disruptive to existing resources, and this operation is supported in both custom and auto mode VPCs.
- A. Correct.
Correct: The new subnet IP range must remain within the overall CIDR block of the VPC. This is a fundamental constraint for subnet expansion in Google Cloud.
- B. Incorrect.
Incorrect: Subnet ranges cannot overlap with other subnets in the same VPC. Overlapping ranges would cause routing conflicts.
- C. Correct.
Correct: Expanding the subnet range does not impact currently running resources or services in the subnet, so no downtime occurs.
- D. Correct.
Correct: The new IP range must not conflict with existing routes or IP ranges in peered VPCs to ensure proper routing and network connectivity.
- E. Incorrect.
Incorrect: Subnet ranges can be expanded in both auto mode and custom mode VPCs, provided the other criteria are met.