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 DevOps team is implementing a Service Level Objective (SLO) error-rate alerting policy in Google Cloud Monitoring for a microservice deployed across 200 Compute Engine virtual machine (VM) instances. The initial configuration computed a ratio across two independent custom metrics: custom.googleapis.com/rpc/total_count and custom.googleapis.com/rpc/error_count.
During low-traffic intervals, on-call engineers receive frequent false-positive alerts caused by anomalous ratio spikes (such as 1/0 or 2/1) evaluated on individual instances. You need to redesign the custom metrics, alignment, and alerting policy condition to eliminate these ratio calculation anomalies, reduce alert fatigue, and minimize monitoring costs.
What should you do?
This strategy maintains two distinct metric types, assigns the rolling window function to percent change to measure growth rate, and divides monitoring into 200 distinct alerting policies (one policy per Compute Engine instance).
percent change window function measures the acceleration or deceleration of a single metric's average value against a previous 10-minute baseline; it cannot compute an error-over-total ratio SLI.percent change compares the current 10-minute sliding window against the prior 10-minute period and cannot be customized for instantaneous ratio thresholds.You specifically wanted to be alerted when the rate of overall resource consumption on a single critical standalone instance surged unexpectedly by 50% compared to its previous 10-minute trend.
This approach keeps the two distinct custom counter metrics and minimizes the alignment window to 1 second while evaluating the ratio condition on raw, unaggregated time series across every VM instance.
1/0 and 2/1 ratio anomalies whenever error counters arrive in adjacent 1-second windows separate from total count updates.The microservice were an ultra-high-throughput real-time streaming system where every individual node had hardware-synchronized metrics emitting thousands of samples per second without concern for monitoring costs or low-traffic anomalies.
This option attempts to construct a multi-condition alerting policy that combines a log-entry filter condition using the LogMatch condition type alongside a MetricThreshold ratio condition over unaggregated logs.
LogMatch condition, it must be the only condition in the policy. You cannot combine LogMatch with metric-threshold conditions in a multi-condition policy.AND/OR) with metric conditions.LogMatch alerts on immediate log occurrences rather than computing regularized ratios over sliding time windows.You needed an immediate notification whenever an explicit, rare fatal exception string appeared in application logs (such as an unrecoverable database corruption error) independent of any numerical threshold or ratio.
Computing ratios using a single metric type with dimensional labels (such as response_code or status="OK"|"ERROR") ensures that every event is recorded atomically within the exact same time series stream. Combining this with an extended alignment window and cross-series reduction regularizes time-series data into stable aggregates before evaluating ratio thresholds.
status label ensures consistent alignment interval boundaries for both successful and failed events.Google Cloud Monitoring strongly recommends using a single metric with label filters for ratio conditions because cross-metric calculations across different metric descriptors inherently introduce sampling drift. Aggregating across time series avoids individual node noise while ensuring true service-level degradation is rapidly detected.
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