Google ACE Study Plan 2026 — 6 Weeks to Pass (Hour-by-Hour)

Most ACE study plans you find online are dishonest in one of two directions: they tell you 2 weeks is enough (it is not, unless you already work in GCP every day), or they tell you 4 months is needed (it is not, unless you have never used a cloud provider). This plan is calibrated for the actual median candidate — an engineer, SRE, or DevOps practitioner who has used AWS or Azure before and now needs to add Google Cloud to their toolkit.

The structure is six weeks of roughly 9 hours of study per week. It sequences the domains in roughly the order GCP itself uses, builds hands-on reps alongside reading, and front-loads the highest-weight Domain 3 content so you have a buffer.

Plan assumptions

This plan assumes you have:

• Some prior cloud experience on AWS, Azure, or another provider (you understand what a VPC, an IAM role, and a load balancer are).
• Approximately 9 hours per week available (think 1 hour weekday mornings + a 4-hour weekend block).
• A free-tier Google Cloud account (the $300 trial). You will not exhaust the credit on this plan.
• Access to the CertSharp ACE question bank (500 questions). The free tier covers 30 questions; the full bank is $11.99 lifetime.

If those assumptions do not match you, jump to Variations for the 4-week and 10-week versions.

Before week 1 — setup (about 2 hours)

1. Create a GCP account and activate the $300 free trial. Use a personal Google account, not a corporate one (corporate IAM constraints will trip you up).
2. Install the gcloud CLI locally. Run gcloud init and authenticate.
3. Create a CertSharp account and run a 10-question diagnostic across all five domains. Note your weakest domain — you will weight effort toward it in weeks 2-5.
4. Skim Google's official ACE exam guide end-to-end. Do not memorise; just understand the shape.
5. Read the Google ACE Exam Guide 2026 for the exam format and the ACE Roadmap 2026 for the domain breakdown.

Week 1 — Foundations + Domain 1 (Setting up environment)

Goal: understand the GCP resource hierarchy and get fluent with the gcloud CLI.

Week 1 totals: ~8.5 hours, 60 CertSharp questions, 1 lab. Target accuracy on Domain 1 questions by Sunday: 75%+.

Week 2 — Compute deep dive (the biggest week)

Goal: know cold when to pick GCE, GKE, Cloud Run, App Engine, or Cloud Functions.

Week 2 totals: ~9 hours, 90 CertSharp questions across Domain 2 + Domain 3 compute, 2 labs. End-of-week: book your exam for the end of week 6.

See Compute Engine vs GKE vs Cloud Run for the decision tree these questions test.

Week 3 — Storage and databases

Goal: Cloud Storage classes and lifecycle, Cloud SQL operations, BigQuery basics, Pub/Sub basics.

Week 3 totals: ~9 hours, 75 CertSharp questions across Domains 2 + 3, 2 labs.

Week 4 — Networking

Goal: VPC, subnets, firewall rules, peering, load balancers, Cloud NAT.

Week 4 totals: ~9 hours, 60 CertSharp questions, 1 lab. Networking is dense — see GCP Networking Fundamentals for the concept refresher.

Week 5 — IAM, security, monitoring, logging

Goal: Domain 4 + Domain 5 combined are 40% of the exam. This is the most decisive week.

Week 5 totals: ~9.5 hours, 80 CertSharp questions, 3 labs. See GCP IAM Explained for the IAM concept refresher.

Week 6 — Mocks and weak spots

Goal: two full-length timed mocks, gap-drill the weak domains, taper before exam day.

Week 6 totals: ~11 hours, 2 mocks + 50 targeted questions, 1 lab.

A realistic daily rhythm

Most candidates who pass on this plan run something like:

• Weekday mornings (45-60 min before work): 1 topic, 15-20 practice questions, read the explanations.
• Weekday evenings (optional, 30-45 min): only if you missed a morning. Avoid stacking heavy material at 10pm.
• Saturday block (3-4 hrs): 1 hands-on lab + 30-50 practice questions on that lab's domain.
• Sunday off. Rest matters more than candidates realise. Trying to study 7 days a week leads to skim-reading and false confidence.

Two hours of focused study beats four hours of distracted study. Phone in another room while you study; treat the practice-question explanations as the most valuable part (not the question itself).

The 10 hands-on labs

Reading is not enough for ACE. Run all 10 of these in your free-tier GCP account:

1. Lab 1 (Week 1): Create project, link billing, enable APIs, deploy + SSH into an e2-micro VM, set a budget alert.
2. Lab 2 (Week 2): Build a custom VM image, instance template, deploy a managed instance group with autoscaling.
3. Lab 3 (Week 2): Create a GKE Autopilot cluster, deploy 2-replica nginx, expose via LoadBalancer service.
4. Lab 4 (Week 3): Cloud Storage bucket with lifecycle policy (Standard → Nearline after 30 days). Signed URL.
5. Lab 5 (Week 3): Cloud SQL Postgres with read replica. Demonstrate failover.
6. Lab 6 (Week 4): Custom-mode VPC, 2 subnets in different regions, firewall rule allowing internal traffic by tag, Cloud NAT for a private VM.
7. Lab 7 (Week 5): Custom IAM role with 2 specific permissions, bind to a service account, attach SA to a VM.
8. Lab 8 (Week 5): Uptime check on a public URL, email alert at 99% SLO.
9. Lab 9 (Week 5): Log sink exporting Cloud Run logs to BigQuery, run a SQL query against exported logs.
10. Lab 10 (Week 6): Cloud Run service with 90/10 traffic split between two revisions.

Each lab should take 30-90 minutes the first time you do it. Do not skip them. Several exam questions show command output or a YAML manifest and ask what is wrong — you will recognise these faster if you have actually run the commands.

How to use full-length mocks

Two mocks are non-negotiable. Both must be run under real exam conditions:

• 50 questions, 120-minute timer, no pause, no notes, no second screen.
• Phone in another room or face-down. Take a bathroom break only if absolutely needed (and stop the timer manually — the real exam pauses too).
• After submitting, read every explanation including questions you got right. The right answer for the wrong reason is a future fail.

Mock 1 target: 70%+. Below 70% means your week 6 needs to extend by a week.
Mock 2 target: 80%+. Below 80% means push the real exam 1-2 weeks; above 85% means you are over-prepared and should book sooner.

Variations: 4-week and 10-week

4-week compressed plan (for engineers with active GCP experience): collapse weeks 1 + 2 into week 1, weeks 3 + 4 into week 2, week 5 into week 3, week 6 stays as-is. Bump hours per week to 14-15. Skip half the hands-on labs only if you have already done those workflows in production. Both mocks remain mandatory.

10-week extended plan (for first-time cloud candidates): add a pre-week 0 doing the entire Google Cloud Skills Boost ACE learning path. Spread weeks 1-5 across 8 weeks at the same total hours (more time to absorb). Add a mid-plan mock at week 5 in addition to the two in week 6.

What if you are behind schedule

The most common failure mode is week 4 — life intervenes and you lose 4-5 days. Here is the recovery playbook:

1. Reschedule the exam. Free up to 72 hours before. Bump it 1-2 weeks; the $200 is not worth a 50% pass odds.
2. Do not skip labs to catch up. Skip the next week's reading instead — labs are where the durable knowledge lives.
3. Do not skip mocks. Even at 65% on mock 1, the diagnostic value is high. You need to know your weak domain before exam day.
4. Cut the “nice to know” tail. If you have to drop content, drop Cloud Trace / Cloud Profiler (2-3 questions at most), App Engine flex (1-2 questions), and the deep BigQuery slot-pricing material. Do not drop IAM, GKE, or VPC.

Frequently asked questions