Answer-first summary for fast verification
Answer: An explanation of the root cause of the incident., A list of action items to prevent a recurrence of the incident
A postmortem aims to document an incident, learn from it, and prevent recurrence. According to Google's DevOps practices and industry standards: - **A (Root cause explanation)**: Essential for understanding the underlying issues to address systemic failures. - **C (Action items)**: Critical for implementing preventive measures and tracking improvements. Options B, D, and E are not recommended: - **B**: Blaming individuals violates blameless postmortem principles, fostering fear instead of learning. - **D**: Subjective severity comparisons distract from factual analysis and actionable outcomes. - **E**: Including full design documents is unnecessary; postmortems should focus on incident specifics, not exhaustive documentation.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
When drafting a postmortem for a user-impacting incident to prevent recurrence, which two of the following sections must be included? (Select two.)
A
An explanation of the root cause of the incident.
B
A list of employees responsible for causing the incident
C
A list of action items to prevent a recurrence of the incident
D
Your opinion of the incident's severity compared to past incidents
E
Copies of the design documents for all the services impacted by the incident
No comments yet.