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: Automated Promotion: Releases successfully deployed to staging must automatically promote to prod after a mandatory 30-minute stabilization soak period without manual intervention. Canary Phase Progression: The prod target uses a multi-phase canary deployment strategy; Cloud Deploy must automatically advance through the canary phases upon successful completion of preceding phases. Failure Recovery: If a rollout in 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?

Define a Cloud Deploy Automation resource attached to the delivery pipeline containing a `promoteReleaseRule` with a 30-minute wait time, an `advanceRolloutRule` for the canary target, and a `repairRolloutRule` configured for retries and rollback.: ### What Cloud Deploy Automation Is **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. ### How It Meets the Requirements - **Automated Promotion:** Cloud Deploy's `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. - **Canary Phase Progression:** The `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. - **Failure Recovery:** The `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. ### Key Advantages and Capabilities - **Native Pipeline Integration:** Automation resources are declaratively defined in YAML and registered alongside pipelines using `gcloud deploy apply`. - **Reduced Operational Overhead:** Eliminates the need for external cron jobs or custom CI/CD scripting to poll pipeline status. - **Fine-Grained Safety Controls:** Supports delays, phase selectors, and retry thresholds to balance automation with delivery safety. - **Auditability and Observability:** All automated actions generate standard Cloud Audit Logs and Cloud Deploy execution events. ### Why This Is Optimal 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.

Cloud Deploy Automation Rules Canary Rollback Promotion | Professional Cloud DevOps Engineer

Cloud Deploy Automation Rules Canary Rollback Promotion

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:

Automated Promotion: Releases successfully deployed to staging must automatically promote to prod after a mandatory 30-minute stabilization soak period without manual intervention.
Canary Phase Progression: The prod target uses a multi-phase canary deployment strategy; Cloud Deploy must automatically advance through the canary phases upon successful completion of preceding phases.
Failure Recovery: If a rollout in 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?

Configure a Cloud Tasks queue to trigger Cloud Workflows after every staging deployment, executing API calls to Cloud Deploy to advance canary phases, promote releases, and invoke rollbacks.

Define a Cloud Deploy Automation resource attached to the delivery pipeline containing a promoteReleaseRule with a 30-minute wait time, an advanceRolloutRule for the canary target, and a repairRolloutRule configured for retries and rollback.

Configure Skaffold profiles in the application repository with custom lifecycle hooks to execute deployment retries, rollback scripts, and phase advancement flags during the render and apply stages.

Implement an Apache Beam pipeline deployed on Dataflow to continuously monitor Cloud Deploy audit logs, calculating soak times and calling gcloud deploy rollback upon detecting target failure events.

Professional Cloud DevOps Engineer

Cloud Deploy Automation Rules Canary Rollback Promotion

Related questions