Home › Certifications › ITIL 4 Foundation › The Seven Practices in Detail
85 multiple-choice questions and 44 flashcards on The Seven Practices in Detail, about 38% of the ITIL 4 Foundation bank. Every one carries a written rationale.
The Seven Practices in Detail is one of 6 chapters in CoStudy's ITIL 4 Foundation bank, and it holds 85 of the bank's 221 multiple-choice questions — roughly 38% of the total. That proportion is not arbitrary: chapters follow the certifying body's published exam outline, and the number of questions in each is set by that domain's published weight, so the share of your practice time this chapter takes matches the share of the real exam it accounts for.
Studying by chapter is worth doing once you have a diagnostic score. A single overall percentage tells you whether you are close; it does not tell you which domain is dragging. Working a weak chapter in isolation, and re-testing it in isolation, is the fastest way to move a score that has stalled — and it is why the mock exams in CoStudy report by domain rather than as one number.
10 questions drawn from this chapter, with the full rationale shown — the controlling principle behind the right answer, and why each wrong option tempts and fails.
Which statement BEST defines a known error?
Answer: A — A problem that has been analysed but has not been resolved
A) Correct — a known error is a problem that has been analysed but not resolved, so its cause is understood even though the fault remains. B) describes recurring incidents, which may prompt a problem record but are not the definition. C) reverses the meaning: once permanently corrected, the error is no longer outstanding. D) describes a workaround, the term most often confused with known error.
Which set correctly lists the three types of change in ITIL 4?
Answer: C — Standard, normal and emergency changes
C) Correct — ITIL 4 recognises standard, normal and emergency changes. A) borrows sizing language used informally in many tools but is not the ITIL 4 classification. B) invents a timing-based split. D) mixes vocabulary from incident handling and escalation into change terminology.
Which BEST describes the relationship between Service Desk and Incident Management?
Answer: B — The service desk captures demand; incident management restores service
B is right because the two are distinct but tightly coupled: the desk is the entry point capturing demand, and incident management is the practice that minimizes impact by restoring service. A merges them. C removes the entry point. D narrows the desk to work it does not own.
Which is the PURPOSE of Service Level Management?
Answer: B — To set business-based service targets and manage delivery to them
B is right because service level management sets clear business-based targets and assesses, monitors and manages delivery against them. A is the purpose of incident management. C belongs to financial management of services. D is change enablement, a separate practice with its own authority model.
Which TYPE of change is pre-authorized, low-risk, and follows a well-known procedure?
Answer: B — Standard change
Standard change = pre-authorized, low-risk, well-known (e.g., password reset). Normal = assess + authorize. Emergency = urgent. 'Major' isn't a standard ITIL 4 type at this level.
An organization closes incidents as 'resolved' once the workaround is applied. What is the BEST critique?
Answer: B — Resolving the incident is fine, but a problem record should stay open
B is right because restoring service legitimately resolves the incident, yet the unaddressed cause justifies a live problem record. A stops at restoration and loses the cause. C is the common misconception that mitigation equals resolution. D holds incidents open needlessly and distorts restoration metrics.
The purpose of the service level management practice is to:
Answer: B — Set clear business-based targets for service performance, so delivery can be managed against them
B) Correct — service level management sets clear business-based targets for service levels so that delivery can be assessed, monitored and managed against them. A) is service request management. C) is supplier management, which supports service levels through underpinning contracts but is a separate practice. D) is change enablement.
Which BEST describes the purpose of the Problem Management practice?
Answer: A — To reduce incident likelihood and impact by managing causes and known errors
A is right because the practice reduces the likelihood and impact of incidents by identifying actual and potential causes and managing workarounds and known errors. B is incident management. C is change enablement. D belongs to information security management and access control work.
Which is the PURPOSE of Change Enablement?
Answer: C — To maximize successful changes by assessing risk and authorizing them
C is right because the practice maximizes the number of successful service and product changes through risk assessment, authorization and management of the change schedule. A and B treat change as something to suppress rather than enable. D describes service request management.
The continual improvement model has seven steps. What is the FIRST step?
Answer: E — What is the vision? Establishing where the business is going before anything else is decided
E is step one. The model runs: what is the vision, where are we now, where do we want to be, how do we get there, take action, did we get there, how do we keep the momentum going. A and D start with action, which risks improving something that does not serve the vision. C is 'where are we now' and 'did we get there', which come after the vision is set. B is not a step in the model at all.
4 cards from the 44 in this chapter.
SLA (Service Level Agreement)?
Documented agreement between service provider and customer. Specifies services + targets.
Service request?
Request from user for IT service or info (e.g., access, password reset).
Change enablement purpose?
Maximize successful service/product changes by ensuring proper assessment, authorization, scheduling.
What is a service request, and what is the purpose of service request management?
A service request is a request from a user or a user's authorised representative that initiates a service action which has been agreed as a normal part of service delivery. Its purpose is to support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner.
These are a sample. The full The Seven Practices in Detail chapter runs 129 items with per-chapter progress tracking, on the web and in the iOS app.
Open ITIL 4 Foundation in CoStudy →