An enterprise architecture team is configuring a custom-mode Virtual Private Cloud (VPC) network connected to two on-premises data centers via Cloud VPN.
The current network IP address allocations are:
- Data Center A on-premises range:
- Data Center B on-premises range:
- Existing GCP subnet primary range in `europe-west1`:
To accommodate growing compute requirements without creating a new subnet, you must expand the primary IP address range of the `europe-west1` subnet to double its host address capacity. The expanded range must encompass the existing subnet without causing IP address overlap with either on-premises data center.
Which CIDR block must you specify for the expanded primary subnet range?
- Answer
- B
- C
- D
Answer
The correct subnet expansion CIDR is .
In Google Cloud VPC subnet design, expanding a primary IP range requires reducing the netmask prefix length (e.g., from to ) while ensuring the new block completely contains the existing range. The range encompasses all IPs from through , covering the original block () without colliding with Data Center A () or Data Center B ().
Step-by-Step Solution
Key Concept
VPC Subnet CIDR Range Expansion Rules and Hybrid Non-Overlap Requirements
Estimated Time:2m 0s