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.
A DevOps engineer is troubleshooting a Cloud Build failure. The build log shows the error: 'Permission denied for resource projects/my-project/locations/us-central1/repositories/my-repo'. The Cloud Build service account (PROJECT_NUMBER@cloudbuild.gserviceaccount.com) is used. What is the most likely missing role?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
roles/artifactregistry.reader
Why wrong: This only allows reading, not writing.
roles/artifactregistry.admin
Why wrong: This is too broad and grants management permissions.
roles/cloudbuild.builds.builder
Why wrong: This is for Cloud Build execution, not for accessing Artifact Registry.
roles/artifactregistry.writer
This allows pushing artifacts to repositories.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
roles/artifactregistry.writer
The error 'Permission denied for resource projects/my-project/locations/us-central1/repositories/my-repo' indicates that the Cloud Build service account lacks permission to write artifacts to Artifact Registry. The Cloud Build service account needs the `roles/artifactregistry.writer` role to upload build artifacts (e.g., container images) to the repository. Without this role, the build fails at the step that attempts to push artifacts.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
roles/artifactregistry.reader
Why it's wrong here
This only allows reading, not writing.
roles/artifactregistry.admin
Why it's wrong here
This is too broad and grants management permissions.
roles/cloudbuild.builds.builder
Why it's wrong here
This is for Cloud Build execution, not for accessing Artifact Registry.
roles/artifactregistry.writer
Why this is correct
This allows pushing artifacts to repositories.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often confuse `roles/artifactregistry.reader` (which only allows pulling) with the write permission needed for pushing artifacts, or they mistakenly think the default Cloud Build service account role includes Artifact Registry access.
Detailed technical explanation
Artifact Registry uses IAM roles to control access to repositories, and the `artifactregistry.writer` role includes the `artifactregistry.versions.create` permission required to push new versions of artifacts. Cloud Build's default service account (`PROJECT_NUMBER@cloudbuild.gserviceaccount.com`) is automatically granted the `roles/cloudbuild.builds.builder` role, but it must be explicitly granted Artifact Registry roles. In real-world scenarios, failing to grant `roles/artifactregistry.writer` is a common misconfiguration when setting up CI/CD pipelines that push Docker images to Artifact Registry.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
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
500 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Practise PCDOE questions linked to Managing service incidents.
Practise PCDOE questions linked to Managing Google Cloud costs.
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Practise PCDOE questions linked to Implementing service monitoring strategies.
Practise PCDOE questions linked to Optimizing service performance.
Practise PCDOE questions linked to PCDOE fundamentals.
Practise PCDOE questions linked to PCDOE scenario.
Practise PCDOE questions linked to PCDOE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
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..
The correct answer is: roles/artifactregistry.writer — The error 'Permission denied for resource projects/my-project/locations/us-central1/repositories/my-repo' indicates that the Cloud Build service account lacks permission to write artifacts to Artifact Registry. The Cloud Build service account needs the `roles/artifactregistry.writer` role to upload build artifacts (e.g., container images) to the repository. Without this role, the build fails at the step that attempts to push artifacts.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.