- A
Keep the current architecture but modify Cloud Build triggers to only run on the main branch of both repositories. Use the short SHA ($SHORT_SHA) as the image tag.
Why wrong: The short SHA is not guaranteed to be unique across branches and separate repositories still cause race conditions.
- B
Consolidate application code and Kubernetes manifests into a single repository. Configure Cloud Build triggers to build and run tests on all branches, but only deploy to GKE when changes are merged to the main branch. Use the full commit SHA as the image tag.
This ensures that only merged code triggers deployments, and the full commit SHA provides an immutable unique tag for easy rollback.
- C
Move all source code and manifests into a single repository. Use Cloud Build triggers to build and test on every push, and deploy only on pushes to the main branch. Use the commit SHA ($COMMIT_SHA) as the image tag.
Why wrong: This runs tests on every push, which is excessive and uses commit SHA but still deploys on every push to main, which might be fine but does not address the rollback slowness explicitly.
- D
Keep application and manifests in separate repositories. Use Cloud Build triggers to build on changes to the app repo, and use a separate trigger on the manifests repo to deploy. Use the 'latest' tag for the image.
Why wrong: Using 'latest' makes images mutable and separate repos can lead to inconsistency.
Quick Answer
The answer is to consolidate application code and Kubernetes manifests into a single repository, because this ties the immutable image tag—specifically the full commit SHA—directly to the exact code and manifest changes that passed all tests. By configuring Cloud Build triggers to deploy only on merges to the main branch, the team ensures deployment integrity, preventing the scenario where a new image reaches production before its corresponding manifest PR is merged. This approach directly addresses the search intent for "Cloud Build Kubernetes manifests separate repository deployment integrity rollback" by eliminating the synchronization gap between separate repos. On the Google Professional Cloud DevOps Engineer exam, this tests your understanding of CI/CD best practices for GKE, where a common trap is assuming separate repositories improve separation of concerns, when in fact they introduce deployment drift. A helpful memory tip: "One repo, one SHA, one truth"—if the code and manifests live together, the commit SHA guarantees that what you test is exactly what you deploy, and rollbacks are as simple as reverting to a previous SHA.
PCDOE Building and implementing CI/CD pipelines Practice Question
This PCDOE practice question tests your understanding of building and implementing ci/cd pipelines. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
Your team manages a CI/CD pipeline for a microservices application deployed on Google Kubernetes Engine (GKE). The pipeline uses Cloud Build to build container images and push them to Artifact Registry, then uses a Cloud Build step with kubectl to apply Kubernetes manifests stored in a separate 'manifests' repository. Recently, the team has experienced issues: sometimes a new image is deployed to production even though the corresponding pull request (PR) has not been merged into the main branch of the manifests repository. Also, rollbacks are slow because the previous image tag is overwritten. The team wants to ensure that only code that passes all tests and is merged to main is deployed, and that each deployment uses a unique immutable image tag. What should the team do?
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
Consolidate application code and Kubernetes manifests into a single repository. Configure Cloud Build triggers to build and run tests on all branches, but only deploy to GKE when changes are merged to the main branch. Use the full commit SHA as the image tag.
Option B is correct because consolidating the application code and Kubernetes manifests into a single repository ensures that the image tag (full commit SHA) is uniquely tied to the exact code and manifest changes that passed all tests. By configuring Cloud Build triggers to deploy only on merges to the main branch, the team guarantees that only fully tested, merged code reaches production. Using the full commit SHA as the image tag provides immutability and enables fast, precise rollbacks by referencing the exact image from Artifact Registry.
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.
- ✗
Keep the current architecture but modify Cloud Build triggers to only run on the main branch of both repositories. Use the short SHA ($SHORT_SHA) as the image tag.
Why it's wrong here
The short SHA is not guaranteed to be unique across branches and separate repositories still cause race conditions.
- ✓
Consolidate application code and Kubernetes manifests into a single repository. Configure Cloud Build triggers to build and run tests on all branches, but only deploy to GKE when changes are merged to the main branch. Use the full commit SHA as the image tag.
Why this is correct
This ensures that only merged code triggers deployments, and the full commit SHA provides an immutable unique tag for easy rollback.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Move all source code and manifests into a single repository. Use Cloud Build triggers to build and test on every push, and deploy only on pushes to the main branch. Use the commit SHA ($COMMIT_SHA) as the image tag.
Why it's wrong here
This runs tests on every push, which is excessive and uses commit SHA but still deploys on every push to main, which might be fine but does not address the rollback slowness explicitly.
- ✗
Keep application and manifests in separate repositories. Use Cloud Build triggers to build on changes to the app repo, and use a separate trigger on the manifests repo to deploy. Use the 'latest' tag for the image.
Why it's wrong here
Using 'latest' makes images mutable and separate repos can lead to inconsistency.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that separate repositories with branch-based triggers are sufficient for deployment integrity, when in reality the atomicity of code and manifest changes in a single repository is required to prevent untested code from reaching production.
Detailed technical explanation
How to think about this question
Under the hood, Cloud Build triggers evaluate branch patterns and file globs; by consolidating repos, you can use a single trigger that builds, tests, and deploys only on merges to main, ensuring the commit SHA in the image tag matches the exact commit in the manifests. The full commit SHA (40-character hex) provides a globally unique identifier, unlike $SHORT_SHA which can collide in large repositories. In a real-world scenario, this approach also simplifies rollback: you can revert the manifest commit and the pipeline will rebuild with the previous SHA, or you can directly reference the old image tag in a kubectl rollout undo.
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 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. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
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 — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Consolidate application code and Kubernetes manifests into a single repository. Configure Cloud Build triggers to build and run tests on all branches, but only deploy to GKE when changes are merged to the main branch. Use the full commit SHA as the image tag. — Option B is correct because consolidating the application code and Kubernetes manifests into a single repository ensures that the image tag (full commit SHA) is uniquely tied to the exact code and manifest changes that passed all tests. By configuring Cloud Build triggers to deploy only on merges to the main branch, the team guarantees that only fully tested, merged code reaches production. Using the full commit SHA as the image tag provides immutability and enables fast, precise rollbacks by referencing the exact image from Artifact Registry.
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 →
Last reviewed: Jun 30, 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.