Examkin

Question

Difficulty: MediumIncident Management and Automated Alerting

Your organization is establishing an automated incident management workflow in Google Cloud to rapidly mitigate unexpected latency spikes in a critical microservice. Place the following operational and technical steps in the correct chronological order from initial detection setup to post-incident validation.

  1. 1Configure a Cloud Monitoring alerting policy based on microservice latency threshold conditions.
  2. 2Attach a Google Cloud Pub/Sub topic notification channel to the configured alerting policy.
  3. 3Execute automated remediation via an event-driven Cloud Run function triggered by incoming Pub/Sub alert messages.
  4. 4Verify incident resolution and post-remediation service health using Cloud Monitoring dashboards.

Answer

The correct operational sequence is: 1) Configure a Cloud Monitoring alerting policy based on microservice latency threshold conditions, 2) Attach a Google Cloud Pub/Sub topic notification channel to the configured alerting policy, 3) Execute automated remediation via an event-driven Cloud Run function triggered by incoming Pub/Sub alert messages, and 4) Verify incident resolution and post-remediation service health using Cloud Monitoring dashboards.
The workflow follows a standard event-driven incident lifecycle in GCP: first establishing detection thresholds in Cloud Monitoring, next integrating an asynchronous Pub/Sub notification channel, then triggering automated serverless remediation upon incident creation, and finally confirming metric normalization on operational dashboards.

Step-by-Step Solution

1
Define threshold detection rules
Cloud Monitoring policy actively monitors latency telemetry for condition breaches.
Automated incident management requires explicit SLI/SLO threshold boundaries to trigger alerts.
2
Bind Pub/Sub notification channel to the policy
Alert state transitions publish structured incident payloads to the designated Pub/Sub topic.
Pub/Sub provides an asynchronous, decoupled broker for event-driven automation in GCP.
3
Trigger programmatic remediation
Cloud Run function ingests the alert event and scales backend resources or adjusts traffic routing.
Automated mitigation logic must execute in response to alert notifications to reduce mean time to resolution (MTTR).
4
Validate service recovery
Cloud Monitoring metrics confirm latency has subsided and error budgets are preserved.
Post-incident verification confirms the automated action successfully resolved the incident without manual intervention.

Key Concept

Automated Incident Escalation and Event-Driven Remediation
Rate this question

Topics

Incident Management and Automated Alerting

More questions from this topic