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

Google Exam Professional Cloud DevOps Engineer Topic 5 Question 90 Discussion

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

Your team is writing a postmortem after an incident on your external facing application Your team wants to improve the postmortem policy to include triggers that indicate whether an incident requires a postmortem Based on Site Reliability Engineenng (SRE) practices, what triggers should be defined in the postmortem policy?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, C

The best options for defining triggers that indicate whether an incident requires a postmortem based on Site Reliability Engineering (SRE) practices are an external stakeholder asks for a postmortem and data is lost due to an incident. An external stakeholder is someone who is affected by or has an interest in the service, such as a customer or a partner. If an external stakeholder asks for a postmortem, it means that they are concerned about the impact or root cause of the incident, and they expect an explanation and remediation from the service provider. Therefore, this should trigger a postmortem to address their concerns and improve their satisfaction. Data loss is a serious consequence of an incident that can affect the integrity and reliability of the service. If data is lost due to an incident, it means that there was a failure in the backup or recovery mechanisms, or that there was a corruption or deletion of data. Therefore, this should trigger a postmortem to investigate the cause and impact of the data loss, and to prevent it from happening again.


Contribute your Thoughts:

Chaya
2 days ago
Hmm, I think the triggers should be more about the impact of the incident, not just who requests it. I'd say B and D are the way to go - data loss and failed instances seem like clear reasons to do a postmortem.
upvoted 0 times
...
Sheridan
6 days ago
I believe E should also be included as a trigger. Rolling back a release due to an issue is a significant event that requires analysis.
upvoted 0 times
...
Novella
13 days ago
I agree with you, Danilo. Data loss and instance failure are critical incidents that should trigger a postmortem.
upvoted 0 times
...
Danilo
22 days ago
I think B and D should be defined as triggers in the postmortem policy.
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