Courseiva
ITIL Service Value SystemhardMultiple ChoiceObjective-mapped

ITIL4F ITIL Service Value System Practice Question

A software development team frequently deploys minor bug fixes that have been pre-authorized. According to ITIL 4, what type of change is this?

⚠ Common exam trap

Many candidates confuse a pre-authorized standard change with a normal change, as candidates may think any code deployment requires formal approval, missing the key distinction that standard changes are pre-approved based on low risk and repeatability.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Standard change

C is correct because a standard change in ITIL 4 is a pre-authorized, low-risk, and frequently repeated change that follows a defined procedure. Deploying minor bug fixes that have been pre-authorized fits this definition, as the change is already approved and can be implemented without additional authorization.

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 change

    Why it's wrong here

    Normal changes are non-standard service additions, modifications, or removals that require assessment, authorization, and scheduling. They typically follow a defined workflow, often involving a Change Advisory Board (CAB) or a designated Change Authority, to ensure proper risk evaluation and resource allocation. For "frequently deploys minor bug fix," this process would be overly burdensome and inefficient, as normal changes are not designed for routine, low-impact activities.

  • Service request

    Why it's wrong here

    A service request is a formal request from a user for something standard, such as access to a system, information, or a pre-defined service offering. It is a request for the delivery of a service, not an internal operational activity that alters the state of a service component. Deploying a minor bug fix is an internal change to an existing service, not a user-initiated request for a standard service delivery.

  • Standard change

    Why this is correct

    Standard changes are low-risk, pre-authorized changes that are well-understood, fully documented, and can be implemented without additional authorization. They follow a defined procedure, are often automated, and have a known, predictable outcome. "Frequently deploys minor bug fix" perfectly aligns with the characteristics of a standard change, enabling efficient and rapid deployment of routine, low-impact updates.

  • Emergency change

    Why it's wrong here

    Emergency changes are specifically for addressing critical incidents or implementing urgent security patches where immediate action is required to restore service or prevent significant business impact. They bypass normal authorization processes due to extreme urgency, often requiring retrospective review. While bug fixes are important, "frequently deploys minor bug fix" does not inherently suggest the critical urgency or lack of pre-authorization typical of an emergency change.

About these practice questions

This ITIL4F question is part of Courseiva's 531-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ITIL4F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4F exam.