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 team manages critical Compute Engine workloads where unexpected storage and memory exhaustion can cause application downtime. You need to implement a proactive incident management workflow in Cloud Monitoring that satisfies the following requirements:
Which configuration should you implement in Cloud Monitoring?
Create a standard metric-threshold alerting policy configured with 'Missing data points treated as values that violate the policy condition' and add a custom notification subject line.
Configure an alerting policy snooze with a 12-hour recurring schedule, set evaluation of missing data to inactive, and assign the Monitoring Cloud Console Incident Editor role to the responder group.
Create a forecasted metric-value alerting policy with a 12-hour forecast window, configure a retest window under advanced options, attach custom policy user labels for severity, and embed playbook links with markdown variables in the documentation section.
Create a metric-absence alerting policy with a trigger duration of 12 hours, set the auto-close duration to 30 minutes, and configure Cloud Logging export sinks to BigQuery.
Create a standard metric-threshold alerting policy configured with 'Missing data points treated as values that violate the policy condition' and add a custom notification subject line.
Configure an alerting policy snooze with a 12-hour recurring schedule, set evaluation of missing data to inactive, and assign the Monitoring Cloud Console Incident Editor role to the responder group.
Create a forecasted metric-value alerting policy with a 12-hour forecast window, configure a retest window under advanced options, attach custom policy user labels for severity, and embed playbook links with markdown variables in the documentation section.
A forecasted metric-value alerting policy in Cloud Monitoring uses predictive decision algorithms trained on historical time-series data to evaluate whether a metric will violate a specified threshold within a future time window (the forecast window).
severity: critical) annotates incidents for proper upstream routing in incident management systems, while including markdown-formatted playbook links and documentation variables (${metric.display_name}, ${resource.name}) directly delivers actionable remediation context to on-call engineers.Create a metric-absence alerting policy with a trigger duration of 12 hours, set the auto-close duration to 30 minutes, and configure Cloud Logging export sinks to BigQuery.