Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
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.
A Kubernetes rolling update progressively replaces old Pod replicas with new ones based on configured maxSurge and maxUnavailable parameters. Readiness and liveness probes perform periodic HTTP, TCP, or container exec health checks to determine if individual containers are running and capable of receiving network traffic.
kubectl rollout undo or executing an external pipeline trigger.The workload had simple binary failure criteria, did not require advanced statistical canary validation against a control baseline, and tolerated standard rolling update mechanics.
This approach uses Cloud Logging sinks to stream access logs into BigQuery, where scheduled SQL queries aggregate response codes and calculate overall service error rates on a periodic cadence.
The team needed to perform long-term retrospective compliance auditing or complex offline user behavior analysis after a deployment had successfully stabilized.
A Blue/Green deployment provisions a complete replica of the application environment (Green) alongside the existing live environment (Blue). Once the Green environment passes preliminary checks, traffic is transitioned all at once by updating Cloud DNS records or global load balancer target proxies.
The organization prioritized full infrastructure isolation, had incompatible database schema changes that prevented canary side-by-side execution, and accepted instant traffic cutover.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated