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

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 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?

AdvancedProfessional Cloud DevOps Engineer

A DevOps team manages a high-traffic microservices application running on Google Cloud and connected via Cloud Service Mesh. The service has a defined 30-day rolling Service Level Objective (SLO) of 99.9% availability, leaving an error budget of 0.1%. The team needs to design an automated error budget policy and alerting mechanism that achieves the following requirements: Accurately detects rapid budget consumption to page on-call engineers before significant budget is lost. Detects slow, persistent budget leakage to generate work tickets without causing on-call alert fatigue. Formally governs development velocity and operational priorities when the error budget is exhausted or severely threatened. Which strategy should the team implement?

AdvancedProfessional Cloud DevOps Engineer

An e-commerce organization runs a legacy order processing service that outputs structured JSON logs to stdout. The operations team needs to define a Service Level Indicator (SLI) to track the 95th and 99th percentile latency across different checkout categories without refactoring the application code to add OpenTelemetry or Prometheus metric client libraries. A sample log payload emitted by the service contains: { "message": "Order processed successfully", "transaction_type": "express_checkout", "duration_ms": 245.8 } How should the DevOps engineer configure Google Cloud Observability to generate the required latency SLI metrics?

AdvancedProfessional Cloud DevOps Engineer

A DevOps team at a regulated financial institution is architecting a data platform on Google Cloud that must comply with strict data residency regulations in Germany. The compliance rules mandate that all data at rest—including database records, object storage, analytical datasets, and cryptographic keys—must remain exclusively within Germany (europe-west3). Additionally, the relational database must maintain automated failover capabilities for business continuity without transferring data across country borders. Which architecture meets all regulatory compliance, data residency, and high-availability requirements?

AdvancedProfessional Cloud Data Engineer

An enterprise is designing a high-volume retail data warehouse in BigQuery. The data modeling team must capture slowly changing customer attributes (such as address, loyalty status, and assigned sales representative) to ensure accurate point-in-time historical analysis for sales orders. The analytical workload requires fast query performance across billions of sales records while minimizing expensive multi-table JOIN operations and computational shuffle overhead. Which schema design and temporal modeling strategy should the team implement?

Professional Cloud DevOps Engineer

Gke Slo Fast Burn Automated Rollback

Related questions