Courseiva

CCNA ITIL Management Practices Questions

75 of 301 questions · Page 4/5 · ITIL Management Practices · Answers revealed

Practice these questionsDomain overviewAll questions
226
MCQmedium

A service desk manager wants to improve first call resolution (FCR) rate. According to ITIL 4, which practice is MOST directly related to this activity?

A.Service Desk
B.Service Level Management
C.Incident Management
D.Problem Management
AnswerA

The Service Desk is the primary point of contact between the service provider and the users. Its core function includes handling incidents and service requests, and a key measure of its efficiency and effectiveness is First Call Resolution (FCR). Improving FCR directly aligns with the Service Desk's objective to restore normal service operation quickly and efficiently, often by empowering its staff with better tools, knowledge, and processes for immediate resolution.

Why this answer

The Service Desk practice is directly responsible for handling incidents and service requests, and first call resolution (FCR) is a key performance indicator for the service desk. Improving FCR means resolving more incidents during the initial contact without escalation, which is a core operational goal of the service desk practice.

Exam trap

The trap here is that candidates confuse the Incident Management practice (which handles the overall incident lifecycle) with the Service Desk practice (which executes the first-contact resolution), leading them to pick Incident Management instead of Service Desk.

How to eliminate wrong answers

Option B (Service Level Management) is wrong because it focuses on defining, negotiating, and monitoring service level agreements (SLAs), not on the tactical execution of resolving incidents on the first call. Option C (Incident Management) is wrong because while it manages the lifecycle of incidents, the specific activity of improving FCR is a service desk metric and operational target, not a direct responsibility of the incident management process itself. Option D (Problem Management) is wrong because it aims to identify and eliminate the root causes of incidents to prevent recurrence, which is a separate, longer-term activity that does not directly target same-call resolution.

Practice this question →
227
MCQeasy

What is the first step in the ITIL 4 Continual Improvement Model?

A.Where are we now?
B.How do we get there?
C.Take action
D.What is the vision?
AnswerD

This is indeed the correct first step in the ITIL 4 Continual Improvement Model, establishing the clear purpose and desired outcome of any improvement initiative. It involves defining the overall direction, understanding stakeholder value, and ensuring alignment with organizational objectives. This foundational step provides the guiding star for all subsequent activities, ensuring that efforts are focused on achieving a meaningful and beneficial future state.

Why this answer

The ITIL 4 Continual Improvement Model begins with 'What is the vision?' because every improvement initiative must be anchored to the organization's strategic direction, business goals, and the desired future state before any assessment of the current situation occurs. Only after the vision is articulated can the organization meaningfully ask 'Where are we now?' to establish a baseline. This ordering ensures improvements are purposeful rather than reactive.

Exam trap

ITIL4F often tests the exact sequence of the Continual Improvement Model, and candidates frequently confuse 'Where are we now?' with the first step because it feels like the natural starting point for any assessment.

How to eliminate wrong answers

Option A is wrong because 'Where are we now?' is the second step of the model — it performs the current-state assessment only after the vision has been defined. Option B is wrong because 'How do we get there?' is the fourth step, covering the plan for reaching the target state. Option C is wrong because 'Take action' is the fifth step, where the improvement plan is actually executed.

Practice this question →
228
MCQeasy

Which ITIL management practice is responsible for managing the lifecycle of all IT assets?

A.IT Asset Management
B.Supplier Management
C.Service Catalog Management
D.Service Configuration Management
AnswerA

IT Asset Management is the ITIL management practice responsible for systematically managing the full lifecycle of IT assets, from acquisition and deployment through maintenance, upgrade, and eventual disposal. Its primary goal is to maximize value, control costs, and mitigate risks associated with IT assets, ensuring they support organizational objectives effectively. This includes tracking financial, contractual, and inventory details to optimize asset utilization and compliance.

Why this answer

IT Asset Management (ITAM) is the ITIL 4 practice specifically responsible for planning, managing, and controlling the lifecycle of all IT assets, including hardware, software, and digital assets. It ensures assets are accounted for, financially optimized, and compliant with policies from acquisition through disposal. This practice directly aligns with the question's focus on lifecycle management of all IT assets.

Exam trap

The trap here is confusing Service Configuration Management (which manages configuration data and relationships of CIs) with IT Asset Management (which manages the full lifecycle, financials, and compliance of all IT assets), leading candidates to pick D instead of A.

How to eliminate wrong answers

Option B (Supplier Management) is wrong because it focuses on managing relationships, contracts, and performance of external suppliers, not the lifecycle of IT assets themselves. Option C (Service Catalog Management) is wrong because it provides a single source of consistent information on all services and service offerings, but does not manage the lifecycle of physical or digital assets. Option D (Service Configuration Management) is wrong because it manages configuration items (CIs) and their relationships within the service model, but its scope is limited to configuration data and does not cover financial, contractual, or lifecycle aspects of all IT assets.

Practice this question →
229
MCQeasy

What is the PRIMARY difference between an SLA and an OLA?

A.An SLA is between a service provider and a customer; an OLA is between the service provider and another internal team
B.An SLA is for external customers; an OLA is for internal customers
C.An SLA is a written agreement; an OLA is verbal
D.An SLA defines responsibilities; an OLA defines penalties
AnswerA

An SLA, or Service Level Agreement, formally establishes the agreed-upon service levels and responsibilities between a service provider and its customer, who consumes the service. Conversely, an OLA, or Operational Level Agreement, is an internal agreement between different teams or departments within the *same* service provider organization. Its purpose is to define the specific support activities and performance targets required to deliver the overall service levels committed in an SLA to the customer.

Why this answer

The primary difference is that a Service Level Agreement (SLA) is a documented agreement between a service provider and a customer (external or internal) that defines the service level targets, while an Operational Level Agreement (OLA) is an internal agreement between the service provider and another internal team (e.g., IT operations, network team) that supports the delivery of the SLA. Option A correctly captures this distinction, as OLAs are always internal to the organization and support the SLA's commitments.

Exam trap

The trap here is that candidates confuse 'internal customer' with 'internal team,' leading them to choose Option B, but ITIL 4 defines OLAs as agreements between internal teams, not between the service provider and an internal customer.

How to eliminate wrong answers

Option B is wrong because an SLA can be for both external and internal customers (e.g., an internal SLA between IT and HR), and an OLA is always internal between teams, not specifically for internal customers. Option C is wrong because both SLAs and OLAs are formal written agreements; neither is verbal in ITIL 4 practice. Option D is wrong because both SLAs and OLAs define responsibilities and targets, but penalties are not a required component of either; ITIL 4 focuses on service level targets and improvement, not punitive measures.

Practice this question →
230
MCQmedium

Which practice uses the ITIL Continual Improvement Model (7 steps)?

A.Continual Improvement
B.Service Desk
C.Incident Management
D.Change Enablement
AnswerA

The ITIL Continual Improvement Model, often referred to as the 7-step model, is the foundational framework for the Continual Improvement practice. This structured approach guides organizations through identifying opportunities, planning improvements, implementing changes, and reviewing outcomes across all services and products. It ensures that improvements are systematically managed and contribute directly to value creation and organizational objectives, making it central to sustained service excellence.

Why this answer

The Continual Improvement practice is the ITIL 4 practice that uses the Continual Improvement Model, a seven-step process: (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? This practice drives ongoing improvement of products, services, and practices across the organization.

Exam trap

ITIL4F often tests the misconception that the Continual Improvement Model belongs to a specific practice like Service Desk or Incident Management — candidates must remember it is owned by the Continual Improvement practice itself.

How to eliminate wrong answers

Option B is wrong because the Service Desk practice focuses on incident and service request handling, not on the Continual Improvement Model. Option C is wrong because Incident Management is about restoring normal service operation as quickly as possible, not about the seven-step improvement model. Option D is wrong because Change Enablement manages changes to services and components, not the Continual Improvement Model.

Practice this question →
231
MCQmedium

An organization identifies that a recurring incident is caused by a faulty network cable. According to ITIL 4, when should this be documented as a known error?

A.When the problem record is closed
B.When the incident is first reported
C.After root cause analysis and a workaround is found
D.After the cable is replaced
AnswerC

A known error is formally identified in ITIL when the root cause of one or more recurring incidents has been determined, and a temporary workaround has been successfully developed and documented. This critical step allows for quicker restoration of service for future occurrences of the same incident, even if a permanent solution is not yet implemented. This status transitions an unknown problem into a manageable known error, enabling proactive incident management and improving service desk efficiency.

Why this answer

In ITIL 4, a known error is documented after root cause analysis has been performed and a workaround has been identified, even if the permanent fix has not yet been implemented. This allows the service desk to quickly resolve future incidents caused by the same underlying problem using the documented workaround. The faulty network cable is a recurring incident, so the problem management process would first diagnose the root cause (the faulty cable) and then create a known error record with the workaround (e.g., replacing the cable or using a spare port).

Exam trap

The trap here is that candidates confuse the timing of documenting a known error with the timing of implementing the permanent fix, mistakenly thinking the known error is only recorded after the cable is replaced or the problem is fully resolved.

How to eliminate wrong answers

Option A is wrong because closing the problem record occurs after the permanent fix is implemented and verified, which is later in the lifecycle than documenting the known error. Option B is wrong because when the incident is first reported, the root cause is unknown; a known error requires confirmed diagnosis, not just a symptom. Option D is wrong because replacing the cable is the permanent fix, which happens after the known error is documented and the workaround is applied; the known error record is created before the fix is deployed.

Practice this question →
232
MCQmedium

Which practice is responsible for ensuring that services meet agreed levels of performance and availability?

A.Monitoring and Event Management
B.Availability Management
C.Capacity and Performance Management
D.Service Level Management
AnswerD

Service Level Management negotiates, monitors and reports on service level agreements, ensuring delivered services meet agreed performance and availability targets. It owns the continual measurement and improvement cycle against those commitments, exactly the accountability described in the question.

Why this answer

Service Level Management is the ITIL 4 practice responsible for ensuring that services meet agreed levels of performance and availability. This practice defines, agrees, and monitors service level targets (including performance and availability) through service level agreements (SLAs). When targets are not met, Service Level Management initiates corrective actions and escalations to ensure the service provider delivers on its commitments.

While technical practices like Capacity and Performance Management (for performance) and Availability Management (for availability) contribute to achieving these targets, the overall responsibility for ensuring agreed levels rests with Service Level Management.

Exam trap

Candidates often mistake this question for Capacity and Performance Management (Option C) because it explicitly mentions 'performance', or Availability Management (Option B) because of 'availability'. However, the phrase 'agreed levels' points to Service Level Management, which is the practice that manages the agreements and ensures all agreed targets—both performance and availability—are met through coordination with other practices.

How to eliminate wrong answers

Option A is wrong because Monitoring and Event Management is the practice of observing IT services and infrastructure to detect events and trigger responses, but it does not own the responsibility for ensuring agreed performance and availability levels—it provides data that other practices use. Option B is wrong because Availability Management is a separate ITIL practice that specifically focuses on ensuring services meet agreed availability targets (uptime, reliability), but it does not manage performance aspects such as response times or throughput. Option D is wrong because Service Level Management is responsible for negotiating, agreeing, and reporting on service level targets, but it does not directly manage the technical capacity or performance of the underlying infrastructure to achieve those targets.

Practice this question →
233
MCQmedium

An organization wants to improve its incident resolution time. According to the ITIL Continual Improvement Model, what is the FIRST step?

A.Create an improvement register
B.Identify current and desired states
C.Define measurable targets
D.Define the vision and direction
AnswerD

Defining the vision and direction is the correct first step in the ITIL Continual Improvement Model, corresponding to "What is the vision?". This foundational activity involves articulating a clear, high-level understanding of what the organization intends to achieve through its improvement efforts. Establishing this strategic context ensures that all subsequent improvement activities are aligned with organizational objectives, providing a guiding purpose before delving into current states, desired outcomes, or specific actions.

Why this answer

According to the ITIL 4 Continual Improvement Model, the first step is to define the vision and direction. This step establishes the overall goal and scope of the improvement initiative, ensuring alignment with business strategy. Without a clear vision, subsequent steps like identifying current and desired states lack context.

Exam trap

The trap is jumping to tactical steps like identifying current state or defining targets; candidates may overlook that the model starts with a strategic vision, not operational details.

How to eliminate wrong answers

Option A is wrong because creating an improvement register is a later step, typically after identifying improvements. Option B is wrong because identifying current and desired states comes after defining the vision and direction. Option C is wrong because defining measurable targets is part of the 'define the target state' step, which follows the vision.

Practice this question →
234
MCQhard

Which of the following is an example of an output, as defined in ITIL 4?

A.Reduction in average incident resolution time
B.Improved user satisfaction after a system upgrade
C.A monthly performance report generated by the IT system
D.Increased revenue from a new service
AnswerC

"A monthly performance report generated by the IT system" is a clear example of an output. This report is a tangible artifact and a direct deliverable produced by an IT activity (report generation). It is a specific product that can be consumed or used by stakeholders, providing information, even though its ultimate purpose is to enable better decision-making (an outcome).

Why this answer

An output, as defined in ITIL 4, is a tangible, deliverable result produced by an activity or process. A monthly performance report is a concrete, measurable artifact generated by the IT system, which aligns with the ITIL 4 definition of an output as something that is directly produced, not an outcome or benefit.

Exam trap

The trap here is that candidates often confuse outputs with outcomes, mistakenly selecting options that describe benefits or improvements (like reduced resolution time or increased revenue) instead of the tangible, directly produced deliverables defined in ITIL 4.

How to eliminate wrong answers

Option A is wrong because a reduction in average incident resolution time is an outcome—a measurable change in performance or state resulting from the output, not the output itself. Option B is wrong because improved user satisfaction is an outcome, specifically a perception-based result of a change, not a tangible deliverable. Option D is wrong because increased revenue is a business outcome or benefit derived from a service, not a direct, concrete product of an activity or process.

Practice this question →
235
Multi-Selectmedium

Which TWO of the following are examples of utility in ITIL 4?

Select 2 answers
A.The system processes transactions within 2 seconds
B.The system is available 99.9% of the time
C.The system supports automated billing
D.The system allows users to generate reports
E.The system is secure and compliant
AnswersC, D

This statement identifies a specific functional capability that the system provides, enabling the automation of billing processes. In ITIL 4, utility refers to the functionality offered by a service, determining whether it is 'fit for purpose' by supporting the performance of tasks or the achievement of desired outcomes for the consumer. Providing automated billing directly contributes to the value derived from the service's core capabilities.

Why this answer

Utility in ITIL 4 refers to the functionality offered by a product or service to meet a specific user need. Option C is correct because automated billing directly fulfills a business requirement by performing a specific function, which is the essence of utility. Option D is correct because report generation is a functional capability that enables users to achieve a desired outcome.

Exam trap

The trap here is confusing warranty attributes (like performance, availability, security) with utility features, leading candidates to incorrectly select options that describe service quality or assurance rather than functional capability.

Practice this question →
236
Multi-Selecthard

Which THREE of the following are purposes of the Service Level Management practice?

Select 3 answers
A.Monitor and report on service levels
B.Resolve incidents within agreed times
C.Ensure customer engagement and feedback
D.Manage relationships with suppliers
E.Negotiate and agree service level agreements (SLAs)
AnswersA, C, E

Service Level Management (SLM) is fundamentally responsible for the ongoing monitoring of actual service performance against the agreed-upon targets defined in Service Level Agreements (SLAs). This process involves collecting relevant data, analyzing deviations, and providing regular, transparent reports to both customers and internal stakeholders. Such monitoring and reporting ensure accountability and facilitate proactive identification of service delivery issues, enabling timely corrective actions.

Why this answer

Option A is correct because Service Level Management (SLM) continuously monitors and reports on achieved service levels against agreed targets, typically through SLAs, OLAs, and service level reports reviewed in service review meetings. Option C is correct because SLM ensures customer engagement and feedback by capturing customer requirements, expectations, and satisfaction, and using that input to shape and improve services. Option E is correct because negotiating, agreeing, and maintaining SLAs with customers is a core SLM activity, along with ensuring they remain relevant and achievable.

Option B is not an SLM purpose because resolving incidents within agreed times is the responsibility of the Incident Management practice, although SLM may define the targets. Option D is not an SLM purpose because managing relationships with suppliers belongs to Supplier Management, even though SLM may rely on underpinning contracts and OLAs.

Exam trap

PeopleCert often tests the distinction between practices that define targets (SLM) versus those that execute operational tasks (Incident Management) or manage external parties (Supplier Management), leading candidates to confuse 'managing' with 'doing'.

Practice this question →
237
MCQhard

An organization has a pre-approved process for adding new users to a system. A manager requests access for a new employee. According to ITIL 4, how should this request be classified?

A.As a normal change, because it involves granting access
B.As an emergency change, to expedite the request
C.As an incident, because the new employee cannot access the system yet
D.As a service request, because it is a predefined, pre-approved fulfillment
AnswerD

A pre-approved, predefined process for adding users is a standard change handled through the service request practise, not incident or problem management. Routing it as a service request lets the request fulfil through the established workflow without separate authorisation, matching ITIL 4's definition of normal service requests.

Why this answer

Per ITIL 4, a service request is a predefined, pre-approved, and standardized request for a service action, such as granting access to a system. The process for adding new users is already approved and documented, so the manager's request fits the definition of a service request, not a change or incident.

Exam trap

The trap here is that candidates confuse a pre-approved process with a 'standard change' (which is still a change) rather than recognizing that predefined, low-risk fulfillment activities are classified as service requests in ITIL 4.

How to eliminate wrong answers

Option A is wrong because a normal change is used for modifications that require assessment and approval through the change control process, whereas granting access via a pre-approved process is a standard fulfillment activity. Option B is wrong because an emergency change is reserved for resolving a critical incident or urgent issue that cannot wait for the normal change process, and a new employee access request is not urgent or critical by default. Option C is wrong because an incident is an unplanned interruption or reduction in quality of a service, not a planned request for access; the new employee has not yet been granted access, so there is no service interruption.

Practice this question →
238
Multi-Selectmedium

Which TWO of the following are key activities of Service Level Management?

Select 2 answers
A.Negotiating and agreeing service level agreements (SLAs)
B.Monitoring and reporting service performance against SLAs
C.Authorizing changes to IT services
D.Managing contracts with external suppliers
E.Handling user requests and incidents
AnswersA, B

Negotiating and agreeing SLAs is a core Service Level Management activity, directly satisfying the stem's requirement for key activities. SLM engages customers to define targets, then documents them in SLAs, ensuring services align with business needs and expectations before performance is measured.

Why this answer

Service Level Management (SLM) is the ITIL practice responsible for setting clear, measurable targets for service quality and then verifying that those targets are met. Option A is correct because negotiating and agreeing SLAs (together with OLAs and underpinning contracts) is the foundational SLM activity that defines what the customer will receive and the targets against which performance will be judged. Option B is correct because SLM must continuously monitor actual service performance, compare it to the agreed SLA targets, and report the results to customers and stakeholders, often through service reviews and SLA breach reporting.

Option C does not belong because authorizing changes to IT services is the role of Change Enablement (Change Management), not SLM. Option D does not belong because managing contracts with external suppliers is primarily the Supplier Management practice, although SLM may provide input on service targets. Option E does not belong because handling user requests and incidents is the responsibility of Incident Management and Service Request Management, not SLM.

Exam trap

The trap here is that candidates confuse Service Level Management with operational support activities (like handling incidents or managing supplier contracts) because they all involve 'service' and 'management,' but ITIL 4 explicitly separates these practices by their specific focus on performance agreements versus execution or procurement.

Practice this question →
239
MCQmedium

A change request to upgrade an application is classified as 'normal'. What is the correct sequence of activities for this type of change?

A.Request, implement, review, close
B.Plan, authorize, implement, review, close
C.Assess, authorize, implement, close
D.Request, assess, authorize, plan, implement, review
AnswerD

This sequence accurately reflects the logical and controlled flow of activities within the ITIL 4 change enablement practice. It begins with a formal "Request," followed by a thorough "Assess" phase to understand impact and risk. "Authorize" grants permission, "Plan" details the execution, "Implement" performs the change, and "Review" confirms success and captures lessons learned, ensuring a structured and effective change process.

Why this answer

ITIL 4 defines the normal change sequence as: request, assess, authorize, plan, implement, and review. This ensures that all normal changes are properly evaluated for risk and impact before authorization, then planned and implemented, followed by a review to confirm success and capture lessons learned.

Exam trap

The trap here is that candidates often confuse the normal change sequence with the simpler 'request, authorize, implement' model used for standard changes, forgetting the mandatory assessment, planning, and review steps for normal changes.

How to eliminate wrong answers

Option A is wrong because it omits the critical steps of assessment, authorization, and planning, which are mandatory for normal changes to manage risk. Option B is wrong because it starts with 'plan' instead of 'request' and omits the initial 'assess' step, which is required before authorization. Option C is wrong because it skips the 'plan' and 'review' phases, leaving no structured implementation or post-implementation evaluation.

Practice this question →
240
MCQmedium

An organization uses the ITIL continual improvement model. What is the FIRST step in this 7-step model?

A.What is the vision?
B.Take action
C.Where are we now?
D.Define the improvement strategy
AnswerA

This is the foundational first step in the ITIL Continual Improvement Model. It establishes the overall direction and purpose for any improvement initiative, clearly articulating the desired future state and the value it aims to deliver. Without a clear vision, subsequent improvement efforts lack focus and a measurable target, making it impossible to align activities or assess success effectively. This initial step ensures all stakeholders understand the ultimate goal.

Why this answer

The ITIL 4 continual improvement model is a 7-step iterative process that begins with defining the guiding vision. Step 1, 'What is the vision?', establishes the high-level business goals and strategic direction that align all subsequent improvement activities. Without a clear vision, later steps like assessing current state or defining improvement strategies lack context and purpose.

Exam trap

The trap here is that candidates often confuse 'Define the improvement strategy' (a common phrase in other frameworks) with the ITIL model's first step, or mistakenly think 'Where are we now?' is the logical starting point, but ITIL explicitly requires the vision to be set first to provide direction for the assessment.

How to eliminate wrong answers

Option B is wrong because 'Take action' is the final step (step 7) of the model, not the first. Option C is wrong because 'Where are we now?' is step 2, which assesses the current state after the vision is defined. Option D is wrong because 'Define the improvement strategy' is not a separate step in the ITIL continual improvement model; the model uses 'What is the vision?' (step 1), 'Where are we now?' (step 2), and then 'Where do we want to be?' (step 3) before defining measurable targets and plans.

Practice this question →
241
MCQmedium

An organization wants to ensure that IT services meet current and future demand. Which ITIL 4 practice is primarily responsible for this?

A.Capacity and Performance Management
B.Service Level Management
C.Availability Management
D.Monitoring and Event Management
AnswerA

Capacity and Performance Management is the ITIL practice specifically designed to ensure that services and service components can meet current and future demand in a cost-effective way. It proactively plans, monitors, and optimizes the utilization of resources, including infrastructure, applications, and people, to guarantee that services consistently achieve their agreed-upon performance targets and user experience requirements. This practice involves understanding demand patterns, forecasting future needs, and making informed decisions about scaling or optimizing resources.

Why this answer

The Capacity and Performance Management practice is specifically designed to ensure that services, service components, and infrastructure have the capacity to meet current and future demand in a cost-effective manner. It involves activities such as demand forecasting, capacity planning, performance monitoring, and tuning to align resources with business needs. This practice directly addresses the requirement to meet both current and future demand, making it the primary responsible practice.

Exam trap

ITIL4F often tests the distinction between practices that seem similar, such as Capacity and Performance Management versus Availability Management, by focusing on the specific responsibility for meeting demand, which is a key differentiator.

How to eliminate wrong answers

Option B is wrong because Service Level Management focuses on negotiating, agreeing, and monitoring service level agreements (SLAs) to ensure that services meet agreed targets, but it does not directly manage capacity or demand. Option C is wrong because Availability Management ensures that services are available when needed, meeting availability targets, but it does not primarily address capacity or demand forecasting. Option D is wrong because Monitoring and Event Management is responsible for observing services and components, recording and reporting events, and triggering actions, but it does not own the capacity planning process.

Practice this question →
242
MCQmedium

A service provider wants to ensure that the IT services meet agreed levels of performance and availability. Which practice should they use to negotiate and agree on targets with customers?

A.Service Level Management
B.Availability Management
C.Supplier Management
D.Capacity and Performance Management
AnswerA

Service Level Management is the practice responsible for setting clear, measurable targets for service performance and ensuring these are met. It involves negotiating Service Level Agreements (SLAs) with customers, continuously monitoring actual service performance against these agreed-upon levels, and reporting on achievements. This practice directly ensures that IT services consistently meet the agreed requirements and expectations of the business.

Why this answer

Service Level Management is the ITIL practice responsible for negotiating, agreeing, and documenting service level targets with customers, ensuring that IT services meet agreed performance and availability levels. This practice defines, monitors, and reports on Service Level Agreements (SLAs) that specify measurable targets such as uptime percentages and response times. Without Service Level Management, there is no formal mechanism to align customer expectations with actual service delivery.

Exam trap

The trap here is that candidates confuse the practice that sets targets (Service Level Management) with the practices that fulfill those targets (Availability Management or Capacity and Performance Management), leading them to pick a technical implementation practice instead of the negotiation and agreement practice.

How to eliminate wrong answers

Option B (Availability Management) is wrong because it focuses on ensuring that IT services are available when required, but it does not negotiate or agree on targets with customers; it works within targets set by Service Level Management. Option C (Supplier Management) is wrong because it manages relationships with external suppliers and their contracts, not the negotiation of service targets directly with internal or external customers. Option D (Capacity and Performance Management) is wrong because it ensures that current and future capacity and performance requirements are met, but it does not handle the negotiation or agreement of service level targets with customers.

Practice this question →
243
MCQeasy

What is the primary focus of the Continual Improvement practice?

A.To manage the lifecycle of IT assets
B.To align IT services with the changing needs of the business and improve them over time
C.To restore normal service operation as quickly as possible
D.To monitor and manage events in the IT infrastructure
AnswerB

This statement accurately defines the primary focus of the Continual Improvement practice. Its purpose is to align an organization's practices and services with changing business needs through ongoing identification and improvement of all elements involved in the effective management of products and services. This involves a structured approach to ensure services consistently deliver value and evolve over time.

Why this answer

The Continual Improvement practice is focused on aligning IT services with evolving business needs and systematically improving them over time. This involves identifying improvement opportunities, prioritizing them, and implementing changes to enhance service value, efficiency, and effectiveness. It is not about reactive fixes or asset lifecycle management, but about proactive, iterative enhancement.

Exam trap

The trap here is that candidates often confuse Continual Improvement with Incident Management or Event Management because all three involve changes to services, but only Continual Improvement is proactive and focused on long-term alignment with business needs, not reactive restoration or monitoring.

How to eliminate wrong answers

Option A is wrong because managing the lifecycle of IT assets is the primary focus of the IT Asset Management (ITAM) practice, not Continual Improvement. Option C is wrong because restoring normal service operation as quickly as possible is the goal of the Incident Management practice, which is reactive, not proactive improvement. Option D is wrong because monitoring and managing events in the IT infrastructure is the core of the Monitoring and Event Management practice, which focuses on detecting and responding to operational events, not on driving long-term service improvements.

Practice this question →
244
Multi-Selecthard

Which TWO of the following activities are part of the ITIL Continual Improvement Model?

Select 2 answers
A.Where are we now?
B.Define the scope
C.Allocate resources
D.How do we get there?
E.Implement the change
AnswersA, D

This activity is the second step of the ITIL Continual Improvement Model, focusing on establishing a clear understanding of the current state. It involves baselining existing services, processes, and practices to measure current performance and identify areas requiring improvement. This critical assessment provides the factual basis for setting realistic targets and tracking progress effectively throughout the improvement journey.

Why this answer

The ITIL Continual Improvement Model consists of seven steps. Option A ('Where are we now?') is step 2, which involves assessing the current state to identify gaps and opportunities. Option D ('How do we get there?') is step 4, which defines the action plan.

Both are correct because they are part of the model's sequence, even though the model starts with 'What is the vision?' (step 1).

Exam trap

The trap here is that candidates confuse the ITIL Continual Improvement Model steps with generic project management phases (like 'Define scope' or 'Allocate resources'), leading them to select options that sound plausible but are not part of the model's specific seven-step sequence. Additionally, 'Implement the change' is not a step in the model, as it belongs to other practices. The correct steps are 'Where are we now?' (step 2) and 'How do we get there?' (step 4).

Practice this question →
245
MCQmedium

A customer requests a new software installation that is listed in the service catalogue. According to ITIL 4, this should be handled as a:

A.Incident
B.Service request
C.Problem
D.Emergency change
AnswerB

A service request is a formal request from a user for something standard that is part of normal service delivery, often pre-defined and pre-approved within a service catalogue. Requesting a new software installation, especially if it's a standard offering, perfectly aligns with this definition. These requests are typically low-risk, frequently occurring, and follow a standardized process for fulfillment.

Why this answer

According to ITIL 4, a service request is a formal request from a user for something to be provided, such as a new software installation, password reset, or information. Service requests are a normal part of service delivery and are handled through the request management practice, not incident management. Since the software is already listed in the service catalogue, it is a pre-approved, standard request, making it a service request.

Exam trap

ITIL4F often tests the distinction between incidents and service requests. Candidates may incorrectly classify a routine request as an incident because it requires action, but the key is whether it is a disruption (incident) or a standard request (service request).

How to eliminate wrong answers

Option A is wrong because an incident is an unplanned interruption or reduction in service quality, not a routine request for a new service. Option C is wrong because a problem is the underlying cause of one or more incidents, not a user request for fulfillment. Option D is wrong because an emergency change is a change that must be implemented immediately to resolve a major incident or security issue; a standard software installation from the catalogue does not meet the criteria for an emergency change.

Practice this question →
246
MCQmedium

Which ITIL 4 practice ensures that services deliver the agreed level of availability to meet customer needs?

A.IT Asset Management
B.Service Level Management
C.Capacity and Performance Management
D.Availability Management
AnswerD

Availability Management ensures that services and components deliver their agreed-upon availability targets, meeting the current and future needs of the organization and its customers. This practice involves planning, designing, implementing, measuring, and improving the availability of services, components, and IT infrastructure. It focuses on maximizing service uptime, reliability, maintainability, and serviceability to ensure services are accessible whenever required by users.

Why this answer

Availability Management is the ITIL 4 practice specifically focused on ensuring that services deliver the agreed level of availability to meet customer needs. It involves defining, analyzing, planning, measuring, and improving all aspects of service availability, and ensuring that all IT infrastructure, processes, tools, roles, and techniques are appropriate for the agreed availability targets. This practice works closely with Service Level Management to negotiate and document availability requirements in SLAs, but it is Availability Management that owns the operational delivery of those availability levels.

Exam trap

ITIL4F often tests the distinction between Service Level Management (which negotiates and monitors SLAs) and Availability Management (which ensures the agreed availability is actually delivered), so candidates must remember that Availability Management is the practice that owns the operational delivery of availability targets.

How to eliminate wrong answers

Option A is wrong because IT Asset Management focuses on tracking and managing the lifecycle of IT assets (hardware, software, etc.) to maximize value and control costs, not on ensuring service availability levels. Option B is wrong because Service Level Management is responsible for negotiating, agreeing, and monitoring service levels (including availability) with customers, but it does not directly ensure that the agreed availability is delivered—that is the role of Availability Management. Option C is wrong because Capacity and Performance Management ensures that services have sufficient capacity and performance to meet demand, which is related to but distinct from availability; availability is about uptime and accessibility, not speed or throughput.

Practice this question →
247
MCQmedium

Which document defines the level of service expected between a service provider and a customer?

A.Service catalogue
B.Operational Level Agreement (OLA)
C.Service Level Agreement (SLA)
D.Underpinning Contract (UC)
AnswerC

A Service Level Agreement (SLA) is a formal, documented agreement between a service provider and a customer that precisely defines the services to be provided and the specific, measurable level of service expected. It outlines key performance indicators (KPIs), availability targets, responsibilities of both parties, and often includes remedies or penalties for non-compliance. This document directly addresses the question by establishing the mutually agreed-upon service quality and performance benchmarks.

Why this answer

A Service Level Agreement (SLA) is a formal document that defines the level of service expected between a service provider and a customer, including metrics like uptime, response times, and penalties for non-compliance. It is the primary contractual agreement for service expectations.

Exam trap

The trap is confusing SLAs with OLAs and UCs. Candidates might think any agreement defining service levels qualifies, but only SLAs are between provider and customer.

How to eliminate wrong answers

Option A is wrong because a service catalogue is a list of services offered, not a document defining service levels. Option B is wrong because an Operational Level Agreement (OLA) is an internal agreement between teams within the same organization, not between provider and customer. Option D is wrong because an Underpinning Contract (UC) is a contract with an external supplier that supports the delivery of services, but it does not directly define the service level to the customer.

Practice this question →
248
MCQmedium

Which ITIL 4 practice manages the lifecycle of all configuration items including their relationships and baselines?

A.Change Enablement
B.Service Configuration Management
C.IT Asset Management
D.Release Management
AnswerB

The Service Configuration Management practice is precisely responsible for maintaining accurate information about Configuration Items (CIs) throughout their entire lifecycle. This includes identifying, controlling, recording, reporting, and verifying CIs, their attributes, and their relationships. It ensures that the organization has a clear understanding of its service components and their interdependencies, supporting effective service delivery and change management through baselines.

Why this answer

Service Configuration Management is responsible for managing configuration items (CIs), their relationships, and configuration baselines throughout their lifecycle. Option B is correct. Option A (Change Enablement) manages changes to services and CIs but does not manage the overall CI lifecycle.

Option C (IT Asset Management) focuses on the financial and contractual aspects of assets, not the detailed configuration management. Option D (Release Management) manages the release of new or changed services, not the ongoing management of CIs.

Practice this question →
249
Multi-Selectmedium

Which TWO of the following are types of changes defined in ITIL 4?

Select 2 answers
A.Emergency change
B.Standard change
C.Problem change
D.Service request change
E.Incident change
AnswersA, B

An emergency change is a high-priority change that must be implemented as soon as possible, typically to resolve an incident or implement a security fix that has an immediate and significant impact on services. These changes bypass some standard steps of the normal change process due to their urgency, often requiring a separate, expedited authorization process to minimize service disruption. Their primary goal is to restore service operation or prevent a major business impact.

Why this answer

In ITIL 4, changes are categorized into three types: standard, emergency, and normal. Option A (Emergency change) is correct because it is a specific type of change that must be implemented as soon as possible, often to resolve an incident or security vulnerability, and follows a expedited process with authorization from the change authority. Option B (Standard change) is correct because it is a pre-authorized, low-risk change that follows a defined procedure, such as password resets or server patching, and does not require additional approval each time.

Exam trap

The trap here is that candidates confuse the change types with other ITIL practices (problem, incident, service request) and incorrectly assume that any change related to an incident or problem is a distinct type, when in fact ITIL 4 only recognizes standard, emergency, and normal changes.

Practice this question →
250
MCQmedium

According to ITIL 4, what is the difference between an SLA and an OLA?

A.SLA is for availability; OLA is for incident response
B.SLA is for services; OLA is for underpinning contracts with suppliers
C.SLA is with the customer; OLA is between internal teams
D.SLA is mandatory; OLA is optional
AnswerC

This statement accurately distinguishes between a Service Level Agreement (SLA) and an Operational Level Agreement (OLA) according to ITIL 4 principles. An SLA is a documented agreement between a service provider and a customer that specifies the service to be provided, the agreed service levels, and the responsibilities of both parties. An OLA, on the other hand, is an internal agreement between different functional units or teams within the service provider organization, outlining their commitments and responsibilities to each other to ensure the delivery of the agreed service levels to the customer.

Why this answer

SLA is between provider and customer; OLA is between internal teams to support the SLA.

Practice this question →
251
Multi-Selectmedium

Which TWO of the following are characteristics of a standard change?

Select 2 answers
A.Only used for major infrastructure upgrades
B.Require a full Change Advisory Board (CAB) meeting
C.Pre-approved with a defined procedure
D.Low risk and pre-approved
E.Implemented via an emergency process
AnswersC, D

A defining characteristic of a standard change is its pre-approval, signifying that its risk has been thoroughly assessed and accepted prior to any implementation. This pre-authorization is coupled with a clearly defined, repeatable procedure that ensures consistent execution and minimizes potential errors. Adherence to such a procedure allows for efficient, predictable, and reliable delivery of these routine changes without requiring individual authorization each time.

Why this answer

A standard change is pre-approved by the Change Authority and follows a defined, low-risk procedure. This means the change does not require a full CAB meeting each time it is implemented, as its risk profile and implementation steps are already documented and authorized.

Exam trap

The trap here is that candidates often confuse standard changes with emergency changes, thinking that 'pre-approved' means they can be used for urgent fixes, but standard changes are for low-risk, routine tasks, not for emergencies that require an emergency change process.

Practice this question →
252
MCQhard

An organization has a change that must be implemented immediately to prevent a major financial loss. According to ITIL 4, what type of change is this?

A.Service request
B.Emergency change
C.Standard change
D.Normal change
AnswerB

Emergency changes are specifically designed for changes that must be implemented as soon as possible, typically to resolve an incident or implement a critical security patch, where delaying the change would cause significant business impact or risk. They bypass some steps of the normal change process, such as full assessment and authorization, to expedite implementation, with authorization often delegated or performed retrospectively.

Why this answer

According to ITIL 4, an emergency change is a change that must be implemented as soon as possible to resolve an incident or prevent a major financial loss. This type of change bypasses the normal change advisory board (CAB) process and follows a separate, expedited procedure to minimize risk while ensuring speed.

Exam trap

The trap here is that candidates confuse 'urgent' with 'standard' or 'normal,' forgetting that ITIL 4 explicitly defines emergency changes for situations requiring immediate implementation to avoid major financial or operational impact.

How to eliminate wrong answers

Option A is wrong because a service request is a pre-defined, low-risk request from a user (e.g., password reset or access grant), not an urgent change to prevent financial loss. Option C is wrong because a standard change is a pre-approved, low-risk change that follows a documented procedure (e.g., patching a known vulnerability), not an immediate response to a critical threat. Option D is wrong because a normal change goes through the full change management lifecycle, including CAB assessment and scheduling, which is too slow for an immediate financial loss prevention scenario.

Practice this question →
253
MCQhard

A company has an agreement with a supplier to provide 99.9% availability for a cloud service. This agreement is documented in a contract that is reviewed annually. According to ITIL 4, which type of agreement is this?

A.Service Level Target (SLT)
B.Operational Level Agreement (OLA)
C.Underpinning Contract (UC)
D.Service Level Agreement (SLA)
AnswerC

An Underpinning Contract (UC) is a formal, legally binding agreement between a service provider and an *external third-party supplier*. This contract specifies the goods or services the supplier will provide, along with their agreed-upon performance levels, which are essential for the service provider to deliver its own services to customers. The question describes precisely this relationship: an agreement with a supplier to provide a specific level of service (99.9%), directly supporting the service provider's commitments.

Why this answer

An Underpinning Contract (UC) is a legally binding agreement between a service provider and an external supplier that supports the delivery of services to the customer. Since the agreement is with a supplier for a cloud service and is documented in a contract reviewed annually, it fits the ITIL 4 definition of a UC. UCs underpin SLAs by ensuring external dependencies meet required service levels.

Exam trap

ITIL4F often tests the confusion between OLAs and UCs; candidates mistakenly select OLA because both are 'underpinning' agreements, but the key differentiator is whether the other party is internal (OLA) or external (UC).

How to eliminate wrong answers

Option A is wrong because a Service Level Target (SLT) is an internal target or goal for a service level, not a formal contract with a supplier. Option B is wrong because an Operational Level Agreement (OLA) is an internal agreement between teams or departments within the same organization, not with an external supplier. Option D is wrong because a Service Level Agreement (SLA) is an agreement between a service provider and its customer, not between the provider and a supplier.

Practice this question →
254
MCQmedium

Which of the following is a key activity in the Change Enablement practice?

A.Assessing and authorizing changes
B.Restoring service after an incident
C.Conducting root cause analysis
D.Monitoring service desk performance
AnswerA

Change Enablement's primary objective is to maximize successful IT changes by ensuring they are properly evaluated, approved, and implemented with minimal risk. This involves a structured process of assessing potential impacts, benefits, and risks associated with each proposed change, followed by formal authorization to proceed. It balances the need for organizational agility with the imperative of maintaining service stability and security.

Why this answer

The Change Enablement practice (formerly Change Management) is responsible for ensuring that risks are properly assessed, authorizing changes to proceed, and managing the change schedule. Assessing and authorizing changes is a core activity within this practice, as it directly supports the practice's purpose of maximizing the number of successful service and product changes by properly assessing risk and authorizing changes to proceed. This activity is explicitly listed in the ITIL 4 Change Enablement practice as a key step in the change control process.

Exam trap

ITIL4F often tests the confusion between practices by mixing up their key activities, so candidates must remember that assessing and authorizing changes belongs to Change Enablement, while incident restoration, root cause analysis, and service desk monitoring belong to other practices.

How to eliminate wrong answers

Option B is wrong because restoring service after an incident is a key activity of the Incident Management practice, not Change Enablement. Option C is wrong because conducting root cause analysis is a key activity of the Problem Management practice, which focuses on identifying the underlying causes of incidents. Option D is wrong because monitoring service desk performance is a key activity of the Service Desk practice, which is responsible for handling user requests and communication.

Practice this question →
255
MCQeasy

Which ITIL 4 practice is responsible for negotiating and agreeing on service level targets?

A.Incident Management
B.Availability Management
C.Service Level Management
D.Supplier Management
AnswerC

Service Level Management is the practice of setting clear, business-based targets for service performance and ensuring that the delivery of services meets these agreed-upon levels. This practice is explicitly responsible for defining, documenting, negotiating, monitoring, and reporting on service level agreements (SLAs) with customers, thereby establishing the mutual understanding of service expectations and responsibilities. It acts as the primary interface for all service-related performance discussions.

Why this answer

Service Level Management (SLM) is the ITIL 4 practice specifically tasked with negotiating, agreeing, and documenting service level targets (SLTs) within Service Level Agreements (SLAs). It ensures that the agreed levels of service align with business requirements and are formally captured, reviewed, and reported upon throughout the service lifecycle.

Exam trap

The trap here is that candidates confuse 'managing availability' (Availability Management) with 'agreeing on availability targets' (Service Level Management), leading them to pick B instead of C.

How to eliminate wrong answers

Option A is wrong because Incident Management focuses on restoring normal service operation as quickly as possible after an incident, not on negotiating service level targets. Option B is wrong because Availability Management is responsible for ensuring that IT services meet agreed availability levels, but it does not negotiate or agree on those targets; it uses SLTs defined by SLM. Option D is wrong because Supplier Management manages relationships and contracts with external suppliers, but it does not negotiate service level targets for the overall IT service; those are defined by SLM.

Practice this question →
256
MCQhard

A user submits a request to install a standard software package on their workstation. According to ITIL 4, how should this be classified?

A.As a normal change, requiring assessment by the change authority
B.As a service request, to be fulfilled via the service catalogue
C.As an incident, because the user needs software to work
D.As a problem, because the user may have multiple issues
AnswerB

A service request is a formal request from a user for something that is a normal part of service delivery, such as providing information, a standard change, or access to a service. Installing a standard software pack perfectly fits this definition, as it is a pre-defined, repeatable action. These requests are typically fulfilled through established procedures, often initiated via a self-service portal or service catalogue, ensuring efficiency and consistency.

Why this answer

In ITIL 4, a request for a standard software package is classified as a service request because it is a pre-defined, standardized offering that users can request through the service catalogue. Service requests follow a standard fulfillment process with low risk and no need for individual assessment by a change authority, unlike changes which require formal evaluation.

Exam trap

The trap here is confusing a pre-approved standard change with a service request, but ITIL 4 explicitly categorizes user requests for standard services (like software installation) as service requests, not changes, because they follow a fulfillment model rather than a change control model.

How to eliminate wrong answers

Option A is wrong because a standard software package is a pre-approved, low-risk item that does not require assessment by a change authority; it is not a normal change, which would involve a new or modified service requiring formal change control. Option C is wrong because an incident is an unplanned interruption or reduction in quality of a service, not a planned request for software installation; the user is not reporting a failure. Option D is wrong because a problem is the cause of one or more incidents, not a user request for a standard service; there is no evidence of underlying issues.

Practice this question →
257
MCQmedium

An SLA defines the expected level of service between a service provider and a customer. What is an OLA?

A.A legal contract with an external customer
B.An agreement between internal teams to support the SLA
C.An agreement between the service provider and an external supplier
D.A plan for service improvement
AnswerB

This option correctly describes an Operational Level Agreement (OLA). An OLA is an internal agreement between different departments or teams within the same service provider organization, outlining their specific responsibilities and commitments required to deliver the agreed-upon service levels defined in an external Service Level Agreement (SLA). It ensures that internal support functions are aligned and capable of meeting customer expectations.

Why this answer

An OLA (Operational Level Agreement) is an internal agreement between teams within the same organization that defines how they will work together to support the SLA. It specifies the responsibilities, deliverables, and performance targets for each internal group, ensuring that the service provider can meet the SLA commitments to the customer.

Exam trap

The trap here is that candidates often confuse the OLA with an Underpinning Contract (UC), but the key distinction is that an OLA is internal to the organization, while a UC is with an external supplier.

How to eliminate wrong answers

Option A is wrong because an SLA is a legal contract with an external customer, not an OLA; an OLA is internal. Option C is wrong because an agreement between the service provider and an external supplier is called an Underpinning Contract (UC), not an OLA. Option D is wrong because a plan for service improvement is a CSI (Continual Service Improvement) plan, not an OLA.

Practice this question →
258
MCQeasy

Which practice is responsible for managing the lifecycle of all IT assets?

A.Change Enablement
B.Service Configuration Management
C.IT Asset Management
D.Deployment Management
AnswerC

IT Asset Management is the practice specifically designed to plan, monitor, and control the full lifecycle of all IT assets, both tangible and intangible. This encompasses everything from the initial acquisition and deployment, through maintenance and upgrades, to eventual retirement and disposal, ensuring value is realized, costs are optimized, and risks are mitigated. It focuses on the financial, contractual, and inventory aspects of assets to support effective service delivery and organizational objectives.

Why this answer

IT Asset Management (ITAM) is the correct practice because it is specifically responsible for managing the lifecycle of all IT assets, including financial, contractual, and inventory aspects from acquisition to disposal. This aligns with the ITIL 4 definition, which states ITAM oversees the entire lifecycle of assets to optimize value and control costs, unlike other practices that focus on changes, configurations, or deployments.

Exam trap

The trap here is that candidates confuse Service Configuration Management (which tracks CIs and their relationships) with IT Asset Management (which tracks the financial and contractual lifecycle), leading them to pick Option B because both involve inventory, but only ITAM covers the full lifecycle including cost and disposal.

How to eliminate wrong answers

Option A is wrong because Change Enablement manages the lifecycle of changes (e.g., RFCs, approvals, and risk assessment), not the lifecycle of IT assets themselves. Option B is wrong because Service Configuration Management manages configuration items (CIs) and their relationships within the CMDB, focusing on service model integrity rather than the financial or contractual lifecycle of assets. Option D is wrong because Deployment Management handles the movement of new or changed components to live environments (e.g., release packages, rollback plans), not the full asset lifecycle from procurement to retirement.

Practice this question →
259
MCQmedium

A user contacts the service desk to request a new laptop because their current one is outdated. According to ITIL 4, what type of record should be raised?

A.Problem record
B.Change request
C.Service request
D.Incident record
AnswerC

A service request is a formal request from a user for something that is a standard part of service delivery, such as requesting information, a standard change, or access to a service. Obtaining a new laptop falls squarely into this category as it is a pre-defined, pre-approved offering within the service catalog, designed for efficient and often automated fulfillment. This practice ensures consistent and timely provision of common user needs.

Why this answer

A service request is the correct record type because the user is asking for something standard and pre-approved, such as a new laptop, rather than reporting a fault or outage. In ITIL 4, service requests are a normal part of service delivery and are handled through the request management practice, not incident or problem management. The request may trigger a change later, but the initial record is a service request.

Exam trap

ITIL4F often tests the confusion between service requests and change requests, especially when fulfilling a request might involve a change; candidates must remember that the user-facing record is a service request, not a change.

How to eliminate wrong answers

Option A is wrong because a problem record is raised to investigate the root cause of one or more incidents, not to fulfill a standard user request. Option B is wrong because a change request is used when a modification to a service or infrastructure needs to be assessed, authorized, and scheduled; the user's laptop request is not itself a change, even if fulfillment might involve one. Option D is wrong because an incident record is for an unplanned interruption or degradation of a service, whereas the outdated laptop is not causing a service outage.

Practice this question →
260
MCQeasy

What is the purpose of a service level agreement (SLA)?

A.To document the internal targets for the IT department
B.To define the technical specifications of a service
C.To describe the services available in the service catalogue
D.To negotiate and agree on service level targets with the customer
AnswerD

This option is correct because a Service Level Agreement (SLA) serves as a formal, negotiated document between a service provider and a customer. Its core purpose is to clearly define, agree upon, and document the specific service level targets, responsibilities, and expectations for a particular service. This agreement ensures mutual understanding and provides a basis for measuring, monitoring, and reporting service performance from the customer's perspective.

Why this answer

The purpose of a Service Level Agreement (SLA) is to formally negotiate and document the agreed service level targets between the service provider and the customer. This ensures both parties have a clear, measurable understanding of service expectations, such as availability, response times, and resolution times, which are directly tied to business needs.

Exam trap

The trap here is that candidates confuse an SLA with internal targets (Option A) or technical specs (Option B), but ITIL 4 explicitly distinguishes SLAs as customer-facing agreements focused on outcomes, not internal operations or technical details.

How to eliminate wrong answers

Option A is wrong because an SLA is not an internal document for the IT department; internal targets are documented in an Operational Level Agreement (OLA) or a underpinning contract, not the SLA. Option B is wrong because technical specifications of a service are defined in the Service Design Package (SDP) or technical documentation, not in an SLA, which focuses on performance and outcomes rather than technical details. Option C is wrong because the service catalogue describes the available services and their details, but the SLA is a separate agreement that defines the specific targets for those services, not a description of the catalogue itself.

Practice this question →
261
MCQmedium

A monitoring tool detects that a server's CPU usage has exceeded 90% for 10 minutes. According to ITIL 4, this event is classified as which type?

A.Exception
B.Critical
C.Informational
D.Warning
AnswerD

A warning event is specifically designed to indicate that a predefined threshold has been breached, signaling a potential issue that requires attention before it escalates into a service degradation or failure. Detecting high CPU usage falls precisely into this category, as it provides an early alert, enabling proactive intervention to prevent a more severe incident. This allows operations teams to investigate and mitigate the cause before an actual service impact occurs, aligning with proactive service management principles.

Why this answer

In ITIL 4 event management, events are classified by significance: informational events are routine notifications, warnings indicate a threshold has been approached or exceeded but service is not yet critically impacted, and exceptions indicate a service has failed or breached a critical threshold. A CPU exceeding 90% for 10 minutes is a threshold breach that signals potential degradation but not yet a service failure, which maps to a warning. Critical is not a standard ITIL 4 event classification — ITIL uses informational, warning, and exception.

Exam trap

ITIL4F often tests the three event types (informational, warning, exception) and candidates frequently select 'critical' because it is a familiar severity term from incident management, even though it is not an ITIL 4 event classification.

How to eliminate wrong answers

Option A is wrong because an exception in ITIL 4 denotes a service failure or a breach of a critical threshold that requires immediate action — a 90% CPU reading is a precursor, not a failure. Option B is wrong because 'critical' is not one of the three ITIL 4 event types (informational, warning, exception); it is a priority or severity label used in incident management, not event classification. Option C is wrong because informational events are routine status notifications that require no action — a sustained 90% CPU threshold breach is actionable and therefore not merely informational.

Practice this question →
262
MCQeasy

What is the difference between an SLA and an OLA?

A.SLA covers availability, OLA covers security
B.SLA is with the customer, OLA is with another internal department
C.SLA is for services, OLA is for projects
D.SLA is internal, OLA is external
AnswerB

This statement accurately defines the core difference. A Service Level Agreement (SLA) is a formal agreement between a service provider and its customer, detailing the service to be provided and the agreed-upon service levels. In contrast, an Operational Level Agreement (OLA) is an internal agreement between different departments or teams within the same service provider organization, outlining their responsibilities to support the delivery of a service and ensure the external SLA can be met.

Why this answer

A Service Level Agreement (SLA) is a documented agreement between a service provider and a customer that defines the level of service expected, while an Operational Level Agreement (OLA) is an internal agreement between IT support teams or departments within the same organization to support the SLA. The core distinction is the external vs. internal nature of the parties involved: the SLA faces the customer, and the OLA supports the SLA through internal coordination.

Exam trap

The trap here is that candidates confuse the direction of the agreement, often thinking an SLA is internal and an OLA is external, or they mistakenly associate the terms with specific metrics like availability vs. security rather than the relationship between parties.

How to eliminate wrong answers

Option A is wrong because both SLA and OLA can cover availability and security; the difference is not about specific metrics but about the parties involved. Option C is wrong because both SLA and OLA are used for ongoing services, not projects; projects are governed by project charters or contracts, not SLAs or OLAs. Option D is wrong because it reverses the relationship: an SLA is external (with the customer), and an OLA is internal (between internal departments).

Practice this question →
263
MCQeasy

What is the purpose of the Continual Improvement practice?

A.To manage the lifecycle of all IT assets
B.To align IT services with business needs through ongoing improvements
C.To ensure services are available as agreed
D.To manage the resolution of incidents
AnswerB

This is the correct purpose of the continual improvement practice. It ensures that an organization's services and practices are continuously aligned with evolving business needs and objectives, driving ongoing value co-creation. This practice employs a structured approach, often iterative, to identify and implement improvements across all aspects of the service value system, ensuring relevance and optimal performance over time.

Why this answer

The Continual Improvement practice ensures that IT services and processes remain aligned with evolving business needs by identifying and implementing ongoing improvements. It is a core ITIL 4 practice that drives value through iterative enhancements, not a one-time fix. This practice integrates with all other practices to close the loop on service performance and business alignment.

Exam trap

The trap here is that candidates confuse Continual Improvement with a reactive fix or a single project, when ITIL 4 defines it as a proactive, ongoing practice that applies to all services and processes, not just asset or incident management.

How to eliminate wrong answers

Option A is wrong because managing the lifecycle of all IT assets is the purpose of the IT Asset Management practice, not Continual Improvement. Option C is wrong because ensuring services are available as agreed is the purpose of the Service Availability Management practice. Option D is wrong because managing the resolution of incidents is the purpose of the Incident Management practice.

Practice this question →
264
MCQhard

You are the IT service manager for a mid-sized e-commerce company. The company has been experiencing intermittent service outages affecting the checkout process during peak hours. The monitoring system shows that the application server's CPU utilization spikes to 95% during these periods. The database server appears healthy. The incident management team has been creating multiple incidents for each outage, but no permanent fix has been implemented. The problem management team has identified that the application server's auto-scaling configuration is not triggering correctly due to a misconfigured threshold. However, changing the threshold requires a change request that must be approved by the Change Advisory Board (CAB), which meets only once a week. The business is losing revenue with each outage. What should you do first to minimize the impact of the issue while a permanent solution is being developed?

A.Expedite the change request by requesting an emergency change approval from the CAB chair
B.Implement a workaround by manually scaling the application server during peak hours to handle the load
C.Conduct a root cause analysis and document the problem in the known error database
D.Increase the priority of all related incidents to ensure faster response from the service desk
AnswerB

Implementing a workaround, such as manually scaling the application server, directly addresses the immediate symptom of performance degradation and its impact on revenue. This ITIL practice focuses on restoring service functionality as quickly as possible, even if the underlying root cause is not yet resolved. It provides immediate relief, mitigating financial losses and maintaining customer satisfaction while a more permanent solution is developed through formal change management.

Why this answer

Manually scaling the application server during peak hours provides an immediate workaround to handle the load, directly reducing the impact of the misconfigured auto-scaling threshold. This aligns with ITIL's guidance on using workarounds to restore service while a permanent fix is developed. The business is losing revenue with each outage, so the priority is to stabilize the service first, not to wait for a CAB meeting or to analyze the root cause.

Exam trap

The trap here is that candidates may confuse 'first response' with 'problem management' and choose root cause analysis (Option C), but ITIL emphasizes restoring service as the immediate priority before investigating the underlying cause.

How to eliminate wrong answers

Option A is wrong because expediting an emergency change through the CAB chair still requires approval and coordination, which introduces delay; the question asks what to do 'first' to minimize impact, and a manual workaround can be implemented immediately without waiting for any approval process. Option C is wrong because conducting a root cause analysis and documenting the problem in the known error database is a problem management activity that does not directly address the ongoing outages; it is a longer-term step that should follow the immediate restoration of service. Option D is wrong because increasing the priority of incidents does not resolve the underlying capacity issue; it only triggers faster response from the service desk, but the service desk cannot fix the auto-scaling misconfiguration or manually scale the server.

Practice this question →
265
Multi-Selectmedium

Which THREE are examples of unplanned downtime that Availability Management seeks to minimize?

Select 3 answers
A.Scheduled maintenance
B.Hardware failure
C.Cyberattack causing service disruption
D.Planned upgrade of a server
E.Software bug causing service outage
AnswersB, C, E

Hardware failure, such as a disk crash, power supply malfunction, or memory error, is inherently an unplanned event that can lead to service disruption. These incidents occur without prior warning, necessitating immediate reactive measures to restore service functionality. The unpredictable nature of component breakdown makes it a prime example of unplanned downtime, directly impacting system availability without prior scheduling.

Why this answer

Availability Management aims to minimize unplanned downtime, which is any outage not scheduled or agreed in advance. Option B (Hardware failure) is correct because a sudden disk, PSU, or NIC failure is an unexpected event that directly reduces service availability and must be mitigated through redundancy, monitoring, and fast recovery. Option C (Cyberattack causing service disruption) is correct because a DDoS, ransomware, or intrusion-induced outage is unplanned and Availability Management addresses it via security controls, resilience, and incident response.

Option E (Software bug causing service outage) is correct because an unexpected defect that crashes a service or corrupts data is unplanned downtime requiring patching, testing, and rollback strategies. Options A (Scheduled maintenance) and D (Planned upgrade of a server) are not unplanned downtime; they are planned, pre-agreed activities typically handled by Change Management and excluded from the unplanned downtime that Availability Management seeks to minimize.

Exam trap

The trap is that candidates see 'maintenance' and 'upgrade' and assume any downtime counts; ITIL explicitly separates planned downtime (change management) from unplanned downtime (availability management), and the exam tests that distinction.

Practice this question →
266
MCQhard

A service desk analyst receives a call from a user who cannot access the network drive. The analyst quickly resets the user's permissions and the issue is resolved. Which ITIL 4 practice is being demonstrated?

A.Change Enablement
B.Service Request Management
C.Problem Management
D.Incident Management
AnswerD

Incident Management is the practice of minimizing the negative impact of incidents by restoring normal service operation as quickly as possible. An incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. A user unable to access a system directly fits this definition, making immediate restoration the core activity of Incident Management.

Why this answer

The analyst resolved an unplanned interruption to a service (network drive access) by restoring normal service operation as quickly as possible. This aligns with the Incident Management practice, which focuses on minimizing the negative impact of incidents by returning to normal service operation. The immediate reset of permissions is a standard incident resolution step, not a planned change or a service request.

Exam trap

The trap here is that candidates confuse a 'permission reset' with a 'service request' (Option B), but the key differentiator is that the user reported an unplanned interruption (cannot access), not a standard request for new access, making it an incident by definition.

How to eliminate wrong answers

Option A is wrong because Change Enablement manages the lifecycle of all changes to IT services, including assessment, authorization, and implementation of planned changes; resetting a user's permission is an unplanned, reactive action, not a pre-approved change. Option B is wrong because Service Request Management handles pre-defined, standardized requests from users (e.g., password resets, access requests) that follow an established, low-risk procedure; while a permission reset could be a service request, the context of a user 'cannot access' indicates an unplanned interruption, making it an incident. Option C is wrong because Problem Management aims to identify the root cause of one or more incidents and prevent recurrence; the analyst resolved the immediate issue without performing root cause analysis or implementing a permanent fix.

Practice this question →
267
MCQmedium

A service desk analyst receives a call from an executive who is unable to print from her laptop. The analyst resolves the issue by restarting the print spooler. According to ITIL 4, how should this interaction be recorded?

A.As a problem
B.As an incident
C.As a service request
D.As a change request
AnswerB

This situation should be classified as an incident because an incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. The executive's printer not working represents an unexpected disruption to their ability to perform work, directly impacting their productivity. The primary goal of incident management is to restore normal service operation as quickly as possible to minimize business impact.

Why this answer

This interaction is recorded as an incident because the executive experienced an unplanned interruption to the printing service (failure to print), which directly aligns with the ITIL 4 definition of an incident: any unplanned reduction in service quality. Restarting the print spooler is a restoration action that returns the service to normal operation, not a permanent fix or a request for something new.

Exam trap

The trap here is that candidates confuse a 'service request' with any user call for help, but ITIL 4 strictly distinguishes between a request for something new (service request) and a report of a service failure (incident), even if the fix is simple like restarting a service.

How to eliminate wrong answers

Option A is wrong because a problem is the underlying root cause of one or more incidents, not the single event of a user being unable to print; recording this as a problem would imply a formal problem management investigation, which is not warranted for a simple spooler restart. Option C is wrong because a service request is a pre-defined, standardized request from a user for something new (e.g., access, information, a new printer driver), not a restoration of an existing service that has failed. Option D is wrong because a change request is a formal proposal to alter a controlled service or component (e.g., upgrading the print server OS), not a reactive fix to restore service after a failure.

Practice this question →
268
MCQmedium

Which ITIL 4 practice involves the detection, classification, and response to events?

A.Incident Management
B.Change Enablement
C.Problem Management
D.Monitoring and Event Management
AnswerD

The Monitoring and Event Management practice systematically observes services and service components, recording and reporting selected changes of state identified as events. It is specifically designed to detect events, make sense of them through classification, and determine the appropriate control action, which directly aligns with the question's premise. This practice provides the foundation for operational awareness and proactive intervention.

Why this answer

Monitoring and Event Management practice is responsible for detecting events, classifying them (informational, warning, exception), and responding appropriately.

Practice this question →
269
MCQmedium

Which document defines the agreed level of service between an IT provider and a customer?

A.Underpinning Contract (UC)
B.Service Level Agreement (SLA)
C.Operational Level Agreement (OLA)
D.Continual Improvement Register (CIR)
AnswerB

A Service Level Agreement (SLA) is the definitive document that formally establishes the agreed level of service between a service provider and its customer. It meticulously outlines the specific services to be delivered, the expected performance targets, responsibilities of both parties, and any associated penalties or rewards. This critical agreement ensures clear expectations and provides a measurable framework for service delivery and customer satisfaction.

Why this answer

The Service Level Agreement (SLA) is the formal document that specifies the agreed level of service between an IT provider and a customer, including metrics such as availability, response times, and resolution targets. In ITIL 4, the SLA is a key output of the service level management practice, defining measurable targets that the provider commits to meet. It is distinct from other agreements because it directly represents the customer-facing promise of service quality.

Exam trap

The trap here is that candidates often confuse the SLA with the OLA or UC, mistakenly thinking any 'agreement' between parties qualifies, but ITIL strictly differentiates based on the parties involved (customer vs. internal vs. supplier).

How to eliminate wrong answers

Option A is wrong because an Underpinning Contract (UC) is an agreement between the IT provider and a third-party supplier, not directly with the customer; it supports the SLA by ensuring external vendors meet their obligations. Option C is wrong because an Operational Level Agreement (OLA) is an internal agreement between teams within the same IT provider organization, defining how they will support the SLA, not a customer-facing document. Option D is wrong because the Continual Improvement Register (CIR) is a log of improvement opportunities and actions, not a service level agreement; it is used to track improvements, not define agreed service levels.

Practice this question →
270
MCQeasy

Which ITIL 4 practice is responsible for ensuring that all IT assets are tracked and managed throughout their lifecycle?

A.Supplier Management
B.Service Configuration Management
C.Service Desk
D.IT Asset Management
AnswerD

IT Asset Management is the ITIL practice specifically responsible for planning, monitoring, and controlling the full lifecycle of all IT assets, from procurement through disposal. Its objective is to maximize value, control costs, manage risks, and support decision-making related to the acquisition, utilization, and retirement of hardware, software, and other IT infrastructure components. This holistic approach ensures assets are accounted for, optimized, and compliant throughout their entire lifespan, aligning with the question's intent.

Why this answer

IT Asset Management is the ITIL 4 practice whose explicit purpose is to plan and manage the full lifecycle of IT assets — from acquisition through disposal — ensuring they are tracked, accounted for, and their value realized. It maintains the asset inventory and financial/contractual records that underpin decisions about hardware, software, and related components. Service Configuration Management, by contrast, focuses on the relationships and configuration of CIs that deliver services, not on lifecycle tracking of the assets themselves.

Exam trap

ITIL4F often tests the overlap between Asset Management and Configuration Management, tricking candidates into choosing the configuration practice because both involve tracking items — the discriminator is lifecycle/financial tracking versus relationship/CI tracking.

How to eliminate wrong answers

Option A is wrong because Supplier Management governs relationships, performance, and contracts with external vendors — it does not track internal IT assets through their lifecycle. Option B is wrong because Service Configuration Management records and manages configuration items (CIs) and their relationships to support service delivery, not the acquisition-to-disposal lifecycle of assets. Option C is wrong because the Service Desk is the single point of contact for users to report incidents and requests; it performs no asset tracking or lifecycle management function.

Practice this question →
271
MCQmedium

A supplier is consistently failing to meet contractual targets. Which practice is responsible for managing this?

A.IT Asset Management
B.Supplier Management
C.Service Level Management
D.Change Enablement
AnswerB

The Supplier Management practice is specifically designed to ensure that an organization's suppliers and their performance are managed appropriately to support the seamless provision of quality products and services. This includes establishing and maintaining strong relationships with suppliers, negotiating and managing contracts, monitoring their adherence to agreed-upon targets, and addressing any performance shortfalls. Therefore, a supplier consistently failing to meet contractual targets falls directly under the purview of this practice.

Why this answer

Supplier Management is the ITIL 4 practice responsible for managing suppliers and their performance to ensure they meet contractual targets. When a supplier consistently fails to meet these targets, the Supplier Management practice owns the process of monitoring, reporting, and initiating corrective actions or escalations, including contract termination if necessary. This practice directly handles supplier relationships, performance reviews, and compliance with agreed service levels.

Exam trap

The trap here is confusing Service Level Management (which manages customer-facing SLAs) with Supplier Management (which manages supplier contracts and performance), leading candidates to incorrectly select Option C when the issue is with a supplier, not an internal service commitment.

How to eliminate wrong answers

Option A is wrong because IT Asset Management focuses on managing the lifecycle of IT assets (hardware, software, licenses) and does not handle supplier performance or contractual compliance. Option C is wrong because Service Level Management is responsible for defining, negotiating, and monitoring service level agreements (SLAs) with customers, not managing supplier contracts or addressing supplier failures. Option D is wrong because Change Enablement controls the lifecycle of changes to IT services and infrastructure, and has no role in managing supplier contractual performance.

Practice this question →
272
MCQeasy

Which of the following is the correct sequence for the ITIL Continual Improvement Model?

A.What is the vision? → Where do we want to be? → Where are we now? → How do we get there? → Take action → Did we get there? → How do we keep the momentum going?
B.Where are we now? → What is the vision? → Where do we want to be? → How do we get there? → Take action → Did we get there? → How do we keep the momentum going?
C.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?
D.What is the vision? → Where are we now? → How do we get there? → Where do we want to be? → Take action → Did we get there? → How do we keep the momentum going?
AnswerC

This sequence correctly represents the seven steps of the ITIL Continual Improvement Model. It logically progresses from establishing a clear vision, to assessing the current state, defining the target state, planning the necessary actions, executing those actions, verifying the achievement of objectives, and finally, sustaining the momentum for ongoing improvement. This structured approach ensures effective and continuous service improvement.

Why this answer

It follows the exact sequence prescribed by the ITIL 4 Continual Improvement Model: starting with 'What is the vision?' to align improvement with business strategy, then assessing the current state ('Where are we now?'), defining the target state ('Where do we want to be?'), planning the approach ('How do we get there?'), executing ('Take action'), verifying the outcome ('Did we get there?'), and finally embedding the change ('How do we keep the momentum going?'). This order ensures that improvement is driven by strategic intent before any analysis or action, which is a core principle of the ITIL 4 guiding concept 'Focus on value'.

Exam trap

The trap here is that candidates often confuse the ITIL Continual Improvement Model with the Deming Cycle (PDCA) or other improvement frameworks, leading them to start with 'Where are we now?' (Option B) or misorder the middle steps (Options A and D), but the ITIL 4 model explicitly mandates 'What is the vision?' as the first step to ensure strategic alignment before any assessment or planning.

How to eliminate wrong answers

Option A is wrong because it places 'Where do we want to be?' before 'Where are we now?', which violates the logical flow of first understanding the current state before defining the target state; in ITIL 4, you must assess the baseline before setting the improvement goal. Option B is wrong because it starts with 'Where are we now?' instead of 'What is the vision?', which omits the critical first step of establishing strategic alignment; without a vision, the improvement lacks direction and may not support business objectives. Option D is wrong because it swaps 'Where do we want to be?' and 'How do we get there?', placing the planning step before defining the target state; this is illogical because you cannot determine how to reach a goal without first specifying what that goal is.

Practice this question →
273
Multi-Selecthard

Which TWO of the following are differences between Incident Management and Problem Management?

Select 2 answers
A.Incident Management is triggered by events, while Problem Management is triggered by changes
B.Incident Management aims to restore service as soon as possible, while Problem Management aims to identify the root cause
C.Incident Management focuses on individual disruptions, while Problem Management looks for underlying patterns
D.Incident Management is performed by the service desk only, while Problem Management is performed by technical teams
E.Incident Management does not use workarounds, while Problem Management does
AnswersB, C

Incident Management's primary objective is to restore normal service operation as quickly as possible, minimizing the business impact of an unplanned interruption. In contrast, Problem Management focuses on identifying the root cause of incidents, often after service has been restored, to prevent recurrence and improve overall service stability and reliability.

Why this answer

Option B is correct because Incident Management is oriented toward quickly restoring normal service (often via workarounds to meet SLAs), whereas Problem Management is oriented toward finding and eliminating the root cause of one or more incidents to prevent recurrence. Option C is correct because Incident Management handles individual disruptions as discrete events, while Problem Management analyzes multiple incidents to detect underlying patterns and systemic causes. Option A is wrong because Problem Management is typically triggered by recurring or major incidents (and by proactive analysis), not by changes; changes are handled by Change Management.

Option D is wrong because Incident Management is not limited to the service desk—technical and support teams also resolve incidents—and Problem Management is not exclusively performed by technical teams. Option E is wrong because Incident Management does use workarounds to restore service quickly; in fact, workarounds are a standard incident-handling technique, while Problem Management seeks permanent fixes.

Exam trap

ITIL4F often tests the distinction between Incident and Problem Management — candidates incorrectly assume Incident Management is only service desk or that Problem Management is triggered by changes, confusing it with Change Enablement.

Practice this question →
274
Multi-Selecthard

Which THREE are key performance indicators (KPIs) for the Service Desk practice?

Select 3 answers
A.First Contact Resolution (FCR)
B.Mean Time to Resolve (MTTR)
C.Number of changes implemented
D.Percentage of SLA targets met
E.Customer Satisfaction (CSAT)
AnswersA, B, E

First Contact Resolution (FCR) is a highly valued Service Desk KPI that measures the percentage of incidents or service requests successfully resolved by the Service Desk agent during the initial interaction, without requiring further escalation or follow-up. Achieving a high FCR rate significantly enhances customer satisfaction by providing immediate solutions and also improves operational efficiency by reducing the workload from repeat contacts and subsequent escalations to other support tiers.

Why this answer

First Contact Resolution (FCR) (A) is a core Service Desk KPI because it measures the percentage of incidents or requests resolved during the initial interaction without escalation or callback, directly reflecting Service Desk efficiency and effectiveness. Mean Time to Resolve (MTTR) (B) is also a key Service Desk KPI, as it quantifies the average elapsed time from incident/request logging to resolution, indicating how quickly the desk restores service. Customer Satisfaction (CSAT) (E) is a key Service Desk KPI because it captures end-user perception of support quality, typically via post-interaction surveys, and reflects the user experience the desk delivers.

Number of changes implemented (C) is a change management metric, not a Service Desk performance indicator, and Percentage of SLA targets met (D) is a broader service-level or SLA management measure rather than a Service Desk-specific KPI.

Exam trap

ITIL4F often tests the confusion between Service Desk KPIs and other practice KPIs, such as change metrics, where candidates may incorrectly include number of changes or SLA targets as service desk KPIs.

Practice this question →
275
MCQhard

In the context of ITIL 4, which activity is part of Problem Management but NOT part of Incident Management?

A.Applying workarounds to restore service
B.Conducting root cause analysis
C.Logging and categorizing issues
D.Escalating issues to higher-level support
AnswerB

Conducting root cause analysis (RCA) is a fundamental and defining activity of Problem Management. Its purpose is to systematically investigate and identify the underlying causes of incidents, rather than just addressing their symptoms. This deep analysis aims to prevent future recurrences of incidents, distinguishing it from the immediate service restoration focus of Incident Management.

Why this answer

Root cause analysis is the defining activity of Problem Management: it seeks to identify and eliminate the underlying cause of one or more incidents. Incident Management focuses on restoring service quickly, often through workarounds, and does not own the deeper causal investigation. This makes root cause analysis the activity unique to Problem Management.

Exam trap

ITIL4F often tests the boundary between Incident and Problem Management, tricking candidates with activities like logging or escalation that occur in both — root cause analysis is the discriminator that belongs only to Problem Management.

How to eliminate wrong answers

Option A is wrong because applying workarounds to restore service is a core Incident Management activity — it is a temporary fix to get users working again, not a permanent problem resolution. Option C is wrong because logging and categorizing issues happens in both Incident and Problem Management as part of recording and classification. Option D is wrong because escalation to higher-level support occurs in Incident Management (functional or hierarchical escalation) and is not exclusive to Problem Management.

Practice this question →
276
MCQmedium

Which of the following is a difference between a standard change and a normal change?

A.Normal changes require approval from the CAB, while standard changes do not require any approval
B.Standard changes can be implemented without a change request
C.Standard changes are always low risk, while normal changes are high risk
D.Standard changes are pre-approved and follow a predefined procedure
AnswerD

This statement accurately describes standard changes in ITIL 4. Standard changes are routine, low-risk, and have a well-understood implementation process, allowing them to be pre-authorized by the change authority. This pre-approval means they do not require additional authorization each time they are implemented, as long as they strictly follow their established, predefined procedure, which ensures efficiency and consistent execution.

Why this answer

Standard changes are pre-approved and have a defined procedure; normal changes require assessment and approval by a change authority.

Practice this question →
277
MCQeasy

What type of change is pre-authorized and has a defined procedure?

A.Optional change
B.Normal change
C.Emergency change
D.Standard change
AnswerD

Standard changes are low-risk, pre-authorized changes that are well-understood and have a fully documented, repeatable procedure. These changes are typically initiated as service requests and do not require additional authorization each time they are implemented, as the risk has been assessed and approved in advance. Their predictable nature allows for efficient, routine execution without the need for a change authority's individual approval.

Why this answer

A standard change is pre-authorized by change management and follows a defined, low-risk procedure that does not require additional approval each time it is executed. This aligns with the ITIL 4 definition of a standard change as a change that is well-understood, fully documented, and can be implemented without a formal change advisory board (CAB) meeting.

Exam trap

The trap here is that candidates confuse 'pre-authorized' with 'emergency' changes, thinking emergency changes bypass approval, but in reality emergency changes still require expedited authorization, while only standard changes are truly pre-approved with a fixed procedure.

How to eliminate wrong answers

Option A is wrong because 'optional change' is not a recognized ITIL 4 change type; ITIL defines standard, normal, and emergency changes. Option B is wrong because a normal change requires assessment and approval by the change authority (e.g., CAB) before implementation, not pre-authorization. Option C is wrong because an emergency change is implemented urgently to resolve an incident or critical issue, but it still requires expedited approval (e.g., via an emergency CAB) and does not have a fully pre-authorized, routine procedure.

Practice this question →
278
Multi-Selecthard

Which TWO of the following statements about Service Desk and Incident Management are correct?

Select 2 answers
A.Incident Management may use workarounds to restore service quickly
B.The Service Desk acts as the single point of contact for incident reporting
C.Incident Management focuses on finding the root cause of incidents
D.The Service Desk is responsible for root cause analysis
E.All service requests must be logged as incidents
AnswersA, B

Incident Management's primary objective is to restore normal service operation as quickly as possible, minimizing the business impact of service disruptions. To achieve this rapid restoration, it is entirely appropriate and often necessary to implement known workarounds. These temporary solutions allow users to continue working, even if the underlying problem remains unresolved, thereby reducing downtime and meeting service level targets.

Why this answer

The Service Desk is the single point of contact for incident reporting, making Option B correct. Incident Management focuses on restoring service quickly, often using workarounds, which makes Option A correct. Option C is false because finding root cause is the goal of Problem Management, not Incident Management.

Option D is false because the Service Desk does not perform root cause analysis. Option E is false because service requests are not necessarily logged as incidents; they are handled by Service Request Management.

Practice this question →
279
MCQeasy

Which of the following is a key activity of Problem Management?

A.Identifying the root cause of incidents
B.Authorizing changes
C.Fulfilling user requests
D.Restoring service as quickly as possible
AnswerA

Problem Management's primary objective is to reduce the likelihood and impact of incidents by identifying and resolving their underlying causes. This involves performing root cause analysis (RCA) to understand *why* incidents occur, often after Incident Management has restored service. By proactively eliminating these root causes, Problem Management prevents recurrence and improves overall service stability and reliability.

Why this answer

Problem Management aims to prevent incidents from recurring by identifying and eliminating their root causes. Identifying the root cause of incidents is a core activity of Problem Management, as it enables the creation of known errors and the implementation of permanent solutions. This distinguishes it from Incident Management, which focuses on restoring service quickly.

Exam trap

The trap here is that candidates confuse the goal of Incident Management (restoring service quickly) with the goal of Problem Management (finding root causes), leading them to select Option D.

How to eliminate wrong answers

Option B is wrong because authorizing changes is a key activity of Change Enablement, not Problem Management; Change Enablement manages the lifecycle of all changes to ensure they are assessed, authorized, and implemented with minimal risk. Option C is wrong because fulfilling user requests is the responsibility of Service Request Management, which handles pre-defined, low-risk requests like password resets or access provisioning. Option D is wrong because restoring service as quickly as possible is the primary objective of Incident Management, which focuses on minimizing downtime rather than analyzing underlying causes.

Practice this question →
280
Multi-Selecthard

Which TWO of the following are key measures used for the Service Desk practice?

Select 2 answers
A.Customer Satisfaction Score (CSAT)
B.First Contact Resolution (FCR)
C.Service Uptime
D.Mean Time to Repair (MTTR)
E.Number of changes implemented
AnswersA, B

Customer Satisfaction Score (CSAT) is a direct measure of how satisfied users are with the service desk's interactions, resolutions, and overall support experience. It typically involves surveying users immediately after an interaction to gauge their perception of the service quality, responsiveness, and helpfulness of the service desk agent. A high CSAT score indicates effective communication, efficient problem-solving, and a positive user journey, making it a crucial indicator of service desk performance.

Why this answer

Customer Satisfaction Score (CSAT) (A) is a key Service Desk measure because it directly captures users' perception of the support they received, which is the primary outcome the Service Desk practice aims to manage. First Contact Resolution (FCR) (B) is also a key Service Desk measure because it reflects how effectively the desk resolves incidents or requests at the first interaction without escalation or callbacks, a core efficiency and quality indicator for the practice. Service Uptime (C) is not a Service Desk measure; it is an availability metric typically owned by service level management or infrastructure/operations teams.

Mean Time to Repair (MTTR) (D) is an incident management or technical resolution metric, not a defining Service Desk practice measure. Number of changes implemented (E) belongs to change enablement, not the Service Desk practice.

Exam trap

PeopleCert often tests the distinction between Service Desk metrics (CSAT, FCR) and broader IT operations metrics (uptime, MTTR, change counts) to see if candidates confuse practice-specific measures with general IT performance indicators.

Practice this question →
281
MCQhard

Which ITIL 4 practice is responsible for managing known errors and ensuring workarounds are documented?

A.Change Enablement
B.Incident Management
C.Problem Management
D.Service Request Management
AnswerC

Problem Management is the practice responsible for reducing the likelihood and impact of incidents by identifying and managing the causes of incidents and potential incidents. This includes the crucial 'error control' activity, where known errors are documented, their workarounds are managed, and permanent solutions are initiated. Therefore, managing known errors is a core responsibility of Problem Management.

Why this answer

Problem Management is the ITIL 4 practice responsible for managing known errors and ensuring workarounds are documented. It identifies the root causes of incidents, creates known error records in the Known Error Database (KEDB), and documents workarounds to reduce the impact of recurring issues, aligning with the ITIL 4 'Problem Management' practice definition.

Exam trap

The trap here is that candidates confuse Incident Management's focus on restoring service quickly with Problem Management's responsibility for documenting known errors and workarounds, leading them to select Incident Management instead of Problem Management.

How to eliminate wrong answers

Option A is wrong because Change Enablement manages the lifecycle of changes to IT services, not the documentation of known errors or workarounds. Option B is wrong because Incident Management focuses on restoring normal service operation as quickly as possible after an incident, not on managing known errors or documenting workarounds for root causes. Option D is wrong because Service Request Management handles pre-defined, standard user requests (e.g., password resets), not the identification and documentation of known errors or workarounds.

Practice this question →
282
MCQmedium

Which ITIL 4 practice is responsible for managing the lifecycle of all IT assets?

A.Service Configuration Management
B.Supplier Management
C.Capacity and Performance Management
D.IT Asset Management
AnswerD

The IT Asset Management practice is specifically responsible for planning, controlling, and protecting the full lifecycle of IT assets, from acquisition through disposal. This includes managing financial, contractual, and inventory aspects to maximize value, control costs, and mitigate risks associated with IT assets. It directly addresses the management of an asset's entire journey within the organization, aligning with the question's focus on "managing the lifecy" (lifecycle).

Why this answer

IT Asset Management (ITAM) is the ITIL 4 practice specifically responsible for managing the lifecycle of all IT assets, including hardware, software, and licenses, from acquisition to disposal. It ensures financial and contractual accountability, tracking assets through their entire lifecycle to optimize value and control costs.

Exam trap

The trap here is confusing Service Configuration Management with IT Asset Management, as both involve tracking items, but ITAM focuses on financial lifecycle and ownership, while Configuration Management focuses on technical service relationships.

How to eliminate wrong answers

Option A is wrong because Service Configuration Management manages configuration items (CIs) and their relationships in the CMDB, focusing on service model integrity rather than the financial lifecycle of assets. Option B is wrong because Supplier Management manages relationships with external suppliers and their performance, not the lifecycle of internal IT assets. Option C is wrong because Capacity and Performance Management ensures services and infrastructure meet current and future capacity and performance requirements, not asset lifecycle management.

Practice this question →
283
MCQhard

An organization wants to improve first-level resolution rate. Which practice should be primarily involved?

A.Monitoring and Event Management
B.Problem Management
C.Service Level Management
D.Service Desk
AnswerD

The Service Desk practice is specifically designed to be the single point of contact between the service provider and its users, aiming to restore normal service operation as quickly as possible. A core objective of an effective Service Desk is to maximize first-level resolution (FLR) or first contact resolution (FCR) by providing immediate support, access to comprehensive knowledge, and appropriate diagnostic tools. Therefore, any organizational effort to improve FLR directly involves enhancing the capabilities, processes, and resources of the Service Desk.

Why this answer

First-level resolution rate measures how many incidents are resolved at the first point of contact, which is the Service Desk's core responsibility. The Service Desk owns incident logging, initial diagnosis, and first-line resolution, so improving this metric is primarily a Service Desk practice concern.

Exam trap

ITIL4F often tests whether candidates confuse the practice that owns the metric (Service Desk) with practices that influence it indirectly (Problem Management, Service Level Management), tempting them to pick the 'root cause' practice instead of the frontline one.

How to eliminate wrong answers

Option A is wrong because Monitoring and Event Management detects and correlates events; it feeds incidents into the Service Desk but does not resolve them at first level. Option B is wrong because Problem Management addresses root causes of recurring incidents, which improves long-term resolution but not the first-contact resolution rate. Option C is wrong because Service Level Management defines and monitors SLAs/targets; it measures the metric but does not directly improve first-level resolution capability.

Practice this question →
284
MCQeasy

What is a configuration baseline?

A.A standard change that updates the CMDB
B.A policy for managing configuration data
C.A list of all configuration items in the CMDB
D.A snapshot of the configuration of a service or infrastructure at a specific point in time
AnswerD

A configuration baseline is precisely defined as a formally agreed-upon snapshot of the configuration of a service, product, or infrastructure component at a specific point in time. This snapshot captures the attributes and relationships of all relevant configuration items (CIs) as they existed at that moment. It serves as a known, good state for comparison, recovery, and auditing purposes, providing a stable reference point for future changes.

Why this answer

A configuration baseline is defined in ITIL 4 as a snapshot of the configuration of a service, product, or infrastructure at a specific point in time. This baseline serves as a reference point for future changes, audits, or recovery, ensuring that the exact state of Configuration Items (CIs) and their relationships is captured and can be compared against later states.

Exam trap

The trap here is that candidates confuse a configuration baseline with the entire CMDB inventory or a general policy, when in fact it is a specific, time-stamped snapshot used for comparison and recovery.

How to eliminate wrong answers

Option A is wrong because a configuration baseline is not a standard change; a standard change is a pre-approved, low-risk change procedure, while a baseline is a recorded state of CIs, not an update process. Option B is wrong because a policy for managing configuration data describes the configuration management policy or strategy, not the baseline itself, which is a specific recorded snapshot. Option C is wrong because a list of all configuration items in the CMDB is the entire inventory of CIs, whereas a baseline is a time-specific subset or full snapshot of that inventory, not the entire dynamic list.

Practice this question →
285
MCQhard

A change is being implemented to replace a server. The change is low risk and follows a pre-approved procedure. According to ITIL 4, what type of change is this?

A.Standard change
B.Emergency change
C.Normal change
D.Service request
AnswerA

Standard changes are pre-authorized, low-risk, and frequently implemented changes that follow a well-defined and documented procedure. A routine server replacement, if it adheres to an established playbook and has been previously approved through a change authority, perfectly fits this category. This approach streamlines common operational activities, reducing the overhead of individual assessments for each instance.

Why this answer

A standard change is a low-risk, pre-approved change that follows a documented procedure, often pre-authorized. Replacing a server with a pre-approved procedure fits this definition. Thus, it is a standard change.

Exam trap

ITIL4F often tests the distinction between standard and normal changes, and candidates may think any pre-approved change is normal, but standard changes are specifically pre-authorized.

How to eliminate wrong answers

Option B is wrong because an emergency change is for urgent, high-impact situations that require immediate action, not low-risk pre-approved changes. Option C is wrong because a normal change requires assessment and authorization through the change control process, not pre-approved. Option D is wrong because a service request is a user request for something like password reset, not a change to infrastructure.

Practice this question →
286
MCQhard

An organization is implementing a new IT service. Which practice is responsible for negotiating and agreeing on service level targets with the customer?

A.Change Enablement
B.Supplier Management
C.Service Level Management
D.Service Desk
AnswerC

Service Level Management is the dedicated practice responsible for defining, documenting, and agreeing upon service levels with customers for new and existing services. When implementing a new IT service, this practice ensures that realistic and measurable performance targets are established, negotiated, and formally agreed upon with stakeholders, forming the basis for ongoing service delivery and improvement. It bridges the gap between customer expectations and service provider capabilities.

Why this answer

Service Level Management is the ITIL practice responsible for negotiating, agreeing, and documenting service level targets with the customer, ensuring that the service provider delivers measurable performance that meets business needs. This practice defines, monitors, and reports on service level agreements (SLAs), operational level agreements (OLAs), and underpinning contracts, directly linking customer expectations to technical metrics such as availability, response time, and throughput.

Exam trap

The trap here is that candidates often confuse Service Level Management with Supplier Management, mistakenly thinking that negotiating targets with external vendors is the same as negotiating with the customer, but ITIL clearly separates these practices: Service Level Management handles customer-facing SLAs, while Supplier Management handles supplier contracts that support those SLAs.

How to eliminate wrong answers

Option A is wrong because Change Enablement manages the lifecycle of changes to IT services, including risk assessment and approval, but it does not negotiate service level targets with customers. Option B is wrong because Supplier Management oversees relationships with external suppliers and their contracts, but it does not directly negotiate service level targets with the internal customer; instead, it ensures supplier performance aligns with SLAs set by Service Level Management. Option D is wrong because the Service Desk provides a single point of contact for incidents and service requests, handling operational communication, but it is not responsible for negotiating or agreeing on service level targets.

Practice this question →
287
MCQeasy

Which practice involves the negotiation, agreement, and monitoring of service level targets?

A.Supplier Management
B.Incident Management
C.Service Desk
D.Service Level Management
AnswerD

Service Level Management negotiates, agrees, documents, and monitors service level targets with customers, ensuring delivery meets commitments. This directly satisfies the stem's requirement for the practice covering negotiation, agreement, and monitoring of service level targets.

Why this answer

Service Level Management is responsible for defining, negotiating, and monitoring SLAs to ensure service quality meets agreed levels.

Practice this question →
288
MCQmedium

A user requests a new laptop because their current one is failing frequently. The service desk analyst determines that the user is eligible for a replacement under the existing policy. What type of record should the analyst create?

A.Problem record
B.Service request
C.Incident record
D.Change request
AnswerB

A service request is a formal request from a user for something that is part of normal service delivery, such as information, advice, a standard change, or access to a service. A new laptop for a user, especially when their current one is failing, typically falls under a pre-defined, standardized procedure for asset replacement or provisioning. This aligns perfectly with the definition of a service request, which aims to fulfill user needs efficiently and predictably through established channels.

Why this answer

The user is requesting a standard, pre-approved service (a laptop replacement under an existing policy), which is a classic service request. Service requests are defined in ITIL 4 as the formal request from a user for something to be provided – such as a new device – and follow a standard, low-risk procedure. This is not an incident (a failure) or a problem (a root cause), and it does not require a change request because the replacement is already authorized by policy.

Exam trap

The trap here is that candidates confuse a 'failing laptop' with an 'incident,' but the question explicitly states the user is eligible for a replacement under an existing policy, making it a service request, not an incident record.

How to eliminate wrong answers

Option A is wrong because a problem record is used to investigate the root cause of one or more incidents, not to fulfill a user's request for a new laptop. Option C is wrong because an incident record is created to restore normal service operation after an unplanned interruption or reduction in quality, whereas here the user is proactively requesting a replacement under a policy, not reporting a current failure. Option D is wrong because a change request is needed when a modification to a controlled service or component is required that is not already pre-authorized; a standard laptop replacement under an existing policy is a pre-approved service request, not a change.

Practice this question →
289
MCQhard

An organization is designing a new service. The service owner wants to ensure that the service can be operated within agreed service levels. Which ITIL management practice should be applied to define the acceptable performance levels?

A.Service Continuity Management
B.Capacity and Performance Management
C.Service Level Management
D.Service Catalog Management
AnswerC

Service Level Management is the practice responsible for setting clear, business-focused service level targets and ensuring that the organization meets them. It involves defining, documenting, agreeing, monitoring, and reviewing service levels with customers, making it central to establishing the performance expectations for a new service during its design phase. This practice acts as the crucial interface for translating customer needs into measurable service commitments.

Why this answer

Service Level Management (SLM) is the ITIL practice responsible for negotiating, agreeing, and documenting measurable service level targets (SLTs) with customers, and then monitoring and reporting on achievement against those targets. In this scenario, defining 'acceptable performance levels' directly corresponds to establishing SLTs within a Service Level Agreement (SLA), which is the core function of SLM.

Exam trap

The trap here is confusing the practice that *defines* the targets (Service Level Management) with the practice that *ensures* the targets can be met operationally (Capacity and Performance Management), leading candidates to pick B instead of C.

How to eliminate wrong answers

Option A is wrong because Service Continuity Management focuses on ensuring the organization can continue operating during and after a disaster or major disruption, not on defining day-to-day acceptable performance levels. Option B is wrong because Capacity and Performance Management ensures that services and infrastructure can meet agreed capacity and performance demands, but it does not define what those acceptable performance levels are; it works to fulfill the targets set by Service Level Management. Option D is wrong because Service Catalog Management maintains a single source of consistent information on all live services and their details, but it does not define performance targets or acceptable service levels.

Practice this question →
290
MCQmedium

A user contacts the service desk requesting a new software license for a standard application that is listed in the service catalogue. According to ITIL 4, how should this request be classified?

A.As a service request
B.As a problem, because the user cannot access the software
C.As an incident, because it requires action from IT
D.As a change request, because a new license changes the environment
AnswerA

A service request is a formal request from a user for something standard and pre-defined, typically available through a service catalogue. Requesting a new software license falls under this category as it's a common, repeatable, and usually pre-approved fulfillment item, rather than an unexpected interruption or a complex change. The service request management practice ensures efficient and standardized handling of such user needs.

Why this answer

This request is classified as a service request because the user is asking for a new software license for a standard application already listed in the service catalogue. According to ITIL 4, a service request is a pre-defined, standardized request from a user for information, advice, access, or a service component (like a license) that does not involve a failure or a change to the live environment. The request follows an established, low-risk procedure and does not require a formal change authorization.

Exam trap

The trap here is that candidates confuse a service request with a change request because both involve a request for something new, but ITIL 4 clearly separates them based on whether the request is pre-authorized and standardized (service request) or requires formal assessment and authorization (change request).

How to eliminate wrong answers

Option B is wrong because a problem is the root cause of one or more incidents, not a request for a new license; the user is not reporting a failure or an error. Option C is wrong because an incident is an unplanned interruption or reduction in quality of an IT service, whereas this is a planned, standard request for access to a service component. Option D is wrong because a change request involves the addition, modification, or removal of an authorized, planned, or supported service or service component that could affect the live environment; a standard license request for a catalogue item is a pre-approved service request, not a change.

Practice this question →
291
Multi-Selectmedium

Which TWO of the following are typical metrics for a Service Desk?

Select 2 answers
A.Number of known errors
B.Customer Satisfaction Score (CSAT)
C.Mean Time to Repair (MTTR)
D.First Contact Resolution (FCR)
E.Percentage of changes that are emergency
AnswersB, D

CSAT directly measures users' perceived quality of each Service Desk interaction, satisfying the stem's requirement for typical Service Desk metrics. Unlike operational measures such as first-contact resolution, it captures the customer experience dimension that ITIL 4 identifies as central to service desk value, making it a standard reported indicator.

Why this answer

Customer Satisfaction Score (CSAT) (option B) is a typical Service Desk metric because it directly measures user perception of the support experience after each interaction, making it a core indicator of service quality. First Contact Resolution (FCR) (option D) is also a standard Service Desk metric, as it tracks the percentage of incidents resolved during the initial contact without escalation or callback, reflecting the desk's efficiency and effectiveness. Option A (Number of known errors) is a problem management metric, not a Service Desk performance metric.

Option C (Mean Time to Repair, MTTR) is typically associated with incident or technical resolution performance at a support tier or engineering level rather than the Service Desk itself. Option E (Percentage of changes that are emergency) is a change management metric, not a Service Desk metric.

Exam trap

The trap here is that candidates often confuse service desk metrics with incident management or change management metrics, mistakenly selecting MTTR or emergency change percentages because they seem related to service restoration or urgency.

Practice this question →
292
Multi-Selectmedium

Which TWO of the following are examples of warranty?

Select 2 answers
A.The system performs transactions within 2 seconds
B.The system is available 99.9% of the time
C.The system provides the required functionality
D.The system encrypts all data at rest
E.The system allows users to generate reports
AnswersA, B

This statement describes a performance characteristic, specifically the speed at which a core function (transaction processing) is executed. Performance, while crucial for user satisfaction, falls under the utility aspect of a service. Utility defines what the service does and whether it is fit for purpose, meaning it delivers the specific functionality required to support the customer's desired outcomes.

Why this answer

In IT service and requirements terminology, a warranty is a measurable, testable statement about how well a service or system performs its function — its non-functional, operational characteristics — rather than what it does. Option A is correct because "the system performs transactions within 2 seconds" is a quantified performance (response-time) commitment, which is a classic warranty attribute. Option B is correct because "the system is available 99.9% of the time" is a quantified availability commitment, another classic warranty attribute.

Options C, D, and E are not warranties but rather functional requirements (fitness for purpose): C describes required functionality, D describes a security function (encryption at rest), and E describes a reporting capability — each states what the system does, not how well it performs.

Exam trap

The trap here is that candidates confuse utility (what the service does) with warranty (how well it is delivered). While functional features like 'generates reports' are utility, performance metrics such as 'performs transactions within 2 seconds' are aspects of warranty, not utility.

Practice this question →
293
MCQeasy

Which practice ensures that the IT service provider has sufficient resources to meet current and future demands?

A.Service Configuration Management
B.Availability Management
C.IT Asset Management
D.Capacity and Performance Management
AnswerD

Capacity and Performance Management ensures that services and the IT infrastructure can deliver agreed-upon performance targets and meet current and future demand in a cost-effective way. This practice involves monitoring resource utilization, analyzing trends, forecasting future requirements, and planning for necessary adjustments to ensure the IT service provider always has sufficient resources to support business needs. It directly addresses the question of having enough resources to perform effectively.

Why this answer

Capacity and Performance Management is the ITIL 4 practice that ensures services meet current and future demand by optimizing resource allocation and performance. It involves forecasting demand, monitoring usage, and adjusting capacity to maintain service quality. This practice directly addresses the need for sufficient resources to handle both present and anticipated workloads.

Exam trap

ITIL4F often tests the distinction between practices that manage resources (Capacity and Performance Management) and those that manage assets or configurations, causing candidates to confuse similar-sounding practices.

How to eliminate wrong answers

Option A is wrong because Service Configuration Management focuses on maintaining accurate configuration items (CIs) and their relationships, not on resource capacity. Option B is wrong because Availability Management ensures services are available as agreed, but does not specifically handle resource sufficiency for demand. Option C is wrong because IT Asset Management tracks and manages assets throughout their lifecycle, but does not ensure capacity meets demand.

Practice this question →
294
MCQhard

An organization wants to improve its service desk's first-level resolution rate. Which approach BEST aligns with ITIL 4 guidance?

A.Create more detailed escalation procedures
B.Increase the number of service desk agents
C.Implement a shift-left strategy by training service desk staff and providing better knowledge tools
D.Increase the number of second-level support teams
AnswerC

Implementing a shift-left strategy directly addresses the goal of improving first-level resolution by empowering the service desk. Comprehensive training equips agents with a broader skill set and deeper understanding of common issues, while robust knowledge management tools provide immediate access to solutions, workarounds, and diagnostic steps. This strategic combination enables the first line to resolve a significantly higher percentage of incidents at the initial point of contact, reducing escalations and improving customer satisfaction.

Why this answer

A shift-left strategy involves moving resolution capabilities closer to the user, often by empowering first-level service desk staff with better training and knowledge tools. This aligns with ITIL 4's guidance to optimize value streams and improve efficiency by resolving issues at the first point of contact.

Exam trap

The trap is choosing options that seem to improve service desk performance but do not align with ITIL 4's shift-left principle. Candidates might think more staff or escalation procedures are the answer, but the focus is on empowerment and knowledge.

How to eliminate wrong answers

Option A is wrong because creating more detailed escalation procedures does not directly improve first-level resolution; it may even encourage escalation. Option B is wrong because simply increasing the number of agents does not address the root cause of low first-level resolution. Option D is wrong because increasing second-level support teams does not improve first-level resolution and may increase costs.

Practice this question →
295
MCQhard

A company has an SLA that guarantees 99.9% availability. The IT team measures actual availability at 99.95%. Which practice is directly responsible for monitoring and reporting this?

A.Monitoring and Event Management
B.IT Asset Management
C.Service Level Management
D.Availability Management
AnswerC

This is the core ITIL practice responsible for establishing, monitoring, and continually improving the relationship with customers regarding agreed service levels. It ensures that all services, including their guaranteed availability (e.g., 99.9%), are clearly defined, documented in Service Level Agreements (SLAs), and measured against specific targets. This practice encompasses the critical activities of negotiating SLAs, collecting and analyzing performance data from various sources, and formally reporting service performance against those agreed targets to customers.

Why this answer

Service Level Management (SLM) is the ITIL practice responsible for negotiating, agreeing, documenting, and reviewing service level targets (like 99.9% availability) and for monitoring and reporting actual performance against those targets. In this scenario, the IT team measures actual availability at 99.95%, which exceeds the SLA guarantee; SLM owns the process of comparing this measured data to the SLA, producing compliance reports, and managing stakeholder expectations. Monitoring and Event Management provides the raw data (e.g., uptime logs), but SLM is the practice that interprets and reports the SLA-specific metric.

Exam trap

The trap here is that candidates confuse the technical practice of Availability Management (which designs for uptime) with the governance practice of Service Level Management (which monitors and reports SLA compliance), leading them to pick D instead of C.

How to eliminate wrong answers

Option A is wrong because Monitoring and Event Management is responsible for collecting raw data (e.g., via SNMP traps, syslog, or synthetic probes) and generating events, but it does not own the SLA reporting or the comparison of measured availability against contractual targets. Option B is wrong because IT Asset Management focuses on tracking the lifecycle of hardware and software assets (e.g., CMDB entries, license compliance, procurement), not on monitoring or reporting service availability metrics. Option D is wrong because Availability Management is a technical practice that designs and implements measures to achieve availability targets (e.g., redundancy, failover), but the monitoring and reporting of SLA compliance is explicitly owned by Service Level Management.

Practice this question →
296
MCQmedium

A company allows employees to request new software through a pre-approved catalogue. Which type of request is this?

A.Change request
B.Incident
C.Service request
D.Problem
AnswerC

A Service Request is a formal request from a user for something that is a standard part of service delivery, typically pre-defined and often automated. These requests are usually initiated through a service catalogue and can include actions like requesting access to a system, obtaining information, or acquiring a pre-approved piece of software. It represents a normal, expected interaction between a user and the service provider, designed for efficient fulfillment.

Why this answer

A service request is a request from a user for something they need, such as new software, hardware, or access, that is part of a pre-approved catalogue. This is a standard service request, not an incident or change.

Exam trap

ITIL4F often tests the distinction between service requests (pre-approved, standard) and incidents (unplanned interruptions), causing candidates to select 'incident' for a routine request like software installation.

How to eliminate wrong answers

Option A (Change request) is wrong because a change request is for modifying an IT service, often requiring approval from change management; pre-approved catalogue items are typically service requests. Option B (Incident) is wrong because an incident is an unplanned interruption or degradation of service, not a request for new software. Option D (Problem) is wrong because a problem is the cause of one or more incidents, not a request for software.

Practice this question →
297
MCQeasy

Which of the following is the correct sequence of steps in the ITIL Continual Improvement Model?

A.What is the vision? → Where do we want to be? → Where are we now? → How do we get there? → Take action → Did we get there? → How do we keep momentum?
B.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 momentum?
C.Where are we now? → What is the vision? → How do we get there? → Take action → Did we get there? → How do we keep momentum? → Business case
D.Where are we now? → Where do we want to be? → What is the vision? → How do we get there? → Take action → Did we get there? → How do we keep momentum?
AnswerB

This option correctly represents the ITIL 7-step continual improvement model. It begins with establishing a clear vision, followed by assessing the current state to understand the starting point. Subsequently, the desired future state is defined, and a plan for achieving it is developed. The model concludes with taking action, verifying success, and sustaining the momentum for ongoing improvement, ensuring a structured and effective approach.

Why this answer

It follows the exact sequence of the ITIL Continual Improvement Model as defined in ITIL 4: starting with 'What is the vision?', then 'Where are we now?', followed by 'Where do we want to be?', 'How do we get there?', 'Take action', 'Did we get there?', and finally 'How do we keep momentum?'. This order ensures that the current state is assessed before defining the target state, which is a core principle of the model.

Exam trap

The trap here is that candidates often confuse the order of 'Where are we now?' and 'Where do we want to be?', mistakenly thinking the target state should be defined before assessing the current state, which is a common misconception tested in ITIL 4 Foundation exams.

How to eliminate wrong answers

Option A is wrong because it places 'Where do we want to be?' before 'Where are we now?', which violates the model's requirement to first understand the current state before defining the desired state. Option C is wrong because it starts with 'Where are we now?' instead of 'What is the vision?', and it incorrectly ends with 'Business case' instead of 'How do we keep momentum?', omitting the final step. Option D is wrong because it places 'Where do we want to be?' before 'What is the vision?', and also starts with 'Where are we now?' instead of the vision step, disrupting the logical flow from vision to assessment to target.

Practice this question →
298
MCQmedium

In which phase of Problem Management are known errors created and managed?

A.Incident management
B.Problem control (root cause analysis)
C.Error control
D.Problem identification
AnswerC

Error control is the specific phase of problem management where a problem, once its root cause has been identified and confirmed, is formally documented as a "known error." This phase involves creating and maintaining known error records, which detail the root cause, symptoms, and any available workarounds. Additionally, error control is responsible for initiating change requests to implement permanent solutions for these known errors, thereby preventing future incidents.

Why this answer

Known errors are created and managed during the Error Control phase of Problem Management. This phase focuses on documenting known errors in the Known Error Database (KEDB) after root cause analysis is complete, and managing them through their lifecycle until a permanent resolution (e.g., a change via RFC) is implemented. Error Control ensures that workarounds are available and that the known error is tracked for future resolution.

Exam trap

The trap here is that candidates confuse Problem Control (root cause analysis) with Error Control, mistakenly thinking known errors are created during root cause analysis rather than after it, when the cause is known and documented as a known error.

How to eliminate wrong answers

Option A is wrong because Incident Management handles restoring normal service operation as quickly as possible, not the creation or management of known errors. Option B is wrong because Problem Control (root cause analysis) identifies the underlying cause of problems but does not create or manage known errors; that occurs in the subsequent Error Control phase. Option D is wrong because Problem Identification is the initial phase where problems are detected and logged, not where known errors are created or managed.

Practice this question →
299
Multi-Selectmedium

Which TWO of the following are elements of the ITIL 4 Service Value System (SVS)?

Select 2 answers
A.Governance
B.Products and Services
C.Opportunity/Demand
D.Guiding Principles
E.Outcome
AnswersA, D

Governance is a fundamental component of the ITIL 4 Service Value System (SVS), providing the means by which an organization is directed and controlled. It ensures that the organization's activities, including its service management, are aligned with its strategic objectives and stakeholder requirements. This element establishes the framework for decision-making, accountability, and oversight across all levels of the enterprise.

Why this answer

The ITIL 4 Service Value System (SVS) is composed of five core components: Guiding Principles, Governance, the Service Value Chain, Practices, and Continual Improvement. Option A (Governance) is correct because governance is one of these five central components, directing how the organization is run and controlled within the SVS. Option D (Guiding Principles) is correct because the guiding principles are also one of the five core components, providing recommendations that guide an organization in all circumstances.

Option B (Products and Services) is incorrect because products and services are the outputs delivered to consumers, not a structural element of the SVS itself. Option C (Opportunity/Demand) is incorrect because opportunity and demand are the inputs that enter the SVS from outside, feeding into the service value chain rather than being a component of the SVS. Option E (Outcome) is incorrect because outcomes are the results of service delivery for stakeholders, not one of the SVS's constituent elements.

Exam trap

The trap here is that candidates confuse the triggers (Opportunity/Demand) or outputs (Products and Services, Outcomes) with the structural elements of the SVS, leading them to select options that are part of the value creation process but not the SVS framework itself.

Practice this question →
300
Multi-Selectmedium

Which THREE are key metrics for the Service Desk practice?

Select 3 answers
A.First Contact Resolution (FCR)
B.Average time to resolve an incident
C.Number of problems recorded
D.Customer Satisfaction Score (CSAT)
E.Mean Time Between Failures (MTBF)
AnswersA, B, D

First Contact Resolution (FCR) is a critical metric for the service desk practice, measuring the percentage of incidents or service requests successfully resolved during the initial interaction with the customer. A high FCR rate indicates efficient service delivery, reduces customer effort, and minimizes the need for follow-up contacts, thereby improving overall customer satisfaction and optimizing service desk resource allocation. It directly reflects the service desk's ability to provide immediate value and effective support.

Why this answer

First Contact Resolution (FCR) is a key Service Desk metric because it measures the percentage of user contacts resolved at the first point of contact without escalation, directly reflecting the desk's efficiency and autonomy. Average time to resolve an incident is also a core Service Desk metric, as it tracks the mean elapsed time from incident logging to resolution, indicating how quickly the desk restores service to users. Customer Satisfaction Score (CSAT) is a key Service Desk metric because it captures users' perception of the support experience, typically via post-interaction surveys, and is a primary indicator of service quality.

The number of problems recorded is not a Service Desk metric but rather a Problem Management metric, since problems are the underlying causes of incidents handled by that separate practice. Mean Time Between Failures (MTBF) is a reliability metric for components or systems, typically used in availability and capacity management, not a Service Desk performance measure.

Exam trap

ITIL4F often tests the distinction between metrics for different practices; candidates may incorrectly associate problem or availability metrics with the Service Desk.

Practice this question →
← PreviousPage 4 of 5 · 301 questions totalNext →

Ready to test yourself?

Try a timed practice session using only ITIL Management Practices questions.

Start 20-question session