Google Professional Cloud Network Engineer Question 234
Select 3Google Cloud PlatformYour team manages a Google Cloud Virtual Private Cloud (VPC) with a subnet in the us-central1 region. The subnet was initially created with a CIDR range of 10.0.0.0/24. Due to increased demand, you need to expand the range to accommodate more IP addresses. What steps must you follow to achieve this successfully while ensuring minimal disruption?
- A
Update the subnet's CIDR range to a larger range, such as 10.0.0.0/16, using the Google Cloud Console or gcloud CLI.
- B
Verify that no overlapping IP ranges exist in the VPC or with any peered networks before expanding the subnet range.
- C
Delete and recreate the subnet with the desired CIDR range.
- D
Ensure that any firewall rules, routes, and IAM policies referencing the subnet are updated after the range is expanded.
- E
Confirm that the expanded IP address range does not conflict with any existing on-premises IP ranges in a hybrid setup.
Show answer and explanation
Correct answers: A, B, E
Explanation
To expand a VPC subnet range, you need to use the Google Cloud Console or gcloud CLI to update the CIDR range. Before doing so, you must verify that the expanded range does not overlap with existing ranges in the VPC, peered networks, or on-premises networks, as this could cause routing issues. Deleting and recreating the subnet is unnecessary, and existing configurations like firewall rules and routes automatically adapt to the expanded CIDR range.
- A. Correct.
Correct. Expanding the CIDR range can be done directly via the Google Cloud Console or the gcloud CLI. Deleting the subnet is not required.
- B. Correct.
Correct. Overlapping CIDR ranges with other VPCs or peered networks can cause connectivity issues, so this must be checked before expanding.
- C. Incorrect.
Incorrect. Deleting and recreating the subnet is unnecessary and would likely cause service disruption. Subnet CIDR ranges can be expanded without deletion.
- D. Incorrect.
Incorrect. Firewall rules, routes, and IAM policies referencing the subnet do not need to be updated after expanding the range. These configurations are automatically applied to the expanded range.
- E. Correct.
Correct. If the expanded range overlaps with existing on-premises IP ranges in a hybrid setup, routing conflicts can occur, so this must be confirmed.