Google ACE A GCP organization has 150 projects Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Manually enable the API in each of the 150 projects via the Cloud Console

  Why it's wrong here

  Manually enabling the API in each of the 150 projects through the Cloud Console is not a repeatable or auditable process. It requires an administrator to switch between projects, search for the specific API, and click the enable button each time, which is time-consuming and highly error-prone—there is a real risk of skipping a project, enabling the wrong API, or making inconsistent changes. This manual approach also offers no easy way to verify that all projects have been updated, and it does not scale beyond a handful of projects. For fleet-wide operations, Google recommends using gcloud scripting or Infrastructure as Code like Terraform to automate the task and ensure uniformity.

• ✓

  Use a gcloud script to iterate over all projects and enable the API for each

  Why this is correct

  Using a gcloud script to iterate over all projects is a recommended, scalable, and auditable approach. A script can call `gcloud projects list` to enumerate the project IDs and then execute `gcloud services enable <api> --project=<id>` for each one, making the operation idempotent and repeatable. This can be filtered to target only the relevant 150 projects and easily integrated into CI/CD pipelines or run as a one-time maintenance task. It is preferable because it eliminates the risk of human error, provides a clear command log, and requires minimal effort even for hundreds of projects.

• ✗

  Enable the API at the organization level — it inherits down to all projects

  Why it's wrong here

  The Google Cloud API enablement model is strictly project-scoped. There is no organization-level setting or flag that, when enabled, automatically turns on a given API for all existing or future projects. Organization policies can enforce constraints on resource configurations but cannot control Service Usage service states. Attempting to enable an API at the organization level would not cause the API to be enabled in any project, so this approach would not meet the requirement.

• ✗

  Create an organization policy enabling all APIs on all projects

  Why it's wrong here

  Organization policies in Google Cloud are declarative constraints that restrict resource properties—such as allowed locations, resource shapes, or IAM settings—but they do not enable APIs. API enablement is a Service Usage operation that must be performed separately on each project; an organization policy cannot flip a service from DISABLED to ENABLED in any project. Even if one could create a policy allowing all APIs, that would not actually enable any API and would be a severe security and billing risk. The only way to enable an API is to explicitly call the Service Usage API or use `gcloud services enable` on each project.

Go deeper

Related to this question