The correct answer is to use the gcloud deploy rollback command targeting the production target. This command is the precise tool for rolling back a Cloud Deploy target to its previous successful release without impacting other targets like staging, because it redeploys the last known good release exclusively to the specified target while preserving the promotion history for all other environments. On the Google Professional Cloud Developer exam, this scenario tests your understanding of Cloud Deploy’s target-level release management, often appearing as a distractor where candidates might mistakenly try to re-run a previous promotion or manually redeploy an old artifact. A common trap is assuming a rollback affects the entire pipeline, but gcloud deploy rollback operates per target, allowing you to revert production independently. Memory tip: think of it as a surgical rollback—only the target you name gets the rewind, leaving the rest of the pipeline untouched.
PCD Building and testing applications Practice Question
This PCD practice question tests your understanding of building and testing applications. 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.
A company uses Cloud Deploy for continuous delivery with multiple targets (dev, staging, prod). After a successful promotion to staging, the team discovers a critical bug and needs to roll back the production target to the previous release. The production target has already been promoted to the current release, but the staging target should remain on the current release. How should the team roll back the production target?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the 'gcloud deploy rollback' command targeting the production target.
Option B is correct because the 'gcloud deploy rollback' command is specifically designed to roll back a Cloud Deploy target to its previous successful release without affecting other targets. This command reverts the production target to the prior release while leaving the staging target on the current release, as required. It operates by redeploying the last known good release to the specified target, ensuring minimal disruption and preserving the promotion history.
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.
✗
Create a new release with the same image tag as the previous release and promote it to production.
Why it's wrong here
Creating a new release manually is error-prone; the rollback command automates this process.
✓
Use the 'gcloud deploy rollback' command targeting the production target.
Why this is correct
Rollback creates a new release with the previous rollout's configuration and deploys it to the target.
Related concept
Read the scenario before looking for a memorised answer.
✗
Redeploy the previous release by running the previous Cloud Deploy command.
Why it's wrong here
Redeploying manually may not preserve the exact state and is not the standard rollback method.
✗
Manually delete the current release and then promote the previous release again.
Why it's wrong here
Deleting releases can cause inconsistencies and is not recommended for rollback.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that rolling back a target requires creating a new release or manually manipulating releases, when in fact Cloud Deploy provides a dedicated rollback command that handles the process cleanly without affecting other targets or the release history.
Trap categories for this question
Command / output trap
Creating a new release manually is error-prone; the rollback command automates this process.
Detailed technical explanation
How to think about this question
Cloud Deploy uses a release-based model where each release is immutable and linked to a specific target via promotion. The 'gcloud deploy rollback' command leverages the rollout history stored in the delivery pipeline to identify the previous successful rollout for the specified target, then creates a new rollout that deploys the same artifact (e.g., container image) as that prior release. This ensures that the rollback is atomic and does not alter the release sequence for other targets, which is critical in multi-target pipelines where staging and prod may be at different release versions.
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 testing applications — This question tests Building and testing applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the 'gcloud deploy rollback' command targeting the production target. — Option B is correct because the 'gcloud deploy rollback' command is specifically designed to roll back a Cloud Deploy target to its previous successful release without affecting other targets. This command reverts the production target to the prior release while leaving the staging target on the current release, as required. It operates by redeploying the last known good release to the specified target, ensuring minimal disruption and preserving the promotion history.
What should I do if I get this PCD 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 →
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.
This PCD 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 PCD 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.