Overview
Learning outcome 6 is worth 7 marks and is assessed at recall level. Criterion 6.1, worth five marks, asks you to recall the purpose of fifteen practices: information security management, relationship management, supplier management, IT asset management, monitoring and event management, release management, service configuration management, deployment management, continual improvement, change enablement, incident management, problem management, service request management, service desk and service level management.
Criterion 6.2, worth two marks, asks you to recall seven definitions: IT asset, event, configuration item, change, incident, problem and known error. The ITIL 4 practices are grouped into general management, service management and technical management practices. That grouping is background only; the exam tests the purposes and terms. Seven of the fifteen practices return in learning outcome 7, where they are examined in more depth.
How it's tested
Questions quote a purpose statement and ask which practice it belongs to, or name a practice and ask for its purpose. Definition questions do the same for the seven terms. Missing-word formats are common, and negative questions occasionally ask which statement is not a purpose of a named practice.
-
Purpose to practice
A purpose statement such as protecting the information needed to conduct business is given, and you pick the practice.
-
Term definition
A definition such as a cause or potential cause of one or more incidents is given, and you pick the term.
-
Near-neighbour practices
The four options are practices with similar scope, such as release, deployment, change enablement and service configuration management.
A stem asks which practice moves new or changed hardware, software, documentation or processes to live environments. Release management is tempting because releases contain new features. But release management's purpose is to make new and changed services and features available for use, which may happen separately from moving components. Moving components to live environments is the purpose of deployment management, so that is the answer.
Assessment criteria 2
Official assessment criteria from the PeopleCert outline, in outline order.
6.1 Recall the purpose of the following ITIL practices: information security management, relationship management, supplier management, IT asset management, monitoring and event management, release management, service configuration management, deployment management, continual improvement, change enablement, incident management, problem management, service request management, service desk, service level managementOne purpose statement per practice for fifteen practices.
- What it means
- Information security management protects the information needed to conduct business. Relationship management establishes and nurtures links with stakeholders at strategic and tactical levels. Supplier management ensures suppliers and their performance are managed appropriately. IT asset management plans and manages the full lifecycle of IT assets. Monitoring and event management systematically observes services and components and records and reports selected changes of state as events. Release management makes new and changed services and features available for use. Service configuration management ensures accurate, reliable configuration information is available when and where needed. Deployment management moves new or changed components to live environments.
- What to understand
- Learn the remaining seven alongside the first eight. Continual improvement aligns practices and services with changing business needs through ongoing improvement. Change enablement maximizes successful changes by assessing risk, authorizing changes and managing the change schedule. Incident management minimizes the negative impact of incidents by restoring normal operation quickly. Problem management reduces the likelihood and impact of incidents by identifying causes and managing workarounds and known errors. Service request management supports agreed quality by handling predefined, user-initiated requests effectively. The service desk captures demand for incident resolution and service requests and is the single point of contact for users. Service level management sets business-based targets and manages delivery against them.
- How it shows up
- Five marks of recall: match a quoted purpose to its practice, often with near-neighbour distractors.
- Common confusion
- Swapping release management and deployment management, which ITIL deliberately separates.
6.2 Recall definitions of the following ITIL terms: IT asset, event, configuration item, change, incident, problem, known errorSeven core definitions used across the practices.
- What it means
- An IT asset is any financially valuable component that can contribute to the delivery of an IT product or service. An event is any change of state that has significance for the management of a service or other configuration item. A configuration item is any component that needs to be managed in order to deliver an IT service. A change is the addition, modification or removal of anything that could have a direct or indirect effect on services.
- What to understand
- An incident is an unplanned interruption to a service or reduction in the quality of a service. A problem is a cause, or potential cause, of one or more incidents. A known error is a problem that has been analysed but has not been resolved. These terms connect: monitoring detects events, some events signal incidents, problems explain incidents, and known errors are problems awaiting a permanent fix. Note that an IT asset is defined by financial value, while a configuration item is defined by the need to manage it.
- How it shows up
- Two marks of recall: match a definition to the term, or choose the correct definition for a term.
- Common confusion
- Defining a known error as a problem that has been resolved; it is analysed but not yet resolved.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Information security management
Protects the information needed to conduct business.
- Remember
- Confidentiality, integrity, availability, plus authentication and non-repudiation.
- Tested as
- Purpose recall.
- Trap
- Limiting it to technical controls such as firewalls.
-
Relationship management
Establishes and nurtures links with stakeholders at strategic and tactical levels.
- Remember
- Strategic and tactical, not operational ticket handling.
- Tested as
- Purpose recall.
- Trap
- Confusing it with the service desk.
-
Supplier management
Ensures suppliers and their performance are managed appropriately.
- Remember
- Supports seamless provision of quality products and services.
- Tested as
- Purpose recall.
- Trap
- Confusing it with relationship management.
-
IT asset management
Plans and manages the full lifecycle of IT assets.
- Remember
- Maximize value, control cost, manage risk, support decisions.
- Tested as
- Purpose recall.
- Trap
- Confusing it with service configuration management.
-
Monitoring and event management
Observes services and components, recording and reporting selected changes of state.
- Remember
- Events are changes of state that matter.
- Tested as
- Purpose recall.
- Trap
- Treating every event as an incident.
-
Release vs deployment
Release makes services and features available; deployment moves components to live.
- Remember
- The two can happen at different times.
- Tested as
- Near-neighbour purpose questions.
- Trap
- Treating them as one activity.
-
Service configuration management
Ensures accurate, reliable configuration information is available when and where needed.
- Remember
- About information on CIs and their relationships.
- Tested as
- Purpose recall.
- Trap
- Defining it as managing asset costs.
-
Change enablement
Maximizes successful changes through risk assessment, authorization and schedule management.
- Remember
- Three parts: assess risk, authorize, manage the change schedule.
- Tested as
- Purpose recall.
- Trap
- Calling it change control aimed at preventing change.
-
Incident
An unplanned interruption to a service or reduction in its quality.
- Remember
- Reduction in quality counts, not only outages.
- Tested as
- Definition recall.
- Trap
- Requiring a complete outage.
-
Problem
A cause, or potential cause, of one or more incidents.
- Remember
- Potential causes count before any incident happens.
- Tested as
- Definition recall.
- Trap
- Defining a problem as a serious incident.
-
Known error
A problem that has been analysed but not resolved.
- Remember
- Analysed, not resolved.
- Tested as
- Definition recall.
- Trap
- Saying a known error is resolved or has a permanent fix.
-
Configuration item
Any component that needs to be managed to deliver an IT service.
- Remember
- Need to manage defines a CI.
- Tested as
- Definition recall.
- Trap
- Confusing it with an IT asset, defined by financial value.
-
Event
Any change of state significant for managing a service or CI.
- Remember
- Significance is the qualifier.
- Tested as
- Definition recall.
- Trap
- Equating events with failures.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Practices with similar purposes
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Release management | Makes new and changed services and features available for use | About availability to users | Merged with deployment |
| Deployment management | Moves components to live environments | About moving components | Credited with making features available |
| Change enablement | Assesses risk, authorizes changes, manages the schedule | About successful change | Thought to perform the deployment |
| Service configuration management | Keeps configuration information accurate and available | About information | Confused with IT asset management |
Incident, problem and known error
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Incident | Unplanned interruption or reduction in quality | The symptom users notice | Thought to need a full outage |
| Problem | Cause or potential cause of incidents | The underlying cause | Treated as a major incident |
| Known error | Problem analysed but not resolved | Cause understood, fix pending | Assumed already fixed |
Relationship-oriented practices
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Relationship management | Links with stakeholders at strategic and tactical levels | Broad stakeholder focus | Applied only to customers |
| Supplier management | Manages suppliers and their performance | Supplier focus | Merged with relationship management |
| Service level management | Sets business-based targets and manages delivery against them | Target and measurement focus | Treated as contract law |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Release does deployment
- What candidates pick
- Release management for moving software to production.
- Why it looks right
- Releases and deployments are often done together.
- Why it's wrong
- ITIL separates them: deployment moves components to live; release makes services and features available for use.
Clue to watch for Words like move or transfer to live environments.
-
Known error resolved
- What candidates pick
- An option defining a known error as a problem with a permanent solution.
- Why it looks right
- The cause is known, so it sounds fixed.
- Why it's wrong
- A known error has been analysed but not yet resolved.
Clue to watch for The phrase not resolved or not yet fixed.
-
Incident means outage
- What candidates pick
- A definition requiring the service to be fully unavailable.
- Why it looks right
- Many people think of incidents as outages.
- Why it's wrong
- An incident also includes any reduction in the quality of a service.
Clue to watch for Mentions of slow or degraded service.
-
Change control mindset
- What candidates pick
- Change enablement described as preventing unnecessary change.
- Why it looks right
- Older approaches emphasised control.
- Why it's wrong
- Its purpose is to maximize successful changes by assessing risk, authorizing changes and managing the schedule.
Clue to watch for Words like maximize successful changes.
-
Asset equals CI
- What candidates pick
- IT asset management for keeping configuration data accurate.
- Why it looks right
- Both deal with components.
- Why it's wrong
- Accurate configuration information is service configuration management; asset management covers financial lifecycle.
Clue to watch for Mentions of relationships between components or configuration data.
-
Service desk resolves everything
- What candidates pick
- A purpose stating the service desk fixes all incidents.
- Why it looks right
- The desk is the visible support team.
- Why it's wrong
- Its purpose is to capture demand for incident resolution and service requests and act as the single point of contact.
Clue to watch for The word capture or single point of contact.
Answer framework
For any recall item in this outcome, work through these quick checks.
- Decide whether the stem quotes a practice purpose or a term definition, since they come from different criteria.
- Find the verb in the purpose: protect, nurture, manage, plan, observe, make available, ensure information, move, align, maximize, minimize, reduce, support, capture, set targets.
- Match the verb and its object to one practice, and check near neighbours such as release, deployment and change enablement.
- For definitions, look for the qualifier that makes each term unique, such as financially valuable, significance, needs to be managed, unplanned, cause, or not resolved.
- Eliminate options that borrow a real purpose or definition from a different practice or term.
Practice question
Want more like this? The ITIL 4 Foundation practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Make fifteen practice cards with the name on one side and the purpose on the other, and underline the key verb. Seven more cards cover the terms. Drill both sides: name to purpose and purpose to name. Missing-word and matching formats both appear, so being able to go in each direction matters.
Group the cards into near-neighbour sets and study each set together: release, deployment, change enablement and service configuration management; incident, problem and known error; relationship, supplier and service level management; IT asset management and service configuration management. For each set, write one sentence explaining what separates its members. These sentences are what you will need when two options look right.
Plan four to five hours, split across several short sessions, with a final recall check in the last week. The seven practices that reappear in learning outcome 7 deserve extra attention here, because a solid purpose statement is the foundation for the detailed questions later.
FAQ
How much of the exam is Purpose and Key Terms of 15 ITIL Practices?
Purpose and Key Terms of 15 ITIL Practices, learning outcome 6, carries 7 marks out of 40, which is 17.5%: five on practice purposes and two on definitions.
Do I need to know all 34 ITIL 4 practices?
No. The Foundation exam tests the purposes of the fifteen practices listed in the syllabus, and seven of those in more detail in learning outcome 7.
Is the exact wording of purposes tested?
Close wording matters. Questions often quote a purpose with small changes, and distractors borrow wording from neighbouring practices.
What is the difference between release and deployment management?
Deployment management moves components to live environments. Release is about making new or changed functionality available to users. The two can happen at different times, for example when features are deployed hidden and released later.
How do incident, problem and known error relate?
An incident is the interruption or reduced quality. A problem is its cause or potential cause. A known error is a problem that has been analysed but not resolved.
Are the practice groupings tested?
The general, service and technical management groupings are useful background, but the syllabus criteria test purposes and definitions rather than which group a practice belongs to.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 6 knowledge
Run timed recall drills on fifteen purposes and seven definitions, focusing on near neighbours such as release and deployment.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ITIL 4 Foundation AI tutor Get any concept explained your way