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.
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?
Custom dashboards in Cloud Monitoring provide visual representations of time-series data, charts, and log widgets for operational troubleshooting. An alert snooze temporarily mutes notifications for specified alerting policies during planned events such as maintenance windows.
DevOps engineers were performing planned infrastructure database migrations during an off-hours window and needed to prevent transient threshold alerts from paging on-call staff.
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.
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.
A metric-absence alerting policy triggers when Cloud Monitoring ceases to receive time-series data points from a monitored resource for a specified retest window (up to 23.5 hours). It is primarily designed to detect total service outages, crashed daemons, or network partitions where no telemetry is emitted.
The goal was to receive an email alert when an unmanaged monitoring agent on a standalone virtual machine stops streaming telemetry data altogether.
Exporting Cloud Logging entries to BigQuery via a Log Router sink allows organizations to run complex analytical SQL queries across petabytes of historical log data. It is well-suited for security forensics, long-term auditing, and monthly reporting.
You needed to generate bi-weekly or monthly retrospective reports analyzing overall error trends across microservices for capacity planning.
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