Theory
Every objective of the Associate Cloud Engineer exam guide that went live on 30 June 2026, taught once.
The guide has four sections, weighted 20 / 30 / 30 / 20. It replaced the five-section guide and added new objectives: Workforce and Workload Identity Federation, Cloud NGFW with secure tags, standalone organizations, GPUs vs TPUs, AI-assisted tooling, Agent Runtime, Cloud Hub, Database Center, Autopilot resource requests, and more. Anything new is marked with a purple New in the June 2026 guide callout wherever it is taught.
It is organised by dependency rather than by the guide’s sections, so each part only assumes the parts before it.
| Part | Covers |
|---|---|
| 1 · The exam, locations and the tools | The paper, how items are written, regions and zones, the interfaces |
| 2 · Organization, projects, billing and quotas | The resource hierarchy, APIs, quotas, budgets, Asset Inventory |
| 3 · Identity and access | IAM, federation, service accounts, short-lived credentials, Secret Manager |
| 4 · Networking | VPCs, firewalls and Cloud NGFW, hybrid connectivity, DNS, NAT, load balancing |
| 5 · Compute Engine | Machine families, disks, access, snapshots, managed instance groups, GPUs and TPUs |
| 6 · Containers and serverless | GKE, Artifact Registry, Cloud Run and functions |
| 7 · Storage and data | Cloud Storage, the databases, BigQuery, pipelines, backup and redundancy, encryption |
| 8 · Tooling | Terraform, AI-assisted planning, AI and developer platforms |
| 9 · Operations | Monitoring, logging, audit logs, service health, optimisation |
| 10 · Compression for the last 48 hours | Confusion pairs, the numbers, the command atlas, the words in a stem |
| Appendix A · The guide, mapped | Every guide bullet and the section that teaches it |
| Appendix B · Provenance and limits | What this was built from, and how far to trust it |
| Practice scenarios | 47 decision paths across eight companies, answers hidden until you open them |
Each part ends in a recall card: the whole part on one screen, for the second pass.
How to read the callouts:
The fact to carry into the exam room.
The wrong answer the exam is written to attract.
The words in a stem that give the answer away.
Two things that sound alike and are tested against each other.
Useful context that is less likely to decide an item.
Introduced by the June 2026 guide.
Highlighted text is the single most exam-relevant fact in a section.
The loop
- Read a part.
- Drill that part in the simulator’s Learning mode, filtered to its objectives.
- Sit a Certifying exam, and reread the parts where you scored under 70%.
Volatile facts are marked verify. Commands show the shape of a call, and were checked against the Google Cloud SDK on 29 September 2026. The ~70% pass mark is a community convention: Google publishes no cut score. Found something wrong? Every page has a Suggest a fix link.
Building a PDF (optional)
The pages above are the source. A printable booklet can be built locally from them, and PDFs are not committed:
cd theory/pdf
./build-theory.sh # assembles the pages, runs the QA gate, then compiles ACE-Theory-Recap.pdf
./build-theory.sh --check # QA gate only: needs no LaTeX
It needs pandoc 3.9+, XeLaTeX and the macOS fonts Helvetica Neue and Menlo. check-gcloud.py also checks every
gcloud command against the release tracks of your installed SDK.
Table of contents
- Part 1 — The exam, locations and the tools
- Part 2 — Organization, projects, billing and quotas
- Part 3 — Identity and access
- Part 4 — Networking
- Part 5 — Compute Engine
- Part 6 — Containers and serverless
- Part 7 — Storage and data
- Part 8 — Tooling: infrastructure as code, AI assistance, developer platforms
- Part 9 — Operations: observability, health and optimisation
- Part 10 — Compression for the last 48 hours
- Appendix A — The exam guide, mapped to this booklet
- Appendix B — Provenance and limits
- Practice scenarios