Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Consolidate into a single custom metric type that records all RPCs and uses a response status label, then configure the alerting condition to aggregate across instances using an alignment window longer than the metric sampling period.
Retain the two separate custom metrics, set the rolling window function to percent change without alignment, and create 200 distinct single-condition alerting policies targeting each individual VM instance.
Retain both separate custom metrics, set the condition alignment window to 1 second to capture real-time granularity, and evaluate the ratio across raw, unaggregated time series for each VM instance.
Combine a LogMatch condition scanning application error logs with a MetricThreshold ratio condition in a single multi-condition alerting policy using unaggregated log views.
Consolidate into a single custom metric type that records all RPCs and uses a response status label, then configure the alerting condition to aggregate across instances using an alignment window longer than the metric sampling period.
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.
StudyCerts
StudyCertsstatus 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.
Retain the two separate custom metrics, set the rolling window function to percent change without alignment, and create 200 distinct single-condition alerting policies targeting each individual VM instance.
Retain both separate custom metrics, set the condition alignment window to 1 second to capture real-time granularity, and evaluate the ratio across raw, unaggregated time series for each VM instance.
Combine a LogMatch condition scanning application error logs with a MetricThreshold ratio condition in a single multi-condition alerting policy using unaggregated log views.