- A
Enable the Container Analysis API; no changes to the build configuration are needed.
Cloud Build automatically pushes images to defined registry, and Container Analysis scans them when API is enabled.
- B
Migrate images from Container Registry to Artifact Registry and enable vulnerability scanning there.
Why wrong: Artifact Registry has scanning, but Container Registry also integrates with Container Analysis.
- C
Add a build step to run a vulnerability scanner CLI tool before pushing the image.
Why wrong: Manual scanning is not minimal; Cloud Build auto-scans.
- D
Enable Binary Authorization to block deployment of vulnerable images.
Why wrong: Binary Authorization requires vulnerability info but doesn't scan itself.
PCDOE Building and implementing CI/CD pipelines Practice Question
This PCDOE practice question tests your understanding of building and implementing ci/cd pipelines. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 company uses Cloud Build to deploy a microservices application to Google Kubernetes Engine (GKE). They want to integrate Container Analysis to scan images for vulnerabilities before deployment. What is the minimal set of changes needed 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
Enable the Container Analysis API; no changes to the build configuration are needed.
Option D is correct because Cloud Build natively integrates with Container Analysis; enabling the API and building the image triggers scanning automatically. Option A is incorrect - no need for a separate scan step. Option B is incorrect - Binary Authorization is for policy enforcement, not scanning. Option C is incorrect - Artifact Registry does not replace scanning.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable the Container Analysis API; no changes to the build configuration are needed.
Why this is correct
Cloud Build automatically pushes images to defined registry, and Container Analysis scans them when API is enabled.
Related concept
Authentication checks who the user is.
- ✗
Migrate images from Container Registry to Artifact Registry and enable vulnerability scanning there.
Why it's wrong here
Artifact Registry has scanning, but Container Registry also integrates with Container Analysis.
- ✗
Add a build step to run a vulnerability scanner CLI tool before pushing the image.
Why it's wrong here
Manual scanning is not minimal; Cloud Build auto-scans.
- ✗
Enable Binary Authorization to block deployment of vulnerable images.
Why it's wrong here
Binary Authorization requires vulnerability info but doesn't scan itself.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
- Authentication checks who the user is.
- Authorization controls what the user is allowed to do after login.
- Privilege levels affect access to EXEC and configuration commands.
- AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
- Do not assume successful login means full administrative access.
- Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
- Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PCDOE questions on access control and AAA configuration.
- →
Building and implementing CI/CD pipelines — study guide chapter
Learn the concepts, then practise the questions
- →
Building and implementing CI/CD pipelines 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
Related PCDOE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
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.
PCDOE troubleshooting practice questions
Practise PCDOE questions linked to PCDOE troubleshooting.
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?
Building and implementing CI/CD pipelines — This question tests Building and implementing CI/CD pipelines — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Enable the Container Analysis API; no changes to the build configuration are needed. — Option D is correct because Cloud Build natively integrates with Container Analysis; enabling the API and building the image triggers scanning automatically. Option A is incorrect - no need for a separate scan step. Option B is incorrect - Binary Authorization is for policy enforcement, not scanning. Option C is incorrect - Artifact Registry does not replace scanning.
What should I do if I get this PCDOE question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PCDOE questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 set up a CI/CD pipeline using Cloud Build and Cloud Deploy for a Cloud Run service.
- Order the steps to configure a VPC Network Peering between two projects.
- Order the steps to respond to a Google Cloud security incident involving a compromised service account key.
- 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 CI/CD pipelines that need access to API keys stored in Secret Manager. The pipelines run…
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.