How to Pass the GCP Associate Cloud Engineer Exam in 2 Weeks

Two weeks can be enough for the Google Cloud Associate Cloud Engineer (ACE) exam if you already know basic cloud concepts and can study 3-4 hours a day. The exam is 2 hours, 50-60 multiple choice and multiple select questions, and costs USD 125 (plus tax). Google does not publish a passing score.

The current exam guide has four sections: setting up a cloud solution environment (~20%), planning and implementing a cloud solution (~30%), ensuring successful operation (~30%), and configuring access and security (~20%). Facts are from the Google pages under Sources, checked October 15, 2026.

This is not a plan for complete beginners. For a longer plan, read the Associate Cloud Engineer study guide.

What do you need before you start?

Before starting your 14-day plan, you should have:

• Basic understanding of cloud computing concepts (IaaS, PaaS, SaaS)
• Some experience with a command line interface
• A Google Cloud account with free trial credits ($300 for 90 days)
• A practice question source, such as the StudyKits ACE app (its questions follow the previous exam outline; update in progress)

If you lack these prerequisites, add one week of foundational study before starting this plan.

What are the ground rules for a 14-day plan?

• Study 3-4 hours every day. No days off.
• Answer at least 50 practice questions per day in StudyKits starting from Day 5.
• Do hands-on labs in Cloud Shell or your local terminal with gcloud CLI. Reading documentation is not enough.
• Review every wrong answer immediately. Understand why the correct answer is correct.
• Focus on gcloud commands. The exam tests practical knowledge, and knowing the CLI demonstrates real experience.

What should you study each day?

Day 1: GCP Fundamentals and IAM (3.5 hours)

Study (1.5 hours):

• GCP global infrastructure: regions, zones, multi-region
• Resource hierarchy: Organization, Folders, Projects, Resources
• Billing accounts and budgets
• IAM: roles (basic, predefined, custom), members, policies, service accounts

Hands-on (1.5 hours):

gcloud projects list
gcloud projects create my-test-project --name="Test Project"
gcloud config set project my-test-project

gcloud iam roles list --filter="name:roles/compute"
gcloud projects get-iam-policy my-test-project
gcloud projects add-iam-policy-binding my-test-project \
  --member="user:test@example.com" --role="roles/viewer"

gcloud iam service-accounts create my-sa --display-name="My SA"
gcloud iam service-accounts keys create key.json \
  --iam-account=my-sa@my-test-project.iam.gserviceaccount.com

Practice (30 min): 20 questions on IAM and project management in StudyKits.

Day 2: Compute Engine (3.5 hours)

Study (1 hour):

• Machine types: general-purpose, compute-optimized, memory-optimized, custom
• Images, snapshots, instance templates, managed instance groups (MIGs)
• Preemptible and spot VMs
• Startup scripts and metadata

Hands-on (2 hours):

gcloud compute instances create my-vm \
  --zone=us-central1-a --machine-type=e2-medium \
  --image-family=debian-12 --image-project=debian-cloud

gcloud compute instances list
gcloud compute ssh my-vm --zone=us-central1-a

gcloud compute instance-templates create my-template \
  --machine-type=e2-small --image-family=debian-12 \
  --image-project=debian-cloud

gcloud compute instance-groups managed create my-mig \
  --template=my-template --size=2 --zone=us-central1-a

gcloud compute instance-groups managed set-autoscaling my-mig \
  --zone=us-central1-a --max-num-replicas=5 --min-num-replicas=1 \
  --target-cpu-utilization=0.6

Practice (30 min): 25 questions on Compute Engine.

Day 3: GKE and Cloud Run (3.5 hours)

Study (1 hour):

• GKE: clusters, nodes, pods, services, deployments
• GKE Standard vs Autopilot
• Cloud Run: containerized serverless, concurrency, autoscaling
• Cloud Functions: event-driven, triggers, runtimes

Hands-on (2 hours):

gcloud container clusters create my-cluster \
  --zone=us-central1-a --num-nodes=2 --machine-type=e2-small

gcloud container clusters get-credentials my-cluster \
  --zone=us-central1-a

kubectl create deployment nginx --image=nginx
kubectl expose deployment nginx --port=80 --type=LoadBalancer
kubectl get services
kubectl scale deployment nginx --replicas=3

gcloud run deploy my-service --image=gcr.io/cloudrun/hello \
  --region=us-central1 --allow-unauthenticated

Practice (30 min): 25 questions on GKE and serverless.

Day 4: Networking (4 hours)

Study (1.5 hours):

• VPC: subnets, firewall rules, routes
• Shared VPC and VPC peering
• Load balancing: HTTP(S), TCP/UDP, internal, network
• Cloud NAT, Cloud DNS, Cloud CDN
• Cloud VPN, Cloud Interconnect

Hands-on (2 hours):

gcloud compute networks create my-vpc --subnet-mode=custom
gcloud compute networks subnets create my-subnet \
  --network=my-vpc --region=us-central1 --range=10.0.0.0/24

gcloud compute firewall-rules create allow-ssh \
  --network=my-vpc --allow=tcp:22 --source-ranges=0.0.0.0/0

gcloud compute firewall-rules create allow-http \
  --network=my-vpc --allow=tcp:80 --target-tags=web-server

gcloud compute addresses create my-ip --region=us-central1
gcloud compute forwarding-rules list

Practice (30 min): 30 questions on networking.

Day 5: Storage and Databases (3.5 hours)

Study (1 hour):

• Cloud Storage: buckets, objects, storage classes, lifecycle policies, ACLs vs IAM
• Cloud SQL: MySQL, PostgreSQL, SQL Server, HA, read replicas
• Cloud Spanner, Firestore, Bigtable, Memorystore — when to use each
• Persistent disks: standard, SSD, balanced

Hands-on (1.5 hours):

gcloud storage buckets create gs://my-unique-bucket-name \
  --location=us-central1

gcloud storage cp local-file.txt gs://my-unique-bucket-name/
gcloud storage ls gs://my-unique-bucket-name/

gcloud sql instances create my-db --database-version=POSTGRES_15 \
  --tier=db-f1-micro --region=us-central1

gcloud sql databases create mydb --instance=my-db

Practice (1 hour): 50 questions across all topics covered so far.

Day 6: Monitoring, Logging, and Operations (3 hours)

Study (1 hour):

• Cloud Monitoring: metrics, dashboards, alerting policies, uptime checks
• Cloud Logging: log sinks, log-based metrics, log routing
• Cloud Trace, Error Reporting, Cloud Profiler
• Cloud Debugger (deprecated — know this)

Hands-on (1 hour):

gcloud logging read "resource.type=gce_instance" --limit=10
gcloud logging sinks create my-sink \
  storage.googleapis.com/my-log-bucket --log-filter="severity>=ERROR"

gcloud monitoring channels list
gcloud monitoring policies list

Practice (1 hour): 50 questions across all topics.

Day 7: Deployment and Management Tools (3 hours)

Study (1 hour):

• Cloud Build: build steps, triggers, cloudbuild.yaml
• Artifact Registry and Container Registry
• Cloud Deployment Manager and Terraform basics
• Cloud Source Repositories
• gcloud config configurations for managing multiple projects

Hands-on (1 hour):

gcloud config configurations create dev-config
gcloud config set project dev-project
gcloud config set compute/zone us-central1-a

gcloud config configurations create prod-config
gcloud config set project prod-project
gcloud config set compute/zone us-east1-b

gcloud config configurations list
gcloud config configurations activate dev-config

gcloud builds submit --tag gcr.io/my-project/my-app .

Practice (1 hour): 50 questions. Focus on weak areas.

Day 8: Review and Gap Analysis (4 hours)

• Review StudyKits analytics to identify your weakest topics
• Re-study the two weakest areas in depth
• Re-do hands-on labs for services you scored lowest on
• 60 practice questions with a focus on weak areas

Day 9: Full Practice Exam 1 (3.5 hours)

• Take a full-length 50-question practice exam in StudyKits, timed to 2 hours
• Score yourself and review every incorrect answer
• For each wrong answer, write down the correct answer and why
• Study the underlying concepts for any topic where you scored below 70%

Day 10: Deep Review of Weak Areas (3.5 hours)

• Based on Practice Exam 1 results, deep dive into your two weakest domains
• Re-read documentation for services you got wrong
• Do additional hands-on practice with those services
• 60 practice questions focused on weak areas

Day 11: Full Practice Exam 2 (3.5 hours)

• Take another full-length practice exam
• Target improvement in areas that were weak on Practice Exam 1
• Review all incorrect answers
• If scoring above 80% consistently, you are on track

Day 12: gcloud CLI Command Review (3 hours)

• Review all gcloud commands you have used over the past 11 days
• Practice running commands from memory without looking at notes
• Focus on commands for: compute, container, sql, storage, iam, config
• Know the pattern: gcloud [GROUP] [SUBGROUP] [ACTION] [NAME] [FLAGS]
• 50 practice questions

Day 13: Final Practice Exam and Review (4 hours)

• Take a final full-length practice exam
• You should be scoring 80%+ consistently
• Review any remaining weak areas
• Light review of all major topics — do not cram new material
• 30 practice questions as a light warm-up

Day 14: Exam Day

• Light review in the morning (30 minutes maximum). Do not study new material.
• Review your notes on gcloud commands and service selection criteria
• Arrive early, or check your online-proctoring setup the day before

Which gcloud commands should you know?

These command groups come up across the exam guide sections. Know what each does and when to use it:

# Project and config
gcloud config set project PROJECT_ID
gcloud config list
gcloud config configurations activate CONFIG_NAME

# Compute
gcloud compute instances create/delete/list/describe
gcloud compute instance-groups managed create/set-autoscaling
gcloud compute firewall-rules create/list
gcloud compute networks create/subnets create

# GKE
gcloud container clusters create/get-credentials/delete
kubectl create deployment/expose/scale/get

# Storage
gcloud storage buckets create/ls
gcloud storage cp/mv/rm

# SQL
gcloud sql instances create/list
gcloud sql databases create

# IAM
gcloud iam service-accounts create
gcloud projects add-iam-policy-binding
gcloud iam roles create

What if two weeks is not enough?

If you are consistently scoring below 80% on practice exams by Day 11, consider pushing your exam date back by one week. An extra week costs less than a retake fee and a waiting period.

Signs you need more time:

• You cannot explain the difference between VPC peering and Shared VPC
• You confuse Cloud SQL, Spanner, Firestore, and Bigtable use cases
• You struggle with gcloud command syntax
• Networking concepts (subnets, firewall rules, load balancing) feel unclear

When should you book the ACE exam on a 2-week plan?

Book the exam for Day 14 only if your Day 11 practice scores meet our rule of thumb: 80% or more on fresh questions, with no domain below 70%. Read the official exam guide once before Day 1 so you know the four sections, then follow the schedule. Each day builds on the one before.

Frequently asked questions

How long is the Associate Cloud Engineer exam?

2 hours, with 50-60 multiple choice and multiple select questions.

What is the ACE passing score?

Google does not publish one. Before you book, aim for our rule of thumb: 80% or more on fresh questions, with no domain below 70%.

How much does the ACE exam cost?

USD 125, plus tax where applicable.

How long is the ACE certification valid?

3 years. Google also offers a 1-hour, 20-question renewal exam (USD 75).

Can I take the exam in Japanese?

Yes. ACE is offered in English, Japanese, Spanish and Portuguese.

Keep reading

• Google Cloud Certification Path: Which Exam to Take First
• Spaced Repetition for Certification Exams: How It Helps
• Google Cloud certification hub: every Google Cloud exam guide and practice app

Sources

Checked October 15, 2026:

• Google Cloud Associate Cloud Engineer
• ACE exam guide (PDF)
• Google Cloud certification FAQ