An enterprise architecture team is designing the network foundation in Google Cloud for a workload that will expand across multiple regions and connect to on-premises data centers via Cloud Interconnect. The team needs to establish IP address management (IPAM) guidelines for the Virtual Private Cloud (VPC) topology to avoid IP space conflicts and ensure explicit control over regional subnet creation. Which TWO architectural decisions should the team implement during the VPC network and subnet planning phase? (Select TWO.)
- Create the Virtual Private Cloud (VPC) network in Custom mode rather than Auto mode.Answer
- Allocate non-overlapping primary IPv4 CIDR blocks across all GCP subnets and connected on-premises networks.Answer
- CCreate the Virtual Private Cloud (VPC) network in Auto mode to automatically provision pre-configured /20 subnets in every GCP region.
- DAssign identical primary IPv4 CIDR ranges to subnets located in different regions within the same VPC network to conserve private IP address space.
Answer
The team should create the VPC network in Custom mode and allocate non-overlapping primary IPv4 CIDR blocks across all GCP subnets and connected networks.
Creating the VPC network in Custom mode gives network administrators full control to define subnets only in chosen regions using custom IPv4 ranges. Allocating non-overlapping primary IPv4 CIDR blocks across all cloud subnets and on-premises environments ensures clean routing table generation and avoids IP collision issues over Cloud Interconnect.
Step-by-Step Solution
Key Concept
Planning Custom Mode VPC Networks and Non-Overlapping Subnet Addressing
Estimated Time:1m 30s