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.

• ✗

  A standard change cannot be scheduled, while a normal change can be scheduled

  Why it's wrong here

  Standard changes, by definition, are routine and repeatable, making them ideal candidates for scheduling, either at fixed intervals or upon specific triggers. The statement incorrectly implies a lack of scheduling capability, when in fact, effective management of standard changes often relies on their predictable scheduling. Normal changes are also planned and scheduled through the change enablement process, often with more extensive planning cycles.

• ✗

  A standard change is only used for emergency fixes, while a normal change is for planned improvements

  Why it's wrong here

  Standard changes are specifically designed for low-risk, frequently occurring activities that have a proven, documented procedure, such as password resets or software installations. They are distinct from emergency changes, which address critical incidents requiring immediate resolution to restore service and prevent significant business impact. While normal changes often encompass planned improvements, they also cover any non-standard, non-emergency change that requires formal assessment and authorization.

• ✓

  A standard change is pre-approved and follows a defined procedure, while a normal change requires approval from a change authority

  Why this is correct

  A standard change is characterized by its pre-authorization, meaning it has already undergone risk assessment and approval, allowing for immediate implementation upon request or trigger, following a strict, documented procedure. Conversely, a normal change requires a formal assessment and explicit approval from a designated change authority, such as a Change Advisory Board (CAB) or an individual, before it can proceed. This distinction in the approval mechanism is fundamental to ITIL 4's change enablement practice, balancing speed with control.

• ✗

  A standard change has no defined procedure, while a normal change has a defined procedure

  Why it's wrong here

  The very essence of a standard change is its adherence to a well-defined, repeatable, and documented procedure, which is a prerequisite for its pre-approval and low-risk classification. Without a clear procedure, a change cannot be consistently executed or deemed 'standard,' as its outcome would be unpredictable and its risk profile unmanaged. While normal changes also follow defined processes for assessment and implementation, the assertion that standard changes lack procedures is fundamentally incorrect and contradicts their core definition.

Go deeper

Related to this question