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.

• ✗

  Implementing a new firewall to protect the network

  Why it's wrong here

  Implementing a new firewall represents a significant infrastructure modification, introducing new components and altering the security posture of the network. This type of change requires thorough planning, detailed risk assessment, and formal authorization from a change authority, classifying it as a normal change. It is far too complex and impactful to be considered a pre-approved, low-risk standard change.

• ✗

  Patenting a critical server vulnerability during business hours

  Why it's wrong here

  "Patenting" a critical server vulnerability is not an IT service change type within the ITIL framework; it refers to intellectual property rights. However, if the intent was to "patching" a critical server vulnerability, this would typically be classified as an emergency change. Emergency changes are reserved for urgent fixes to critical incidents that require immediate action to restore service or prevent significant business impact, bypassing standard change procedures due to the severity and urgency.

• ✗

  Upgrading the entire email system to a new version

  Why it's wrong here

  Upgrading an entire email system is a major undertaking involving substantial planning, extensive testing, potential service disruption, and significant user impact across the organization. Such a complex and high-impact initiative necessitates a formal normal change process, including detailed assessment, scheduling, and multiple levels of authorization. It is not a routine, pre-approved, or low-risk activity characteristic of a standard change.

• ✓

  Resetting a user's password after they forget it

  Why this is correct

  Resetting a user's password is a classic example of a standard change because it is a routine, frequently occurring, and low-risk activity with a well-defined and proven procedure. This type of request is typically pre-authorized, allowing service desk staff to execute it immediately without requiring additional approvals, thereby ensuring efficient and rapid resolution for common user issues.

Go deeper

Related to this question