- A
Use a custom Cloud Function that runs every time a project is created and enables the APIs.
Correct. A Cloud Function triggered by project creation events can automatically enable required APIs on each new project, ensuring consistency without manual effort.
- B
Grant the roles/serviceusage.serviceUsageAdmin role to the DevOps team and have them manually enable APIs when creating projects.
Why wrong: Manual processes are error-prone and not enforced.
- C
Use organization policies to define the constraints 'compute.requireOsLogin' and 'serviceuser.services' to restrict/enable APIs.
Why wrong: Incorrect. Organization policies can restrict API usage (e.g., prevent disabling), but they do not provision or enable APIs. They cannot automatically enable APIs on new projects.
- D
Create a folder with a 'Required APIs' setting that applies to all child projects.
Why wrong: No such folder setting exists; organization policies are used for this.
PCDOE Practice Question: Bootstrapping a Google Cloud organization for DevOps
This PCDOE practice question tests your understanding of bootstrapping a google cloud organization for devops. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
During bootstrapping, a DevOps engineer wants to ensure that all new projects automatically have a set of APIs enabled, such as Cloud Resource Manager API and Cloud Billing API. They also want to enforce that certain APIs cannot be disabled accidentally. What is the most efficient way to achieve this?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use a custom Cloud Function that runs every time a project is created and enables the APIs.
Option A is correct because Google Cloud provides event-driven capabilities through Cloud Functions that can be triggered by project creation events (via Cloud Audit Logs or Eventarc). By deploying a Cloud Function that listens for new projects and enables the desired APIs (e.g., Cloud Resource Manager API, Cloud Billing API), the DevOps engineer can automate API enablement without manual intervention. This is the most efficient and reliable approach for automatically enabling APIs on new projects. Option C is incorrect because organization policies enforce constraints (e.g., 'serviceuser.services') that restrict which APIs can be disabled, but they cannot automatically enable APIs. Organization policies are used to prevent disabling of APIs, not to enable them proactively.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use a custom Cloud Function that runs every time a project is created and enables the APIs.
Why this is correct
Correct. A Cloud Function triggered by project creation events can automatically enable required APIs on each new project, ensuring consistency without manual effort.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Grant the roles/serviceusage.serviceUsageAdmin role to the DevOps team and have them manually enable APIs when creating projects.
Why it's wrong here
Manual processes are error-prone and not enforced.
- ✗
Use organization policies to define the constraints 'compute.requireOsLogin' and 'serviceuser.services' to restrict/enable APIs.
Why it's wrong here
Incorrect. Organization policies can restrict API usage (e.g., prevent disabling), but they do not provision or enable APIs. They cannot automatically enable APIs on new projects.
- ✗
Create a folder with a 'Required APIs' setting that applies to all child projects.
Why it's wrong here
No such folder setting exists; organization policies are used for this.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse folder-level settings with organization policies, assuming folders have a built-in 'Required APIs' feature, when in reality only organization policies can enforce API enablement and disablement restrictions across projects.
Detailed technical explanation
How to think about this question
The `serviceuser.services` constraint is a list constraint that can be set to `deny` all services except those explicitly allowed, or to `allow` only specified services. When used in conjunction with the `constraints/serviceuser.services` policy, you can define a list of required APIs (e.g., `cloudresourcemanager.googleapis.com`, `cloudbilling.googleapis.com`) that must be enabled and cannot be disabled by any project-level role, as the policy overrides project-level permissions. This is enforced by the Resource Manager hierarchy, ensuring inheritance to all child projects.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Bootstrapping a Google Cloud organization for DevOps — study guide chapter
Learn the concepts, then practise the questions
- →
Bootstrapping a Google Cloud organization for DevOps practice questions
Targeted practice on this topic area only
- →
All PCDOE questions
1,000 questions across all exam domains
- →
Google Professional Cloud DevOps Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDOE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDOE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design and Plan Database Solutions practice questions
Practise PCDOE questions linked to Design and Plan Database Solutions.
Manage Database Solutions practice questions
Practise PCDOE questions linked to Manage Database Solutions.
Migrate Database Solutions practice questions
Practise PCDOE questions linked to Migrate Database Solutions.
Design for Reliability, Scalability, and Disaster Recovery practice questions
Practise PCDOE questions linked to Design for Reliability, Scalability, and Disaster Recovery.
Bootstrapping a Google Cloud organization for DevOps practice questions
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Managing service incidents practice questions
Practise PCDOE questions linked to Managing service incidents.
Managing Google Cloud costs practice questions
Practise PCDOE questions linked to Managing Google Cloud costs.
Building and implementing CI/CD pipelines practice questions
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Implementing service monitoring strategies practice questions
Practise PCDOE questions linked to Implementing service monitoring strategies.
Optimizing service performance practice questions
Practise PCDOE questions linked to Optimizing service performance.
PCDOE fundamentals practice questions
Practise PCDOE questions linked to PCDOE fundamentals.
PCDOE scenario practice questions
Practise PCDOE questions linked to PCDOE scenario.
Practice this exam
Start a free PCDOE practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PCDOE question test?
Bootstrapping a Google Cloud organization for DevOps — This question tests Bootstrapping a Google Cloud organization for DevOps — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a custom Cloud Function that runs every time a project is created and enables the APIs. — Option A is correct because Google Cloud provides event-driven capabilities through Cloud Functions that can be triggered by project creation events (via Cloud Audit Logs or Eventarc). By deploying a Cloud Function that listens for new projects and enables the desired APIs (e.g., Cloud Resource Manager API, Cloud Billing API), the DevOps engineer can automate API enablement without manual intervention. This is the most efficient and reliable approach for automatically enabling APIs on new projects. Option C is incorrect because organization policies enforce constraints (e.g., 'serviceuser.services') that restrict which APIs can be disabled, but they cannot automatically enable APIs. Organization policies are used to prevent disabling of APIs, not to enable them proactively.
What should I do if I get this PCDOE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More PCDOE practice questions
- Order the steps to configure a VPC Network Peering between two projects.
- Refer to the exhibit. The Cloud Build fails with a permission error. The Cloud Build service account has roles/cloudbuil…
- A company is setting up a new Google Cloud organization. They want to ensure that all projects inherit common IAM polici…
- A DevOps team is bootstrapping their Google Cloud organization and wants to enable Infrastructure as Code (IaC) using Te…
- To securely manage secrets (e.g., API keys) used in Cloud Build pipelines, which service should be used?
- A DevOps engineer needs to set up a centralized logging solution for multiple projects. They want to store logs in a Big…
Last reviewed: Jun 24, 2026
This PCDOE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDOE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.