Networking for Google Clouds
Google Cloud networking is how resources talk to each other and to the internet. A VPC network defines subnets, routes and firewall rules, while Cloud Load Balancing distributes incoming traffic across backends. Understanding these pieces lets you keep services private, expose only what is needed and keep applications available.
Stage: Data and Networking · Part of the Google Cloud roadmap · Last reviewed 19 November 2026
What to learn in Networking
- Create a custom-mode VPC with subnets in more than one region
- Write firewall rules that allow only required ports and sources
- Set up an external HTTP(S) load balancer with a backend service
- Explain how Cloud NAT lets private VMs reach the internet
- Use health checks to remove unhealthy backends from rotation
Networking interview questions
Is a Google Cloud VPC regional or global?
A VPC network is a global resource, while its subnets are regional. That means VMs in different regions can sit in the same VPC and talk over internal IPs without a separate peering setup, subject to firewall rules.
What is the difference between an external and an internal load balancer?
An external load balancer receives traffic from the internet and routes it to backends. An internal load balancer uses a private IP reachable only inside your VPC or connected networks, which suits traffic between tiers of an application.
Where Networking fits in the Google Cloud roadmap
Networking belongs to the Data and Networking stage (intermediate level). Store and connect.
Other units in this stage
Back to the full Google Cloud roadmap