Google Cloud Services for ACE Exam (2026)
Passing the Associate Cloud Engineer exam requires more than knowing a list of service names. You need to understand what each service does, when to use it, and how it connects to other parts of Google Cloud. This page introduces the core services that form the backbone of the ACE certification. Use it as a strategic guide—not an encyclopedia—to direct your study toward the most important areas.
CloudCertPro focuses on practical understanding. You won’t find implementation tutorials here, but you will learn the purpose and context of every service you need. For detailed, hands-on technical guides, visit CloudComputingDevPro.
Core Google Cloud Services Overview
The table below lists the services most frequently tested on the ACE exam. Each entry includes its category, primary purpose, and relative exam importance.
| Service | Category | Primary Purpose | Exam Importance |
|---|---|---|---|
| Compute Engine | Compute | Virtual machines (IaaS) with full control | Very High |
| Cloud Storage | Storage | Object storage for unstructured data | Very High |
| Cloud SQL | Database | Managed MySQL, PostgreSQL, SQL Server | High |
| Cloud Run | Compute (Serverless) | Container-to-production in seconds | High |
| Google Kubernetes Engine (GKE) | Compute (Containers) | Managed Kubernetes clusters | High |
| App Engine | Compute (PaaS) | Platform for web apps, automatic scaling | Medium |
| Cloud Functions | Compute (Serverless) | Event-driven serverless functions | Medium |
| Virtual Private Cloud (VPC) | Networking | Isolated software-defined network | Very High |
| Cloud Load Balancing | Networking | Global, scalable traffic distribution | Medium |
| Cloud DNS | Networking | Domain name system service | Medium |
| IAM | Identity & Security | Manage access to resources | Very High |
| Cloud Monitoring | Operations | Visibility into performance and health | Very High |
| Cloud Logging | Operations | Centralized log management | Very High |
| Pub/Sub | Messaging | Asynchronous messaging service | Medium |
| Secret Manager | Security | Store and manage secrets securely | Low |
Compute Services
Google Cloud offers several compute options, each suited to different workloads. The ACE exam tests your ability to choose the right one.
- Compute Engine – Virtual machines on demand. You have full control over the OS, configuration, and networking. Use for lift-and-shift migrations, long-running batch jobs, and any workload that needs a custom environment. Know how to create instances, attach persistent disks, and set up startup scripts.
- App Engine – A fully managed platform for building web applications. You upload code and Google handles the rest. Ideal for standard web apps where you don't want to manage infrastructure. Understand the difference between Standard and Flexible environments.
- Cloud Run – Serverless for containers. Deploy any containerized application and pay only for the resources used during requests. Excellent for stateless, HTTP-driven microservices. You'll need to know how to deploy a container image and manage concurrency settings.
- Cloud Functions – Functions as a Service. Write small pieces of code triggered by events (HTTP requests, Cloud Storage changes, Pub/Sub messages). Great for lightweight automation, data processing, and API backends. Focus on deployment and basic triggers.
- Google Kubernetes Engine (GKE) – Managed Kubernetes. Use when you need container orchestration, service discovery, and advanced scaling. The ACE exam expects you to perform basic GKE tasks: creating a cluster, deploying a workload, and exposing it via a LoadBalancer Service.
Comparison Table:
| Service | When to Use | Management Overhead | Scaling |
|---|---|---|---|
| Compute Engine | Full control, legacy apps, custom OS | High (you manage VMs) | Manual or managed instance groups |
| App Engine | Standard web apps, no server management | Low | Automatic |
| Cloud Run | Containerized microservices, fast deployments | Very Low | Automatic (can scale to zero) |
| Cloud Functions | Event-driven small tasks | Minimal | Automatic per event |
| GKE | Multi-container orchestration, microservices | Medium (cluster management) | Horizontal Pod Autoscaler |
Storage Services
Data is central to almost every cloud application. The ACE exam evaluates your ability to choose the appropriate storage service and configure it correctly.
- Cloud Storage – Unified object storage. Use it for serving website content, storing data for archival, and as a data lake. Know the storage classes: Standard, Nearline, Coldline, Archive. Understand Object Lifecycle policies to automatically move data to cheaper classes or delete it. You must also know how to control access with IAM and signed URLs.
- Persistent Disk – Block storage for Compute Engine and GKE. Boot disks and data disks. Choose between standard (HDD) and SSD for performance. Snapshots provide backup; you should know how to create and restore from them.
- Filestore – Managed file storage (NFS). Use when multiple VMs need shared access to a file system. Less frequent in ACE than the others, but understand its existence.
- Cloud SQL – Managed relational database service (MySQL, PostgreSQL, SQL Server). Backups, replication, and failover are handled automatically. ACE expects you to know how to create an instance, set up a database, and connect from a VM.
Networking Services
Networking knowledge is tested heavily in ACE. You must be able to set up connectivity, secure traffic, and troubleshoot basic issues.
- Virtual Private Cloud (VPC) – A logically isolated network. You define subnets, IP ranges, and firewall rules. Know the difference between auto mode and custom mode VPCs. Subnets are regional, but VPCs are global—a unique Google Cloud feature.
- Firewall Rules – Stateful rules that control traffic to and from VM instances. Rules can be defined using IP addresses or service accounts. You'll need to troubleshoot why a VM can't reach the internet or why an application isn't accessible.
- Cloud Load Balancing – Distributes traffic to healthy backend instances. Google offers global HTTP(S) load balancing, as well as regional TCP/UDP load balancers. For ACE, know when to use a load balancer and how to set up a basic HTTP load balancer with a managed instance group as backend.
- Cloud DNS – Managed DNS service. Create zones and records to map domain names to IP addresses. Essential for any production application, but simple to configure.
- Cloud NAT – Allows VMs in a private subnet to access the internet without external IP addresses. Important for security and exam scenarios.
- Cloud VPN – Encrypted tunnel to an on-premises network or another cloud. ACE only tests basic awareness of the service.
Identity and Security Services
Controlling who can access what is a fundamental responsibility of any cloud engineer.
- IAM (Identity and Access Management) – The policy language of Google Cloud. You assign roles to members (users, groups, service accounts) on resources. Know the difference between primitive roles (Owner, Editor, Viewer) and predefined roles (Compute Admin, Storage Object Admin). The exam frequently asks you to choose the most restrictive, appropriate role.
- Service Accounts – Identities for applications, not people. A VM or Cloud Run service uses a service account to access other Google Cloud services. Understand how to create a service account, assign it roles, and attach it to a resource.
- Secret Manager – Store API keys, database passwords, and other secrets. Use it instead of hard-coding credentials in your code or startup scripts. ACE might test your awareness of this secure alternative.
- Cloud Identity – Manage users and groups if you're not using Google Workspace. Basic understanding is sufficient.
- Encryption – Google encrypts data at rest by default. For customer-managed encryption keys (CMEK), you can use Cloud KMS, but this is more advanced than typical ACE material. Know that encryption is automatic.
Operations and Monitoring
Once resources are running, you need to observe them. The ACE exam dedicates a significant portion to operational tasks.
- Cloud Monitoring – Metrics, dashboards, and alerts. You should be able to view CPU utilization of a VM, create an uptime check for a website, and set up an alert that sends an email when something fails.
- Cloud Logging – Centralized log repository. Filter logs to find errors, export logs to Cloud Storage or BigQuery for long-term retention. Know how to view logs from Compute Engine, Cloud Run, and GKE.
- Error Reporting – Automatically aggregates and notifies you about errors in your code. Simple integration with Cloud Functions and App Engine.
- Alerting – Create alerting policies based on metrics or log events. Know how to notify via email, SMS, or trigger an auto-remediation action.
Service Relationships
Understanding how services connect is more important than memorizing each in isolation. The diagram below shows a typical deployment on Google Cloud.
A web request comes through a global load balancer to a serverless container on Cloud Run. The container writes data to Cloud SQL and Cloud Storage. It publishes events to Pub/Sub, triggering a Cloud Function for asynchronous processing. IAM controls access at every layer; Monitoring and Logging provide observability.
Service Learning Priority
Not every service demands equal attention. Use this table to focus your study.
| Priority | Service | Why It Matters |
|---|---|---|
| High | Compute Engine, Cloud Storage, VPC, IAM, Cloud Monitoring, Cloud Logging | They appear in nearly every exam objective and form the foundation of all cloud operations. |
| Medium | Cloud SQL, GKE, Cloud Run, Cloud Load Balancing, Cloud DNS, Pub/Sub | Important for specific scenarios; you must know their core capabilities and when to use them. |
| Advanced | Cloud Functions, App Engine, Secret Manager | Less frequent, but still part of the ACE scope. Understand their basic purpose. |
Recommended Study Roadmap
Build your knowledge in this sequence. Each step depends on the previous one.
- Compute Engine – Start with VMs; they ground you in the basics of regions, zones, disks, and networking.
- Cloud Storage – Learn object storage, the life of files, and access control.
- VPC – Understand how networks are built and firewalled.
- IAM – Master identity and access, the control plane of Google Cloud.
- Cloud SQL – Add managed relational databases to your skillset.
- Cloud Monitoring – Learn to observe your resources and set alerts.
- Cloud Run – Move to serverless containers; bridges VM knowledge with modern development.
- GKE – Introduce container orchestration for multi-container workloads.
- Pub/Sub – Tie services together asynchronously.
This order starts with the foundational IaaS components and progresses to modern, managed platforms, mirroring how you would evolve a real environment.
Common Mistakes
- Memorizing service names – Don't just know that Cloud Run exists. Know that it's for containerized, HTTP-driven workloads, and that it scales to zero. Understand the why, not just the what.
- Ignoring networking – VPC, firewall rules, and subnets are the fabric of your cloud. Many troubleshoot questions depend on networking knowledge.
- Overlooking IAM – IAM appears in every corner of the exam. A question about a service often requires you to first check whether the role has sufficient permissions.
- Skipping operational concepts – Monitoring, logging, and backups are not afterthoughts. The ACE exam explicitly tests your ability to manage and maintain resources.
- Avoiding hands-on practice – You cannot fake familiarity with
gcloudcommands or the Cloud Console. Regularly practice creating, managing, and destroying resources.
Continue Learning
- ACE Certification Overview – Full exam guide and learning framework.
- ACE Exam Objectives – Official objectives mapped to services.
- ACE Labs – Hands-on exercises for every core service.
- ACE Scenarios – Apply your knowledge in real-world operational problems.
- ACE Resources – Study guides, checklists, and official Google Cloud references.
For detailed Google Cloud service implementation guides, architecture tutorials, and hands-on labs, continue learning on CloudComputingDevPro.
Frequently Asked Questions
Which Google Cloud services appear most often in ACE?
Compute Engine, Cloud Storage, VPC, IAM, Cloud Monitoring, and Cloud Logging. They are the foundation and appear across all objectives.
Should I learn Kubernetes before the exam?
You don't need to be a Kubernetes expert, but you must understand basic GKE operations: creating a cluster, deploying a container, exposing it with a service. Practice with kubectl basics.
Is Cloud Run important?
Yes. It represents Google Cloud's serverless container platform and is increasingly common in exam scenarios. Know how to deploy a container and manage its access.
How much networking knowledge is required?
You need to understand VPCs, subnets, firewall rules, and basic load balancing. DNS and VPN concepts appear less frequently but are still part of the exam.
Is hands-on practice necessary?
Absolutely. The ACE exam tests operational competence. You must be able to choose the correct gcloud command and navigate the console. Practice regularly in your own Google Cloud project.
Key Takeaways
- Focus your service study on the High Priority category: Compute Engine, Cloud Storage, VPC, IAM, Cloud Monitoring, and Cloud Logging. These are the building blocks.
- Understanding the role of a service—what problem it solves and when to use it—is far more valuable than memorizing every configuration flag.
- Services do not operate in isolation. Practice combining them in the Service Relationships pattern until the integration becomes natural.
- Use CloudCertPro's structured learning path: objectives → services → labs → scenarios. This cycle builds the operational fluency the ACE exam demands and that your career requires.