The August 2026 revision of the Cloud Digital Leader exam guide gives networking its own item in Domain 1. You need to be able to define fundamental networking concepts such as IP addresses, DNS, latency, and bandwidth, explain how Google Cloud's global network supports digital transformation, and describe how regions, zones, and edge locations work together. Cloud VPC, Cloud VPN, and Cloud Interconnect also appear in the list of security products in Domain 5.
Networking is the least familiar area for people without a technical background, but the level CDL asks for is about the same as understanding how a parcel gets delivered. This post starts with the basic networking terms, then covers the components of Google's global network, Network Service Tiers, VPC, connecting on-premises environments, and the services that deliver content to users quickly. IaaS, PaaS, SaaS and the cloud deployment models are covered first in Digital Transformation and Cloud Fundamentals.
---
Basic Networking Terms: Addresses, Names, and Speed
Data moving across the internet is a lot like a parcel delivery. You need the recipient's address, you need a directory when you only know their name, the delivery takes time to arrive, and the size of the truck decides how much you can carry in one trip.
| Term | Meaning | In parcel-delivery terms | |------|------|------| | IP address | A numeric address that identifies a device on a network (for example, 203.0.113.10) | The recipient's street address | | Public IP vs. internal IP | An address visible on the internet vs. one used only inside the organization's network | A company's main address vs. a department's location inside the building | | DNS | The system that translates domain names such as example.com into IP addresses | An address book that finds the address from a name | | Latency | The time it takes data to reach its destination and come back, usually in milliseconds | How long the parcel takes to arrive | | Bandwidth | The maximum amount of data that can be sent in a given time, in Mbps or Gbps | The size of the truck and the number of lanes on the road |
Latency and bandwidth are different problems. However wide the road, a long distance still means a long trip; and even over a short distance, a small truck means many trips. So the fixes are different too. You reduce latency by processing closer to the user, and you increase bandwidth with a bigger connection.
Exam tip: "Web pages load slowly for overseas users" is a latency problem, so the answer is a region close to the users or Cloud CDN. "Moving large amounts of data from the data center to the cloud takes far too long" is a bandwidth problem, so the answer is a bigger connection such as Cloud Interconnect.
---
The Components of Google's Global Network
Google Cloud runs on the same worldwide network that supports Google Search, YouTube, and Gmail. According to the official page as of October 2026, 43 regions, 130 zones, and more than 200 network edge locations are connected by subsea and terrestrial fiber.
| Component | Meaning | What it does | |------|------|------| | Region | An independent geographic area, usually made up of three or more zones | Places resources close to users and keeps data inside a particular country (data residency) | | Zone | A deployment area within a region and a single failure domain | Spreading deployments across zones provides high availability | | Multi-region | A large area that spans several regions (for example, US or EU) | High availability for services such as Cloud Storage and BigQuery | | Network edge location | A point where Google's network meets the internet | Receives user requests nearby, hands them to Google's network, and caches content | | Global backbone | Google's private network linked by subsea and terrestrial fiber | Data travels less over the public internet, so it moves faster and more securely |
Each resource belongs to a particular scope, and that scope determines how well it withstands failures.
| Scope | Examples | Impact of failures | |------|------|------| | Zonal resources | Compute Engine VMs, persistent disks | Affected if that zone fails | | Regional resources | Regional Cloud Storage buckets, Cloud Run services, VPC subnets | Survive the failure of a single zone | | Multi-regional resources | Multi-region Cloud Storage buckets, BigQuery multi-region datasets | Designed to survive the failure of a region | | Global resources | VPC networks, firewall rules, global load balancers | Not tied to a specific location |
Exam tip: "The service must keep running even if one zone fails" means deploying across multiple zones. "Prepare for the failure of an entire region" means deploying across multiple regions. "Customer data must stay in the country" means choosing a region in that country.
---
Network Service Tiers: Premium vs. Standard
Google Cloud lets you choose between two tiers for the path traffic takes between internet users and your Google Cloud resources. Premium Tier is the default: traffic enters Google's network at an edge close to the user and travels over Google's backbone. Standard Tier travels over regular carrier networks and enters Google's network near the region.
!Premium Tier rides Google's backbone from an edge near the user, while Standard Tier crosses the public internet and enters near the region
| Aspect | Premium Tier | Standard Tier | |------|------|------| | Routing | Travels within Google's network to reach users | Reaches users through peering, ISP, or transit networks | | Security | Protected on Google's backbone until the last mile | Comparable to other public clouds | | Networking features | Supports all Google Cloud networking features | Foundational features such as Cloud NAT and regional load balancers | | Pricing | At parity with other public clouds | Lower cost | | SLA | 99.99% | 99.9% |
Exam tip: "The best performance for users around the world" means Premium Tier, while "users in one area and we want to cut costs" means Standard Tier. If a question asks about Google's global network as a differentiator, the key point is that "traffic crosses less of the public internet, so latency is lower and the path is more secure."
---
VPC: Your Company's Network Inside the Cloud
A VPC (Virtual Private Cloud) is your organization's own private network, logically isolated inside Google Cloud. It is like renting floors in a large building that only your company uses, then dividing them into areas for each department.
| Component | Description | |------|------| | VPC network | The organization's private network; a global resource, so a single network spans multiple regions | | Subnet | A range of IP addresses created per region | | Firewall rules | Rules that decide which traffic is allowed and which is denied | | Routes | Rules that decide where traffic should go | | Cloud NAT | Lets VMs without external IP addresses reach the internet, without allowing unsolicited inbound connections |
What sets Google Cloud VPC apart is that the network itself is global. VMs in the Seoul region and a US region that sit in the same VPC can talk to each other directly over internal IP addresses without crossing the public internet. Subnets are created per region, so a common design is one subnet in each region.
Exam tip: "VMs in several regions communicate over internal IP addresses without the public internet" is solved by a single global VPC. "Let VMs receive software updates without giving them external IP addresses" is Cloud NAT.
---
Connecting On-Premises: Cloud VPN and Cloud Interconnect
To run a hybrid cloud you need to connect your company's data center to Google Cloud. Cloud VPN is a security escort driving on public roads, while Cloud Interconnect is a private highway for your company.
| Aspect | Cloud VPN (HA VPN) | Dedicated Interconnect | Partner Interconnect | |------|------|------|------| | How it connects | An IPsec-encrypted tunnel over the public internet | A direct physical connection between your data center and Google's network | Through a supported service provider | | Crosses the public internet | Yes (encrypted) | No | No | | Bandwidth | About 1–3 Gbps per tunnel | 10, 100, or 400 Gbps circuits | 50 Mbps to 50 Gbps per VLAN attachment | | Setup | Fast and inexpensive | Requires a direct connection at a colocation facility and takes the longest | Relatively quick through a provider | | When it fits | Quick setup, light traffic, backup connection | Large volumes and a stable low-latency connection | You cannot reach a Google colocation facility directly or need medium bandwidth |
HA VPN provides a 99.99% SLA for most topologies. With Cloud Interconnect, your on-premises network can reach the VPC's internal IP addresses directly. To connect with other clouds, Cross-Cloud Interconnect links Google's network directly to another cloud's network such as AWS or Azure.
Exam tip: "Fast and inexpensive, and there is not much traffic" is Cloud VPN. "Move large volumes of data reliably without crossing the public internet" is Dedicated Interconnect. "We cannot connect directly at a Google colocation facility" is Partner Interconnect.
---
Delivering Fast and Safely to Users: Load Balancing, CDN, and DNS
Once regions and networks are in place, the last step is responding quickly and reliably to users around the world.
| Service | What it does | Clues in the question | |------|------|------| | Cloud Load Balancing | Receives worldwide traffic on a single anycast IP address, spreads it across backends in multiple regions, and routes around a failed region | "One IP address for users worldwide," "handle traffic spikes automatically" | | Cloud CDN | Caches content on Google's edge network and responds close to the user | "Images and videos load slowly," "reduce the load on the origin server" | | Cloud DNS | A managed DNS service for your domain names, with public and private