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
A DevOps team manages a tier-1 microservices platform on Google Cloud and uses Google Cloud Monitoring for observability. The team is integrating their alerting infrastructure with PagerDuty and Rootly to automate incident response workflows.
They have the following operational requirements:
How should the team configure Google Cloud Monitoring and the incident response platform to achieve this lifecycle integration?
Create distinct notification channels in Cloud Monitoring for each service level using corresponding integration routing keys, map these channels to alerting policies based on severity, and rely on Cloud Monitoring's native incident state notifications for automatic resolution.
Configure Cloud Monitoring to send alerts to a Pub/Sub topic and schedule a Cloud Task to batch process and escalate incidents every 15 minutes based on cumulative error count.
Configure an Account API User Token across all Cloud Monitoring notification channels and use alerting policy user labels to dynamically override external escalation rules at trigger time.
Configure a single global Webhook notification channel pointing to a generic REST endpoint, write a custom middleware to filter severity, and disable auto-close settings in Cloud Monitoring to force manual engineer acknowledgment.
Create distinct notification channels in Cloud Monitoring for each service level using corresponding integration routing keys, map these channels to alerting policies based on severity, and rely on Cloud Monitoring's native incident state notifications for automatic resolution.
Native integration between Google Cloud Monitoring and incident management platforms like PagerDuty or Rootly connects alerting policies directly to external incident response services. By utilizing service-specific integration keys (routing keys), Cloud Monitoring dispatches incident lifecycle events—including triggers, acknowledgments, and resolutions—directly into the incident platform.
This approach leverages native platform capabilities to maintain strict synchronization between metric states and incident tickets while upholding least-privilege service routing and automated incident clearance.
Configure Cloud Monitoring to send alerts to a Pub/Sub topic and schedule a Cloud Task to batch process and escalate incidents every 15 minutes based on cumulative error count.
Configure an Account API User Token across all Cloud Monitoring notification channels and use alerting policy user labels to dynamically override external escalation rules at trigger time.
Configure a single global Webhook notification channel pointing to a generic REST endpoint, write a custom middleware to filter severity, and disable auto-close settings in Cloud Monitoring to force manual engineer acknowledgment.