ACE — (Google Cloud Certified: Associate Cloud Engineer – ) Study Plan
A practical study plan for the Google Cloud Certified: Associate Cloud Engineer – ACE exam, with 7-day, 14-day, 30-day, and 60/90-day preparation paths.
Study Plan orientation
This Study Plan is for candidates preparing for the Google Cloud (Google Cloud Certified: Associate Cloud Engineer – ACE) exam, exam code ACE. It is written for practical preparation: diagnostics, objective-based review, hands-on cloud reasoning, missed-question analysis, timed mock exams, and final-week readiness checks.
The ACE exam expects you to understand how to deploy, manage, monitor, secure, and troubleshoot solutions on Google Cloud. Your study time should therefore include both concept review and applied scenario practice.
Use this plan as an independent preparation schedule. It is not affiliated with Google Cloud.
Which plan should you use?
Choose the shortest plan only if you already have meaningful Google Cloud experience. If you are new to Google Cloud, use the 60/90-day path even if you have taken other cloud exams.
| Your situation | Best plan | Daily time target | Main goal |
|---|---|---|---|
| Exam is in one week | 7-day final review | 2.5-4 hours | Find weak areas, tighten exam timing, stop knowledge leaks |
| Exam is in two weeks | 14-day focused plan | 2-3 hours | Cover the full objective set quickly, then drill weak areas |
| Exam is in one month | 30-day balanced plan | 1.5-2.5 hours | Build steady coverage with mocks, review loops, and hands-on reinforcement |
| You are starting early | 60/90-day full path | 45-90 minutes | Build durable Google Cloud operating knowledge and exam confidence |
| You have strong cloud experience but weak Google Cloud specifics | 14 or 30 days | 1.5-3 hours | Translate general cloud knowledge into Google Cloud service choices |
| You are new to IAM, networking, or operations | 60/90 days | 60-90 minutes | Build fundamentals before heavy mock testing |
What to study for ACE
Organize your preparation around the types of tasks an Associate Cloud Engineer should be able to perform.
| Area | What to practice | Example study actions |
|---|---|---|
| Cloud environment setup | Projects, billing concepts, resource hierarchy, Cloud Shell, CLI, SDK, permissions | Trace how an organization, folders, projects, and resources relate; practice identifying where configuration belongs |
| IAM and access control | Principals, roles, service accounts, least privilege, policy troubleshooting | Decide which identity should receive which permission; review service account use cases |
| Compute | Compute Engine, managed instance groups, Cloud Run, Kubernetes Engine basics, App Engine concepts | Compare deployment options for common workloads |
| Storage and databases | Cloud Storage, persistent disks, Filestore concepts, Cloud SQL, Firestore, BigQuery basics | Match storage/database services to access pattern, scaling, and management needs |
| Networking | VPCs, subnets, firewall rules, routes, load balancing concepts, hybrid connectivity basics | Diagnose why traffic is blocked or why a workload is not reachable |
| Operations | Cloud Monitoring, Cloud Logging, alerting, dashboards, error reporting concepts | Identify what metric, log, or alert would help troubleshoot a scenario |
| Security and governance | IAM, encryption concepts, organization policies, audit logs, secrets handling | Apply least privilege and identify safer operating choices |
| Cost and resource management | Billing accounts, budgets, labels, committed/managed resource choices at a high level | Choose cost-aware configurations without memorizing prices |
| Deployment and troubleshooting | Deploying apps, updating workloads, rollback concepts, interpreting symptoms | Work through scenario questions slowly before timing yourself |
Baseline diagnostic: do this before choosing daily depth
Before starting any plan, spend one session measuring your current readiness.
| Step | Time | Action |
|---|---|---|
| 1 | 15 min | Review the ACE exam objective areas at a high level |
| 2 | 60-90 min | Take a mixed diagnostic practice set without notes |
| 3 | 30-45 min | Categorize missed and guessed questions by topic |
| 4 | 20 min | Create a weak-area list with no more than 5 priority areas |
| 5 | 10 min | Pick the plan below and block study sessions on your calendar |
Do not treat the first diagnostic score as your identity. Use it to decide where your time should go.
Daily practice rhythm
Use the same daily structure regardless of plan length. Adjust the number of blocks based on available time.
| Block | Time | What to do | Output |
|---|---|---|---|
| Warm-up recall | 10 min | Write down key services, IAM rules, networking concepts, or commands from memory | Short recall notes |
| Focused concept review | 30-60 min | Study one objective area, not the whole exam | One-page summary or service comparison |
| Applied practice | 30-60 min | Answer scenario questions or walk through hands-on decisions | Marked questions with reasoning |
| Missed-question review | 20-40 min | Analyze wrong, guessed, and slow questions | Error log updates |
| Final recap | 5-10 min | List what to review tomorrow | Next-day target |
If you have only 45 minutes, do this:
- 10 minutes recall.
- 25 minutes targeted practice questions.
- 10 minutes missed-question review.
Missed-question review method
Most ACE improvement comes from reviewing why you chose an answer, not just reading explanations.
Use this table for every missed, guessed, or slow question.
| Field | What to record |
|---|---|
| Topic | IAM, compute, networking, storage, operations, deployment, cost, etc. |
| Question type | Service selection, troubleshooting, command/configuration, security, architecture scenario |
| Your mistake | Misread, did not know service, confused two services, missed keyword, over-engineered |
| Correct rule | The principle that would help you answer a similar question |
| Retest date | Date to retry a similar question |
| Confidence | Low, medium, or high after review |
Common ACE error patterns to watch
| Error pattern | How to fix it |
|---|---|
| Choosing an overly complex architecture | Prefer managed, simple, operationally appropriate services when the scenario calls for them |
| Treating all permissions as broad project-level grants | Think in least privilege and resource scope |
| Confusing identities and resources | Identify who or what needs access before choosing an IAM answer |
| Ignoring networking direction | Check source, destination, ports, firewall rules, routes, and load balancer role |
| Memorizing services without use cases | Build comparison tables: when to use, when not to use, operational concern |
| Reading logs/monitoring questions too quickly | Identify symptom, signal needed, and where that signal would appear |
Timed mock exam strategy
Timed mock exams are useful only after you have enough coverage to learn from them.
| Plan length | First timed mock | Second timed mock | Final timed mock |
|---|---|---|---|
| 7 days | Day 1 or 2 | Day 4 or 5 | Day 6, if stamina is uncertain |
| 14 days | Day 3 or 4 | Day 9 or 10 | Day 12 or 13 |
| 30 days | Day 8-10 | Day 18-22 | Day 26-28 |
| 60/90 days | After first full pass | Midpoint | Final 7-10 days |
How to review a mock
Do not simply check the score and move on.
- Mark every question as correct, wrong, guessed, or slow.
- Review wrong and guessed questions first.
- Group errors by objective area.
- Identify your top 3 recurring mistakes.
- Schedule the next two study sessions around those mistakes.
- Retake only after you have completed targeted review.
7-day final review plan
Use this if your exam is within one week. This is not the time to learn every topic from scratch. Your goal is to remove avoidable mistakes, reinforce core Google Cloud service choices, and build exam-day timing.
| Day | Main focus | Study actions |
|---|---|---|
| 1 | Diagnostic and triage | Take a mixed timed or semi-timed set. Build a weak-area list. Review IAM, projects, resource hierarchy, and service accounts. |
| 2 | Compute and deployment | Review Compute Engine, managed instance groups, Cloud Run, GKE basics, App Engine concepts, deployment updates, and rollback logic. Drill scenario questions. |
| 3 | Storage, databases, and data services | Compare Cloud Storage, persistent disks, Filestore, Cloud SQL, Firestore, and BigQuery use cases. Practice service-selection questions. |
| 4 | Networking and access troubleshooting | Review VPCs, subnets, firewall rules, routes, load balancing concepts, and private/public access patterns. Drill troubleshooting scenarios. |
| 5 | Operations, monitoring, logging, and cost | Review Cloud Monitoring, Cloud Logging, alerting, audit logs, budgets, labels, and resource management concepts. Take a timed mock if not yet done. |
| 6 | Weak-area sprint | Rework missed questions. Build final reference sheets for IAM, networking, compute choices, storage choices, and operations. Do one shorter timed set. |
| 7 | Light final review | Review notes, missed-question rules, and service comparison tables. Stop heavy new material. Prepare exam logistics and rest. |
7-day priorities
Spend more time on:
- IAM roles, service accounts, and least privilege.
- VPC firewall and connectivity troubleshooting.
- Choosing the right compute or storage service for a scenario.
- Monitoring/logging signals for operational problems.
- Deployment and configuration steps at a practical level.
Avoid:
- Deep product internals beyond the ACE scope.
- Memorizing exact pricing or quotas.
- Starting large new labs in the final 24 hours.
- Taking multiple full mocks back-to-back without review.
14-day focused plan
Use this if you have two weeks and can study most days. The goal is one fast full pass, followed by timed practice and weak-area repair.
| Day | Focus | Actions |
|---|---|---|
| 1 | Diagnostic | Take a mixed diagnostic. Build an error log and rank weak areas. |
| 2 | Cloud environment setup | Review projects, billing concepts, resource hierarchy, Cloud Shell, Google Cloud CLI, and configuration scope. |
| 3 | IAM and service accounts | Study principals, predefined/custom role concepts, service accounts, least privilege, and policy troubleshooting. Drill IAM scenarios. |
| 4 | Compute services | Compare Compute Engine, managed instance groups, Cloud Run, GKE basics, and App Engine concepts. Practice deployment decisions. |
| 5 | Storage and databases | Review Cloud Storage, persistent disks, Filestore, Cloud SQL, Firestore, and BigQuery basics. Build a service-selection chart. |
| 6 | Networking | Review VPCs, subnets, firewall rules, routes, load balancing concepts, and hybrid connectivity basics. Drill troubleshooting. |
| 7 | Operations | Review Cloud Monitoring, Cloud Logging, alerting, dashboards, audit logs, and error investigation. Practice operations scenarios. |
| 8 | Security and governance | Revisit IAM, organization-level controls, auditability, secrets handling, and secure deployment choices. |
| 9 | Timed mock | Take a timed mock. Review every wrong, guessed, and slow question. |
| 10 | Weak area 1 and 2 | Study your two weakest domains. Create concise rules for recurring question types. |
| 11 | Weak area 3 and mixed drills | Study third weakest area. Complete mixed scenario practice. |
| 12 | Second timed mock | Take another timed mock or long timed set. Review results the same day. |
| 13 | Final repair | Rework missed topics: IAM, networking, compute, storage, monitoring, or deployment. Stop adding broad new material. |
| 14 | Exam readiness | Light review, error log, service comparison notes, exam timing plan, rest. |
30-day balanced plan
Use this if you want enough time for concept review, practice, and correction without rushing. This is the best fit for many working candidates.
Week 1: Baseline and core Google Cloud operating model
| Day | Focus | Actions |
|---|---|---|
| 1 | Diagnostic | Take a mixed diagnostic and create your error log. |
| 2 | Resource hierarchy | Review organizations, folders, projects, billing concepts, labels, and where configuration applies. |
| 3 | CLI and environment setup | Review Cloud Shell, Google Cloud CLI concepts, configurations, project selection, and authentication flow at a practical level. |
| 4 | IAM foundations | Study principals, roles, policies, service accounts, and least privilege. |
| 5 | IAM scenarios | Drill access-control questions and policy troubleshooting. |
| 6 | Mixed review | Revisit missed questions from Days 1-5. |
| 7 | Rest or light recall | Review notes only; no heavy new topic required. |
Week 2: Compute, storage, and databases
| Day | Focus | Actions |
|---|---|---|
| 8 | Compute Engine | Review VM use cases, disks, images, snapshots, startup scripts conceptually, and instance management. |
| 9 | Managed compute | Review managed instance groups, Cloud Run, App Engine concepts, and GKE basics. |
| 10 | Deployment choices | Compare compute options using workload requirements. Practice scenario questions. |
| 11 | Storage | Review Cloud Storage classes conceptually, buckets, object access, persistent disks, and Filestore. |
| 12 | Databases and analytics basics | Review Cloud SQL, Firestore, BigQuery, and when each is appropriate. |
| 13 | Timed mock or long set | Take your first timed mock or long timed practice set. |
| 14 | Mock review | Analyze the mock, update error log, and schedule weak-area repairs. |
Week 3: Networking, operations, and troubleshooting
| Day | Focus | Actions |
|---|---|---|
| 15 | VPC fundamentals | Review VPCs, subnets, regions, routes, and firewall rules. |
| 16 | Connectivity and load balancing | Review load balancing concepts, public/private access, and hybrid connectivity basics. |
| 17 | Networking troubleshooting | Drill scenarios involving blocked traffic, wrong route assumptions, and access paths. |
| 18 | Monitoring and logging | Review Cloud Monitoring, Cloud Logging, metrics, logs, alerts, and dashboards. |
| 19 | Operations scenarios | Practice questions on diagnosing incidents, alerts, and deployment problems. |
| 20 | Security and governance | Review audit logs, IAM review, organization policies conceptually, and secure operations. |
| 21 | Mixed timed set | Complete a timed mixed set and review all misses. |
Week 4: Exam conditioning and weak-area sprint
| Day | Focus | Actions |
|---|---|---|
| 22 | Weak area 1 | Focused review and drills. |
| 23 | Weak area 2 | Focused review and drills. |
| 24 | Weak area 3 | Focused review and drills. |
| 25 | Architecture scenarios | Practice service selection across compute, storage, networking, IAM, and operations. |
| 26 | Timed mock | Take a full timed mock or the longest available timed set. |
| 27 | Mock review | Review deeply. Create final rules for recurring mistakes. |
| 28 | Final content pass | Review comparison tables and error log. Stop adding broad new material after this day. |
| 29 | Light timed drill | Do a shorter timed set, then review only. |
| 30 | Final readiness | Light review, logistics, rest, and exam timing plan. |
60/90-day full preparation path
Use this if you are new to Google Cloud, coming from another cloud platform, or want to build durable operating knowledge instead of only test-taking familiarity.
Phase 1: Foundations and orientation
| Timeframe | Focus | Actions |
|---|---|---|
| Days 1-7 | Baseline and cloud model | Take diagnostic. Review Google Cloud resource hierarchy, projects, billing concepts, regions/zones, and shared responsibility at a high level. |
| Days 8-14 | Environment and CLI | Review Cloud Console, Cloud Shell, Google Cloud CLI concepts, authentication, project configuration, and deployment workflow basics. |
Phase 2: Identity, access, and security
| Timeframe | Focus | Actions |
|---|---|---|
| Days 15-21 | IAM foundations | Study principals, roles, policies, service accounts, and least privilege. Practice IAM scenarios daily. |
| Days 22-28 | Security operations | Review audit logs, secure access patterns, secrets handling concepts, organization policies conceptually, and governance scenarios. |
Phase 3: Core services
| Timeframe | Focus | Actions |
|---|---|---|
| Days 29-35 | Compute | Review Compute Engine, managed instance groups, Cloud Run, App Engine concepts, and GKE basics. Build a compute comparison table. |
| Days 36-42 | Storage and databases | Review Cloud Storage, persistent disks, Filestore, Cloud SQL, Firestore, and BigQuery basics. Drill service-selection questions. |
| Days 43-49 | Networking | Study VPCs, subnets, firewall rules, routes, load balancing concepts, and connectivity troubleshooting. |
| Days 50-56 | Operations | Review Cloud Monitoring, Cloud Logging, alerting, dashboards, error reporting concepts, and operational troubleshooting. |
Phase 4: Integration and exam practice
| Timeframe | Focus | Actions |
|---|---|---|
| Days 57-63 | Mixed scenarios | Practice architecture and troubleshooting questions across all domains. |
| Days 64-70 | First full timed mock | Take a timed mock. Spend at least one full session reviewing it. |
| Days 71-77 | Weak-area repair | Study your lowest-performing areas and rework similar questions. |
| Days 78-84 | Second timed mock | Take another timed mock. Compare error patterns against the first mock. |
| Days 85-90 | Final sprint | Review error log, service comparisons, IAM rules, networking troubleshooting, and operations signals. Stop adding new broad material. |
If using 60 days instead of 90
Compress the path by combining phases:
| Days | Focus |
|---|---|
| 1-7 | Diagnostic, resource hierarchy, environment setup |
| 8-17 | IAM, service accounts, security, governance |
| 18-30 | Compute, storage, databases |
| 31-40 | Networking, monitoring, logging, troubleshooting |
| 41-50 | Mixed scenarios and first timed mock |
| 51-56 | Weak-area repair and second timed mock |
| 57-60 | Final review and exam readiness |
Hands-on concept review for ACE
ACE preparation should include hands-on reasoning, but avoid turning study time into open-ended lab wandering. Keep each hands-on session tied to an exam objective.
| Topic | Hands-on or applied review goal |
|---|---|
| Project and CLI setup | Understand how project selection, authentication, and configuration affect commands and resources |
| IAM | Trace which principal needs access and where a role should be granted |
| Compute | Understand deployment choices, instance management concepts, and managed compute tradeoffs |
| Storage | Compare object, block, file, relational, document, and analytical storage choices |
| Networking | Reason through firewall, subnet, route, and load-balancing symptoms |
| Monitoring/logging | Identify what signal you would check first during an incident |
| Cost/governance | Recognize budget, label, and resource organization patterns |
A useful hands-on session has a clear endpoint:
- “I can explain why this service fits this workload.”
- “I can identify which IAM grant is too broad.”
- “I can troubleshoot why traffic is not reaching the workload.”
- “I can choose which monitoring signal would confirm the problem.”
Service-selection drill
Use this quick drill several times per week.
| Prompt | Your answer should include |
|---|---|
| Which compute service fits this workload? | Runtime model, scaling needs, operational control, deployment style |
| Which storage/database service fits this data? | Data structure, access pattern, consistency/transaction needs, query style |
| How should access be granted? | Principal, role type, scope, service account involvement |
| Why is traffic failing? | Source, destination, firewall, route, load balancer, identity if relevant |
| What should be monitored? | Metric, log, alert, dashboard, or audit signal |
| What is the simpler managed option? | Whether a managed service reduces operational burden |
Final-week rules
During the final week, your job is to stabilize performance.
Keep doing
- Review your missed-question log every day.
- Practice mixed scenario questions.
- Revisit IAM, service accounts, networking, monitoring, and storage/compute selection.
- Use timed sets to maintain pace.
- Sleep and schedule breaks.
Stop doing
- Stop adding broad new material 48 hours before the exam.
- Stop taking full mocks if you will not review them.
- Stop chasing obscure product details outside the ACE objective set.
- Stop memorizing exact prices, quotas, or product limits unless they are part of your own work context.
- Stop switching between too many resources.
Exam-readiness checks
You are likely ready when you can do the following consistently.
| Readiness check | What “ready” looks like |
|---|---|
| IAM reasoning | You can identify the principal, required access, and appropriate scope in a scenario |
| Compute selection | You can compare VM-based, container-based, and managed application options |
| Storage/database selection | You can choose a service based on data type and access pattern |
| Networking troubleshooting | You can reason through firewall, route, subnet, and load-balancing symptoms |
| Operations | You know when to use logs, metrics, alerts, dashboards, and audit information |
| Cost/governance | You understand budgets, labels, resource organization, and basic cost-aware choices |
| Timing | You can finish timed practice without rushing the final questions |
| Review discipline | You can explain why your previous wrong answers were wrong |
Exam-day timing plan
Use a simple pass strategy.
| Pass | Action |
|---|---|
| First pass | Answer questions you can solve confidently. Flag questions that require deeper comparison. |
| Second pass | Return to flagged questions. Eliminate answers that are too broad, too complex, or do not match the scenario. |
| Final pass | Check unanswered items and obvious misreads. Do not change answers without a specific reason. |
When reading a scenario, identify:
- The workload or operational problem.
- The constraint, such as security, availability, simplicity, or cost awareness.
- The Google Cloud service or control being tested.
- The least complicated answer that satisfies the requirement.
Practical next step
Start with a mixed diagnostic practice set, then choose the 7-day, 14-day, 30-day, or 60/90-day path based on your exam date and current weak areas. Keep an error log from the first session and let missed questions drive your daily review.