A user requests a new software license for a standard application. The IT team processes this through a pre-defined procedure. What type of change is this?
A standard change is a pre-authorized, low-risk, and frequently occurring change that follows a well-documented procedure, requiring no additional authorization each time it is performed. Requesting a new software license for a standard application perfectly aligns with this definition, as the process for provisioning it is typically routine, repeatable, and has minimal associated risk, allowing for efficient and rapid fulfillment.
Why this answer
A standard change is a pre-approved, low-risk change that follows a defined procedure, such as requesting a new software license for a standard application. This type of change does not require additional authorization because it is already authorized by the change authority as part of the pre-defined procedure. The IT team processes it through the established workflow without needing a change advisory board (CAB) review.
Exam trap
The trap here is confusing a service request with the type of change it triggers; candidates often select 'Service request' because the user is making a request, but ITIL 4 classifies the change itself as a standard change when it follows a pre-approved, low-risk procedure.
How to eliminate wrong answers
Option A is wrong because a normal change requires formal approval from the change authority (e.g., CAB) and is not pre-approved; it involves higher risk or complexity than a standard change. Option B is wrong because a service request is a formal request from a user for something to be provided (e.g., information, access, or a standard change), but the change itself is classified as a standard change, not the request type. Option C is wrong because an emergency change is implemented urgently to resolve a major incident or security threat, not for a routine, pre-approved license request.