Study guide

1.2 How to Use This Study Guide & Build a Study Plan

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

1.2 How to Use This Study Guide & Build a Study Plan

Key Takeaways Explain This Topic AI

This guide's 16 chapters map one-to-one onto the five official exam domains in proportion to their weight, so working through it in order mirrors the exam's own emphasis.

A realistic study plan totals roughly 108 hours across 5 phases — Environment Setup (20h), Planning/Deployment (28h), Operations (24h), Security/Access (18h), and Timed Simulations (18h).

At 12-15 study hours per week, most candidates complete the full plan in 6-10 weeks, matching Google's own recommendation of 6+ months of hands-on experience layered with focused exam prep.

Every chapter pairs reading with a hands-on task in a real (or free-tier) Google Cloud project — ACE is a console/CLI exam, and reading alone will not build the muscle memory it tests.

Use the 80% rule: don't advance to the next chapter until you can score 80%+ on that chapter's quiz questions without looking back at the text.

Last updated: July 2026

Why the Structure Matters

This guide is not a generic cloud-computing course with the ACE name attached — every chapter after this one maps directly to a bullet in Google's official exam guide, and the guide is sequenced so that chapter order and depth follow the exam's own domain weights. If you read the guide in order , you automatically spend more time on the material the exam tests more heavily. That matters because ACE candidates who study "everything equally" tend to under-prepare for Domain 3 (Deploying and implementing, ~25% of the exam, the single biggest domain) and over-prepare for narrower areas like billing configuration.

How This Guide's 16 Chapters Map to the 5 Official Domains

  • Chapters Official Domain Weight What You'll Build
  • 1 Introduction (this chapter) — Exam facts + study plan

2-3 1. Setting up a cloud solution environment ~20% Resource hierarchy, IAM basics, Cloud Identity, APIs, quotas, billing

4-5 2. Planning and configuring a cloud solution ~17.5% Compute/storage/network selection decisions

6-10 3. Deploying and implementing a cloud solution ~25% Compute Engine, GKE, Cloud Run/Functions, data products, networking, IaC

11-13 4. Ensuring successful operation of a cloud solution ~20% Managing running workloads, Monitoring, Logging

  • 14-15 5. Configuring access and security ~17.5% IAM policies/roles, service accounts
  • 16 Exam readiness capstone — Cross-domain scenarios, test-day logistics

Notice that Domain 3 alone spans 5 chapters (6-10) — nearly a third of the guide — because it is both the highest-weighted domain and the one with the widest service surface (six deployable compute/serverless options and eight named data products). If you only have time to deeply study one block of chapters before the exam, make it that one.

The 5-Phase Study Plan

Spread your prep across five phases that track the domain groupings above. This plan totals 108 hours , which lines up with the 80-120 hour range most candidates report needing:

  • Phase Focus Hours Guide Chapters
  • 1. Environment Setup Projects, IAM basics, billing, initial config 20h 2-3
  • 2. Solution Planning & Deployment Service selection + hands-on deployment 28h 4-10
  • 3. Operations & Reliability Monitoring, logging, managing running workloads 24h 11-13
  • 4. Security & Access IAM hardening, service accounts 18h 14-15
  • 5. Timed 50-60Q Simulations Full-length mixed-domain practice, gap closing 18h 16 + review

At a sustainable pace of 12-15 hours per week , that's 6-10 weeks end to end — consistent with Google's own guidance and with what this exam's flashcard and cheat-sheet metadata report for typical candidates. If you already have 6+ months of daily hands-on GCP work (Google's stated recommended experience), you can likely compress Phases 1-3 and spend the saved time on Phase 5 simulations instead, since your gaps are more likely to be exam-specific gotchas than fundamentals.

How to Work Through Each Section

Every section in this guide (including this one) follows the same internal pattern, and you'll get the most out of it by using all four parts rather than skimming the text block alone:

Read the text block for definitions, tables, and worked scenarios — bold terms are exam vocabulary worth memorizing exactly as written.

Do the hands-on task. Nearly every ACE chapter maps to an action you can perform in a real project. Create a free Google Cloud account (new accounts get a $300 credit valid for 90 days , enough to run every lab in this guide without a bill) and actually execute the gcloud commands and console steps described — typing gcloud compute instances create yourself builds recall that reading never will.

Answer the quiz questions at the end of the section without looking back at the text first. Score yourself honestly.

Apply the 80% rule. If you score below 80% on a section's quiz, re-read the relevant subsection and redo the hands-on task before moving to the next section — ACE questions build on each other conceptually (e.g., you can't reason about GKE autoscaling in Chapter 11 if IAM roles from Chapter 2 aren't solid).

Complementary Resources for This Exam

Use this guide as your primary spine, but pair it with:

Flashcards for rapid-fire recall of gcloud command syntax, IAM role names, and storage-class names — the kind of fact that's easy to read once and forget.

The cheat sheet as a day-before-the-exam review artifact — a dense, single-page reference rather than a teaching tool.

The 200-question practice bank for full-length timed simulations in Phase 5, so you experience the real 2-hour/50-60-question pressure before test day.

Google Cloud Skills Boost (the official hands-on lab platform) for guided labs that mirror the exact console workflows ACE tests.

A Realistic Weekly Template

For a 15-hour-per-week, 8-week plan: study 2 chapters' worth of material and hands-on labs on 3 weekday evenings (roughly 1.5-2 hours each), then reserve a longer weekend block (4-5 hours) for catching up, redoing labs you rushed, or — once you reach Phase 5 — running one full timed practice set. Track your quiz scores chapter by chapter in a simple spreadsheet; a domain where you're consistently below 80% is your signal to add extra lab time before exam day, not just re-read the text.