ITIL Management Practices: Study Guide for the Largest Foundation Exam Domain

Why Domain 6 Is the Most Important Exam Domain

If you're preparing for the ITIL 4 Foundation exam and you only have limited time to study, there is one domain that deserves more of your attention than any other: Domain 6 — ITIL Management Practices. With approximately 22 out of 40 exam questions drawn from this single domain, it represents over half of your entire score. Pass or fail this domain, and you effectively pass or fail the exam.

The Foundation exam requires a passing score of 65% — that's 26 correct answers out of 40. Because Domain 6 contributes around 22 questions, a candidate who masters this domain and struggles elsewhere can still clear the threshold. Conversely, a candidate who underestimates Domain 6 and breezes through the other six domains will almost certainly fall short. Understanding this math is the first step in building an effective study strategy.

Domain 6 covers 15 of the 34 ITIL 4 management practices — split into two tiers. The 7 Key Practices require you to understand concepts, terminology, activities, and roles in meaningful depth (accounting for roughly 17 questions). The 8 Additional Practices require you to recall their purpose and a handful of defining terms (accounting for roughly 5 questions). Knowing exactly which tier each practice falls into is itself a study advantage.

For a broader picture of how Domain 6 fits into the overall certification, check out How to Pass the ITIL 4 Foundation Exam on Your First Try: Study Guide 2026, which maps all seven domains and their relative weights.

The 34 ITIL 4 Practices: A Quick Overview

ITIL 4 defines a practice as "a set of organizational resources designed for performing work or accomplishing an objective." This is a deliberate shift from ITIL v3's concept of "processes" — practices are broader and incorporate people, information, technology, and value streams, not just procedural steps.

The full set of 34 practices is organized into three categories:

• General Management Practices (14): Adapted from general business management domains and applied to IT service management. Examples include Continual Improvement, Risk Management, and Information Security Management.
• Service Management Practices (17): Developed specifically within service management and ITSM industries. Examples include Incident Management, Service Desk, and Service Level Management.
• Technical Management Practices (3): Adapted from technology management domains. Includes Deployment Management, Infrastructure and Platform Management, and Software Development and Management.

Of the 15 practices assessed in Domain 6, the breakdown covers practices from all three categories. The Foundation exam does not test all 34 practices in depth — only these 15, and with significantly different depth requirements depending on the tier.

The 7 Key Practices: Deep Dive

These seven practices appear most heavily on the exam. For each one, you need to understand its purpose, key activities, important terminology, and how it integrates with other practices and the Service Value Chain. Bloom's taxonomy Level 2 (Understand) applies here — you won't just memorize definitions, you'll be expected to apply concepts to scenario-based questions.

1. Continual Improvement

Continual Improvement is the practice of aligning an organization's services and practices with changing business needs through the ongoing improvement of products, services, and practices. It applies at every level of the organization and is supported by the Continual Improvement Model, a seven-step framework:

1. What is the vision?
2. Where are we now?
3. Where do we want to be?
4. How do we get there?
5. Take action
6. Did we get there?
7. How do we keep the momentum going?

Exam questions frequently test whether you can identify the correct step in the model, or recognize that Continual Improvement is everyone's responsibility — not just a dedicated team's job. The practice also maintains a Continual Improvement Register (CIR), which is a database or document used to track improvement opportunities.

2. Change Enablement

Change Enablement (formerly "Change Management" in ITIL v3) maximizes the number of successful IT changes by ensuring risks are properly assessed, authorizing changes to proceed, and managing the change schedule. Three change types are critical to know:

• Standard Changes: Pre-authorized, low-risk, well-understood changes that follow a documented procedure. No individual authorization needed each time.
• Normal Changes: Must go through a defined assessment, authorization, and scheduling process. Can be further divided into minor, significant, and major.
• Emergency Changes: Must be implemented as soon as possible to restore service or avoid a significant negative impact. Expedited assessment and authorization required.

The Change Advisory Board (CAB) advises the change authority on normal and emergency changes. Emergency changes may use an Emergency CAB (ECAB). Know that the purpose of Change Enablement is not to prevent change, but to enable beneficial change at the right speed with appropriate risk management.

3. Incident Management

Incident Management restores normal service operation as quickly as possible following an unplanned interruption or reduction in the quality of a service. Key concepts:

• An incident is an unplanned interruption to a service or reduction in service quality.
• Incident prioritization is based on impact and urgency.
• Major incidents have a dedicated process with shorter timescales and higher urgency.
• A workaround temporarily reduces the impact before a full resolution is found.
• Incidents are distinct from problems (the root cause) and service requests (normal requests for service).

4. Problem Management

Problem Management reduces the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors. The three phases are:

• Problem Identification: Detect and log problems.
• Problem Control: Analyze and document workarounds and known errors.
• Error Control: Manage known errors and raise change requests to remove them permanently.

A known error is a problem that has been analyzed but not yet resolved. It may have a documented workaround. The Known Error Database (KEDB) stores this information and can be used by Incident Management to speed up resolution.

5. Service Request Management

Service Request Management supports the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner. Service requests include requests for information, access, a standard change, or a complaint or compliment. Key exam points:

• Service requests are not incidents — they are planned, expected requests for routine items.
• They should be handled via standardized procedures with clear fulfillment workflows.
• The goal is efficiency and user satisfaction — policies should enable self-service where possible.

6. Service Desk

The Service Desk is the single point of contact between the service provider and users for day-to-day activities. It captures demand for incident resolution and service requests. Modern service desks can take many forms:

• Local: Physically co-located with users.
• Centralized: One desk serves multiple locations.
• Virtual: Geographically distributed but appears as a single team through technology.
• Follow-the-Sun: Multiple desks in different time zones provide 24/7 coverage.

Service desks require strong empathy, communication, and collaboration skills. They increasingly leverage AI, chatbots, and self-service portals. The desk is not just a technical function — it's a key part of the organization's service experience.

7. Service Level Management

Service Level Management sets clear business-based targets for service performance, then ensures delivery against those targets. Key artifacts include:

• Service Level Agreement (SLA): A documented agreement between a service provider and customer defining service targets and responsibilities.
• Operational Level Agreement (OLA): An agreement between internal teams that supports the SLA.
• Underpinning Contract (UC): A contract with an external supplier supporting service delivery.

Service Level Management also requires ongoing engagement with customers to understand their evolving needs — not just monitoring dashboards after the fact. The practice supports the organization in making data-driven decisions about service improvements.

The 8 Additional Practices: What You Need to Know

For the Foundation exam, these eight practices require a lighter touch — you need to know their purpose and be able to recognize their key terms and contributions. Expect roughly one question per group, not per practice. Efficient study here means memorizing purpose statements and a few distinguishing facts.

Practice	Core Purpose	Key Term to Know
Information Security Management	Protect information needed by the organization to conduct its business	CIA Triad (Confidentiality, Integrity, Availability)
Relationship Management	Establish and nurture links between the organization and its stakeholders	Stakeholder engagement, customer satisfaction
Supplier Management	Ensure suppliers and their performance are managed appropriately to support the provision of quality services	Supplier contracts, Supplier Management Information System (SMIS)
IT Asset Management	Plan and manage the full lifecycle of all IT assets to maximize value and control costs	IT asset, asset register, lifecycle
Monitoring and Event Management	Systematically observe services and service components, and record and report selected changes of state	Event types: informational, warning, exception
Release Management	Make new and changed services and features available for use	Release (not to be confused with Deployment)
Service Configuration Management	Ensure that accurate and reliable information about the configuration of services is available when and where it is needed	Configuration Item (CI), Configuration Management Database (CMDB)
Deployment Management	Move new or changed hardware, software, documentation, processes, or any other component to live environments	Deployment vs. Release distinction

Exam Strategy for Domain 6

Knowing the content is necessary but not sufficient. You also need a strategy for how to approach Domain 6 questions during the 60-minute exam (75 minutes for non-native English speakers). With ~22 questions from this domain, you'll be engaging with practice-related material throughout the entire exam — not just in a specific section.

For detailed time management tactics, see ITIL 4 Foundation Exam Day Tips: Time Management Strategies for 60 Minutes, which covers pacing across all question types.

Recognize the Question Pattern

Domain 6 questions tend to follow recognizable patterns. Many are scenario-based: "A user calls the service desk to report they cannot log into the CRM system. What is this BEST described as?" The answer is an incident, not a problem or service request. Training yourself to identify the key distinguishing phrase in each scenario is essential.

Use Process of Elimination Aggressively

ITIL 4 Foundation questions use a single best answer format. When you're uncertain, eliminating obviously wrong answers first dramatically improves your odds. On Domain 6 questions, watch for distractors that mix up practice purposes — for example, attributing root cause analysis to Incident Management rather than Problem Management.

Map Practices to Value Chain Activities

Several exam questions ask which Service Value Chain activity a given practice primarily supports. Understanding the ITIL 4 Service Value Chain: Understanding the 6 Activities for the Foundation Exam in conjunction with the practices gives you a meaningful framework for answering these questions. For example, Service Desk heavily supports the "Engage" activity; Change Enablement touches "Obtain/Build" and "Deliver and Support."

6 Common Mistakes Candidates Make on Domain 6

Sample Practice Questions

Test your Domain 6 readiness with these representative questions. Answers and explanations follow each question.

Question 1

A user contacts the service desk because the company's email system is slow. The service desk restores performance by restarting a server. The underlying cause is never identified. Which practice is primarily responsible for investigating the root cause?

• A. Incident Management
• B. Problem Management
• C. Change Enablement
• D. Service Level Management

Correct Answer: B. Problem Management investigates root causes of incidents. Incident Management handled the restoration of service (restarting the server). The unresolved underlying cause becomes a problem that Problem Management should investigate.

Question 2

An organization wants to grant a user access to a new software application they need for their role. This request follows a standard documented procedure. What type of change is this BEST described as?

• A. Emergency change
• B. Normal change
• C. Standard change
• D. Major change

Correct Answer: C. Standard changes are pre-authorized, low-risk, well-understood changes that follow a documented procedure. Granting access per a defined workflow fits this definition exactly.

Question 3

Which of the following BEST describes the purpose of the Service Configuration Management practice?

• A. To plan and manage the full lifecycle of all IT assets
• B. To ensure accurate and reliable configuration information about services is available when needed
• C. To restore normal service operation as quickly as possible
• D. To make new and changed services available for use

Correct Answer: B. Service Configuration Management maintains accurate records of configuration items (CIs) in the CMDB. Option A describes IT Asset Management; C describes Incident Management; D describes Release Management.

For more targeted preparation, review the ITIL 4 Foundation Exam Difficulty: Pass Rate, Question Types, and Preparation Tips to understand exactly how scenario questions are constructed and scored.

Building Your Study Plan Around Domain 6

If you have two weeks to prepare, allocate roughly 40-50% of your study time to Domain 6. Within that allocation, spend 70% on the 7 Key Practices and 30% on the 8 Additional Practices. Use active recall techniques — quiz yourself on practice purposes, key terms, and distinguishing characteristics rather than re-reading definitions passively.

For a structured day-by-day approach, the ITIL 4 Foundation Study Plan: How to Prepare in 2 Weeks for the 2026 Exam provides a tested schedule that front-loads Domain 6 study in the first week and uses the second week for cross-domain integration and timed practice tests.

Also, don't neglect complementary domains. The 7 ITIL Guiding Principles: How to Master Them for the Foundation Exam covers Domain 4, which contributes meaningful questions and provides philosophical context that helps interpret ambiguous Domain 6 scenario questions. Understanding principles like "Focus on value" and "Keep it simple and practical" can help you eliminate incorrect answer choices that suggest overly bureaucratic or value-destroying approaches.

Frequently Asked Questions