Google Cloud · ACE

Google Associate Cloud Engineer Exam: Complete Guide

Current Google Associate Cloud Engineer exam guide covering the $125 fee, two-hour format, 50–60 questions, four domains, hands-on prep, and renewal.

Last verified September 6, 2026

ACE exam at a glance

Facts last verified September 6, 2026

Domain breakdown

Who should take the Associate Cloud Engineer exam?

Google's Associate Cloud Engineer certification is for practitioners who deploy and secure applications, services, and infrastructure; monitor projects; and keep solutions operating against performance goals. Typical candidates include cloud engineers, systems administrators, platform engineers, support engineers, and developers with infrastructure responsibilities.

There are no formal prerequisites. Google recommends at least six months of hands-on Google Cloud experience. That recommendation is meaningful: the exam asks about operational workflows, gcloud commands, console tasks, IAM, service choice, deployment, monitoring, and troubleshooting rather than only cloud definitions.

The current English blueprint is version 4.0. It incorporates modern services, infrastructure as code, database fleet management, Google Cloud Observability, Gemini Cloud Assist, and Active Assist. Make sure older courses map to this four-section guide rather than the previous five-section outline.

Skills measured on the Associate Cloud Engineer exam

The current official exam guide became active for English exams on June 30. The weights are approximate. Google can update service details, so use the guide as a scope boundary and current product documentation for implementation.

Setting up a cloud solution environment (~23%)

Create and organize resources through organizations, folders, and projects. Apply organization policies, enable APIs, manage users and groups through Cloud Identity, grant IAM roles, inspect quotas, and confirm whether products are available in required locations.

Understand standalone organizations, initial networking, and observability setup. Cloud Asset Inventory helps search and analyze resources, while Gemini Cloud Assist may help interpret state. AI assistance does not remove the need to validate commands, permissions, or impact.

Billing work includes creating and linking billing accounts, configuring budgets and alerts, and exporting billing data. A budget does not impose a hard spending cap by default. Know which account, project, role, and export destination is involved in each task.

Planning and implementing a cloud solution (~30%)

This largest section combines selection and deployment. For compute, compare Compute Engine, Google Kubernetes Engine, Cloud Run, and Cloud Run functions by workload control, portability, scaling, events, and operational effort. Implement VM instances, managed instance groups, autoscaling, OS Login, VM Manager, Spot VMs, and suitable disks.

For GKE, know kubectl, Autopilot versus Standard implications, regional and private clusters, container deployment, and Artifact Registry. Serverless tasks include deploying applications and handling events from Pub/Sub, Cloud Storage, and Eventarc.

Choose data and storage services by access pattern. The guide names Cloud SQL, BigQuery, Firestore, Spanner, Bigtable, AlloyDB, Dataflow, Pub/Sub, Managed Service for Apache Kafka, Memorystore, Cloud Storage, Filestore, and NetApp Volumes. Understand loading methods, storage classes, and multi-region redundancy rather than treating every database as interchangeable.

Networking includes custom VPCs, subnets, Shared VPC, Cloud Next Generation Firewall policies, secure tags, service accounts, VPN, peering, Interconnect, load balancers, and Network Service Tiers. Connectivity options differ in transitivity, throughput, encryption, and ownership.

Infrastructure as code includes Terraform, Config Connector, Helm, and Google's foundation tooling. Plan state, versioning, review, execution, and updates so deployment is repeatable and recoverable.

Ensuring successful operation of a cloud solution (~27%)

Operate Compute Engine instances, snapshots, images, and inventory. For GKE, inspect clusters, nodes, Pods, Services, StatefulSets, Artifact Registry access, node pools, horizontal and vertical Pod autoscaling, and Autopilot resource requests. Manage Cloud Run versions, traffic splitting, and autoscaling.

Storage operations include object security and lifecycle policies. Database and analytics work includes executing queries, estimating storage cost, backing up and restoring supported databases, reviewing Dataflow and BigQuery job status, and using Database Center to manage the database fleet.

Network operations cover subnet expansion, static addresses, routes, Cloud DNS, and Cloud NAT. Address ranges and route changes require care because a small edit can overlap or redirect traffic.

Observability includes Cloud Monitoring alerts and custom metrics, Cloud Logging filters, log buckets, analytics, routers, exports, diagnostics, Personalized Service Health, Ops Agent, Managed Service for Prometheus, and audit logs. Use Active Assist for optimization recommendations and Gemini Cloud Assist where the guide specifies, while independently confirming actions.

Configuring access and security (~20%)

Manage IAM allow policies and distinguish basic, predefined, and custom roles. Prefer predefined roles with the minimum required permissions; basic roles are usually too broad for production. Understand hierarchy and policy inheritance when a principal receives access unexpectedly.

Service-account work includes creation, IAM assignment, attaching accounts to resources, managing access to the account itself, impersonation, and short-lived credentials. Distinguish using a service account from administering or impersonating one—the required roles differ.

For GKE workloads, use supported identity patterns instead of distributing service-account keys. Practice diagnosing PERMISSION_DENIED by identifying the principal, resource, permission, policy level, and credential actually used.

How to prepare for Associate Cloud Engineer

Create a sandbox project with a budget alert. Use the console and gcloud to enable APIs, assign IAM, deploy a VM, configure a managed instance group, deploy Cloud Run, create a storage bucket with lifecycle rules, and build a small VPC. Record the command and resulting state.

Add GKE or guided labs if budget permits. Deploy a workload, inspect Pods and Services, configure autoscaling, and review logs and metrics. Use Terraform for a subset of resources and practice a safe update and destroy operation only inside the sandbox.

Introduce failures: remove an IAM permission, break a firewall path, fill an address range, fail a health check, and deploy a bad revision. Locate evidence and recover. Map every exercise to the v4.0 guide and close untouched objectives with Google documentation or Skills labs.

Associate Cloud Engineer practice questions

Good questions specify current state, business goal, and operational constraint. Look for the simplest Google-recommended action with least privilege and minimal manual work. Note whether the question asks what to do first, which command is correct, or which service fits.

Use Google's sample questions and objective-aligned practice, not dumps. Unauthorized live content violates exam terms and does not prepare you for new service or command variations.

Associate Cloud Engineer compared with Professional exams

Associate Cloud Engineer tests implementation and daily operations across core Google Cloud services. Professional Cloud Architect goes deeper into requirements and architecture, while Professional Cloud DevOps Engineer emphasizes delivery, reliability, and observability. ACE is a useful starting point but is not a formal prerequisite.

Career value of Associate Cloud Engineer

The credential aligns with junior-to-mid cloud operations and engineering work. It is most useful when paired with a project showing resource hierarchy, least-privilege IAM, infrastructure as code, deployment, monitoring, backup, and cost control.

Google Cloud now provides several renewal routes, including a shorter exam or designated learning. Keep working from current documentation because product names and recommended workflows evolve during the three-year validity period.

Exam-day notes

• The standard exam lasts two hours and contains 50–60 questions.
• The registration fee is $125 plus applicable tax.
• Online-proctored and test-center delivery are available.
• Google does not publish a numeric passing score.
• Read the current language-specific guide; update dates can differ by language.

Prep resources

← More Google Cloud exams