Google Cloud Associate Cloud Engineer (ACE)

The Associate Cloud Engineer is Google Cloud's hands-on associate certification: deploying and securing applications and infrastructure, monitoring projects, and keeping deployed solutions running. Google recommends around six months of hands-on experience, and the questions are phrased as tasks rather than definitions — which is why rote service lists tend not to survive contact with the paper.

The published exam guide splits into four sections at stated weights: setting up a cloud solution environment (~20%), planning and implementing a cloud solution (~30%), ensuring the successful operation of a cloud solution (~30%), and configuring access and security (~20%). These {modules} modules follow those weights, so the time you spend tracks how the exam is actually weighted rather than how easy a topic is to write questions about.

The hardest part for anyone arriving from another cloud is not the new service names, it is the structural differences. A VPC in Google Cloud is global and its subnets are regional, the reverse of the AWS arrangement. There are no security groups — firewall rules target instances by network tag or by service account. An IAM allow policy hangs on the resource and binds roles to members, rather than being a document attached to a principal, and an inherited grant cannot be narrowed further down the hierarchy. Where the two clouds genuinely differ, these cards teach the difference instead of restating the AWS answer.

Exam details change. Confirm the current sections, price and format against Google's own exam guide before you book, and treat any prep material — this one included — as a companion to hands-on practice rather than a substitute for it. If you are still choosing a cloud, the AWS Cloud Practitioner and Azure AI Fundamentals tracks cover the entry-level certifications on the other two.