Which change type is normally absent from the change schedule when it is first raised?
ITIL 4 Foundation, objective 7. Seven ITIL practices in detail hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct Normal changes
Wrong. Normal changes are scheduled by definition — the schedule is a central part of how they are planned, communicated and de-conflicted.
Correct Emergency changes
Correct. By their nature they arise without warning and are implemented as soon as possible, so they are not typically included in the schedule prepared in advance.
Not correct High-risk changes, because the change authority authorises them individually outside the schedule
Wrong. Authorisation and scheduling are separate things: a change can be individually authorised and still appear on the schedule. High-risk normal changes are in fact the ones people most need advance visibility of.
Not correct Changes that affect supplier-provided components
Wrong. Change enablement covers infrastructure, applications, documentation, processes and supplier relationships alike; supplier-related changes are scheduled like any other.
Why
The change schedule is built ahead of time, and emergency changes by definition are not known ahead of time — they exist to respond to something that has already gone wrong. They are therefore not typically part of the schedule when raised, although the organisation still records them so that later incident and problem investigations can see what was changed and when.
Where this comes from
- Cited
- ITIL 4 syllabus clause 7
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 7 and space the ones you get wrong.
More questions on this objective
- Which statement best describes what the incident management practice is intended to achieve? machine-checked
- How is an incident defined in ITIL? machine-checked
- Several incidents are open at once and the support team must decide which to work on first. On what basis should the order be decided? machine-checked
- A difficult incident is worked on by pulling several specialists from different teams into the same session at the same time; once it becomes clear who is best placed to continue, the others step away. What is this technique called? machine-checked
- Why does an organisation define a separate procedure for major incidents rather than handling them exactly like all other incidents? machine-checked
- A support team routinely fixes incidents by phone and updates the incident record only with the word 'fixed'. What is the most significant consequence of this? machine-checked