Valid Professional-Cloud-DevOps-Engineer Dumps shared by ExamDiscuss.com for Helping Passing Professional-Cloud-DevOps-Engineer Exam! ExamDiscuss.com now offer the newest Professional-Cloud-DevOps-Engineer exam dumps, the ExamDiscuss.com Professional-Cloud-DevOps-Engineer exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Professional-Cloud-DevOps-Engineer dumps with Test Engine here:
Your CTO has asked you to implement a postmortem policy on every incident for internal use. You want to define what a good postmortem is to ensure that the policy is successful at your company. What should you do? Choose 2 answers
Correct Answer: B,E
The correct answers are B and E A good postmortem should include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident1. This helps to identify the root cause of the problem, the impact of the incident, and the actions to take to mitigate or eliminate the risk of recurrence. A good postmortem should also include all incident participants in postmortem authoring and share postmortems as widely as possible2. This helps to foster a culture of learning and collaboration, as well as to increase the visibility and accountability of the incident response process. Answer A is incorrect because it assigns blame to a person or team, which goes against the principle of blameless postmortems2. Blameless postmortems focus on finding solutions rather than pointing fingers, and encourage honest and constructive feedback without fear of punishment. Answer C is incorrect because it omits how the incident could have been worse, which is an important factor to consider when evaluating the severity and impact of the incident1. It also avoids naming internal system components, which makes it harder to understand the technical details and root cause of the problem. Answer D is incorrect because it omits how to prevent a future occurrence of the incident, which is the main goal of a postmortem1. It also avoids naming customer information, which may be relevant for understanding the impact and scope of the incident.