Your team manages a high-traffic microservices application running on Google Kubernetes Engine (GKE) and is introducing automated canary deployments through your CI/CD pipeline. You have established request-based availability and latency Service-Level Objectives (SLOs) in Cloud Monitoring. During canary rollouts, you need to evaluate the health of the canary version in real time and automatically trigger a deployment rollback if the canary release severely degrades application performance and rapidly depletes your error budget. Which architectural approach should you implement to satisfy these requirements?

Configure an SLO burn-rate alerting policy with a short lookback period to detect fast-burn conditions on the canary service, and attach a Cloud Pub/Sub notification channel that triggers an automated rollback service.: What SLO Burn-Rate Alerting with Pub/Sub Is An SLO burn-rate alerting policy tracks how rapidly a service is consuming its allotted error budget over a specific evaluation window. In Google Cloud Observability, Cloud Monitoring allows you to define request-based Service-Level Indicators (SLIs) and objectives (SLOs) for microservices. When combined with a Cloud Pub/Sub notification channel, alerting policies can publish structured incident messages to message topics, allowing decoupled event-driven automation (such as Cloud Functions, Cloud Run, or CI/CD webhooks) to consume the event and execute remediation actions like rolling back a canary release. How It Meets the Requirements Real-Time Deployment Health: By defining a fast-burn alert (e.g., alerting when the burn rate is 10x or 14x baseline over a short lookback window of 1 hour), Cloud Monitoring identifies severe performance anomalies and error surges on the canary deployment within minutes of release. Automated Rollback: Attaching a Cloud Pub/Sub notification channel ensures that when an incident is opened, an event containing the incident metadata and resource context is delivered immediately to a subscriber without human intervention, which triggers the automated rollback workflow in your CI/CD pipeline. Key Advantages Reduces Time to Mitigate (TTM): Automated event-driven rollback limits the blast radius of breaking changes during progressive delivery. Precision Alerting: Alerting on error budget burn rates prevents false alarms caused by minor metric spikes during low-traffic windows while guaranteeing rapid responses to catastrophic regressions. Native Integration: Seamlessly connects Cloud Monitoring time-series evaluation with event-driven automation in Google Cloud. Decoupled Architecture: Pub/Sub provides a resilient, asynchronous buffer between monitoring infrastructure and deployment controllers. Why This Is Optimal Using Cloud Monitoring's native SLO burn-rate engine with a Pub/Sub notification channel is the Google SRE-recommended pattern. It avoids the latency of batch log queries, eliminates manual alert triaging, and directly ties deployment stability to business-critical reliability targets.

Gke Slo Fast Burn Automated Rollback | Professional Cloud DevOps Engineer

AdvancedProfessional Cloud DevOps Engineer

Your team is building an automated continuous training (CT) and continuous deployment (CD) pipeline for a mission-critical tabular classification model on Google Cloud. You need to implement a solution using Vertex AI Pipelines that continuously evaluates candidate models and deploys them to production. The pipeline implementation must meet the following operational requirements: Track end-to-end dataset lineage, hyperparameter configurations, and model artifact provenance in Vertex ML Metadata. Execute automated model evaluation on validation test data and compute classification metrics. Use conditional execution logic within the pipeline directed acyclic graph (DAG) to trigger deployment to the production endpoint only if candidate model metrics exceed a target accuracy threshold. Which architecture and pipeline design should you implement?

Deployment strategies (e.g., canary, blue/green, rolling, traffic splitting, feature flags) and defining success metrics based on application or ML pipeline telemetry

AdvancedProfessional Cloud DevOps Engineer

An enterprise runs a high-throughput microservices application on Google Kubernetes Engine (GKE) serving both gRPC and HTTP/2 traffic. The DevOps engineering team is implementing a progressive deployment pipeline to release new microservice versions safely. The deployment strategy must satisfy the following technical requirements: Route a controlled 5% canary slice of live production traffic to the new version, with the ability to dynamically adjust percentage weights without altering replica counts. Route internal quality assurance and beta testers directly to the canary version based on specific HTTP/gRPC request header values. Automatically identify and temporarily eject individual backend Pod instances that fail request thresholds during the canary phase to minimize user blast radius. Which architecture and traffic management strategy should the team implement?

Deployment strategies (e.g., canary, blue/green, rolling, traffic splitting, feature flags) and defining success metrics based on application or ML pipeline telemetry

AdvancedProfessional Cloud DevOps Engineer

Your organization operates a global, mission-critical application hosted on Google Cloud using Compute Engine Managed Instance Groups (MIGs) behind an external Application Load Balancer. To improve release velocity and prevent customer-facing incidents, the SRE team requires the deployment pipeline to automate canary deployments, metric validation, and traffic draining. The automated CI/CD workflow must satisfy the following criteria: Route a small percentage (5%) of live user requests to a canary backend group. Run automated canary analysis for 15 minutes by evaluating Cloud Monitoring metrics and health checks against defined Service Level Objectives (SLOs). Immediately redirect traffic away from the canary and gracefully drain active requests without dropping connections if an anomaly is detected. Automatically promote the canary to 100% traffic and orchestrate graceful connection draining on the retiring legacy backend MIG before deprovisioning. Which strategy should you integrate into your CI/CD pipeline to orchestrate this automated traffic draining and canary workflow?

Draining/redirecting traffic

AdvancedProfessional Cloud DevOps Engineer

A DevOps team is standardizing their cloud development environments across Google Cloud Workstations and Visual Studio Code. The team needs to modernize a legacy microservice codebase by refactoring functions, debugging issues, and automating unit test creation using Gemini Code Assist. The organization mandates strict enterprise security and IP compliance requirements: Local sensitive files containing secrets and proprietary algorithms must be completely excluded from the local AI context. AI-generated code suggestions must never provide direct matches from cited external open-source licensed code. Developers must be able to review proposed code modifications side-by-side against existing code before committing changes. Which configuration and workflow should the team implement to meet these requirements?

Leveraging AI to assist with development and operations (e.g., Gemini Code Assist, Gemini Cloud Assist, Gemini CLI)

AdvancedProfessional Cloud DevOps Engineer

An organization enforces strict data residency requirements by setting the constraints/gcp.resourceLocations constraint at the organization root with allowedValues set to European regions (in:eu-locations). A specialized data science team requires an exception to deploy new resources in us-central1 within their dedicated Google Cloud project, while maintaining European region access and preventing inheritance conflicts. How should the DevOps engineer configure the organization policy on the target project to grant this exception?

Data residency

AdvancedProfessional Cloud Data Engineer

Your organization uses a custom on-premises visualization tool to generate business intelligence reports. The tool currently connects to relational databases using standard SQL protocols and does not natively support the BigQuery API. You need to integrate this tool with BigQuery to analyze large datasets. Security policies mandate that the connection must not traverse the public internet, and BigQuery resources must be protected from data exfiltration by restricting access strictly to your hybrid network environment. How should you securely integrate the on-premises tool with BigQuery?

Connecting to tools

Professional Cloud DevOps Engineer

Gke Slo Fast Burn Automated Rollback

Related questions

Professional Cloud DevOps Engineer

Gke Slo Fast Burn Automated Rollback

What SLO Burn-Rate Alerting with Pub/Sub Is

How It Meets the Requirements

Key Advantages

Why This Is Optimal

Related questions

What SLO Burn-Rate Alerting with Pub/Sub Is

How It Meets the Requirements

Key Advantages

Why This Is Optimal