Examkin

Soru

Zorluk: ZorPlanning Virtual Private Cloud (VPC) Networks and Subnets

A cloud network architect is planning a Virtual Private Cloud (VPC) network in Google Cloud to support a hybrid enterprise environment connected to an on-premises data center via Cloud VPN. The on-premises network uses the 10.128.0.0/910.128.0.0/9 CIDR range for internal services. The planned GCP footprint requires a primary subnet in region `us-central1` starting at 10.200.8.0/2410.200.8.0/24 and another primary subnet in region `us-east1` allocated at 10.200.16.0/2410.200.16.0/24.

Which TWO subnet planning and design requirements must be applied to ensure seamless hybrid connectivity and prevent IP address collisions? (Select TWO.)

  1. Provision the VPC network in custom mode because auto-mode VPC networks automatically allocate subnets within the 10.128.0.0/910.128.0.0/9 range, which creates an IP address space collision with the on-premises network.Cevap
  2. B
    Provision the VPC network in auto mode to streamline cross-region route propagation, and modify the automatically generated subnet CIDRs after creation.
  3. Ensure that any future expansion of the 10.200.8.0/2410.200.8.0/24 primary subnet CIDR block retains the same start IP address or aligns with contiguous CIDR boundaries while avoiding overlap with 10.200.16.0/2410.200.16.0/24 or on-premises networks.Cevap
  4. D
    Expand the primary subnet in `us-central1` to 10.200.0.0/1610.200.0.0/16 when additional IP capacity is required, allowing Google Cloud to automatically merge the 10.200.16.0/2410.200.16.0/24 subnet into the newly expanded range.

Cevap

The network architect must provision the VPC network in custom mode to prevent auto-mode's default 10.128.0.0/910.128.0.0/9 subnets from colliding with the on-premises range, and ensure any future subnet expansions follow contiguous CIDR boundary rules without overlapping existing regional subnets or hybrid network ranges.
Provisioning the VPC in custom mode is essential because auto-mode automatically creates subnets in the 10.128.0.0/910.128.0.0/9 range, which directly collides with the on-premises network range over Cloud VPN. Additionally, expanding a primary subnet's IP range requires adhering to contiguous CIDR boundary rules while ensuring the expanded block does not overlap with existing subnets such as the one in 10.200.16.0/2410.200.16.0/24 or on-premises spaces.

Adım Adım Çözüm

1
Analyze the on-premises IP allocation versus GCP VPC creation modes.
Auto-mode VPCs create subnets in 10.128.0.0/910.128.0.0/9 in every GCP region by default. Since on-premises uses 10.128.0.0/910.128.0.0/9, auto-mode causes immediate CIDR overlap. Custom-mode VPC is mandatory.
Custom-mode VPC networks give architects complete control over subnet IP range selection, avoiding collisions across hybrid VPN tunnels.
2
Evaluate subnet expansion constraints in Google Cloud VPCs.
Subnet primary CIDRs can only be expanded (netmask length decreased), never shrunk. The new expanded block must be contiguous and must not overlap with any other subnet in the VPC or connected routes.
Expanding 10.200.8.0/2410.200.8.0/24 to a contiguous boundary like 10.200.8.0/2310.200.8.0/23 (10.200.8.010.200.8.0 - 10.200.9.25510.200.9.255) is valid and avoids 10.200.16.0/2410.200.16.0/24.
3
Verify distractor invalidity.
Auto-mode cannot be reconfigured to solve overlapping default IP spaces cleanly, and GCP VPCs do not support automatic merging of overlapping subnets.
Any CIDR overlap proposal triggers an API failure during subnet modification.

Anahtar Kavram

VPC Network Modes and Subnet Expansion Rules in GCP
Bu soruyu puanla

Konular

Planning Virtual Private Cloud (VPC) Networks and Subnets

Bu konudan daha fazla soru