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 engineering team is integrating Google Cloud Monitoring alerting policies with an external incident response webhook service. The operations team requires that all triggered incident notifications include rich context, specifically a formatted Markdown runbook link and dynamically resolved runtime metadata (such as the target project ID, affected compute zone, and triggering metric threshold).
Additionally, several test alert notifications fail to reach the external incident management webhook endpoint, and you must identify the root cause of the delivery dropouts.
Which configuration and troubleshooting approach should you implement?
Configure an Eventarc trigger routed to Workflows that intercepts metric violations, reformats raw JSON logs into HTML templates, and parses VPC Flow Logs to diagnose external webhook connection drops.
Embed Jinja2 templating syntax into the alert policy condition filter to render HTML tables, and review Cloud Profiler traces to identify remote webhook latency and delivery timeouts.
Inject custom bash scripts into the alert policy user labels to query Cloud Resource Manager via API, and configure Cloud Trace to capture external HTTP postback latency.
Define the alert policy documentation field using Markdown formatting and dynamic variable substitutions ${resource.labels.zone} and ${project_id}. Query Cloud Logging using Logs Explorer filtering on the notification_channel monitored resource type to inspect delivery error codes, timeouts, and connection failure logs.
Configure an Eventarc trigger routed to Workflows that intercepts metric violations, reformats raw JSON logs into HTML templates, and parses VPC Flow Logs to diagnose external webhook connection drops.
Embed Jinja2 templating syntax into the alert policy condition filter to render HTML tables, and review Cloud Profiler traces to identify remote webhook latency and delivery timeouts.
Inject custom bash scripts into the alert policy user labels to query Cloud Resource Manager via API, and configure Cloud Trace to capture external HTTP postback latency.
Define the alert policy documentation field using Markdown formatting and dynamic variable substitutions ${resource.labels.zone} and ${project_id}. Query Cloud Logging using Logs Explorer filtering on the notification_channel monitored resource type to inspect delivery error codes, timeouts, and connection failure logs.
Google Cloud Monitoring alerting policies support documentation templates that allow engineers to attach contextual guidance, runbooks, and debugging steps directly to triggered incidents. Alert notification channels (including custom HTTPS Webhooks, PagerDuty, and other third-party tools) transmit this documentation as part of the incident payload. When notification delivery issues occur, Google Cloud records operational logs for the notification_channel resource type in Cloud Logging.
StudyCerts
StudyCerts${resource.labels.zone}, ${project_id}, and ${metric.labels.instance_name}). When an incident fires, Cloud Monitoring replaces these placeholders with actual incident metadata.resource.type="notification_channel", providing specific HTTP status codes and diagnostic error messages.This solution relies entirely on native Cloud Monitoring documentation templating and built-in Cloud Logging audit and operational telemetry, avoiding custom scraping infrastructure or unmanaged workarounds.