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

  Why this is correct

  Normal changes are non-pre-approved changes that must follow a full, structured change process, including assessment, authorization, and scheduling, to ensure minimal risk and impact. These changes typically require a change authority's approval based on a thorough evaluation of their potential effects on services and infrastructure. They are scheduled and implemented according to a defined change calendar, balancing speed with stability. This category encompasses most significant service improvements or infrastructure modifications.

• ✗

  Urgent

  Why it's wrong here

  While changes often carry a sense of urgency, "Urgent" is not a recognized type of change within the ITIL 4 framework for change enablement. ITIL 4 categorizes changes based on their risk, approval requirements, and speed of implementation, rather than simply their perceived urgency. The framework uses "Emergency changes" to address situations demanding immediate action, which inherently implies high urgency, but "Urgent" itself is not a distinct classification.

• ✓

  Emergency

  Why this is correct

  Emergency changes are implemented with the highest priority to resolve critical incidents, apply security patches, or address other urgent issues that could severely impact business operations if delayed. These changes often bypass some standard assessment and approval steps to expedite resolution, with authorization typically granted by an emergency change authority. Post-implementation reviews and retrospective approval are common to ensure proper documentation and minimize future risks.

• ✓

  Standard

  Why this is correct

  Standard changes are low-risk, pre-authorized changes that are well-understood, fully documented, and do not require additional authorization before implementation. These are routine service requests or operational tasks, such as password resets or software installations, where the procedure is clear and the outcome predictable. Their pre-approval allows for efficient execution, streamlining common activities and reducing the burden on change authorities.

• ✗

  Minor

  Why it's wrong here

  "Minor" is not an official or recognized classification for types of changes within the ITIL 4 change enablement practice. While changes can vary in scale and impact, ITIL 4 categorizes them primarily into Standard, Normal, and Emergency based on their risk, approval process, and urgency, rather than simply their perceived magnitude. Even small changes must fall into one of these three formal categories to ensure appropriate governance and control.

Go deeper

Related to this question