Blameless Post Mortem Root Cause Analysis Practices | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Blameless Post Mortem Root Cause Analysis Practices

Section: Troubleshooting/root cause analysis best practices

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.

A retail organization recently completed a major peak sales event on Google Cloud. During the event, a critical microservice suffered intermittent downtime when backend database connections were exhausted following an unexpected spike in checkout transactions. The on-call operations team mitigated the outage by restarting backend instances and manually raising connection limits.

Now that the event has concluded, the cloud architecture team is initiating the analysis phase. Which approach should the team adopt to conduct an effective root cause analysis and post-mortem to prevent future recurrence?

Audit operator logs during the outage to identify which engineer misconfigured the connection pool thresholds prior to the event, and require executive sign-off for any future parameter modifications.

Conduct a retrospective focused on identifying contributing systemic causes and establishing a timeline recap, evaluate predicted versus actual traffic, and document actionable remediation steps without attributing fault to individuals or teams.

Immediately migrate the backend database to a multi-region configuration without performing a timeline recap or evaluating resource utilization, as database saturation is inherently an infrastructure capacity limitation.

Close the incident report as fully resolved because manual mitigation successfully restored service health during the event, and archive operational monitoring dashboards.

Professional Cloud Architect

Blameless Post Mortem Root Cause Analysis Practices

Related questions