
Google Cloud VPC networks are created in one of two modes. An auto mode network automatically creates one subnet in every region, and all of those subnets come from the 10.128.0.0/9 block. A custom mode network lets you choose your own subnet ranges. The mode a network uses affects whether it can be peered with other networks, how its address plan can grow and how VMs are placed into it, and each of those shows up in design scenarios on the Professional Cloud Network Engineer exam.
An auto mode network has a subnet in every region, and every one of those subnets is carved from 10.128.0.0/9. The ranges are the same in every auto mode network, region by region. The default network is itself an auto mode network that uses those same ranges.
That uniformity becomes a problem as soon as networks need to be connected. Two auto mode networks get identical regional ranges, so they overlap, and VPC Network Peering between them fails. Because the default network uses the same ranges, it overlaps with any other auto mode network in the same way.
A custom mode network lets you choose your own ranges, and that is how a new network is built so it can peer cleanly with an existing auto mode network. The ranges need to stay outside 10.128.0.0/9.
It helps to see where that block sits. 10.128.0.0/9 is the upper half of 10.0.0.0/8, covering 10.128.0.0 through 10.255.255.255. The lower half, 10.0.0.0/9, covers 10.0.0.0 through 10.127.255.255. A range that sits entirely within 10.0.0.0/9 never collides with anything an auto mode network creates, either in the regions that exist now or in future regions.
A range can look unrelated and still overlap. Any 10.x range with a second octet of 128 or higher falls inside 10.128.0.0/9, the block that auto mode subnets are drawn from, so it can overlap a regional subnet that exists now or one created for a future region. The question to ask is whether the range falls inside 10.128.0.0/9 at all, not whether it matches a subnet in a region currently in use, since an auto mode network has a subnet in every region.
Names need the same forethought as ranges. VPC networks can't be renamed after they are created, so a network's name is fixed from the start.
An auto mode network can be converted to custom mode, but the conversion is one-way. Once a network is in custom mode, it can't go back to auto mode.
The conversion also changes how VMs are created. In an auto mode network, a subnet exists in every region, so Google Cloud can choose the subnet when a new VM names only the network. After the conversion, Google Cloud no longer picks a subnet. Any VM definition that sets only the network field, whether it lives in a script, a template or an infrastructure-as-code configuration, now fails with an error saying a subnetwork must be specified.
The fix is to name a specific subnetwork in the VM's region. Once each instance definition references the correct subnetwork explicitly, VM creation works again. Planning a conversion therefore includes finding every template and configuration that creates VMs in the network and making sure each one names a subnetwork.
For the Professional Cloud Network Engineer exam, the practical rules are to build any network that will be peered with an auto mode network in custom mode, keep its ranges out of 10.128.0.0/9, and treat a conversion from auto mode as permanent and as a change that affects every VM definition that relies on Google Cloud picking the subnet.
Our Professional Cloud Network Engineer practice exams cover auto mode and custom mode networks alongside VPC Network Peering and subnet planning, with detailed explanations that drill these distinctions.