nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #2

Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe…

The correct answer is B. Ensure that test cases that catch errors of this type are run successfully before new software. To prevent future severe incidents, especially those caused by software changes, SRE postmortems advocate for implementing systemic improvements like enhanced pre-deployment testing.

Submitted by yuki_2020· Apr 18, 2026Applying site reliability engineering principles to a service

Question

Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe incidents from happening in the future. What should you do?

Options

  • AIdentify engineers responsible for the incident and escalate to their senior management.
  • BEnsure that test cases that catch errors of this type are run successfully before new software
  • CFollow up with the employees who reviewed the changes and prescribe practices they should
  • DDesign a policy that will require on-call teams to immediately call engineers and management to

How the community answered

(49 responses)
  • A
    12% (6)
  • B
    76% (37)
  • C
    4% (2)
  • D
    8% (4)

Why each option

To prevent future severe incidents, especially those caused by software changes, SRE postmortems advocate for implementing systemic improvements like enhanced pre-deployment testing.

AIdentify engineers responsible for the incident and escalate to their senior management.

Identifying and escalating responsible engineers goes against the SRE blame-free postmortem culture, which focuses on systemic issues rather than individual fault.

BEnsure that test cases that catch errors of this type are run successfully before new softwareCorrect

A core SRE principle for incident prevention, especially post-mortem, is to identify the root cause and implement systemic changes to prevent recurrence. Enhancing pre-release testing with specific test cases designed to catch similar errors is a proactive and effective way to improve software quality and reduce future risks, aligning with a blame-free culture focused on process improvement.

CFollow up with the employees who reviewed the changes and prescribe practices they should

Prescribing practices to reviewers without addressing the underlying systemic issue (like inadequate testing or review processes) is less effective and still has a punitive undertone.

DDesign a policy that will require on-call teams to immediately call engineers and management to

Designing a policy for immediate calls focuses on communication during an incident, not on preventing the incident from happening in the first place.

Concept tested: SRE postmortem culture, incident prevention, automated testing

Source: https://sre.google/sre-book/postmortem-culture/

Topics

#SRE#Postmortem analysis#Incident prevention#Automated testing

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice