Documenting each proposed change in a standardized change-request (RFC) that states its purpose, scope, risk and required stakeholder approvals is a core tenet of change-management frameworks such as ITIL. It ensures every change is reviewed, authorized and tracked before implementation, reducing unforeseen impact and providing accountability.
The other options omit at least one key element (formal approval, documented risk analysis, or pre-implementation record-keeping) and therefore do not by themselves guarantee controlled, predictable change.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is an RFC in the context of IT change management?
Open an interactive chat with Bash
What is ITIL, and how does it relate to change management?
Open an interactive chat with Bash
Why is documenting risks important in a change-request process?