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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
A DevOps engineering team is configuring an automated canary release and rollback strategy for a critical e-commerce API hosted on Google Kubernetes Engine (GKE). The team requires a solution that:
Which strategy best satisfies these requirements while minimizing user impact?
Configure an automated canary analysis pipeline in Spinnaker integrated with Cloud Monitoring metrics to evaluate canary and baseline health against statistical thresholds, triggering an automated pipeline abort and traffic shift back to baseline upon failure.
Implement an all-at-once Blue/Green deployment using Cloud Build, modifying Cloud DNS routing to switch 100% of traffic, and configuring Cloud Monitoring alerts to trigger a manual DNS revert if errors spike.
Execute an in-place rolling update using Cloud Build and rely solely on Kubernetes readiness and liveness probes to catch application faults and initiate cluster-level rollbacks.
Export all GKE ingress request logs to BigQuery, execute an hourly scheduled query in Cloud Build to calculate error percentages, and send an alert to an on-call engineer to roll back the release if needed.
Configure an automated canary analysis pipeline in Spinnaker integrated with Cloud Monitoring metrics to evaluate canary and baseline health against statistical thresholds, triggering an automated pipeline abort and traffic shift back to baseline upon failure.
Automated Canary Analysis (ACA) is an advanced deployment strategy where newly built application code is deployed to a subset of infrastructure (the canary) and evaluated side-by-side against an identical, newly deployed baseline running the current production version. By integrating Spinnaker (utilizing Kayenta) with Cloud Monitoring, the pipeline queries real-time operational telemetry—such as request latency, error counts, and resource utilization—to programmatically score release health against predefined statistical thresholds.
Unlike coarse-grained rolling updates or manual rollbacks, automated canary analysis provides proactive fault isolation. It guarantees that regressions in critical application paths are intercepted dynamically, satisfying rigorous Service Level Objectives (SLOs) without requiring engineering intervention during active release cycles.
Implement an all-at-once Blue/Green deployment using Cloud Build, modifying Cloud DNS routing to switch 100% of traffic, and configuring Cloud Monitoring alerts to trigger a manual DNS revert if errors spike.
Execute an in-place rolling update using Cloud Build and rely solely on Kubernetes readiness and liveness probes to catch application faults and initiate cluster-level rollbacks.
Export all GKE ingress request logs to BigQuery, execute an hourly scheduled query in Cloud Build to calculate error percentages, and send an alert to an on-call engineer to roll back the release if needed.