- A
Define strict version compatibility matrices between services and enforce them in the pipeline by locking versions.
Why wrong: Locking versions reduces flexibility and may not be feasible.
- B
Implement canary deployments in staging: deploy the new payment service alongside the current version, route a percentage of test traffic to the new version, and run integration tests before promoting. If tests pass, promote to production.
Canary deployments in staging catch incompatibilities early without slowing development.
- C
Add a manual testing phase after staging deployment where QA engineers manually test the integration before production promotion.
Why wrong: Manual testing is slow and does not scale with frequent deployments.
- D
Combine all microservice builds into a single pipeline that builds and tests all services together before deploying to staging.
Why wrong: Monolithic pipeline reduces velocity and independence.
Quick Answer
The correct answer is to implement canary deployments in staging, deploying the new payment service alongside the current version and routing a percentage of test traffic to it before promoting to production. This approach directly addresses the need to catch microservice incompatibilities before production canary GKE rollouts by running integration tests against a subset of realistic traffic in staging, ensuring the new payment service works with the current order service without blocking the pipeline or slowing development velocity. On the Google Professional Cloud DevOps Engineer exam, this scenario tests your understanding of progressive delivery strategies and Cloud Deploy’s native support for canary releases—a common trap is to assume that more rigorous pre-production testing or manual approval alone will catch runtime incompatibilities, but only a canary in staging provides the real traffic mix needed. Remember the memory tip: “Staging canary, production merry”—test the new version with a slice of traffic early to keep your deployments safe and fast.
PCDOE Building and implementing CI/CD pipelines Practice Question
This PCDOE practice question tests your understanding of building and implementing ci/cd pipelines. 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.
You are a DevOps engineer for a large e-commerce platform running on Google Kubernetes Engine (GKE). The platform consists of 15 microservices, each with its own code repository. Your team uses Cloud Build for CI and Cloud Deploy for CD. Recently, the deployment to production has been failing intermittently because the new version of the 'payment' service is not compatible with the current version of the 'order' service. This causes a production outage every few weeks. The team wants to implement a strategy to catch such incompatibilities before promoting to production, without slowing down development velocity. Currently, the pipeline builds each service independently, runs unit tests, deploys to a shared staging environment, runs integration tests, and then promotes to production after manual approval. What should you 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
Implement canary deployments in staging: deploy the new payment service alongside the current version, route a percentage of test traffic to the new version, and run integration tests before promoting. If tests pass, promote to production.
Option B is correct because it introduces canary deployments in the staging environment, allowing the new payment service to be tested with a subset of realistic traffic alongside the current order service. This catches incompatibilities early by running integration tests against the canary, without blocking the pipeline or slowing development velocity. Cloud Deploy supports canary deployment strategies natively, making this a practical and automated solution.
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.
- ✗
Define strict version compatibility matrices between services and enforce them in the pipeline by locking versions.
Why it's wrong here
Locking versions reduces flexibility and may not be feasible.
- ✓
Implement canary deployments in staging: deploy the new payment service alongside the current version, route a percentage of test traffic to the new version, and run integration tests before promoting. If tests pass, promote to production.
Why this is correct
Canary deployments in staging catch incompatibilities early without slowing development.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Add a manual testing phase after staging deployment where QA engineers manually test the integration before production promotion.
Why it's wrong here
Manual testing is slow and does not scale with frequent deployments.
- ✗
Combine all microservice builds into a single pipeline that builds and tests all services together before deploying to staging.
Why it's wrong here
Monolithic pipeline reduces velocity and independence.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may choose option A (version locking) because it seems like a straightforward dependency management solution, but it ignores the need for dynamic testing under realistic traffic patterns and the requirement to maintain development velocity.
Detailed technical explanation
How to think about this question
Canary deployments in GKE leverage Kubernetes Service mesh (e.g., Istio) or Cloud Deploy's progressive delivery model to route a percentage of traffic (e.g., 10%) to the new revision while running integration tests. This approach validates real-world behavior under load without affecting all users, and if tests fail, the canary is automatically rolled back. In practice, this catches subtle API contract mismatches or data format changes that unit tests miss, as they often rely on mocked dependencies.
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: Implement canary deployments in staging: deploy the new payment service alongside the current version, route a percentage of test traffic to the new version, and run integration tests before promoting. If tests pass, promote to production. — Option B is correct because it introduces canary deployments in the staging environment, allowing the new payment service to be tested with a subset of realistic traffic alongside the current order service. This catches incompatibilities early by running integration tests against the canary, without blocking the pipeline or slowing development velocity. Cloud Deploy supports canary deployment strategies natively, making this a practical and automated solution.
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 11, 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.