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 team manages a business-critical microservice running on Google Kubernetes Engine (GKE). The team has defined an availability Service Level Objective (SLO) of 99.9% over a rolling 30-day window.
Currently, the team experiences alert fatigue caused by transient error spikes triggering paging alerts, while simultaneously missing slow, steady budget drain that exhausts the monthly error budget before scheduled reviews.
Which alerting strategy should the team implement in Cloud Monitoring to reliably detect both rapid and slow budget depletion while minimizing false positives?
The select_slo_compliance time-series selector calculates the overall ratio of good units to total units since the beginning of the SLO compliance period.
select_slo_compliance selector is explicitly documented as unsupported for alerting policies because it provides a historical, cumulative view rather than an operationally urgent real-time signal.select_slo_compliance in alerting policies.The team needed an executive scorecard metric displayed on a quarterly dashboard to review high-level contract compliance.
The select_slo_budget_fraction selector queries the remaining fraction of an SLO's error budget (ranging from negative infinity to 1.0) over a designated compliance period.
select_slo_budget_fraction is not supported for alerting.MetricThreshold filter conditions.The team were generating monthly reporting dashboards in Metrics Explorer or Cloud Monitoring Dashboards to visually track remaining budget headroom.
Multi-burn-rate alerting is a best-practice Site Reliability Engineering (SRE) strategy that monitors the rate at which an error budget is consumed across multiple time horizons. In Google Cloud Monitoring, this is configured using the select_slo_burn_rate time-series selector, which measures the ratio of the current failure rate to the sustainable failure rate for an SLO.
Using two complementary policies with different lookback windows and burn-rate multipliers ensures comprehensive coverage of failure modes, balancing rapid time-to-detect (TTD) with high alert precision.
This approach configures a single burn-rate alert in Cloud Monitoring using select_slo_burn_rate with a 1-hour lookback period and a threshold of 1 (the exact sustainable failure rate).
The workload experienced completely constant, unvarying traffic 24/7 and the organization required instant alerts for any single deviation from ideal SLO compliance, regardless of operational overhead.
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