SRE Change Management & Postmortem Practices 1 — Questions and Answers

Question 1: What is the primary goal of change management in SRE?

To delay production deployments.
To eliminate the need for updates.
To reduce risk and ensure system stability (Correct answer)
To reduce team workload temporarily.

Correct answer: To reduce risk and ensure system stability

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?

To assign blame.
To document customer complaints.
To highlight individual mistakes.
To learn from incidents and improve systems (Correct answer)

Correct answer: To learn from incidents and improve systems

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?

Skipping QA testing.
Manual updates at peak hours.
Canary deployments and feature flags (Correct answer)
Deploying all updates at once.

Correct answer: Canary deployments and feature flags

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?

A list of people responsible.
Steps for punishing errors.
Technical root causes and future mitigations (Correct answer)
Names of underperforming staff.

Correct answer: Technical root causes and future mitigations

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?

It removes the need for documentation.
It prevents testing from happening.
It supports visibility and rollback during changes (Correct answer)
It limits collaboration among developers.

Correct answer: It supports visibility and rollback during changes

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.

Question 6: Why are frequent, small changes encouraged in SRE?

They are more exciting.
They make debugging more difficult.
They simplify testing and minimize risk (Correct answer)
They reduce team communication.

Correct answer: They simplify testing and minimize risk

Frequent, small changes are a cornerstone of agile and SRE practices. Smaller changes are easier to test thoroughly, isolate potential issues, and debug if problems arise. This approach significantly minimizes the blast radius of any single change, making deployments less risky and allowing for faster recovery if an issue does occur, ultimately leading to greater system stability and confidence in deployments.

Question 7: What is the purpose of a change review board (CRB)?

To automate testing.
To delay all changes.
To approve or deny changes based on impact analysis (Correct answer)
To handle customer service.

Correct answer: To approve or deny changes based on impact analysis

A Change Review Board (CRB) is a formal group responsible for evaluating proposed changes to IT systems or services. Its primary purpose is to assess the potential impact and risks of these changes, ensuring they align with business objectives and minimize disruption. By approving or denying changes based on a thorough impact analysis, the CRB helps maintain system stability and service quality.

Question 8: What does a rollback strategy ensure?

More errors during deployment.
No monitoring is needed.
There’s a backup plan if the change fails (Correct answer)
Increased deployment time.

Correct answer: There’s a backup plan if the change fails

A rollback strategy is a critical component of robust deployment and change management processes. It ensures that if a new change or deployment introduces errors or fails to perform as expected, the system can be quickly and safely reverted to a previous stable state. This backup plan minimizes downtime and reduces the negative impact of failed deployments on users and services.

Question 9: Which tool is useful for tracking incidents and changes?

MS Paint.
YouTube.
Jira or ServiceNow for traceability (Correct answer)
Email only.

Correct answer: Jira or ServiceNow for traceability

Tools like Jira and ServiceNow are invaluable for tracking incidents and changes due to their comprehensive capabilities. They provide centralized platforms for logging, categorizing, assigning, and monitoring the entire lifecycle of incidents, problems, and changes. This ensures clear traceability, accountability, and provides historical data essential for analysis and continuous improvement in IT operations.

SRE Change Management & Postmortem Practices 1

What is the primary goal of change management in SRE?