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.
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?
This architecture exports alert notifications from Google Cloud Monitoring to a Pub/Sub topic, where a scheduled Cloud Tasks queue or worker batches alerts over a 15-minute rolling window before creating incidents.
The goal was to aggregate high-volume, non-urgent telemetry logs or cost-monitoring anomalies where near-real-time response is unnecessary.
This approach routes all Google Cloud Monitoring notifications through a single generic Webhook notification channel to an intermediary custom service (such as a Cloud Function or container) that parses payloads, evaluates severity, and calls third-party APIs.
The organization required advanced custom payload transformations, data masking, or proprietary on-premises incident management tools that lack native Google Cloud Monitoring connectors.
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.
This approach attempts to use an account-level User API token or global administrator credential across all alerting policies, relying on dynamic runtime label injection to modify downstream incident escalation tiers.
The team were performing administrative automation (e.g., provisioning new incident services via Terraform) rather than routing operational alert notifications.
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