Examkin

Soru

Zorluk: Çok zorIncident Management and Automated Alerting

An enterprise Site Reliability Engineering (SRE) team is implementing an automated incident response and notification suppression pipeline on Google Cloud for a mission-critical financial settlement service. The pipeline must detect SLO degradation, prevent alert storms during active outages, execute automated self-healing without relying on long-lived service account keys or primitive IAM roles, and archive operational telemetry for post-mortems. In what chronological sequence should the SRE team structure the operational steps for this automated incident lifecycle?

  1. 1Configure Cloud Monitoring multi-window multi-burn-rate alerting policies to measure fast and slow error budget consumption against service SLOs.
  2. 2Route triggered alert payloads to a Cloud Pub/Sub incident topic while programmatically applying Cloud Monitoring Muting Rules to suppress secondary notification channels.
  3. 3Invoke a Cloud Run remediation service using Workload Identity to fetch correlated diagnostic error logs from Cloud Logging for the incident window.
  4. 4Execute targeted infrastructure recovery (such as shifting traffic via Cloud Load Balancing or initiating a rolling release rollback) using granular IAM role bindings.
  5. 5Confirm metric stabilization in Cloud Monitoring to clear the alert state, un-mute notifications, and export incident telemetry to BigQuery for post-mortem analysis.

Cevap

The correct sequence begins with configuring multi-window multi-burn-rate SLO alerting, followed by publishing incident payloads to Pub/Sub while enabling Cloud Monitoring Muting Rules, invoking a Workload Identity-authenticated Cloud Run remediation handler for diagnostic log extraction, executing targeted recovery using granular IAM roles, and concluding with metric stabilization verification, un-muting alerts, and exporting incident telemetry to BigQuery.
The proper operational order reflects Google Cloud SRE best practices: (1) Detection using multi-window multi-burn-rate SLO alerts ensures precise identification of error budget depletion; (2) Event decoupling via Pub/Sub paired with Cloud Monitoring Muting Rules prevents alert storms during active mitigation; (3) Automated triage workers leverage Workload Identity to inspect correlation logs securely; (4) Targeted remediation executes using least-privilege IAM roles; and (5) Metrics are verified for recovery before resolving the incident, removing muting rules, and streaming telemetry to BigQuery for post-mortem analysis.

Adım Adım Çözüm

1
Detect error budget depletion via Cloud Monitoring multi-window multi-burn-rate alerting policies.
High-fidelity incident alert triggers upon identifying sustained consumption of the service error budget.
SLO multi-burn-rate logic prevents false positives and detects rapidly evolving outages as the initial entry point of the incident lifecycle.
2
Publish alert event to Cloud Pub/Sub and enable Cloud Monitoring Muting Rules.
Incident event dispatches to automated pipelines while downstream notification channels are suppressed.
Alert suppression prevents alert fatigue and notification storms across operations teams while automated remediation is underway.
3
Trigger Cloud Run triage container using Workload Identity federation to inspect Cloud Logging traces.
Diagnostic context is securely fetched without static service account keys or primitive roles.
Automated handlers must query log correlation IDs to confirm failure modes prior to executing stateful remediation actions.
4
Perform infrastructure mitigation using least-privilege IAM service account permissions.
Service baseline health is restored via automated traffic re-routing or canary rollback.
Remediation acts on confirmed telemetry to stabilize the application layer.
5
Verify metric stabilization in Cloud Monitoring, lift muting rules, and stream incident telemetry to BigQuery.
The incident state automatically resolves and historical telemetry is stored for SRE post-mortems.
Formal incident closure requires verifying recovery in Monitoring baselines before resetting alert mutes and capturing post-mortem data.

Anahtar Kavram

End-to-end GCP incident management lifecycle using SLO multi-burn-rate alerting, Pub/Sub orchestration, Muting Rules for alert fatigue mitigation, Workload Identity security, and post-incident analytics.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Incident Management and Automated Alerting

Bu konudan daha fazla soru