Master the terminology behind formal production change approval processes.
0 / 5 completed
1 / 5
At standup, a dev mentions their infrastructure change needs sign-off through a formal process before it can be applied to production. What is this process called?
Change management is the formal process for proposing, reviewing, approving, and tracking changes to production systems, aimed at reducing the risk of unplanned outages from poorly coordinated changes. It typically applies most strictly to higher-risk infrastructure or configuration changes. This differs from a design review, which happens earlier and focuses on technical approach rather than deployment authorization.
2 / 5
During a design review, the team classifies a change as low-risk, routine, and pre-approved for streamlined handling. What category is this?
A standard change is a well-understood, low-risk, previously vetted type of change that can follow a streamlined approval path rather than requiring full case-by-case review each time. This classification speeds up routine, low-risk work. It contrasts with changes requiring more scrutiny due to higher potential impact.
3 / 5
In a code review, a dev needs to push an urgent security patch outside the normal change window. What category of change does this represent?
An emergency change follows an expedited approval path for urgent situations, like a critical security patch, where waiting for the normal change management cycle would itself create unacceptable risk. It typically still requires some lightweight approval and after-the-fact documentation. This balances urgency against the value of oversight.
4 / 5
An incident report shows an unapproved change was applied directly to production, bypassing the review process, and caused an outage. What process gap does this reveal?
An outage caused by a change that bypassed the established review process points to an enforcement gap, not necessarily a flaw in the process design itself. Ensuring the process is consistently followed, with technical guardrails where possible, closes this gap. This is a recurring root cause in postmortems tracing back to unauthorized production changes.
5 / 5
During a PR review, a teammate asks why some low-risk changes skip the full change advisory review while others require it. What determines this?
The risk classification of a change, such as standard, normal, or emergency, determines which approval path it follows, allowing low-risk routine changes to move faster while higher-risk changes get proportionally more scrutiny. This risk-based approach avoids treating every change identically regardless of actual impact potential. It is a core design principle behind effective change management processes.