Why does ITIL say that service requests and their fulfilment should be standardised and automated to the greatest degree possible?
ITIL 4 Foundation, objective 7. Seven ITIL practices in detail medium
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 Because automation removes the need to agree fulfilment times with users
The opposite: expectations about fulfilment times should be clearly communicated and are made more achievable, not unnecessary, by automation.
Correct Because requests are pre-defined and repeatable, so a known workflow can deliver them consistently and quickly with minimal handling
Correct. Standardisation is possible precisely because the outcome and the steps are agreed in advance; automation then removes handling effort and variability from work that has no diagnostic content.
Not correct Because standardisation allows requests to be diagnosed faster when the root cause is unclear
Requests have no root cause to find. Diagnosis belongs to incidents and problems, which is why they cannot be automated in the same wholesale way.
Not correct Because every request must be individually authorised, and automation performs that authorisation
Approval policies are themselves pre-agreed for each request type; many requests need no individual authorisation at all. Automation applies the agreed policy rather than inventing an approval step.
Why
The economics of request handling are unlike incident handling. Because nothing is unknown, the whole workflow can be designed once and then repeated, so effort spent on each request is largely waste that standardisation and automation remove.
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