Your engineering team is designing a continuous deployment and rollback strategy for a critical transaction API hosted on Google Cloud. You need to establish rollback criteria that balance rapid automated mitigation against unwarranted rollbacks caused by ambient noise or external dependencies. The deployment strategy must satisfy two core requirements: Automated rollback: Trigger immediately upon deterministic, high-confidence degradation in direct system health or critical Service Level Indicators (SLIs). Manual intervention: Escalate to the on-call Site Reliability Engineer (SRE) when metric deviations are ambiguous, correlate with business-level signals, or may stem from third-party upstream providers. Which operational criteria correctly distinguish between automated rollback triggers and manual escalation scenarios?

Automate rollback when canary health checks fail consecutively or SLI error rate burn rates exceed critical thresholds; escalate for manual intervention when business conversion rates drop without corresponding infrastructure errors or probe failures.: ### What Automated vs. Manual Rollback Criteria Is An SRE-aligned rollback framework differentiates between **deterministic technical failures** (which can and should be remediated programmatically) and **holistic, multi-variable signals** (which require human context and investigation). Automating rollbacks for high-confidence indicators mitigates blast radius rapidly without human latency. ### How It Meets the Requirements - **Automated rollback requirement**: Consecutive failure of synthetic health checks, readiness probe timeouts, or acute **Service Level Indicator (SLI)** error budget burn rates on canary instances provide direct, deterministic evidence of software regression. Automated rollback scripts or deployment controllers can immediately revert traffic to the stable baseline. - **Manual intervention requirement**: A decline in end-to-end business conversions or checkout completions in the absence of HTTP 5xx errors or host-level anomalies could be caused by external payment processor outages, marketing campaigns, client-side caching, or seasonal traffic trends. These ambiguous signals require an **on-call engineer** to diagnose root causes before initiating a disruptive rollback. ### Key Advantages and Capabilities - **Rapid Mean Time to Resolution (MTTR)**: Automatic rollbacks protect user experience without waiting for human triage during obvious system failures. - **Prevents Unnecessary Thrashing**: Avoids cascading rollbacks triggered by external upstream outages that a software rollback cannot fix. - **Error Budget Protection**: Directly couples rollback logic to Google Cloud Observability SLI burn rates to preserve reliability commitments. - **Context-Aware SRE Operations**: Routes multi-faceted business metric anomalies to engineers who have access to broad telemetry and third-party status dashboards. ### Why This Is Optimal Coupling automated rollback decisions to direct, high-signal infrastructure telemetry while reserving complex anomaly triage for human operators ensures high availability while preventing erroneous rollbacks caused by external environmental factors.

Sre Deployment Rollback Triggers Criteria | Professional Cloud DevOps Engineer

Sre Deployment Rollback Triggers Criteria

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.

Your engineering team is designing a continuous deployment and rollback strategy for a critical transaction API hosted on Google Cloud. You need to establish rollback criteria that balance rapid automated mitigation against unwarranted rollbacks caused by ambient noise or external dependencies.

The deployment strategy must satisfy two core requirements:

Automated rollback: Trigger immediately upon deterministic, high-confidence degradation in direct system health or critical Service Level Indicators (SLIs).
Manual intervention: Escalate to the on-call Site Reliability Engineer (SRE) when metric deviations are ambiguous, correlate with business-level signals, or may stem from third-party upstream providers.

Which operational criteria correctly distinguish between automated rollback triggers and manual escalation scenarios?

Automate rollback when canary health checks fail consecutively or SLI error rate burn rates exceed critical thresholds; escalate for manual intervention when business conversion rates drop without corresponding infrastructure errors or probe failures.

Automate rollback when memory utilization on canary instances reaches 70% during initial cache warm-up; escalate for manual intervention when HTTP 500 error rates exceed 15% across all canary traffic.

Automate rollback when database connection pool latency increases by 5 milliseconds within baseline bounds; escalate for manual intervention when canary pods enter a continuous CrashLoopBackOff state.

Automate rollback when Cloud Audit Logs detect IAM permission updates during deployment; escalate for manual intervention when load balancer backend service probes fail continuously for several minutes.

Professional Cloud DevOps Engineer

Sre Deployment Rollback Triggers Criteria

Related questions