ITIL4F ITIL Management Practices Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Normal changes are always low-risk; emergency changes are high-risk

  Why it's wrong here

  Normal changes are distinguished by their adherence to a predefined, often multi-stage, assessment and approval workflow, irrespective of their inherent risk level. While many normal changes are indeed low-risk, the category encompasses all changes that can follow the standard change enablement process without requiring expedited handling. Conversely, emergency changes are characterized by their immediate need to address critical incidents or prevent severe business impact, necessitating an accelerated process that prioritizes speed over the full standard review, often for high-risk situations but not exclusively defined by risk.

• ✗

  Emergency changes are implemented without any approval

  Why it's wrong here

  The assertion that emergency changes are implemented without any approval is incorrect, as all changes, even urgent ones, require some form of authorization to proceed. While the approval process for emergency changes is significantly streamlined and often delegated to a smaller, more agile group, such as the Emergency Change Advisory Board (ECAB) or a designated authority, formal consent is still a critical governance step. This expedited approval ensures accountability and minimizes potential negative consequences while facilitating rapid resolution of critical issues.

• ✓

  Normal changes are assessed and approved through standard procedures; emergency changes require urgent handling to avoid business impact

  Why this is correct

  This statement accurately differentiates normal and emergency changes by focusing on their procedural characteristics and underlying urgency. Normal changes are systematically planned, assessed, and approved through established, comprehensive procedures, allowing for thorough risk evaluation and resource allocation. In contrast, emergency changes are necessitated by an immediate, critical need to restore service or prevent significant business disruption, demanding an expedited assessment and approval process to mitigate severe impact swiftly.

• ✗

  Emergency changes are only used for security incidents

  Why it's wrong here

  Limiting emergency changes solely to security incidents is an inaccurate and overly narrow definition of their scope within ITIL change management. Emergency changes are broadly applicable to any critical incident or problem that poses an immediate and severe threat to business operations, service availability, or data integrity, requiring urgent resolution. This can include major system outages, critical performance degradations, or other high-impact failures that demand immediate intervention beyond just security-related events.

Go deeper

Related to this question