Study guide
13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT
Google Cloud Associate Cloud Engineer ACE
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Exam Overview
1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan
2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity
2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups
3 Chapter 3: APIs, Quotas & Billing Configuration
3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts
4 Chapter 4: Planning Compute & Storage Resources
4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types
5 Chapter 5: Planning Network Resources
5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard
6 Chapter 6: Deploying Compute Engine Workloads
6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration
7 Chapter 7: Deploying Google Kubernetes Engine Workloads
7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE
8 Chapter 8: Deploying Serverless & Event-Driven Applications
8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc
9 Chapter 9: Deploying Data Solutions
9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud
10 Chapter 10: Deploying Networking Resources & Infrastructure as Code
10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm
11 Chapter 11: Managing Compute Engine & GKE in Production
11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE
12 Chapter 12: Managing Cloud Run, Storage & Database Operations
12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)
13 Chapter 13: Networking Operations, Monitoring & Logging
13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs
14 Chapter 14: IAM Policies & Role Types
14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles
15 Chapter 15: Service Accounts & Security Configuration
15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials
16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy
16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist
13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT
Key Takeaways Explain This Topic AI
A subnet's primary IP range can be expanded in place with gcloud compute networks subnets expand-ip-range — you can only enlarge it (smaller prefix length), never shrink it, and it cannot overlap another subnet's range.
Ephemeral IPs change when a VM stops and restarts; a reserved static external IP that is NOT attached to a running resource is billed hourly — an idle reservation, not an in-use address, is what costs money.
Cloud DNS private zones resolve internal names only inside specified VPC networks; forwarding zones handle hybrid on-prem/cloud name resolution; peering zones let one VPC reuse another VPC's DNS configuration.
Cloud NAT requires a Cloud Router in the same region and network, is a regional resource, and only permits established inbound response traffic — it never allows new unsolicited inbound connections.
The classic ACE scenario 'private VMs need outbound internet access with no external IPs' is solved by Cloud NAT, not by a load balancer or a firewall rule.
Last updated: July 2026
Why This Topic Matters on the Exam
Domain 4, "Ensuring successful operation of a cloud solution," is worth 20% of the ACE exam, and networking day-2 operations are one of its most concrete, gcloud-command-heavy corners. You already learned how to plan networks (Chapter 5) and deploy VPCs, subnets, and firewall rules (Chapter 10). This section is about keeping a running network healthy: growing a subnet that is running out of addresses, giving a resource a stable IP it will not lose on reboot, resolving names for internal services, and letting private VMs reach the internet without ever getting a public IP. Expect scenario questions that describe a symptom ("engineers can no longer create VMs — no free IPs" or "a partner needs a fixed IP to allowlist") and ask which single operation fixes it.
Expanding an Existing Subnet
A subnet (subnetwork) is a regional resource that carves a range of internal IP addresses out of a global VPC network . Subnets are created with a primary IPv4 CIDR range (e.g., 10.0.1.0/24 = 256 addresses) and, optionally, one or more secondary ranges used for alias IPs — most commonly GKE Pod and Service ranges in VPC-native clusters.
When a subnet runs out of usable addresses, you do not need to delete and recreate it. Google Cloud supports expanding a subnet's primary IP range in place, with zero downtime for existing resources: gcloud compute networks subnets expand-ip-range SUBNET_NAME \
- -region=REGION \
- -prefix-length=NEW_PREFIX_LENGTH
Key rules the exam tests:
You can only increase the range (make the prefix length smaller — e.g., /24 → /22 ). You cannot shrink a subnet's range.
The new, larger range must not overlap any other subnet's primary or secondary range in the same network, including ranges reserved (but unused) for future subnets.
Existing VMs keep their current IPs; the operation only grows the pool of available addresses for new resources.
This works for both auto mode and custom mode VPC networks, but auto-mode subnets already use large predefined ranges per region, so custom mode is where you will use this in practice.
Common trap: a candidate assumes they must delete the subnet, which would delete every resource's IP assignment and cause an outage. The exam guide explicitly lists "expanding a subnet's IP range" as a distinct, non-disruptive operation.
Reserving Static IP Addresses
By default, a Compute Engine VM's external IP is ephemeral — Google assigns one from a shared pool, and it changes (or disappears) if you stop and restart the VM. An internal IP is normally static for the life of the VM but is still released if the VM is deleted.
A static IP address is one you explicitly reserve so it stays yours until you release it:
Static external IP — reserve with gcloud compute addresses create , then assign it to a new VM or promote an existing ephemeral IP to static. Needed when an external system (DNS record, partner firewall allowlist, API client) must always reach the same address.
Static internal IP — reserve a specific address inside a subnet's range so a resource (e.g., a database VM other services depend on by IP) never changes, even across recreation.
Regional vs. global : addresses used by regional resources (VMs, regional load balancers) are regional; addresses for global external HTTP(S) load balancers are global.
Cost trap the exam loves: a reserved static external IP address that is not attached to a running resource is billed at an hourly rate — the opposite of what most candidates assume. An in-use static IP attached to a running VM is typically free (standard tier); it is the idle, reserved-but-unattached address that costs money. A scenario describing "unexpected charges for IP addresses that aren't attached to anything" is testing this exact rule — the fix is to release the unused reservation.
Cloud DNS
Cloud DNS is Google's managed, authoritative DNS service, offering 100% uptime SLA and global anycast serving.
- Zone type Visibility Use case
- Public zone Internet-visible Serve your organization's public domain (e.g., example.com )
Private zone Only resolvable inside specified VPC networks Internal service discovery (e.g., db.internal.example.com )
Forwarding zone Routes queries to designated name servers Hybrid resolution — VMs need to resolve on-prem-only names, or on-prem clients need to resolve Cloud DNS private-zone names over VPN/Interconnect
Peering zone Delegates a VPC's DNS resolution to another VPC's Cloud DNS configuration Centralize DNS management for a hub-and-spoke or Shared VPC topology without duplicating zones
Cloud DNS supports standard record types (A, AAAA, CNAME, MX, TXT, NS, SOA, SRV) managed via the console, gcloud dns record-sets , or transactions for atomic multi-record changes.
Exam scenario: "A private zone must resolve payroll.corp.internal only for VMs inside vpc-prod , and on-premises engineers connected via Cloud VPN also need to resolve it." → Create a private managed zone visible to vpc-prod , then configure inbound server policy / forwarding so the on-prem resolver can query Cloud DNS over the VPN tunnel.
Cloud NAT
Cloud NAT (Network Address Translation) is a fully managed, software-defined, distributed service that gives Compute Engine VMs, GKE Pods, and other private resources outbound internet connectivity without an external IP address on each resource.
Requirements and behavior to know cold for the exam:
A Cloud NAT gateway is always attached to a Cloud Router in the same region and network — the router holds the NAT gateway's configuration (you do not need BGP/dynamic routing for NAT-only use).
NAT IP addresses and ports can be allocated automatically (Google manages a pool) or manually (you assign specific reserved static external IPs — useful when a downstream service needs to allowlist your outbound IP range).
Cloud NAT is regional — you must configure a NAT gateway in every region where private resources need outbound access, and you scope it to specific subnets/IP ranges or the whole network.
Cloud NAT supports address translation for established inbound response packets only — it never allows new, unsolicited inbound connections. If you need inbound access, that is a load balancer or firewall rule with an external IP, not NAT.
Port allocation is per-VM (a default minimum ports-per-VM setting, tunable upward for VMs that open many concurrent connections), and idle/established connections eventually time out.
Exam scenario: "A tier of backend VMs has no external IPs (per security policy) but must call a third-party payment API over HTTPS and download OS security patches." → Attach a Cloud NAT gateway (via a Cloud Router) in that subnet's region. This is one of the most frequently tested single-answer scenarios on the real exam.
Quick Decision Table
- Symptom Fix
- "Out of IP addresses in a subnet" Expand the subnet's primary range ( expand-ip-range )
- "A resource's IP keeps changing after stop/start" Reserve (or promote to) a static IP
- "Charged for an IP no one is using" Release the unattached reserved static IP
- "Need to resolve internal service names inside a VPC" Private Cloud DNS zone
- "On-prem needs to resolve Cloud DNS private-zone records" Forwarding (inbound server policy)
- "Private VM needs outbound internet, no public IP allowed" Cloud NAT (via Cloud Router)