Google Cloud Associate Cloud Engineer study guide

How to use this guide

What to focus on:

• Build the resource hierarchy: organisation, folders, projects, and what each level is for
• Enable APIs, set up billing accounts, and link projects to the right one
• Configure billing budgets, alerts and exports, and know who can see them
• Install and configure the Cloud SDK, and manage gcloud configurations and accounts

What to focus on:

• Size compute to the workload and use the pricing calculator before committing
• Choose between Compute Engine, GKE, Cloud Run and Cloud Functions on operational overhead
• Match the storage product to the access pattern: Cloud Storage classes, Cloud SQL, Spanner, Bigtable, Firestore, BigQuery
• Plan VPC layout, subnets and IP ranges, and know what cannot be changed later

What to focus on:

• Launch and manage Compute Engine instances, templates, managed instance groups and autoscaling
• Create GKE clusters and node pools, and deploy workloads with kubectl
• Deploy revisions to Cloud Run and Cloud Functions, and wire up their triggers
• Load data into storage and database products, and stand up Pub/Sub and Dataflow paths
• Create VPCs, firewall rules, load balancers and Cloud DNS records
• Deploy the same resources through infrastructure as code with Terraform

What to focus on:

• Manage instance lifecycle, disks, snapshots and images, and resize live resources
• Operate GKE: scale node pools and workloads, roll out updates, read pod state
• Manage storage lifecycle rules, database backups and restores
• Use Cloud Monitoring, Cloud Logging, Error Reporting and Cloud Trace to find what broke
• Build alerting policies and log sinks, and know where each signal lands

What to focus on:

• Apply IAM roles at the right level: primitive, predefined and custom, and why custom is a last resort
• Grant least privilege, and understand how policies inherit down the hierarchy
• Create and manage service accounts, keys and impersonation
• Assign service accounts to resources, and view audit logs to answer who did what

Common mistakes

• ✕Studying products instead of procedures. The exam asks which command or console path achieves a result, and reading about a service does not produce that answer.
• ✕Never touching the gcloud CLI. Questions quote real flags and subcommands, and they are hard to reason about from documentation alone.
• ✕Skimming IAM. Role types, inheritance down the hierarchy and service-account impersonation together carry 17.5% and are where careless answers cluster.
• ✕Treating the deployment domain as one topic. At 25% it spans Compute Engine, GKE, Cloud Run, Cloud Functions, data, networking and Terraform, each with its own subsection.
• ✕Reaching for the most powerful compute option. The exam consistently rewards the choice with the least operational overhead that still meets the stated requirement.

Exam-day tips

• ✓Read the constraint before the options. Budget, latency, region or compliance usually decides between two configurations that would both work.
• ✓Count the selections asked for. Multiple-select items state how many to pick, and a partial selection earns nothing.
• ✓Prefer the managed option unless the scenario gives an explicit reason to self-manage.
• ✓Watch the scope of a permission question. The same role means different things at organisation, folder and project level.
• ✓Two hours for 50 to 60 questions is comfortable. Flag the long scenarios and come back rather than stalling on them.

How to know you’re ready

One good practice score can be luck. What counts is scoring at or above the real pass mark (Not published by Google) across several full-length sets in a row, with no single domain trailing far behind the others. Kwizza tracks your per-domain readiness automatically as you practice.