SRE Change Management & Postmortem Practices

Question 1

What is the primary goal of change management in SRE?

Accepted Answer

To reduce risk and ensure system stability

Answer

The primary goal of change management in SRE is to introduce changes to systems in a controlled and predictable manner. This involves planning, testing, and carefully rolling out modifications to minimize the risk of outages or performance degradation. By managing changes effectively, SRE teams aim to maintain high system stability and reliability while still enabling continuous improvement and innovation.

Question 2

Why are postmortems important after incidents?

Accepted Answer

To learn from incidents and improve systems

Answer

Postmortems (or Root Cause Analyses) are critical SRE practices conducted after an incident, regardless of its severity. Their purpose is not to assign blame but to thoroughly investigate the incident's contributing factors, understand what went wrong, and identify actionable improvements to prevent recurrence. This learning process is vital for continuous system and process enhancement, fostering a culture of improvement.

Question 3

Which practice helps reduce risk during changes?

Accepted Answer

Canary deployments and feature flags

Answer

Canary deployments and feature flags are powerful techniques for reducing risk during changes. Canary deployments involve rolling out a new version to a small subset of users or servers first, monitoring its performance, and then gradually expanding the rollout if stable. Feature flags allow specific functionalities to be toggled on or off without deploying new code, enabling safe experimentation and quick rollbacks if issues arise, thus minimizing risk.

Question 4

What should a blameless postmortem include?

Accepted Answer

Technical root causes and future mitigations

Answer

A blameless postmortem focuses on systemic issues and technical failures rather than individual mistakes. It should thoroughly analyze the technical root causes of an incident, including contributing factors and latent conditions. Crucially, it must also identify concrete, actionable steps and future mitigations to prevent similar incidents from happening again, fostering a culture of continuous learning and improvement without fear of reprisal.

Question 5

What is the role of version control in change management?

Accepted Answer

It supports visibility and rollback during changes

Answer

Version control systems (like Git) are fundamental to effective change management. They provide a complete, auditable history of all changes made to configuration files, code, and infrastructure definitions. This visibility allows teams to understand the evolution of systems and, critically, enables quick and reliable rollbacks to previous stable states if a change introduces problems, thereby minimizing downtime and supporting safe changes.

(SRE) Site Reliability Engineering Foundation Certification Practice Test

(SRE) Site Reliability Engineering Foundation Certification Practice Test

SRE Change Management & Postmortem Practices