A cloud solutions architect is planning a hybrid network topology for an enterprise migrating workloads to Google Cloud. The existing on-premises data center uses the RFC 1918 private IPv4 block for internal corporate services and will connect to Google Cloud via Cloud Interconnect. The cloud infrastructure requires Compute Engine instances deployed across multiple regions with dynamic routing enabled. The architect must ensure that network traffic routes seamlessly between on-premises systems and Google Cloud resources without IP routing collisions or overlap. Which network configuration strategy should the architect implement?
- Create a custom-mode Virtual Private Cloud (VPC) network and manually define subnets using non-overlapping IP address ranges such as in us-central1 and in europe-west1.Cevap
- BCreate an auto-mode VPC network to automatically provision subnets across all Google Cloud regions using default predefined IP ranges.
- CCreate a custom-mode VPC network and assign subnets using in us-central1 and in europe-west1 to maintain IP convention consistency with on-premises networks.
- DDeploy an auto-mode VPC network and subsequently convert it to a custom-mode VPC network while retaining the existing auto-created subnet ranges.
Cevap
The architect should create a custom-mode VPC network and manually define subnets using non-overlapping IP address ranges (such as and ) that do not conflict with the on-premises CIDR range.
Creating a custom-mode VPC network allows cloud engineers to explicitly define non-overlapping CIDR blocks for each regional subnet. Because auto-mode VPC networks allocate default subnet ranges strictly inside the block, auto-mode would overlap with the on-premises network. Choosing custom mode with distinct ranges ensures clean hybrid IP routing over Cloud Interconnect.
Adım Adım Çözüm
Anahtar Kavram
VPC Custom Mode vs Auto Mode Subnet Planning in Hybrid Architectures
Tahmini Süre:2m 0s