Google ACE Study Planner
A week-by-week study plan for the ACE exam: 2-week, 4-week, and 8-week schedules.
How to use this planner
There are three plans below: 2 weeks (for experienced Google Cloud practitioners), 4 weeks (for candidates with some IT background), and 8 weeks (for beginners or career changers). Each plan assumes the study guides on this site plus hands-on lab time in a real Google Cloud project — the labs are not optional for this exam. Google offers free usage of many products up to monthly limits, plus $300 in free credits for new customers, which covers all the lab work in these plans. Set up a practice project before you start, and perform every task each guide describes.
2-week plan — experienced practitioners
For someone who already works with Google Cloud daily and mainly needs exam style and gap-filling. About 2 hours a day.
| Day | Focus |
|---|---|
| 1–2 | Resource hierarchy, billing, quotas (Guides 1–2) + questions. Lab: build a folder/project structure, set a budget and billing export. |
| 3–4 | Compute, storage, and network planning (Guides 3–5) + questions. Lab: compare machine types, storage classes, load balancer types. |
| 5–7 | Deploying: Compute Engine, GKE, serverless, data, networking (Guides 6–10) + questions. Lab: deploy a MIG, a GKE app, a Cloud Run service, a Cloud SQL instance, a VPC. |
| 8–9 | Operations and monitoring (Guides 11–13) + questions. Lab: snapshots, log-based metric + alert, Cloud NAT. |
| 10 | IAM and service accounts (Guide 14) + questions. Lab: custom role, service account impersonation. |
| 11–12 | Timed mock test. Review every wrong answer by section; re-study the weakest guides. |
| 13 | Second mock test (re-take with fresh eyes) + cheat sheet review. |
| 14 | Light review of the cheat sheet and your missed questions. Rest. Book or sit the exam. |
4-week plan — the standard path
For candidates with some IT background. About 1–2 hours a day, with longer lab sessions at weekends.
| Week | Focus |
|---|---|
| 1 | Environment setup and planning (Guides 1–5). One guide per weekday with its questions; weekend lab: set up a full project hierarchy with billing, budgets, and a VPC. |
| 2 | Deploying (Guides 6–10). One guide per weekday; weekend lab: deploy a complete three-tier application — MIG behind a load balancer, Cloud SQL backend, Cloud Storage for assets. |
| 3 | Operations, monitoring, and IAM (Guides 11–14). One guide per weekday; weekend lab: snapshots and images, an alerting policy with a log-based metric, a custom IAM role. |
| 4 | Timed mock test on Monday; review wrong answers by section and re-study weak guides Tuesday–Thursday; second mock on Friday; cheat sheet and missed-question review over the weekend; sit the exam early the following week. |
8-week plan — beginners and career changers
For candidates new to cloud or to Google Cloud. About 1 hour a day on weekdays, 2–3 hours at weekends. The extra time goes to foundations and lab repetition.
| Week | Focus |
|---|---|
| 1 | Cloud foundations: read the Google Cloud documentation overview, set up a free-tier project, and complete the Cloud Engineer learning path introduction. No exam guides yet — learn the console first. |
| 2 | Guides 1–2 (hierarchy, billing). Lab: build the hierarchy, budgets, and billing export. Repeat until the console navigation feels natural. |
| 3 | Guides 3–5 (planning). Focus on the comparison tables: compute options, storage classes, database choices, load balancer types. |
| 4–5 | Guides 6–10 (deploying), one guide every 2–3 days. Lab every weekend: deploy each service by hand, then again from the command line. |
| 6 | Guides 11–13 (operations and monitoring). Lab: snapshots, log-based alerts, Cloud NAT, subnet expansion. |
| 7 | Guide 14 (IAM) plus a full re-read of the two guides you found hardest. First timed mock test at the end of the week. |
| 8 | Review mock results by section; re-study weak areas; second mock mid-week; cheat sheet and missed questions in the final days. Sit the exam when you score comfortably above 80% on the mock. |
Study tips that matter for this exam
Lab everything. The exam asks what you would do, not what you can define. Creating a MIG, deploying to GKE, writing a firewall rule, and setting up an alert are all things you should have done with your own hands before exam day. Learn the comparisons, not the lists. Most questions ask you to choose between services — Cloud Run vs Cloud Functions, Cloud SQL vs Spanner, regional vs zonal — so the comparison tables in the guides are the highest-value revision material. Read the constraint. Every scenario question contains the word or phrase that decides the answer: "lowest cost", "must survive a zone failure", "no server management", "least privilege". Find it before reading the options. Use the mock honestly. Take it timed, in one sitting, without notes — and treat a score below 80% as a signal to re-study, not to book the exam and hope.