A network engineering lead at a financial institution is designing a multi-tier enterprise architecture in Google Cloud. The infrastructure requires dedicated Virtual Private Cloud (VPC) subnets across multiple regions for database clusters, web microservices, and internal administrative services. To enforce strict administrative segregation and prevent cross-team network provisioning errors, the security governance team dictates that IP address allocations must be explicitly controlled per subnet without automatic default subnet creation across all GCP regions. Furthermore, the architecture must support future IP space expansion without downtime, while maintaining isolation from legacy on-premises RFC 1918 addresses. Which VPC network design approach best satisfies these requirements?
- Create a custom-mode VPC network, explicitly defining subnets with tailored primary CIDR blocks in required regions, and leave auto-create subnets disabled.Cevap
- BCreate an auto-mode VPC network, then convert it to custom mode immediately after creation to clean up unwanted regional subnets.
- CCreate an auto-mode VPC network and modify the firewall rules to block traffic to unapproved regional default subnets.
- DCreate a legacy VPC network with a single global IP address space shared across all regions without using individual subnets.