Exam Professional Cloud DevOps Engineer topic 1 question 105 discussion

Based on the SRE postmortem culture guidelines, the triggers for writing a postmortem should be objective events that signal significant service impact or loss. In this context, the most appropriate triggers are: • A. An external stakeholder asks for a postmortem • B. Data is lost due to an incident These triggers reflect situations where customer or external impact is evident (as in A) or when there is a clear degradation in service reliability (as in B). External requests indicate that the incident affected users or partners enough to demand transparency and learning, while data loss is a critical failure that warrants a detailed investigation to prevent recurrence.

https://sre.google/sre-book/postmortem-culture/ suggests B and E as objective triggers. On a side note, it says any stakeholder can request but that would qualify A and C also but we objectively know B is an answer by the docs. "In addition to these objective triggers, any stakeholder may request a postmortem for an event. Blameless postmortems are a tenet of SRE culture." "On-call engineer intervention (release rollback, rerouting of traffic, etc.)" E is also a toss up since it doesn't state any manual intervention was required and the rollback happened by itself. BE & AB are solid choices. But I would lean more to BE since they are listed under objective requirements although no manual intervention was required for the rollback..

A over D because An external stakeholder requesting a postmortem indicates a significant impact from their perspective. This highlights the need for a thorough investigation to understand the customer experience, mitigate future issues, and potentially regain trust. Not D because Instance failures often happen, and automated systems should handle them gracefully. A postmortem is warranted only if customer impact occurs despite the redundancy and recovery mechanisms.

should be A and B, SRE book says: common postmortem triggers include: User-visible downtime or degradation beyond a certain threshold (N/A) "Data loss of any kind" <----------------------------- (B) On-call engineer intervention (release rollback, rerouting of traffic, etc.) (N/A) A resolution time above some threshold (N/A) A monitoring failure (which usually implies manual incident discovery) (N/A) not manual incident discovery here It is important to define postmortem criteria before an incident occurs so that everyone knows when a postmortem is necessary. In addition to these objective triggers, "any stakeholder may request a postmortem for an event." <-------------------------- (A)

that's right.

Choose B & E. In accordance with Site Reliability Engineering (SRE) practices, the triggers defined in a postmortem policy should be focused on incidents that have significant impact and provide valuable learning opportunities. Option B, "Data is lost due to an incident," is a critical trigger as data loss is a severe consequence that necessitates a thorough examination to prevent future occurrences. Option E, "The CD pipeline detects an issue and rolls back a problematic release," is a crucial trigger indicating that the continuous delivery (CD) pipeline has identified an issue and initiated a rollback, pointing to potential challenges in the release process. These triggers highlight impactful incidents with potential systemic issues, aligning with SRE principles to conduct postmortems for events that contribute to system resilience and reliability.

E is expected behaviour if you set up the pipelines properly so I would go for A and B.

Answer is BE Because those are major incident that disrupted our service.

Right answer

BE for sure.

Answer should be BE.

Answer should be BE