Study guide

5.3 Network Service Tiers: Premium vs. Standard

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

5.3 Network Service Tiers: Premium vs. Standard

Key Takeaways Explain This Topic AI

Premium Tier routes traffic over Google's private global backbone end-to-end and is the only tier supporting global IPs, global load balancers, and Cloud CDN.

Standard Tier is regional-only, routes outside the resource's region over public internet peering, and offers lower per-GB egress pricing.

Premium Tier targets 99.99% availability; Standard Tier targets 99.9% availability.

Network Service Tier defaults at the project level (Premium) but can be overridden per resource.

An existing IP address or forwarding rule's tier cannot be changed in place — migrating tiers requires provisioning a new IP/forwarding rule on the target tier.

Last updated: July 2026

Why Network Service Tiers Show Up on the Exam

Network Service Tiers determine which network your traffic travels on between Google Cloud and the rest of the internet, and that choice directly affects which load balancer types you can use, what SLA you get, and how much you pay for egress. Domain 2 of the ACE exam guide lists Network Service Tiers as an explicit planning topic, and it pairs naturally with the load balancing and regional placement concepts from the previous two sections — because tier selection constrains which load balancer scope (global vs. regional) is even possible.

The Two Tiers

Premium Tier routes traffic over Google's own private global backbone — the same fiber network Google uses for Search and Gmail. Inbound traffic enters at the point of presence (PoP) closest to the end user and rides Google's network all the way to your resource, wherever it is; outbound traffic exits as close to the destination as possible. This minimizes hops across the public internet and delivers the most consistent latency and packet loss.

Standard Tier enters and exits Google's network only in the region where your resource is deployed, then relies on public internet peering and transit/ISP routes for the rest of the journey. It trades some performance consistency for meaningfully lower per-GB egress pricing.

Resource Support Matrix

Not every resource is available in both tiers — this is the single most exam-relevant fact about Network Service Tiers:

  • Resource Premium Tier Standard Tier
  • Global external IP addresses Yes No
  • Regional external IP addresses Yes Yes
  • Global load balancers (e.g., global external Application LB) Yes No
  • Regional load balancers Yes Yes
  • Cloud CDN Yes No
  • Cloud NAT Yes Yes

Standard Tier is a regional-only service. If a design calls for a single global anycast IP, global external Application Load Balancer, or Cloud CDN, Premium Tier is mandatory — there is no Standard Tier equivalent for any of these. This is exactly why the load balancer choice in section 5.1 and the tier choice in this section have to be planned together: choosing a global load balancer implicitly commits you to Premium Tier pricing for that resource.

SLA and Pricing

Google's stated availability commitments differ by tier: Premium Tier targets 99.99% availability , reflecting the fully Google-managed backbone path, while Standard Tier targets 99.9% availability , reflecting its reliance on public internet peering for part of the path. Standard Tier's appeal is cost — its per-GB egress pricing is lower than Premium Tier's — which makes it attractive for workloads where every user and every backend sit in the same region and the extra hop through public peering is an acceptable trade-off (batch processing endpoints, internal tools, regional-only customer bases, or cost-sensitive services with generous latency budgets).

Configuring Tiers

Network Service Tier is set at the project level (Premium is the default for new projects) but can be overridden per resource — for example, giving one external IP address Standard Tier pricing while the rest of the project stays on Premium. A critical operational detail: you cannot change the tier of an existing IP address or forwarding rule in place — changing tiers requires releasing the current external IP/forwarding rule and creating a new one on the desired tier. This is a common trap in "how do you migrate this workload to Standard Tier" scenario questions, where the tempting-but-wrong answer is "edit the existing IP's tier setting."

Exam Scenarios

Scenario 1: A company serves a public web application to users on five continents and needs the lowest possible latency with a single global IP address. Answer: Premium Tier — it is required for the global external Application Load Balancer and delivers routing over Google's backbone for the best cross-continent performance.

Scenario 2: An internal batch-reporting service in asia-southeast1 serves only regional back-office staff, and the team wants to minimize monthly network egress cost with no requirement for global reach. Answer: Standard Tier — since every client and backend is regional, the reduced-cost public-internet path is an acceptable trade, and no global IP or Cloud CDN capability is needed.

Scenario 3: A team currently running a Standard Tier regional external IP now needs to add Cloud CDN in front of that backend. Answer: This isn't possible as-is — Cloud CDN requires Premium Tier, so the team must reserve a new Premium Tier IP (and reconfigure the forwarding rule/load balancer to use it), since the existing IP's tier cannot be changed in place.

Common Traps

Believing Standard Tier is simply "Premium Tier but slower" — it is architecturally different: it is regional-only and cannot back a global load balancer, global anycast IP, or Cloud CDN at all, not just a degraded version of them.

Assuming tier is a one-time, whole-project setting — it defaults at the project level but is overridable per resource , so a single project can mix Premium and Standard IP addresses.

Trying to "switch" an existing IP's tier — the correct migration path is to create a new IP/forwarding rule on the target tier and cut over, not edit the existing resource.

Key Takeaways

Premium Tier routes traffic over Google's global backbone end-to-end and is the only tier that supports global IPs, global load balancers , and Cloud CDN ; it targets 99.99% availability.

Standard Tier is regional-only, uses public internet peering outside the resource's region, costs less per GB of egress, and targets 99.9% availability.

Tier is set at the project level (Premium by default) but can be overridden per resource, and an existing IP address's tier cannot be changed in place — you must provision a new one on the desired tier.