A cloud architect is planning to expand an existing primary subnet CIDR range in a custom-mode Virtual Private Cloud (VPC) that is connected to an on-premises data center via Cloud VPN. To ensure uninterrupted connectivity and prevent IP routing conflicts across the hybrid environment, in what sequence should these steps be executed?
- 1Audit existing on-premises IP subnets and active GCP network ranges to identify available contiguous CIDR blocks.
- 2Select an expanded primary subnet CIDR block (e.g., expanding from /24 to /22) that completely contains the original range and avoids on-premises routes.
- 3Execute the subnet IP range expansion operation to update the primary IP address range of the subnet.
- 4Update Cloud Router BGP advertisements or on-premises static routes to propagate the expanded subnet prefix across the VPN.
Cevap
The correct order of steps is: 1) Audit existing on-premises IP subnets and active GCP network ranges to identify available contiguous CIDR blocks. 2) Select an expanded primary subnet CIDR block (e.g., expanding from /24 to /22) that completely contains the original range and avoids on-premises routes. 3) Execute the subnet IP range expansion operation to update the primary IP address range of the subnet. 4) Update Cloud Router BGP advertisements or on-premises static routes to propagate the expanded subnet prefix across the VPN.
The correct sequence follows a logical lifecycle for hybrid cloud networking: first audit existing address space to prevent overlaps, next select a valid expanded CIDR block that encompasses the original range, then perform the actual subnet expansion in GCP, and finally update hybrid BGP or static routes so the on-premises network can reach the newly expanded address range.
Adım Adım Çözüm
Anahtar Kavram
Planning and expanding GCP VPC subnets in a hybrid environment requires verifying CIDR non-overlap, adhering to GCP expansion rules (must encompass original range), applying the expansion, and updating hybrid BGP/static routing.
Tahmini Süre:1m 30s