An organization needs to expand an existing subnet within a custom-mode Virtual Private Cloud (VPC) network in Google Cloud to accommodate new virtual machines. The target subnet currently uses the primary IP CIDR block . The VPC network is connected via VPC Network Peering to a partner network using the CIDR block ( to ). Which extended CIDR range can be configured to expand the existing subnet without causing an IP address collision or violating GCP subnet expansion rules?
- 10.50.4.0/23Cevap
- B10.50.0.0/20
- C10.50.4.0/25
- D10.50.5.0/23
Cevap
10.50.4.0/23 is the valid expansion range because it encompasses the current range, adheres to CIDR alignment rules, and avoids overlapping with the peered network.
Expanding a primary subnet range in Google Cloud VPC requires choosing a larger prefix block (smaller prefix length) that encloses the original block and aligns with standard netmask boundaries without overlapping any peered VPC ranges. Expanding from 10.50.4.0/24 to 10.50.4.0/23 provides IPs 10.50.4.0 through 10.50.5.255, satisfying all expansion and non-overlap rules.
Adım Adım Çözüm
Anahtar Kavram
Subnet IP Range Expansion in Google Cloud VPC
Tahmini Süre:1m 30s