Study guide

3.1 Enabling APIs and Provisioning Cloud Operations Suite

Google Cloud Associate Cloud Engineer ACE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan

2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups

3 Chapter 3: APIs, Quotas & Billing Configuration

3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts

4 Chapter 4: Planning Compute & Storage Resources

4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types

5 Chapter 5: Planning Network Resources

5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard

6 Chapter 6: Deploying Compute Engine Workloads

6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration

7 Chapter 7: Deploying Google Kubernetes Engine Workloads

7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE

8 Chapter 8: Deploying Serverless & Event-Driven Applications

8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc

9 Chapter 9: Deploying Data Solutions

9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud

10 Chapter 10: Deploying Networking Resources & Infrastructure as Code

10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm

11 Chapter 11: Managing Compute Engine & GKE in Production

11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE

12 Chapter 12: Managing Cloud Run, Storage & Database Operations

12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)

13 Chapter 13: Networking Operations, Monitoring & Logging

13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

14 Chapter 14: IAM Policies & Role Types

14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles

15 Chapter 15: Service Accounts & Security Configuration

15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials

16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy

16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist

3.1 Enabling APIs and Provisioning Cloud Operations Suite

Key Takeaways Explain This Topic AI

Every Google Cloud API is disabled by default on a new project; enable it via 'gcloud services enable SERVICE.googleapis.com' or APIs & Services > Library in the console.

Enabling an API only makes it reachable for the project - it does not grant any IAM permission to use the resulting resources.

The IAM permission to enable/disable services (serviceusage.services.enable) is bundled in the Service Usage Admin role plus the built-in Editor and Owner roles.

A project's Cloud Monitoring metrics scope defaults to itself only; centralizing monitoring across up to 375 projects requires designating one scoping project and adding others to its metrics scope.

Cloud Logging captures Google Cloud platform and audit logs automatically with no manual setup; what you configure is retention, sinks, and exports.

Last updated: July 2026

Enabling APIs and Provisioning Cloud Operations Suite

Quick Answer: Every Google Cloud API is disabled by default on a new project, so before you can call Compute Engine, run a query in BigQuery, or deploy a container to GKE, you (or your automation) must explicitly enable that API's Service. Separately, the Associate Cloud Engineer (ACE) exam guide names two more Section 1.1 bullets you must know cold: enabling APIs within projects and provisioning and setting up products in Google Cloud's operations suite (the rebranded "Stackdriver" toolset — Cloud Monitoring, Cloud Logging, Cloud Trace, Cloud Profiler, and Error Reporting).

Why This Matters on the Exam

ACE loves scenario questions where a gcloud command fails with a permission-denied or "API not enabled" error, and you have to pick the fix. It also tests whether you understand that enabling an API is not the same as being authorized to use it — those are two separate control planes (Service Usage vs. IAM), and mixing them up is one of the most common wrong answers on practice exams. Setting up observability (the operations suite) is graded as its own setup task because a newly provisioned environment is only "done" once someone can actually see what's happening inside it.

APIs Are Disabled by Default

Google Cloud exposes hundreds of APIs (also called services ) — for example, compute.googleapis.com for Compute Engine or container.googleapis.com for Google Kubernetes Engine (GKE). A brand-new project has almost none of them turned on. Attempting to call an API before enabling it returns an error like SERVICE_DISABLED , even if the calling identity has full IAM permissions on the resource type.

Console path: APIs & Services → Library → search for the API → Enable .

  • gcloud path: gcloud services enable compute.googleapis.com
  • gcloud services enable container.googleapis.com --project=my-project
  • gcloud services list --enabled
  • gcloud services list --available
  • Google Cloud product Service (API) name to enable
  • Compute Engine compute.googleapis.com
  • Google Kubernetes Engine container.googleapis.com
  • Cloud Run run.googleapis.com
  • Cloud Functions cloudfunctions.googleapis.com
  • Cloud SQL Admin sqladmin.googleapis.com
  • BigQuery bigquery.googleapis.com
  • Pub/Sub pubsub.googleapis.com
  • Cloud Monitoring monitoring.googleapis.com
  • Cloud Logging logging.googleapis.com

Behind the scenes, all of this is managed by the Service Usage API , which is why the IAM permission you need to enable or disable services is serviceusage.services.enable — bundled into the predefined Service Usage Admin role ( roles/serviceusage.serviceUsageAdmin ) as well as the broader Project Editor and Owner roles.

The Trap: Enablement ≠ Authorization

A project Owner who enables compute.googleapis.com has not thereby given a teammate permission to create VMs. Enabling an API only makes the API reachable for the project; a caller still needs an IAM role (e.g., roles/compute.instanceAdmin.v1 ) granting the specific permissions on the resource. Exam questions frequently describe "a developer can't create a Compute Engine instance" and offer both "enable the Compute Engine API" and "grant the Compute Instance Admin role" as options — you have to read the scenario carefully to tell which layer is actually broken (or whether both are).

Provisioning Google Cloud's Operations Suite

The operations suite (formerly Stackdriver) is Google Cloud's built-in observability toolkit:

Component Purpose

Cloud Monitoring Collects and visualizes metrics (CPU, latency, custom app metrics), dashboards, uptime checks, alerting policies

Cloud Logging Aggregates structured/unstructured logs from GCE, GKE, Cloud Run, App Engine, and audit logs into one searchable location

  • Cloud Trace Distributed tracing — visualizes request latency and call chains across microservices
  • Cloud Profiler Continuous CPU/memory profiling of running production code with minimal overhead
  • Error Reporting Aggregates and groups stack traces from your applications into actionable error groups

Cloud Logging captures Google Cloud platform and audit logs automatically for most services with no setup — the "provisioning" work is mostly about Cloud Monitoring. Every Google Cloud project has a metrics scope , which defines which projects' time-series data can be viewed and charted together. By default, a project's metrics scope contains only itself. To centralize monitoring — a very common ACE scenario — you designate one project as the scoping project and add other projects (dev, staging, prod, or per-team projects) into its metrics scope. A single metrics scope can currently monitor up to 375 projects . Only the scoping project stores the configuration (dashboards, alerting policies, uptime checks, SLOs); the underlying metric data still physically lives in each source project.

Exam Scenario

A platform team has 12 microservice projects under one folder. Leadership wants a single dashboard showing error rates and latency across all 12 without moving any workloads. The correct move is to pick (or create) one scoping project , then add the other 11 projects to its metrics scope in Cloud Monitoring — not to consolidate them into one project, and not to export logs to BigQuery (that solves log analytics, not a live cross-project dashboard).

Common Traps to Avoid

Assuming enabling an API also grants IAM permission to use the resulting resources — it does not.

Believing Cloud Logging must be manually "turned on" per project — platform/audit logging is automatic; what you configure is retention, sinks, and exports (covered in Chapter 13).

Confusing a Workspace (the deprecated pre-2022 model, one project = one workspace) with the current metrics scope model, where one project can now belong to scopes with up to 375 projects.

Forgetting that gcloud services enable requires the Service Usage Admin permission — a Viewer-only account cannot enable new APIs even if it can see that they're disabled.