Study guide
7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise
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
7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise
Key Takeaways Explain This Topic AI
GKE Autopilot bills per-Pod resource requests and removes node management; GKE Standard bills per-VM node plus an optional $0.10/hour cluster fee and requires managing node pools
Regional clusters replicate the control plane across 3 zones for high availability; zonal clusters have a single control-plane replica
Private clusters (--enable-private-nodes, optionally --enable-private-endpoint) need Cloud NAT for private nodes to reach the public internet
GKE Enterprise (formerly Anthos, rebranded November 2023) provides fleet-based multi-cluster/multi-cloud policy management via Config Sync and Policy Controller, now bundled into standard GKE
Production scenarios usually require combining axes (e.g., regional + private + Autopilot), not choosing a single setting
Last updated: July 2026
Why Cluster Configuration Choices Dominate This Objective
The official exam guide bullet reads: "Deploying a Google Kubernetes Engine cluster with different configurations (e.g., Autopilot, regional clusters, private clusters, GKE Enterprise)." This is a decision-making objective, not a memorization one — expect scenario questions that describe a business requirement (cost control, high availability, security posture, multi-team governance) and ask which cluster configuration satisfies it. Getting this right means knowing the trade-offs of each axis, because most real clusters combine more than one of these choices at once (e.g., a regional, private, Autopilot cluster).
Axis 1: Standard vs. Autopilot
GKE Standard GKE Autopilot
Node management You choose machine types, create node pools, and manage upgrades Google fully manages nodes; no node pools to configure
Billing unit Per-VM (node) compute cost, plus a $0.10/hour cluster management fee (one zonal cluster/billing account is fee-waived) Per- Pod resource requests (CPU, memory, ephemeral storage), billed in 1-second increments; no separate cluster fee
Customization Full control: custom machine types, GPUs/TPUs, taints, node-level daemons Restricted to a curated, hardened configuration; some privileged workloads are blocked by default
Ops overhead You size and scale node pools yourself (or configure autoscaling) "Hands-off" — Google scales nodes to match Pod demand automatically
Best fit Workloads needing fine-grained node control, GPUs/specialized hardware, legacy DaemonSets Most new production workloads; teams that want to stop managing nodes entirely
- Creation commands: # Standard mode
- gcloud container clusters create my-cluster --zone us-central1-a
- # Autopilot mode
- gcloud container clusters create-auto my-cluster --region us-central1
Note that Autopilot clusters are regional by default — Google does not offer a zonal Autopilot cluster.
Axis 2: Zonal vs. Regional
A zonal cluster runs a single control plane replica in one zone. If that zone has an outage, the control plane (and therefore kubectl access, scaling decisions, and scheduling) becomes unavailable until the zone recovers — though already-running Pods keep serving traffic.
A regional cluster replicates the control plane across three zones in the chosen region, and can also spread worker nodes across those zones. This is the recommended choice for production because it survives a single-zone failure with no control-plane downtime. gcloud container clusters create my-cluster --region us-central1 # regional
gcloud container clusters create my-cluster --zone us-central1-a # zonal
Zonal clusters are cheaper and faster to provision, which makes them common for dev/test environments in exam scenarios — regional is the answer whenever the scenario says "production" or "high availability."
Axis 3: Public vs. Private Clusters
A private cluster removes public IP addresses from the worker nodes (and optionally the control plane), shrinking the attack surface: gcloud container clusters create my-cluster \
- -region us-central1 \
- -enable-private-nodes \
- -enable-private-endpoint \
- -master-ipv4-cidr-block 172.16.0.16/28
- Flag Effect
- -enable-private-nodes Worker nodes get only internal IPs — no direct inbound/outbound internet access
--enable-private-endpoint The control plane's endpoint is reachable only from inside the VPC (no public IP for the API server)
--master-ipv4-cidr-block Assigns the required /28 CIDR range for the control plane's internal network
--enable-master-authorized-networks Restricts which external CIDR ranges may reach the control plane endpoint at all
Trap to know cold: because private nodes have no public IP, they cannot reach the internet to pull public container images or apply OS patches unless you configure Cloud NAT (or rely on Private Google Access for Google Cloud APIs specifically). If an exam scenario describes a private-nodes cluster where Pods fail to start because images can't be pulled from a public registry, the missing piece is almost always Cloud NAT, not a firewall rule.
Axis 4: GKE Enterprise
GKE Enterprise (rebranded from Anthos in November 2023) adds fleet-based management : a fleet is a logical grouping of one or more GKE clusters — including clusters in other clouds — that lets a platform team apply consistent policy, configuration, and observability across all of them from one control point. Two of its signature capabilities are:
Config Sync — keeps cluster configuration in sync with a Git repository (GitOps).
Policy Controller — enforces guardrail policies (e.g., "no Pods with privileged: true ") consistently across every cluster in the fleet.
As of late 2025, Google folded most of these fleet-management capabilities (fleets, Config Sync, Policy Controller) into standard GKE at no additional cost — GKE is now presented as a single offering rather than separate paid editions/tiers. A handful of advanced capabilities (Cloud Service Mesh, multi-cloud Attached Clusters for AWS/Azure, Backup for GKE, Extended Support, Multi-cluster Gateway) remain separately billed add-ons. For the exam, the concept to remember is: choose "GKE Enterprise" / fleet management whenever a scenario describes centralized policy or configuration across many clusters or clouds , not for a single, single-team cluster.
Putting the Axes Together
Exam scenario: "A retail company runs a customer-facing checkout service on GKE. The security team requires that worker nodes have no public IP addresses and that the workload survive the loss of any single zone. The platform team also wants Google to manage node provisioning entirely." → The answer combines all three : a regional, private-nodes, Autopilot cluster.
Exam scenario 2: "An enterprise runs GKE clusters across three different business units and two cloud providers, and needs one team to enforce a single network-policy standard everywhere." → This describes GKE Enterprise fleet management with Policy Controller , not a single cluster configuration change.
Key Takeaways
Autopilot bills per-Pod resource request and removes node management entirely; Standard bills per-VM plus an optional $0.10/hour cluster management fee and requires you to manage node pools.
Regional clusters replicate the control plane across 3 zones for high availability; zonal clusters have a single control-plane replica and are common for dev/test.
Private clusters ( --enable-private-nodes , optionally --enable-private-endpoint ) need Cloud NAT for private nodes to reach the public internet.
GKE Enterprise (formerly Anthos) provides fleet-based multi-cluster/multi-cloud policy and configuration management (Config Sync, Policy Controller); its core features are now bundled into standard GKE.
Real production clusters usually combine multiple axes at once — expect exam questions to require picking the combination , not a single setting.