PROFESSIONAL-CLOUD-DEVOPS-ENGINEER practice question 20 of 25

[Building and implementing CI/CD pipelines for a service] Your company wants to implement a CD pipeline in Cloud Deploy for a web service deployed to…

Full set: 205 questions
[Building and implementing CI/CD pipelines for a service] Your company wants to implement a CD pipeline in Cloud Deploy for a web service deployed to GKE. The web service currently does not have any automated testing. The Quality Assurance team must manually verify any new releases of the web service before any production traffic is processed. You need to design the CD pipeline. What should you do?
Answer options
A: Create two pipeline stages, and use a canary deployment strategy.
B: Create a single pipeline stage, and use a standard deployment strategy.
C: Create a single pipeline stage, and use a canary deployment strategy.
D: Create two pipeline stages, and use a standard deployment strategy. Correct answer
Correct Answer:
D. Create two pipeline stages, and use a standard deployment strategy.
Explanation

A delivery pipeline should provide a QA target that receives the release first, where the team can run manual tests, and a second production target that receives traffic only after an approval gate is passed. Because no automated analysis is available, a Standard deployment strategy—simply promoting the same manifest from QA to production after manual approval—is sufficient and simpler than a canary rollout. Two stages (QA → prod) plus manual approval fully meet the requirement.

Why Incorrect

A. Canary adds phased rollouts and automatic judgment signals that the team does not (yet) have; unnecessary complexity.
B. A single stage offers no separate environment for QA manual testing before production traffic.
C. Same single-stage problem as B and adds needless canary complexity.

References

1. Google Cloud Deploy – Concepts: Delivery pipelines and targets, “Typical flow (dev → test → prod) with manual approval” (docs, 2023-09-12, Section: Pipeline design).

2. Google Cloud Deploy – Strategies: “Standard strategy: deploys the release all at once; best when no automated analysis is required” (docs, 2023-09-12).

3. Google Cloud Deploy – Approvals: “Manual approval between targets lets QA verify before the release is promoted” (docs, 2023-09-12).

Scroll to Top