Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
An enterprise DevOps engineering team is designing a Google Cloud Deploy delivery pipeline to manage application rollouts across three targets: dev, staging, and prod.
The deployment architecture must satisfy the following operational requirements:
staging must automatically promote to prod after a mandatory 30-minute stabilization soak period without manual intervention.prod target uses a multi-phase canary deployment strategy; Cloud Deploy must automatically advance through the canary phases upon successful completion of preceding phases.prod fails, the pipeline must attempt one automatic retry, and if that retry fails, automatically execute a rollback to the previous successful release.Which Cloud Deploy configuration should the team implement to satisfy these requirements?
Cloud Deploy Automation provides native, declarative policy definitions that govern release progression and error handling across delivery pipelines. It automates operational rollout tasks such as multi-target promotions, canary phase progressions, and failure remediations without requiring custom external orchestrators.
promoteReleaseRule evaluates the state of the upstream staging target and automatically promotes the release to prod once the rollout succeeds and the specified 30-minute wait duration expires.advanceRolloutRule allows targets configured with a canary deployment strategy to automatically advance from one phase to the next upon successful verification of the previous phase.repairRolloutRule defines automated remediation policies, allowing Cloud Deploy to retry a failed rollout a specified number of times and automatically initiate a rollback to the last successful release if retries are exhausted.gcloud deploy apply.Using native Cloud Deploy automation rules (promoteReleaseRule, advanceRolloutRule, and repairRolloutRule) centralizes release management, canary progression, and automated rollback within Google Cloud's managed control plane rather than relying on disparate external tools.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.