How should I use these The Four Dimensions of Service Management practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

ITIL4F · topic practice

The Four Dimensions of Service Management practice questions

Q: Can I practise just The Four Dimensions of Service Management questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the The Four Dimensions of Service Management domain.

Practise ITIL 4 Foundation The Four Dimensions of Service Management practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

12 questionsDomain: The Four Dimensions of Service Management

Practice 10 questions Browse domain →

What the exam tests

What to know about The Four Dimensions of Service Management

The Four Dimensions of Service Management questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common The Four Dimensions of Service Management exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

The Four Dimensions of Service Management questions

12 questions · select your answer, then reveal the explanation

Question 1hardmultiple choice

Read the full The Four Dimensions of Service Management explanation →

A service provider is designing a new digital service for a financial institution. They want to ensure the service is resilient and meets regulatory compliance. Which combination of the four dimensions would be most critical to address first?

Trap 1: Organizations and people, and partners and suppliers

While 'Organizations and people' is a crucial foundational dimension, 'Partners and suppliers' is typically a secondary consideration when initially designing a new digital service. Establishing internal roles, responsibilities, culture, and governance is paramount, but external dependencies are usually defined after the core internal capabilities and technological architecture have been largely determined. Focusing on external partners too early can divert resources from essential internal development.

Trap 2: Partners and suppliers, and value streams and processes

Both 'Partners and suppliers' and 'Value streams and processes' are secondary dimensions for the initial design of a new service. External relationships with partners and suppliers are typically established once internal needs and technological requirements are clearer. Similarly, defining how work gets done through value streams and processes cannot be effectively designed without first understanding who will perform the work and what tools they will use.

Trap 3: Information and technology, and value streams and processes

While 'Information and technology' is indeed a critical foundation for a new digital service, 'Value streams and processes' alone is insufficient as the second foundational dimension. Designing effective value streams and processes inherently depends on understanding the organizational structure, roles, and culture ('Organizations and people') that will execute them. Without clarity on the human element, processes risk being impractical or inefficient, even with robust technology.

Study all The Four Dimensions of Service Management common traps →

A
Organizations and people, and partners and suppliers
Why wrong: While 'Organizations and people' is a crucial foundational dimension, 'Partners and suppliers' is typically a secondary consideration when initially designing a new digital service. Establishing internal roles, responsibilities, culture, and governance is paramount, but external dependencies are usually defined after the core internal capabilities and technological architecture have been largely determined. Focusing on external partners too early can divert resources from essential internal development.
B
Partners and suppliers, and value streams and processes
Why wrong: Both 'Partners and suppliers' and 'Value streams and processes' are secondary dimensions for the initial design of a new service. External relationships with partners and suppliers are typically established once internal needs and technological requirements are clearer. Similarly, defining how work gets done through value streams and processes cannot be effectively designed without first understanding who will perform the work and what tools they will use.
C
Organizations and people, and information and technology
These two dimensions are foundational and critical for designing any new digital service. 'Organizations and people' ensures the necessary skills, roles, responsibilities, culture, and governance structures are in place to manage the service. Concurrently, 'Information and technology' provides the essential technical architecture, data management, security, and automation capabilities required to build and deliver the digital service effectively and compliantly.
D
Information and technology, and value streams and processes
Why wrong: While 'Information and technology' is indeed a critical foundation for a new digital service, 'Value streams and processes' alone is insufficient as the second foundational dimension. Designing effective value streams and processes inherently depends on understanding the organizational structure, roles, and culture ('Organizations and people') that will execute them. Without clarity on the human element, processes risk being impractical or inefficient, even with robust technology.

Full breakdown with real-world context →

Question 2easymultiple choice

Read the full The Four Dimensions of Service Management explanation →

A service desk is experiencing high ticket volumes for password resets. After analysis, they find that users are not following the self-service password reset process. Which dimension should be improved to address this issue?

Trap 1: Value streams and processes

This dimension focuses on how an organization creates, delivers, and supports services through defined workflows and activities. While a password reset process certainly exists, the problem isn't a flaw in the process design itself (e.g., missing steps, inefficient flow) but rather a lack of user adoption or awareness of alternative, more efficient process paths, such as self-service. Therefore, redesigning the value stream or process isn't the primary solution to the high ticket volume.

Trap 2: Information and technology

This dimension encompasses the information and knowledge required to manage services, as well as the technologies that support and enable services. Since a self-service password reset tool is already in place and presumably functional, the issue is not a deficiency in the technology itself (e.g., the tool is broken, inadequate, or unavailable). The problem lies elsewhere, preventing users from leveraging the existing technological solution effectively to reduce service desk load.

Trap 3: Partners and suppliers

This dimension describes an organization's relationship with other organizations that are involved in the design, development, delivery, support, or continual improvement of services. Given that the service desk is an internal function dealing with internal user password resets, there is no indication that external partners or suppliers are directly contributing to the high ticket volume issue. The problem originates within the organization's internal service consumption and delivery model, not from third-party dependencies.

Study all The Four Dimensions of Service Management common traps →

A
Value streams and processes
Why wrong: This dimension focuses on how an organization creates, delivers, and supports services through defined workflows and activities. While a password reset process certainly exists, the problem isn't a flaw in the process design itself (e.g., missing steps, inefficient flow) but rather a lack of user adoption or awareness of alternative, more efficient process paths, such as self-service. Therefore, redesigning the value stream or process isn't the primary solution to the high ticket volume.
B
Information and technology
Why wrong: This dimension encompasses the information and knowledge required to manage services, as well as the technologies that support and enable services. Since a self-service password reset tool is already in place and presumably functional, the issue is not a deficiency in the technology itself (e.g., the tool is broken, inadequate, or unavailable). The problem lies elsewhere, preventing users from leveraging the existing technological solution effectively to reduce service desk load.
C
Organizations and people
This dimension addresses the roles, responsibilities, organizational structure, culture, and required competencies for service management. High ticket volumes for password resets, despite a self-service option, directly indicate a challenge with user behavior, awareness, or skill. Users may not be adequately trained on how to use the self-service tool, or there might be cultural resistance to adopting new methods, necessitating focus on communication, education, and user empowerment to shift demand.
D
Partners and suppliers
Why wrong: This dimension describes an organization's relationship with other organizations that are involved in the design, development, delivery, support, or continual improvement of services. Given that the service desk is an internal function dealing with internal user password resets, there is no indication that external partners or suppliers are directly contributing to the high ticket volume issue. The problem originates within the organization's internal service consumption and delivery model, not from third-party dependencies.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full The Four Dimensions of Service Management explanation →

A cloud service provider uses third-party data centers and network providers. Recently, a network outage at one data center caused a major service disruption. Which dimension should the provider focus on to prevent recurrence?

Trap 1: Information and technology

This dimension primarily concerns the knowledge, information, and technologies managed directly by the service provider to deliver value. While a network failure is indeed a technology issue, the critical distinction here is that it occurred within a third-party's infrastructure, not the service provider's own servers or software. Therefore, the immediate management challenge isn't internal technology remediation but rather external dependency management, making this option incorrect as the primary dimension.

Trap 2: Organizations and people

The Organizations and People dimension focuses on the structure, culture, and required skills of an organization's internal workforce to deliver services effectively. In this scenario, the disruption originated from an external partner's infrastructure, implying that internal organizational design, staffing, or skill gaps were not the root cause of the service interruption. While internal teams respond to the incident, the source of the problem doesn't lie within this dimension.

Trap 3: Value streams and processes

The Value Streams and Processes dimension focuses on how an organization's activities are structured and managed to create value, including specific processes like incident management or service request fulfillment. While a service disruption will undoubtedly trigger internal incident management processes, the root cause of the problem in this scenario is not a flaw in the service provider's internal processes or value stream design. Instead, the issue stems from the reliability of a critical external partner, which is addressed by a different dimension.

Study all The Four Dimensions of Service Management common traps →

A
Information and technology
Why wrong: This dimension primarily concerns the knowledge, information, and technologies managed directly by the service provider to deliver value. While a network failure is indeed a technology issue, the critical distinction here is that it occurred within a third-party's infrastructure, not the service provider's own servers or software. Therefore, the immediate management challenge isn't internal technology remediation but rather external dependency management, making this option incorrect as the primary dimension.
B
Organizations and people
Why wrong: The Organizations and People dimension focuses on the structure, culture, and required skills of an organization's internal workforce to deliver services effectively. In this scenario, the disruption originated from an external partner's infrastructure, implying that internal organizational design, staffing, or skill gaps were not the root cause of the service interruption. While internal teams respond to the incident, the source of the problem doesn't lie within this dimension.
C
Partners and suppliers
The Partners and Suppliers dimension is explicitly concerned with the relationships an organization has with other entities involved in the design, development, delivery, support, and continual improvement of services. When a cloud service provider relies on third-party data centers, managing the performance, reliability, and contractual obligations, such as Service Level Agreements, of these external partners is paramount. A disruption originating from a third-party data center's network directly falls under the scope of managing these critical external dependencies.
D
Value streams and processes
Why wrong: The Value Streams and Processes dimension focuses on how an organization's activities are structured and managed to create value, including specific processes like incident management or service request fulfillment. While a service disruption will undoubtedly trigger internal incident management processes, the root cause of the problem in this scenario is not a flaw in the service provider's internal processes or value stream design. Instead, the issue stems from the reliability of a critical external partner, which is addressed by a different dimension.

Full breakdown with real-world context →

Question 4hardmulti select

Read the full The Four Dimensions of Service Management explanation →

Which THREE of the following are examples of applying the four dimensions of service management? (Choose three.)

Trap 1: Setting up a monitoring tool for server performance

Setting up a monitoring tool for server performance primarily addresses the Information and Technology dimension, focusing on the technical components and data involved. While it involves individuals (Organizations and People) and supports operational processes (Value Streams and Processes), the action itself does not explicitly define organizational structures, integrate with external partners, or redesign an end-to-end value stream. Therefore, it does not demonstrate a holistic application across all four dimensions of service management.

Trap 2: Creating an employee training program on new tools

Incorrect. Creating an employee training program on new tools involves Organizations and People and Information and Technology, but does not clearly incorporate Partners and Suppliers or Value Streams and Processes, so it is not a strong example of applying all four dimensions.

Study all The Four Dimensions of Service Management common traps →

A
Conducting quarterly audits of supplier performance
Conducting quarterly audits of supplier performance exemplifies applying all four dimensions of service management. It directly addresses the Partners and Suppliers dimension by evaluating external entities. The audit itself constitutes a structured Value Stream and Process, requiring defined Organizations and People to execute and manage. Furthermore, it relies on Information and Technology for data collection, analysis, and reporting to ensure effective oversight and continuous improvement of supplier contributions to value.
B
Setting up a monitoring tool for server performance
Why wrong: Setting up a monitoring tool for server performance primarily addresses the Information and Technology dimension, focusing on the technical components and data involved. While it involves individuals (Organizations and People) and supports operational processes (Value Streams and Processes), the action itself does not explicitly define organizational structures, integrate with external partners, or redesign an end-to-end value stream. Therefore, it does not demonstrate a holistic application across all four dimensions of service management.
C
Creating an employee training program on new tools
Why wrong: Incorrect. Creating an employee training program on new tools involves Organizations and People and Information and Technology, but does not clearly incorporate Partners and Suppliers or Value Streams and Processes, so it is not a strong example of applying all four dimensions.
D
Defining roles and responsibilities for incident management
Correct. Defining roles and responsibilities for incident management explicitly addresses Organizations and People (roles) and Value Streams and Processes (incident management process), with potential links to Information and Technology (tools) and Partners and Suppliers (if external parties involved).
E
Designing a new service desk process
Correct. Designing a new service desk process involves Value Streams and Processes, and typically requires consideration of Organizations and People (staff), Information and Technology (service desk tools), and possibly Partners and Suppliers (if outsourced), thus applying multiple dimensions.

Full breakdown with real-world context →

Question 5hardmultiple choice

Read the full The Four Dimensions of Service Management explanation →

Refer to the exhibit. A team is using Terraform to provision an AWS EC2 instance for a new application. They need to ensure that the instance is part of the company's service management framework. Which dimension is most directly impacted by the code in the exhibit?

Exhibit

Refer to the exhibit.

resource "aws_instance" "app_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "AppServer"
  }
}

output "instance_id" {
  value = aws_instance.app_server.id
}

Trap 1: Organizations and people

The Terraform code primarily defines infrastructure resources and their configurations, not the human elements of service management. It does not specify organizational structures, define roles and responsibilities for teams or individuals, or describe the competencies required to manage the EC2 instance. While people interact with and manage this code, the code itself does not describe the 'Organizations and people' dimension.

Trap 2: Partners and suppliers

This Terraform code focuses on provisioning internal cloud resources rather than managing external relationships. It does not describe contractual agreements, service level agreements (SLAs), or the governance of interactions with third-party vendors or external partners. While the cloud provider (e.g., AWS) is a supplier, the code merely utilizes its services and does not detail the 'Partners and suppliers' relationship management aspect.

Trap 3: Value streams and processes

The Terraform code is a declarative definition of an infrastructure resource's desired state, not a description of a dynamic workflow or a sequence of activities. It does not illustrate the steps involved in delivering value, such as the process for requesting, provisioning, or maintaining the EC2 instance. Therefore, it does not represent the 'Value streams and processes' dimension, which focuses on how work flows to create value.

Study all The Four Dimensions of Service Management common traps →

A
Organizations and people
Why wrong: The Terraform code primarily defines infrastructure resources and their configurations, not the human elements of service management. It does not specify organizational structures, define roles and responsibilities for teams or individuals, or describe the competencies required to manage the EC2 instance. While people interact with and manage this code, the code itself does not describe the 'Organizations and people' dimension.
B
Partners and suppliers
Why wrong: This Terraform code focuses on provisioning internal cloud resources rather than managing external relationships. It does not describe contractual agreements, service level agreements (SLAs), or the governance of interactions with third-party vendors or external partners. While the cloud provider (e.g., AWS) is a supplier, the code merely utilizes its services and does not detail the 'Partners and suppliers' relationship management aspect.
C
Value streams and processes
Why wrong: The Terraform code is a declarative definition of an infrastructure resource's desired state, not a description of a dynamic workflow or a sequence of activities. It does not illustrate the steps involved in delivering value, such as the process for requesting, provisioning, or maintaining the EC2 instance. Therefore, it does not represent the 'Value streams and processes' dimension, which focuses on how work flows to create value.
D
Information and technology
The Terraform code explicitly defines a technological resource, an Amazon EC2 instance, specifying its attributes like the Amazon Machine Image (AMI) and instance type. This code itself is a form of information (configuration data) that dictates the deployment and configuration of technology. It directly embodies the technological components and the critical information required to manage and operate them, aligning perfectly with the 'Information and technology' dimension.

Full breakdown with real-world context →

Question 6hardmultiple choice

Read the full The Four Dimensions of Service Management explanation →

A medium-sized e-commerce company uses a hybrid cloud infrastructure with on-premises servers and AWS. The service desk handles around 2000 tickets per month, but recently there has been a 30% increase in incidents related to 'application timeouts'. The operations team noticed that the on-premises application servers often reach 90% CPU utilization during peak hours, while the AWS instances are underutilized. The company has a policy to use AWS for auto-scaling, but the auto-scaling group is configured with a static threshold of 80% CPU and a cooldown period of 5 minutes. Additionally, the load balancer uses a round-robin algorithm, sending traffic equally to on-prem and cloud instances. The application is designed to be stateless. The company wants to resolve the timeouts using ITIL best practices, considering the four dimensions. What is the most appropriate course of action?

Trap 1: Increase the CPU threshold for auto-scaling to 90% and reduce…

Increasing the CPU threshold for auto-scaling to 90% is counterproductive, as it allows servers to operate at near-maximum capacity for longer, exacerbating performance bottlenecks and increasing the likelihood of timeouts before new instances are provisioned. While reducing the cooldown period improves responsiveness, the high threshold negates this benefit by delaying the initial scaling trigger. Retraining the operations team on monitoring tools, while generally beneficial for skill development, does not directly resolve the immediate infrastructure misconfigurations related to load balancing or the auto-scaling policy itself.

Trap 2: Create a training program for developers to optimize application…

While optimizing application code to reduce CPU usage is a valuable long-term strategy for efficiency and cost reduction, it does not address the immediate infrastructure configuration issues causing performance problems. The question implies an operational bottleneck related to how traffic is distributed and how resources scale, rather than fundamental inefficiencies in the application's core logic. This approach would be a lengthy development effort, failing to provide a timely resolution to the current service degradation.

Trap 3: Move all application servers to AWS and decommission on-premises…

Moving all application servers to AWS and decommissioning on-premises servers represents a significant architectural and strategic shift, not a targeted solution for immediate performance issues. This action fails to address the root cause of misconfigured load balancing or auto-scaling policies; it merely relocates the problem to a different environment. Such a large-scale migration could introduce new complexities, potentially increase costs, and might contradict the company's existing hybrid cloud strategy or regulatory compliance requirements, making it an inappropriate and disproportionate response.

Study all The Four Dimensions of Service Management common traps →

A
Change the load balancer algorithm to least connections, adjust auto-scaling threshold to 70% CPU with a 2-minute cooldown, and update the incident management process to include a step for reviewing auto-scaling metrics.
This option provides a comprehensive solution by addressing multiple facets of the problem. Changing the load balancer algorithm to 'least connections' ensures more equitable distribution of traffic, preventing individual servers from becoming overloaded. Adjusting the auto-scaling threshold to 70% CPU with a 2-minute cooldown allows for more proactive and responsive scaling, adding capacity before performance degrades significantly. Finally, updating the incident management process to review auto-scaling metrics ensures continuous learning and improvement, preventing similar issues from recurring by optimizing the system based on operational data.
B
Increase the CPU threshold for auto-scaling to 90% and reduce cooldown to 2 minutes, and retrain the operations team on monitoring tools.
Why wrong: Increasing the CPU threshold for auto-scaling to 90% is counterproductive, as it allows servers to operate at near-maximum capacity for longer, exacerbating performance bottlenecks and increasing the likelihood of timeouts before new instances are provisioned. While reducing the cooldown period improves responsiveness, the high threshold negates this benefit by delaying the initial scaling trigger. Retraining the operations team on monitoring tools, while generally beneficial for skill development, does not directly resolve the immediate infrastructure misconfigurations related to load balancing or the auto-scaling policy itself.
C
Create a training program for developers to optimize application code to reduce CPU usage.
Why wrong: While optimizing application code to reduce CPU usage is a valuable long-term strategy for efficiency and cost reduction, it does not address the immediate infrastructure configuration issues causing performance problems. The question implies an operational bottleneck related to how traffic is distributed and how resources scale, rather than fundamental inefficiencies in the application's core logic. This approach would be a lengthy development effort, failing to provide a timely resolution to the current service degradation.
D
Move all application servers to AWS and decommission on-premises servers, simplifying infrastructure.
Why wrong: Moving all application servers to AWS and decommissioning on-premises servers represents a significant architectural and strategic shift, not a targeted solution for immediate performance issues. This action fails to address the root cause of misconfigured load balancing or auto-scaling policies; it merely relocates the problem to a different environment. Such a large-scale migration could introduce new complexities, potentially increase costs, and might contradict the company's existing hybrid cloud strategy or regulatory compliance requirements, making it an inappropriate and disproportionate response.

Full breakdown with real-world context →

Question 7mediummultiple choice

Read the full The Four Dimensions of Service Management explanation →

An IT organization is adopting ITIL 4 and wants to ensure all aspects of service management are covered. They are currently focusing on defining roles, responsibilities, and decision-making authority. Which dimension are they addressing?

Trap 1: Partners and suppliers

This dimension covers external relationships, not internal roles.

Trap 2: Information and technology

This dimension covers data, technology, and information management, not roles.

Trap 3: Value streams and processes

This dimension covers activities and workflows, not organizational structure.

Study all The Four Dimensions of Service Management common traps →

A
Organizations and people
Correct. This dimension includes roles, responsibilities, and governance.
B
Partners and suppliers
Why wrong: This dimension covers external relationships, not internal roles.
C
Information and technology
Why wrong: This dimension covers data, technology, and information management, not roles.
D
Value streams and processes
Why wrong: This dimension covers activities and workflows, not organizational structure.

Full breakdown with real-world context →

Question 8mediummulti select

Read the full The Four Dimensions of Service Management explanation →

Which TWO of the following are considered to be part of the four dimensions of service management? (Choose two.)

Trap 1: Products and services

These are outputs, not a dimension.

Trap 2: Governance

Governance is part of the organizations and people dimension, not a separate dimension.

Trap 3: Customers

Customers are stakeholders, not a dimension.

Study all The Four Dimensions of Service Management common traps →

A
Products and services
Why wrong: These are outputs, not a dimension.
B
Governance
Why wrong: Governance is part of the organizations and people dimension, not a separate dimension.
C
Information and technology
Correct. This is one of the four dimensions.
D
Customers
Why wrong: Customers are stakeholders, not a dimension.
E
Organizations and people
Correct. This is one of the four dimensions.

Full breakdown with real-world context →

Question 9mediumdrag order

Read the full The Four Dimensions of Service Management explanation →

Drag and drop the steps of the incident management process into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Identification & Logging, then Investigation, then Categorization &…

Placing investigation before categorization and prioritization is inefficient and potentially risky in incident management. Without first assessing the incident's impact and urgency, critical issues might not receive the immediate attention they warrant, while minor issues could consume disproportionate resources. Categorization and prioritization are essential for directing investigative efforts effectively and aligning them with business needs and service level agreements.

Trap 2: Categorization & Prioritization, then Identification & Logging,…

This sequence is fundamentally flawed because an incident must first be formally identified and logged into the system before any subsequent actions, such as categorization or prioritization, can occur. Logging creates the official record and unique identifier, which is a prerequisite for all further management activities. Without a logged incident, there is no recognized event to categorize or prioritize, making the process unmanageable.

Trap 3: Identification & Logging, then Categorization & Prioritization,…

Attempting resolution before investigation is premature and often ineffective in incident management. Investigation is crucial for understanding the incident's nature, identifying its root cause or a viable workaround, and determining the most appropriate course of action. Resolving an incident without proper investigation risks applying incorrect fixes, leading to recurrence or further service disruption, thereby prolonging the impact on users.

Study all The Four Dimensions of Service Management common traps →

A
Identification & Logging, then Categorization & Prioritization, then Investigation, then Resolution, then Closure.
This is the correct order because incident management starts with logging the incident, then categorizing and prioritizing it, followed by investigation to find a workaround or root cause, implementing a resolution, and finally closing the incident.
B
Identification & Logging, then Investigation, then Categorization & Prioritization, then Resolution, then Closure.
Why wrong: Placing investigation before categorization and prioritization is inefficient and potentially risky in incident management. Without first assessing the incident's impact and urgency, critical issues might not receive the immediate attention they warrant, while minor issues could consume disproportionate resources. Categorization and prioritization are essential for directing investigative efforts effectively and aligning them with business needs and service level agreements.
C
Categorization & Prioritization, then Identification & Logging, then Investigation, then Resolution, then Closure.
Why wrong: This sequence is fundamentally flawed because an incident must first be formally identified and logged into the system before any subsequent actions, such as categorization or prioritization, can occur. Logging creates the official record and unique identifier, which is a prerequisite for all further management activities. Without a logged incident, there is no recognized event to categorize or prioritize, making the process unmanageable.
D
Identification & Logging, then Categorization & Prioritization, then Resolution, then Investigation, then Closure.
Why wrong: Attempting resolution before investigation is premature and often ineffective in incident management. Investigation is crucial for understanding the incident's nature, identifying its root cause or a viable workaround, and determining the most appropriate course of action. Resolving an incident without proper investigation risks applying incorrect fixes, leading to recurrence or further service disruption, thereby prolonging the impact on users.

Full breakdown with real-world context →

Question 10mediumdrag order

Read the full The Four Dimensions of Service Management explanation →

Drag and drop the steps of the service desk function in handling a user request into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Categorization, Logging, Support, Confirmation, Updating

This sequence is incorrect because the fundamental first step in any service desk interaction is logging the request to create a formal record and assign a unique identifier. Attempting to categorize a request before it has been logged means there is no official entry to apply categorization criteria to, making the process untraceable and unmanageable. Additionally, confirming resolution with the user before updating the ticket with the final resolution details creates an incomplete audit trail and hinders knowledge management efforts.

Trap 2: Logging, Support, Categorization, Updating, Confirmation

This order is incorrect because initiating support activities immediately after logging, but before categorization, is highly inefficient and prone to errors. Categorization is essential for accurately assessing the request's impact, urgency, and type, which dictates proper routing to the correct support group or specialist. Without this crucial step, support efforts might be misdirected, leading to delays, rework, and a suboptimal resolution experience for the user.

Trap 3: Support, Logging, Categorization, Updating, Confirmation

This sequence is fundamentally flawed as it suggests providing 'Support' before 'Logging' or 'Categorization.' The service desk's role as the single point of contact requires every interaction to be formally logged first to establish a record, track progress, and ensure accountability. Providing support without logging means there is no audit trail, no data for performance analysis, and no structured approach to problem-solving, which contradicts core ITIL principles of transparency and control.

Study all The Four Dimensions of Service Management common traps →

A
Logging, Categorization, Support, Updating, Confirmation
This is the correct order because the service desk first logs the request, then categorizes it to assign priority, provides support to resolve it, updates the ticket with resolution details, and finally confirms closure with the user.
B
Categorization, Logging, Support, Confirmation, Updating
Why wrong: This sequence is incorrect because the fundamental first step in any service desk interaction is logging the request to create a formal record and assign a unique identifier. Attempting to categorize a request before it has been logged means there is no official entry to apply categorization criteria to, making the process untraceable and unmanageable. Additionally, confirming resolution with the user before updating the ticket with the final resolution details creates an incomplete audit trail and hinders knowledge management efforts.
C
Logging, Support, Categorization, Updating, Confirmation
Why wrong: This order is incorrect because initiating support activities immediately after logging, but before categorization, is highly inefficient and prone to errors. Categorization is essential for accurately assessing the request's impact, urgency, and type, which dictates proper routing to the correct support group or specialist. Without this crucial step, support efforts might be misdirected, leading to delays, rework, and a suboptimal resolution experience for the user.
D
Support, Logging, Categorization, Updating, Confirmation
Why wrong: This sequence is fundamentally flawed as it suggests providing 'Support' before 'Logging' or 'Categorization.' The service desk's role as the single point of contact requires every interaction to be formally logged first to establish a record, track progress, and ensure accountability. Providing support without logging means there is no audit trail, no data for performance analysis, and no structured approach to problem-solving, which contradicts core ITIL principles of transparency and control.

Full breakdown with real-world context →

Question 11mediummatching

Read the full The Four Dimensions of Service Management explanation →

Match each ITIL 4 guiding principle to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Everything the organization does must map to stakeholder value

Use existing services, processes, and tools as a foundation

Work in small, incremental steps with regular reviews

Involve stakeholders and make work visible to reduce silos

Minimize complexity and eliminate unnecessary steps

Trap 1: Focus on value: Use automation to reduce manual effort.

While reducing manual effort through automation can contribute to efficiency and potentially value, this description specifically aligns with the 'Optimize and automate' guiding principle. The 'Focus on value' principle is broader, demanding a holistic understanding of stakeholder value and ensuring all efforts, automated or manual, are aligned with delivering that value, not just reducing effort. Automation is a means, not the primary focus of this principle.

Trap 2: Start where you are: Reduce complexity by eliminating unnecessary…

This statement describes the 'Keep it simple and practical' guiding principle, which focuses on designing solutions that are easy to understand and use by removing anything that does not contribute to value. The 'Start where you are' principle, in contrast, is about recognizing and utilizing current organizational assets and capabilities as a foundation for improvement, rather than primarily focusing on simplification.

Study all The Four Dimensions of Service Management common traps →

A
Focus on value: Ensure that everything you do delivers value to stakeholders.
This principle emphasizes that all activities within an organization, from strategy to operations, must directly or indirectly contribute to the creation of value for customers, users, and the organization itself. It requires understanding who the stakeholders are, what they consider valuable, and then designing, delivering, and improving services to meet those expectations effectively. Value can be defined subjectively by stakeholders and encompasses outcomes, costs, and risks.
B
Focus on value: Use automation to reduce manual effort.
Why wrong: While reducing manual effort through automation can contribute to efficiency and potentially value, this description specifically aligns with the 'Optimize and automate' guiding principle. The 'Focus on value' principle is broader, demanding a holistic understanding of stakeholder value and ensuring all efforts, automated or manual, are aligned with delivering that value, not just reducing effort. Automation is a means, not the primary focus of this principle.
C
Start where you are: Assess the current state and build on existing capabilities.
This principle advocates for a pragmatic approach, urging organizations to critically evaluate their current services, processes, tools, and people before initiating new work or improvements. It encourages leveraging existing successful elements and avoiding the unnecessary creation of new resources or "reinventing the wheel." A thorough assessment helps identify what works well and what needs improvement, providing a realistic baseline for progress.
D
Start where you are: Reduce complexity by eliminating unnecessary steps.
Why wrong: This statement describes the 'Keep it simple and practical' guiding principle, which focuses on designing solutions that are easy to understand and use by removing anything that does not contribute to value. The 'Start where you are' principle, in contrast, is about recognizing and utilizing current organizational assets and capabilities as a foundation for improvement, rather than primarily focusing on simplification.
E
Progress iteratively with feedback: Use iterative development and seek feedback to improve.
This principle promotes breaking down large initiatives into smaller, manageable iterations, allowing for continuous learning and adaptation. Each iteration should deliver a tangible outcome and be followed by a feedback loop, enabling adjustments and improvements based on stakeholder input and lessons learned. This approach minimizes risk, accelerates delivery, and ensures solutions remain relevant and effective.
F
Collaborate and promote visibility: Work together across teams and make work visible to build trust.
This principle emphasizes the importance of cross-functional teamwork and transparent communication to achieve shared objectives. By breaking down silos and making work, progress, and challenges visible to all relevant stakeholders, organizations can foster a culture of trust, shared ownership, and informed decision-making. Effective collaboration ensures diverse perspectives are considered and integrated.

Full breakdown with real-world context →

Question 12mediummatching

Read the full The Four Dimensions of Service Management explanation →

Match each ITIL 4 term related to incidents and problems.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Unplanned interruption or reduction in quality of a service

Root cause of one or more incidents

Temporary solution to restore service until permanent fix is available

A problem with a documented root cause and workaround

A pre-defined request from a user for information or access

Trap 1: Incident: A cause of one or more incidents.

This definition incorrectly describes a Problem, not an Incident. An Incident is an unplanned interruption of service, an *effect*, whereas 'a cause of one or more incidents' points to the underlying *reason* for such interruptions. Confusing these terms can lead to misdirected efforts, focusing on root cause analysis when immediate service restoration is paramount.

Trap 2: Problem: Unplanned interruption of service.

This statement incorrectly defines a Problem as an 'unplanned interruption of service,' which is the precise definition of an Incident. A Problem, conversely, is the underlying cause of such interruptions, not the interruption itself. Misidentifying a Problem as an Incident can lead to a reactive 'fix the symptom' approach rather than proactive 'eliminate the cause' problem management.

Study all The Four Dimensions of Service Management common traps →

A
Incident: Unplanned interruption or reduction in quality of an IT service.
An Incident represents an immediate, adverse event impacting an IT service, such as a system outage or degraded performance. Its primary characteristic is the unplanned nature of the interruption, directly affecting users' ability to consume the service. Effective incident management focuses on restoring normal service operation as quickly as possible to minimize business impact.
B
Problem: A cause of one or more incidents.
A Problem, in ITIL 4, is the underlying cause of one or more incidents, even if the cause is not yet known. It represents a deeper issue that, if left unaddressed, can lead to recurring service disruptions. Problem Management aims to identify, analyze, and eliminate these root causes to prevent future incidents.
C
Workaround: A temporary solution that reduces or eliminates impact of an incident or problem.
A Workaround is a temporary measure designed to reduce or eliminate the impact of an incident or problem when a full resolution is not immediately available. Its purpose is to restore service functionality or mitigate disruption for users while a permanent fix is being developed. Workarounds are crucial for maintaining service continuity and managing user expectations during complex issue resolution.
D
Known Error: A problem that has been analyzed and has a documented root cause and workaround.
A Known Error signifies a problem that has been thoroughly analyzed, leading to a documented root cause and a defined workaround. This status indicates that the underlying issue is understood, and a temporary solution is available to mitigate its impact. Managing Known Errors efficiently helps in preventing future incidents and expediting incident resolution by providing pre-defined solutions.
E
Incident: A cause of one or more incidents.
Why wrong: This definition incorrectly describes a Problem, not an Incident. An Incident is an unplanned interruption of service, an *effect*, whereas 'a cause of one or more incidents' points to the underlying *reason* for such interruptions. Confusing these terms can lead to misdirected efforts, focusing on root cause analysis when immediate service restoration is paramount.
F
Problem: Unplanned interruption of service.
Why wrong: This statement incorrectly defines a Problem as an 'unplanned interruption of service,' which is the precise definition of an Incident. A Problem, conversely, is the underlying cause of such interruptions, not the interruption itself. Misidentifying a Problem as an Incident can lead to a reactive 'fix the symptom' approach rather than proactive 'eliminate the cause' problem management.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused The Four Dimensions of Service Management sessions

Start a The Four Dimensions of Service Management only practice session

Every question in these sessions is drawn from the The Four Dimensions of Service Management domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all The Four Dimensions of Service Management questions →Mixed ITIL4F session

Frequently asked questions

What does the ITIL4F exam test about The Four Dimensions of Service Management?: The Four Dimensions of Service Management questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just The Four Dimensions of Service Management questions in a focused session?: Yes — the session launcher on this page draws every question from the The Four Dimensions of Service Management domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other ITIL4F topics?: Use the topic links above to move to related areas, or go back to the ITIL4F question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the ITIL4F exam covers. They are not copied from any real exam or dump site.

The Four Dimensions of Service Management only

10 questions 20 questions 30 questions 50 questions

Mixed ITIL4F session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All ITIL4F questions The Four Dimensions of Service Management domain overview ITIL4F exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

The Four Dimensions of Service Management practice questions

What to know about The Four Dimensions of Service Management

Common The Four Dimensions of Service Management exam traps

The Four Dimensions of Service Management questions

A service provider is designing a new digital service for a financial institution. They want to ensure the service is resilient and meets regulatory compliance. Which combination of the four dimensions would be most critical to address first?

A service desk is experiencing high ticket volumes for password resets. After analysis, they find that users are not following the self-service password reset process. Which dimension should be improved to address this issue?

A cloud service provider uses third-party data centers and network providers. Recently, a network outage at one data center caused a major service disruption. Which dimension should the provider focus on to prevent recurrence?

Which THREE of the following are examples of applying the four dimensions of service management? (Choose three.)

Refer to the exhibit. A team is using Terraform to provision an AWS EC2 instance for a new application. They need to ensure that the instance is part of the company's service management framework. Which dimension is most directly impacted by the code in the exhibit?

Exhibit

An IT organization is adopting ITIL 4 and wants to ensure all aspects of service management are covered. They are currently focusing on defining roles, responsibilities, and decision-making authority. Which dimension are they addressing?

Which TWO of the following are considered to be part of the four dimensions of service management? (Choose two.)

Drag and drop the steps of the incident management process into the correct order.

Drag and drop the steps of the service desk function in handling a user request into the correct order.

Match each ITIL 4 guiding principle to its description.

Match each ITIL 4 term related to incidents and problems.

Track your progress over time

Start a The Four Dimensions of Service Management only practice session

Related ITIL4F topic practice pages