Examkin

Soru

Zorluk: Çok zorPlanning Virtual Private Cloud (VPC) Networks and Subnets

A cloud engineering team is planning to expand the primary IP address range of an active custom-mode Virtual Private Cloud (VPC) subnet connected to an on-premises data center via Cloud Router using BGP. What is the correct sequence of steps the team must perform to safely plan, execute, and propagate this subnet expansion?

  1. 1Audit contiguous IP space across both the GCP VPC and connected on-premises networks to verify the prospective expanded block is unallocated.
  2. 2Verify that the planned CIDR modification decreases the netmask prefix length (e.g., from /24/24 to /22/22) without changing the network start address.
  3. 3Run the subnet expansion operation in Google Cloud to update the primary IP range of the subnet.
  4. 4Update the Cloud Router custom route advertisement configuration to broadcast the newly expanded CIDR block to on-premises BGP peers.

Cevap

The correct procedural order begins with auditing contiguous IP space across hybrid networks to prevent IP collisions, validating GCP subnet expansion constraints (prefix length reduction only without shifting base IP), performing the subnet expansion in GCP, and finally updating Cloud Router BGP custom route advertisements to inform on-premises networks.
The sequence follows the required architectural workflow: auditing hybrid IP space first to prevent overlap, verifying GCP netmask expansion rules, modifying the VPC subnet resource, and updating BGP routing advertisements on Cloud Router to complete hybrid connectivity.

Adım Adım Çözüm

1
Audit contiguous IP address space across all interconnected environments.
Ensures the expanded block does not overlap with existing subnets, GKE secondary ranges, or on-premises CIDR ranges.
GCP VPC subnets require contiguous unallocated space to expand. Overlapping IP space causes routing failures and IP collisions.
2
Validate the proposed CIDR change against GCP VPC expansion rules.
Confirms the target prefix length is smaller than the current prefix length (e.g., /23/23 expanded to /21/21).
GCP subnets cannot be shrunk, and the network starting address cannot be changed during an expansion.
3
Execute the primary subnet range expansion in GCP.
Modifies the subnet's netmask in the GCP control plane without downtime for existing instances.
Applies the configuration change to the target subnet resource in Google Cloud.
4
Update Cloud Router custom route advertisements.
On-premises BGP routers receive updated prefix announcements covering the newly added IP addresses.
Ensures full bi-directional reachability between on-premises hosts and newly provisioned workloads in the expanded IP range.

Anahtar Kavram

Planning and executing non-disruptive primary subnet CIDR expansions in hybrid VPC topologies
Bu soruyu puanla

Konular

Planning Virtual Private Cloud (VPC) Networks and Subnets

Bu konudan daha fazla soru