Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Google Exam Professional Cloud DevOps Engineer Topic 1 Question 85 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 85
Topic #: 1
[All Professional Cloud DevOps Engineer Questions]

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

A. Ensure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident. and how to prevent a future occurrence of the incident.

Show Suggested Answer Hide Answer
Suggested 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.


by Jenelle at Jan 15, 2025, 05:13 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Davida
3 months ago
Option E is crucial - getting everyone involved in the postmortem process will help foster a collaborative spirit and shared ownership of solutions.
upvoted 0 times
Wayne
1 months ago
E. Ensure that all postmortems include all incident participants in postmortem authoring and share postmortems as widely as possible.
upvoted 0 times
...
Daren
1 months ago
A. Ensure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident. and how to prevent a future occurrence of the incident.
upvoted 0 times
...
...
Gracia
3 months ago
Haha, I bet the CTO is hoping for a 'no-blame' culture, but good luck with that! People are gonna want to know who screwed up.
upvoted 0 times
Romana
2 months ago
B) Ensure that all postmortems include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident.
upvoted 0 times
...
Adaline
2 months ago
A. Ensure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident, and how to prevent a future occurrence of the incident.
upvoted 0 times
...
...
Cherry
3 months ago
Option C is interesting - it avoids naming internal components, which could be sensitive information. And focusing on the severity and prevention is important too.
upvoted 0 times
King
2 months ago
C. Ensure that all postmortems include the severity of the incident, how to prevent a future occurrence of the incident, and what caused the incident without naming internal system components.
upvoted 0 times
...
Elli
3 months ago
A. Ensure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident, and how to prevent a future occurrence of the incident.
upvoted 0 times
...
...
Lonny
3 months ago
I prefer option C. It focuses on the severity of the incident and prevention without naming internal system components.
upvoted 0 times
...
Twana
3 months ago
I agree with Chantell. Option A covers all the important aspects of a good postmortem.
upvoted 0 times
...
Brent
3 months ago
I'm not sure about naming the person or team responsible. That could create a blame culture, which is the opposite of what we want. Maybe we could focus more on the systemic issues that led to the incident.
upvoted 0 times
Nan
2 months ago
E. Ensure that all postmortems include all incident participants in postmortem authoring and share postmortems as widely as possible.
upvoted 0 times
...
Terina
2 months ago
I agree, focusing on systemic issues is key to improving processes and preventing future incidents.
upvoted 0 times
...
Herman
3 months ago
C. Ensure that all postmortems include the severity of the incident, how to prevent a future occurrence of the incident, and what caused the incident without naming internal system components.
upvoted 0 times
...
Tennie
3 months ago
A. Ensure that all postmortems include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident.
upvoted 0 times
...
...
Chantell
3 months ago
I think option A is the best choice. We need to identify the root cause and the responsible party to prevent future incidents.
upvoted 0 times
...
Elenor
4 months ago
Option A seems the most comprehensive, as it covers the key elements of what caused the incident, who was responsible, and how to prevent it from happening again. This will help ensure the postmortem is actionable and effective.
upvoted 0 times
Alease
3 months ago
Sharing postmortems widely can also help prevent similar incidents in the future by increasing awareness.
upvoted 0 times
...
Margot
3 months ago
I think including the person or team responsible for causing the incident is crucial for accountability.
upvoted 0 times
...
Craig
3 months ago
I agree, option A covers all the important aspects of a good postmortem.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77