First 50 of 195 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Purpose and key concepts of the change enablement practice
What is the purpose of the change enablement practice?
- To design, build, and deploy the technical components required by a change
- To record and resolve incidents caused by changes as quickly as possible
- To ensure that every proposed change is reviewed by a change advisory board before it is implemented
- To maximize successful changes by assessing risk, authorizing changes, and managing the schedule Correct answer.
Explanation
Change enablement exists to maximize the number of successful service and product changes by ensuring that risks are properly assessed, authorizing changes to proceed, and managing the change schedule. It does not prescribe that all changes follow the same path, nor does it build or resolve anything itself.
Question 2Purpose and key concepts of the change enablement practice
How does ITIL 4 define a 'change'?
- A documented request from a user for something new or improved in an IT service
- Any modification to the production environment that requires the deployment team to schedule a period of downtime
- The addition, modification, or removal of anything that could have a direct or indirect effect on services Correct answer.
- The transition of a service or service component into the live environment
Explanation
A change is defined broadly as the addition, modification or removal of anything that could have a direct or indirect effect on services. The breadth of the definition is deliberate so that dependencies and indirect effects are not overlooked.
Question 3Purpose and key concepts of the change enablement practice
Which change type is pre-authorized because it is low risk and well understood?
- High-priority change
- Normal change
- Standard change Correct answer.
- Emergency change
Explanation
A standard change is one that is low risk, relatively common and follows a documented procedure, so it is pre-authorized by the change authority. It is then raised and actioned without further authorization each time it occurs.
Question 4Purpose and key concepts of the change enablement practice
What is the main purpose of the change schedule?
- To list the individuals who are permitted to raise a change request
- To capture the lessons learned from changes that later failed
- To help plan changes, assist in communication, and avoid conflicts between planned changes Correct answer.
- To record in detail the authorization decisions taken by the change authority for each individual change
Explanation
The change schedule shows planned changes and their dates so that people can plan work, communicate with affected parties, and avoid clashes between changes. It is a planning and communication tool, not an authorization record.
Question 5Purpose and key concepts of the change enablement practice
Which statement describes an emergency change?
- A change that is assessed and authorized through the normal change model
- A change that must be implemented as soon as possible, often to resolve a major incident or security issue Correct answer.
- A change that is reviewed by the full change advisory board before anyone is allowed to act on it
- A change that has already been pre-authorized because it is low risk and very well understood by the team
Explanation
Emergency changes are those that must be introduced as soon as possible, for example to restore service after a major incident. They use an expedited assessment and authorization route defined in the emergency change model.
Question 6Purpose and key concepts of the change enablement practice
What is a change authority?
- The group that records all change requests in the management tool
- The team that builds and tests the change before it goes live
- The supplier contract owner responsible for change costs
- The person or group who authorizes a change Correct answer.
Explanation
The change authority is the person or group accountable for authorizing a change. Organizations may define several change authorities so that authorization happens at the level appropriate to the change's risk.
Question 7Purpose and key concepts of the change enablement practice
What is the typical role of a change advisory board (CAB)?
- To implement and deploy approved changes during the agreed change window
- To audit the change enablement practice against internal and regulatory requirements
- To own the change schedule and approve every standard change
- To assess and advise on changes, and authorize them where delegated Correct answer.
Explanation
A CAB reviews and assesses changes and provides advice to the change authority. It authorizes changes only where the change authority has explicitly delegated that power to it.
Question 8Purpose and key concepts of the change enablement practice
Which statement best describes a normal change?
- A change that does not need to be assessed because it is low cost
- A change that is assessed and authorized by the appropriate change authority before implementation Correct answer.
- A change that is implemented only after a major incident has been formally declared by the incident manager
- A change that is pre-authorized and follows a defined procedure every single time it occurs
Explanation
A normal change is assessed and then authorized by the change authority appropriate to its risk before it is implemented. Organizations often define several normal change models so that higher-risk changes receive deeper scrutiny.
Question 9Purpose and key concepts of the change enablement practice
A change authority has decided that all changes to a well-understood, low-risk laptop build will be pre-authorized. Which change model does this represent?
- The deployment model
- The emergency change model
- The standard change model Correct answer.
- The normal change model
Explanation
Standard change models cover low-risk, repeatable changes whose procedure has been pre-authorized. Once the model is agreed, each occurrence is triggered by a defined condition without further authorization.
Question 10Purpose and key concepts of the change enablement practice
An IT director delegates authority to approve low-cost changes to the service desk manager. What does this illustrate?
- Change authority can be delegated to an appropriate level within the organization Correct answer.
- The director no longer retains any accountability for the changes that are approved by the delegate
- The service desk manager has become the change advisory board
- Low-cost changes no longer need to be assessed for risk
Explanation
Change authority should sit at the level that matches the risk being taken, and it can be delegated down the organization. Accountability for defining and overseeing that delegation remains with the delegating level.
Question 11Purpose and key concepts of the change enablement practice
A major incident has been declared and the fix requires a change that cannot wait. How should change enablement support this?
- Ask the incident manager to raise a problem record first
- Reclassify the change as standard so that it can proceed without assessment
- Use the emergency change model so the change can be assessed and authorized quickly Correct answer.
- Refuse the change until the next scheduled meeting of the change advisory board takes place
Explanation
Emergency change models exist so that urgent changes can still be assessed and authorized, but by an expedited route. Speed is achieved through a pre-agreed model, not by abandoning assessment.
Question 12Purpose and key concepts of the change enablement practice
Which statement correctly distinguishes change enablement from release management?
- Change enablement applies only to infrastructure components, while release management applies only to application software
- Change enablement focuses on assessing risk and authorizing changes, while release management makes the change available to users Correct answer.
- Both practices are the same and are always performed by the same team
- Change enablement moves finished changes into the live environment, while release management assesses and authorizes them before they are scheduled
Explanation
Change enablement decides whether a change may proceed by assessing risk and authorizing it. Release management then makes the new or changed service and its features available for use.
Question 13Purpose and key concepts of the change enablement practice
Which set of conditions best fits a standard change?
- Unknown impact, requiring a full CAB review before every single occurrence
- Urgent, unplanned, and authorized only after implementation
- High risk, novel, and requiring senior management approval each time
- Low risk, well understood, repeatable, with a defined trigger Correct answer.
Explanation
A standard change is low risk, relatively common, follows a documented procedure and is pre-authorized, with a defined trigger that starts the procedure. This allows routine work to proceed without repeated authorization.
Question 14Purpose and key concepts of the change enablement practice
A change manager wants to reduce the risk of two approved changes clashing in the same maintenance window. Which element of change enablement is most relevant?
- The change schedule Correct answer.
- The emergency change model
- The service catalogue
- The change authority register
Explanation
The change schedule records planned changes and their timing so that conflicts, collisions and resource clashes can be spotted and avoided. It also supports communication with affected parties.
Question 15Purpose and key concepts of the change enablement practice
Which statement about change authorization is correct?
- Authorization is only needed for changes costing more than a set amount
- Every change must be authorized by the change advisory board before it is implemented in the live environment
- Authorization can only ever be given by the person who raised the change
- The change authority for different types of change can be defined at different levels in the organization Correct answer.
Explanation
Organizations define change authorities so that the level of authorization matches the risk and impact of each type of change. Standard, normal and emergency changes are therefore authorized in different ways.
Question 16Purpose and key concepts of the change enablement practice
A supplier changes a component that supports a live service, although the organization does not operate that component. How does change enablement treat this?
- It is a standard change by default
- It is a supplier management issue only and therefore needs no change record to be created
- It is in scope, because a change is anything that could have a direct or indirect effect on services Correct answer.
- It is out of scope for change enablement because the organization does not own or operate the supplier's component
Explanation
The definition of a change covers anything with a direct or indirect effect on services, which includes changes made by suppliers and other parties in the value chain. Change enablement therefore needs visibility of such changes even when it does not perform them.
Question 17Purpose and key concepts of the change enablement practice
Why does ITIL 4 emphasize that change enablement should balance effectiveness with speed?
- Because the change advisory board must approve every change before it is even raised as a request
- Because too much control slows the organization down while too little increases risk Correct answer.
- Because control is only needed for emergency changes
- Because faster changes are always safer than slower ones and should therefore always be given priority
Explanation
Change enablement must support the organization's ability to change quickly while still protecting value. Over-control creates delay and bureaucracy, while under-control exposes services to avoidable risk.
Question 18Purpose and key concepts of the change enablement practice
A change was implemented to restore service during an incident and authorized afterwards. Which statement is correct?
- The change must be re-raised as a normal change and then implemented again from the beginning
- The change should be reversed immediately in all cases
- This is never acceptable under any circumstances and the change should be reversed immediately
- Where the emergency change model allows it, emergency changes may be authorized afterwards Correct answer.
Explanation
Emergency change models may permit retrospective authorization so that urgent work is not blocked. The organization must define this in advance and ensure the change is properly recorded and reviewed afterwards.
Question 19Purpose and key concepts of the change enablement practice
Which of the following is a typical measure of the change enablement practice?
- The percentage of changes that were successful Correct answer.
- The average time taken to deploy a release into production
- The number of incidents closed within the agreed service level target
- The number of problem records that have an identified known error
Explanation
Change enablement measures reflect how well changes are assessed, authorized and delivered, such as the proportion of successful changes. Other metrics listed belong to incident, deployment and problem practices.
Question 20Purpose and key concepts of the change enablement practice
Which practice investigates the underlying cause of recurring incidents and may then raise a change to remove it?
- Service request management
- Service level management
- Incident management
- Problem management Correct answer.
Explanation
Problem management identifies root causes and can raise change requests to eliminate them permanently. Change enablement then assesses and authorizes those changes.
Question 21Purpose and key concepts of the change enablement practice
How does change enablement relate to organizational change management?
- Change enablement manages changes to services and components; organizational change management addresses people aspects Correct answer.
- The two terms are interchangeable in ITIL 4
- Change enablement covers the people aspects of change, while organizational change management deals with the technical changes
- Organizational change management is an ITIL 4 practice that replaces change enablement for HR changes
Explanation
Change enablement governs changes to services and their components, assessing risk and authorizing work. Organizational change management concerns the human side of change, such as adoption, engagement and capability, and complements it.
Question 22Purpose and key concepts of the change enablement practice
Which condition must be met before a change can be handled as a standard change?
- It must have failed at least once previously so that its risks are already properly understood by the team
- It must be approved by the change advisory board at least once in every quarter of the year
- It must be triggered by a major incident so that it can be handled quickly
- The change must be low risk and the procedure must have been pre-authorized by the change authority Correct answer.
Explanation
Standard status depends on the change being low risk and repeatable, with a documented procedure that the change authority has pre-authorized. The defined trigger then allows it to be raised and actioned without further approval.
Question 23Purpose and key concepts of the change enablement practice
An organization wants more changes handled through standard change models. What is the most important requirement for doing this safely?
- The organization should reduce the number of change authorities to a single person
- Change records should only be created after the change has been implemented
- Each standard change model should be based on a well-understood procedure with a defined trigger Correct answer.
- All changes should first be reviewed by the change advisory board before they are classified as standard
Explanation
Pre-authorization is only safe when the underlying procedure is proven, well understood and started by a clearly defined trigger. Over time, recurring successful changes can be analysed and turned into new standard models.
Question 24Purpose and key concepts of the change enablement practice
How do the change authority and a CAB relate when a CAB is used?
- The CAB assesses and advises on changes and authorizes them only when that power has been delegated Correct answer.
- The CAB always supersedes the change authority for every decision that has to be made
- The CAB authorizes all standard changes, while the change authority handles all of the normal changes
- The CAB is a committee of the service desk that records all change requests in the IT service management tool
Explanation
A CAB is a group that reviews changes and provides advice to the change authority. It becomes an authorizing body only if the change authority has delegated that decision to it.
Question 25Purpose and key concepts of the change enablement practice
A change has a low probability of failure but a very high potential impact on a critical service. How should change enablement handle this?
- Assess the risk carefully and authorize it at a level appropriate to the potential impact Correct answer.
- Treat it as a standard change because the probability of failure is low and it is therefore routine
- Reject it because high-impact changes are not permitted
- Approve it automatically because the probability of failure is low
Explanation
Risk combines the likelihood of failure with the consequences if it fails, so a high-impact change needs thorough assessment and senior authorization even when failure is unlikely. The level of authorization should match the impact, not only the probability.
Question 26Purpose and key concepts of the change enablement practice
Which statement describes the purpose of the change enablement practice?
- To ensure that services are delivered within agreed service levels and at an acceptable cost to the organization
- To restore normal service operation as quickly as possible and to minimize the adverse impact of incidents
- To design products and services that meet agreed requirements and are fit for purpose and use in the target environment
- To maximize successful changes by assessing risk, authorizing change and managing the schedule Correct answer.
Explanation
Change enablement exists to maximize the number of successful service and product changes. It does this by making sure risks are properly assessed, by authorizing changes to proceed, and by managing the change schedule. Its focus is on enabling beneficial change, not on restoring service or designing services.
Question 27Purpose and key concepts of the change enablement practice
Which three types of change does ITIL 4 describe?
- Pre-authorized, authorized and retrospectively authorized
- Minor, significant and major
- Standard, normal and emergency Correct answer.
- Planned, unplanned and reactive
Explanation
ITIL 4 describes standard changes, normal changes and emergency changes. Each type is handled differently in terms of assessment and authorization. Size-based or timing-based labels are not the way the practice categorizes change.
Question 28Purpose and key concepts of the change enablement practice
What is the purpose of a change model?
- To define a repeatable approach for handling a particular type of change Correct answer.
- To record every change that has been implemented during a reporting period so that trends can be analysed
- To identify which individuals are permitted to approve high-risk changes to critical live services
- To forecast the cost and resource requirements of a proposed change before it is submitted for approval
Explanation
A change model is a repeatable, pre-defined approach to handling a particular type of change. It sets out the steps, the roles involved and how the change is assessed and authorized. Because the approach is agreed in advance, similar changes can be handled consistently and with less effort.
Question 29Purpose and key concepts of the change enablement practice
Which statement about the scope of change enablement is correct?
- It covers any change that could affect services, including supplier and internal components Correct answer.
- It covers only changes that are delivered as part of a formal project with a business case
- It covers only changes that are assessed and approved by a change advisory board
- It covers only changes to infrastructure components that are owned and operated by the IT department
Explanation
The practice applies to any change that could have a direct or indirect effect on services, whoever makes it and wherever the component sits. This includes changes to components and services provided by suppliers. Restricting scope to internally owned infrastructure or to one approval body would leave significant risk unmanaged.
Question 30Purpose and key concepts of the change enablement practice
Which statement best describes an emergency change?
- A change that was requested after the agreed change freeze date had already started
- A change that must be introduced as soon as possible to resolve a major incident Correct answer.
- A change that is raised by a supplier rather than by an internal IT team member
- A change that has been pre-authorized because its risk has been assessed as low
Explanation
An emergency change is one that must be introduced as soon as possible, typically to resolve a major incident or to close a significant security exposure. Because time is short, the assessment and authorization steps are streamlined but still performed. The type is defined by urgency, not by who raised the change or when it was submitted.
Question 31Purpose and key concepts of the change enablement practice
Which statement about risk assessment in change enablement is correct?
- Risk should be assessed after implementation so that actual impacts can be measured
- Risk assessment is required only for changes that affect financially critical services
- The depth of risk assessment should be proportionate to the change's potential impact Correct answer.
- Every change must undergo a full quantitative risk analysis before it can be authorized
Explanation
Risk assessment should be scaled so that effort matches the potential impact and likelihood of failure of the change. High-impact or uncertain changes warrant deeper analysis, while well-understood low-risk changes need only light assessment. Requiring the same heavy analysis for every change slows delivery without adding proportional value.
Question 32Purpose and key concepts of the change enablement practice
A change enablement practice has a very low change failure rate, but teams report that changes take weeks to be approved. Which interpretation is most consistent with ITIL 4 guidance?
- Approval delays are outside the scope of change enablement and should be handled by project management
- The organization should remove all change authorization so that teams can deploy changes without delay
- The practice is performing well, because a low failure rate is the primary purpose of change enablement
- Control has been over-emphasized relative to speed, so assessment should be scaled to risk Correct answer.
Explanation
Change enablement must balance effectiveness with speed, so a low failure rate achieved through excessive control is not a good outcome. The remedy is to scale assessment and authorization to the risk of each change, for example through pre-authorized standard changes and clearer models. Neither doing nothing nor abandoning authorization addresses the imbalance.
Question 33Purpose and key concepts of the change enablement practice
How does change enablement support continual improvement?
- It provides a controlled route for implementing improvements that have been identified Correct answer.
- It measures the availability and reliability of services against agreed service level targets
- It maintains the improvement register and prioritizes ideas according to business value
- It investigates the root causes of recurring incidents and records the findings in a problem record
Explanation
Improvements usually require something to be altered, and change enablement provides the assessed, authorized and scheduled route by which those alterations are made. It does not itself decide what to improve or own the improvement backlog. Its contribution is to let improvements reach live services safely.
Question 34Purpose and key concepts of the change enablement practice
Which statement correctly distinguishes change enablement from deployment management?
- Both practices cover the same work, but change enablement applies only to emergency changes and deployment management only to normal changes.
- Change enablement moves components into live use, while deployment management grants the approvals for that work.
- Change enablement authorizes and schedules changes; deployment management performs the actual deployment. Correct answer.
- Change enablement maintains configuration data, while deployment management decides who holds change authority.
Explanation
Change enablement focuses on maximizing the number of successful service and product changes by assessing risk, authorizing the change and planning when it will happen. Deployment management is the separate practice that moves new or changed hardware, software, documentation and processes into the live environment. The two practices coordinate closely, but authorizing a change is not the same activity as deploying it.
Question 35Change types, change models and risk-based categorization
Which type of change is pre-authorized and typically raised as a service request because it is low-risk, repeatable and well understood?
- A standard change Correct answer.
- A major change
- A normal change
- An emergency change
Explanation
Standard changes are low-risk, repeatable and follow a documented procedure, so authority is granted in advance rather than for each occurrence. This is why a request for one can be handled through the normal service request route.
Question 36Change types, change models and risk-based categorization
A change that is not pre-authorized and must be assessed, scheduled and authorized individually each time it is raised is known as:
- A standard change
- A normal change Correct answer.
- An emergency change
- A service request
Explanation
Normal changes follow a change model and are assessed, scheduled and authorized on each occasion. They are often further categorized (for example as major or minor) according to their risk.
Question 37Change types, change models and risk-based categorization
Which change type is appropriate when a change must be implemented as soon as possible, for example to restore a failed service or close a security vulnerability?
- A minor change
- A standard, pre-authorized change
- An emergency change Correct answer.
- A normal change requiring CAB approval
Explanation
Emergency changes are those that must be implemented urgently, so they follow a deliberately streamlined path. They are still assessed and authorized, often by a delegated emergency authority.
Question 38Change types, change models and risk-based categorization
What is a change model in change enablement?
- A technique for estimating the cost of a change
- A repeatable approach for handling a type of change Correct answer.
- A list of people allowed to raise change requests
- A schedule showing when each planned change will be implemented
Explanation
A change model defines the repeatable approach for a category of change, including its triggers, steps, roles, responsibilities and escalation points. It lets similar changes be handled consistently at a control level suited to their risk.
Question 39Change types, change models and risk-based categorization
In change enablement, what is the change authority?
- The person or group accountable for authorizing a change Correct answer.
- The owner of the IT service affected by the change
- The group that assesses and prioritizes changes before they are authorized
- The person who records changes in the change schedule
Explanation
The change authority is whoever is accountable for authorizing a change, and it may be an individual or a group. Authority is often delegated according to the type and risk of the change.
Question 40Change types, change models and risk-based categorization
What is the purpose of the change schedule in change enablement?
- To store the configuration items affected by changes
- To replace the need for change authorization
- To record all unauthorized changes for later disciplinary action
- To plan changes and avoid scheduling conflicts between them Correct answer.
Explanation
The change schedule, sometimes called a change calendar, shows planned changes and their timing. It helps plan work, avoid conflicts and collisions, and communicate with stakeholders.
Question 41Change types, change models and risk-based categorization
On what basis are normal changes usually categorized as major, significant or minor?
- On the seniority of the person who requested the change
- On the assessed risk, usually considering impact and likelihood Correct answer.
- On the cost of the change only
- On the number of teams and suppliers involved in implementing the change
Explanation
Risk-based categorization weighs the potential impact of a change against the likelihood of an unwanted outcome. The resulting category determines the level of assessment and authorization required.
Question 42Change types, change models and risk-based categorization
Which statement best describes the purpose of the change enablement practice?
- To ensure that all changes are approved by the CAB before implementation
- To document the configuration of services and their components
- To prevent any change that could affect live services
- To maximize successful changes by assessing risk and authorizing them properly Correct answer.
Explanation
Change enablement exists to maximize the number of successful service and product changes by ensuring risks are properly assessed, changes are authorized, and the change schedule is managed. It enables change rather than blocking it.
Question 43Change types, change models and risk-based categorization
Which set of characteristics makes a change a good candidate for being defined as a standard change?
- Low risk, repeatable and well understood, with a documented procedure Correct answer.
- Unknown risk, requiring senior management approval before each implementation
- High urgency, needed to restore service within minutes
- High impact, low frequency and high cost
Explanation
A standard change must be low-risk, repeatable and well understood, with a documented procedure and pre-agreed authority. Frequency alone, or urgency alone, does not qualify a change as standard.
Question 44Change types, change models and risk-based categorization
Which of the following should be defined within a change model?
- The steps, roles, responsibilities and escalation criteria Correct answer.
- The personal objectives and development plan of the change manager
- The supplier contract terms for the affected IT asset
- The financial budget code for the change
Explanation
A change model describes the repeatable approach for a type of change, including its triggers, steps, roles, responsibilities and escalation criteria. It should also identify who has authority for that type of change.
Question 45Change types, change models and risk-based categorization
In many organizations, which body or role authorizes emergency changes?
- The full change advisory board at its next scheduled meeting
- The service desk manager, in all circumstances
- An emergency change authority such as an ECAB Correct answer.
- The problem management team, in all circumstances
Explanation
Emergency changes need authorization at short notice, so authority is delegated to a small group or role, often an emergency change advisory board. The emergency change model should name that authority in advance.
Question 46Change types, change models and risk-based categorization
What is the role of the change advisory board (CAB) within change enablement?
- It supports assessment and prioritization of changes Correct answer.
- It approves the IT strategy and the annual budget
- It implements all normal changes on behalf of the technical teams
- It owns and maintains the configuration management database
Explanation
A CAB is a group that supports the assessment and prioritization of changes, and the change authority may be delegated to it. Its value lies in bringing the right perspectives to bear on changes before they proceed.
Question 47Change types, change models and risk-based categorization
An organization applies a monthly security patch to a widely deployed operating system. The patch is well understood, has rarely failed, and follows a documented procedure. How should this be handled?
- As a pre-authorized standard change Correct answer.
- Outside change enablement, because patching is a purely technical task
- As a normal change requiring full CAB review each month
- As an emergency change requiring ECAB approval each month
Explanation
The work is repeatable, low-risk and supported by a documented procedure, which are the conditions for a standard change. Authority is granted when the procedure is agreed, so each occurrence only needs to follow it.
Question 48Change types, change models and risk-based categorization
Which two factors are most central when assessing the risk of a proposed change in order to categorize it?
- The number of open change requests and the size of the change team
- The potential impact of the change and its likelihood of failure Correct answer.
- The seniority of the requester and the length of the change window
- The vendor of the affected technology and the age of the equipment
Explanation
Risk is typically judged by combining the potential impact of a change with the likelihood of an unwanted outcome. These two dimensions drive the change category and the level of authorization needed.
Question 49Change types, change models and risk-based categorization
Why might an organization define several different change models rather than a single one?
- Because each change manager is allowed to choose their own preferred approach
- Because ITIL requires one model per IT service
- Because different changes need different levels of control and workflow Correct answer.
- Because a single model cannot be documented
Explanation
Tailoring models to the type and risk of change keeps control proportionate and avoids unnecessary bureaucracy. Low-risk repeatable work can move quickly, while high-risk work receives deeper assessment.
Question 50Change types, change models and risk-based categorization
Who authorizes a standard change?
- The ECAB, immediately before implementation
- No authorization at all, because standard changes bypass change enablement
- The CAB, at the meeting before each occurrence
- Whoever pre-authorized it when the standard change procedure was agreed Correct answer.
Explanation
A standard change is authorized in advance, when the change procedure and its conditions are agreed. Each occurrence then only needs to follow that agreed procedure.