A cloud infrastructure engineer is designing a Google Cloud Virtual Private Cloud (VPC) network for a workload deployed across specific regions: `us-central1` and `europe-west1`. Corporate policy mandates full control over IP address range allocations to prevent collisions with existing corporate networks, and strictly prohibits provisioning subnets in any unused regions. Which VPC creation method and configuration should the engineer implement?
- Create a custom-mode VPC network and manually define subnets only in `us-central1` and `europe-west1` with non-overlapping CIDR ranges.Cevap
- BCreate an auto-mode VPC network and select `us-central1` and `europe-west1` as the designated subnet regions during creation.
- CCreate an auto-mode VPC network and delete the automatically generated subnets in all regions except `us-central1` and `europe-west1`.
- DCreate a custom-mode VPC network with the automatic subnet allocation flag enabled specifically for `us-central1` and `europe-west1`.
Cevap
Create a custom-mode VPC network and manually define subnets only in `us-central1` and `europe-west1` with non-overlapping CIDR ranges.
Creating a custom-mode VPC network allows full architectural control because no subnets are created automatically. The network engineer can manually define subnets only in the required regions (`us-central1` and `europe-west1`) and assign specific, non-overlapping IP address ranges that conform to corporate IP governance policies.
Adım Adım Çözüm
Anahtar Kavram
Custom-mode vs. Auto-mode VPC Network Planning