Sign in
Home/ITIL/ITIL 4 Foundation/Free questions

ITIL 4 Foundation — Free Practice Questions

10 free sample questions from a bank of 347, with the correct answers and explanations. No signup required — start practising right now.

1How are target resolution times used in the 'incident management' practice?
  • They are agreed, documented, and communicated to help set user expectations
  • They are established, reviewed, and reported to ensure that customers are happy with the service
  • They are initiated, approved, and managed to ensure that predictable responses are achieved
  • They are scheduled, assessed and authorized to reduce the risk of service failures
Answer: A

The short version

A — Target times set user expectations in incident management. Agreed and communicated resolution targets tell users when to expect restoration. They are not happiness reports or failure-prevention authorizations.

Key concepts in this question

  • Incident management focus: restore normal service operation as quickly as possible after interruption.
  • Target resolution times: SLA-derived time objectives for incident resolution by priority.
  • Expectation setting: documented and communicated targets align user and support understanding.
  • Happiness-report distractor: customer-satisfaction reporting belongs to broader service review, not target use.
  • Authorization language: schedule, assess, and authorize belong to change control, not incident targets.

Why A is correct

ITIL 4 teaches that target resolution times are agreed with stakeholders, documented in SLAs, and communicated so users know the expected restoration window. That expectation-setting purpose directly supports incident handling prioritization and communication. Settled key A captures that agreed-documented-communicated definition, while the other options misplace the concept into satisfaction reporting or change authorization.

Why the others are wrong

  • B. Established-reviewed-reported for happiness describes service-level reporting outcomes, not the use of target times.
  • C. Initiated-approved-managed for predictable responses misstates the expectation-setting role with change-like wording.
  • D. Scheduled-assessed-authorized to reduce failures describes change enablement controls, not incident targets.

ITILFND-V4 exam tip

Target resolution times equal agreed plus communicated expectations for users.

2Which ITIL practice recommends performing service reviews to ensure that services continue to meet the needs of the organization?
  • Service desk
  • Service request management
  • Service level management
  • Service configuration management
Answer: C

The short version

C — Service level management owns service reviews. Reviews verify services still meet evolving needs and SLA targets. Desk, request, and config practices do not own that review accountability.

Key concepts in this question

  • Service level management: sets, monitors, and reviews service targets and service quality.
  • Service reviews: periodic joint reviews with customers on performance and improvement.
  • Service desk scope: single point of contact for incidents and requests, not service reviews.
  • Request management scope: handles predefined service requests through fulfillment workflows.
  • Config management scope: tracks configuration items and relationships, not service-needs alignment.

Why C is correct

ITIL 4 assigns service level management the duty to ensure services meet agreed needs through regular monitoring and service reviews. Performing those reviews with stakeholders confirms continued fitness and triggers improvement where gaps appear. Settled key C therefore names the practice accountable for review cadence, while desk, request, and config options describe adjacent operational scopes.

Why the others are wrong

  • A. Service desk restores and communicates, it does not own cross-service performance reviews.
  • B. Service request management fulfills standard requests rather than reviewing service fitness.
  • D. Service configuration management maintains CI accuracy rather than reviewing business-needs alignment.

ITILFND-V4 exam tip

See service reviews, answer service level management immediately.

3What is used to link activities within the service value chain?
  • Service level agreements
  • Inputs, outputs and triggers
  • Opportunity, demand and value
  • Service desk
Answer: B

The short version

B — Inputs, outputs, and triggers connect value-chain activities. SLAs govern service levels, opportunity-demand-value frames value, and the desk is a practice. Activity chaining needs I-O-T linkage.

Key concepts in this question

  • Service value chain activities: plan, improve, engage, design-transition, obtain-build, deliver-support.
  • Activity linkage: each activity consumes inputs, produces outputs, and reacts to triggers.
  • SLA role: service-level agreements set targets, they do not wire activities together.
  • Opportunity-demand-value: inputs to the system, not inter-activity connectors.
  • Practice vs chain: service desk executes work, it does not link value-chain steps.

Why B is correct

ITIL 4 models the value chain as interoperating activities where the output of one becomes the input or trigger of another. That inputs-outputs-triggers mechanism is what allows value to flow from opportunity and demand through delivery. Settled key B names the exact linking construct, while agreements, value concepts, and the desk describe different layers of the model.

Why the others are wrong

  • A. Service level agreements define targets, not the handoffs between chain activities.
  • C. Opportunity, demand, and value are system inputs and outcomes, not activity connectors.
  • D. Service desk is a management practice, not the linkage inside the value chain.

ITILFND-V4 exam tip

Linking chain activities, always answer inputs outputs and triggers.

4Which two practices use workarounds?
  • Change enablement and continual improvement
  • Change enablement and problem management
  • Problem management and incident management
  • Incident management and continual improvement
Answer: C

The short version

C — Problem and incident management both use workarounds. Incidents need rapid restoration and problems need temporary containment. Change and continual improvement do not own workaround use.

Key concepts in this question

  • Workaround definition: temporary solution that reduces impact without removing underlying cause.
  • Incident use: restore service quickly when full resolution is not yet available.
  • Problem use: contain known-error impact while root cause is investigated.
  • Change scope: controls normal changes, not temporary incident containment.
  • Improvement scope: drives systemic betterment rather than immediate workarounds.

Why C is correct

ITIL 4 explicitly notes workarounds in both incident management for fast restoration and problem management for known-error containment pending permanent fixes. Those two practices share workaround techniques and knowledge articles. Settled key C pairs exactly those practices, while change enablement and continual improvement pursue controlled change and long-term uplift rather than temporary relief.

Why the others are wrong

  • A. Change plus continual improvement omits incident, the primary workaround consumer.
  • B. Change plus problem omits incident restoration, which is a core workaround scenario.
  • D. Incident plus continual improvement omits problem containment of known errors.

ITILFND-V4 exam tip

Workaround appears twice, incident for speed plus problem for containment.

5Which is included in the purpose of the 'deliver and support' value chain activity?
  • Meeting stakeholder expectations for time to market
  • Understanding the organization's service vision
  • Understanding stakeholder needs
  • Providing services to agreed specifications
Answer: D

The short version

D — Deliver and support provides services to agreed specs. Time-to-market belongs to obtain-build, vision to plan, and needs to engage. Delivery executes to specification.

Key concepts in this question

  • Deliver and support activity: delivers services to users and supports ongoing use per agreements.
  • Agreed specifications: SLA and requirement baselines that delivery must meet.
  • Plan contrast: understanding vision and strategy sits in the plan activity.
  • Engage contrast: understanding stakeholder needs sits in engage.
  • Build contrast: time-to-market enablement sits in obtain and build.

Why D is correct

The deliver-and-support value-chain activity covers service provision, fulfilment, and support against agreed service specifications and targets. Providing services to those specifications is its stated purpose in the ITIL 4 model. Settled key D matches that purpose verbatim, while the other options quote purposes of plan, engage, and obtain-build activities.

Why the others are wrong

  • A. Meeting time-to-market expectations belongs to obtain-build responsiveness, not delivery purpose.
  • B. Understanding service vision belongs to the plan activity, not deliver and support.
  • C. Understanding stakeholder needs belongs to engage, which feeds delivery inputs.

ITILFND-V4 exam tip

Deliver and support equals provide to spec, other verbs point elsewhere.

6Which are elements of the service value system?
  • Service provision, service consumption, service relationship management
  • Governance, service value chain, practices
  • Outcomes, utility, warranty
  • Customer value, stakeholder value, organization
Answer: B

The short version

B — SVS elements are governance, chain, and practices. Provision-consumption describes service relationships, outcomes-utility-warranty describes value, and value lists describe results. System structure needs governance plus chain plus practices.

Key concepts in this question

  • Service value system: how all organizational components co-create value through services.
  • Governance: direction and control means that guide the whole system.
  • Service value chain: operating model of six activities that convert inputs to outcomes.
  • Practices: capabilities and resources for performing work across the chain.
  • Continual improvement and principles: supporting SVS pieces, but the asked trio is governance-chain-practices.

Why B is correct

ITIL 4 defines the service value system as governance plus guiding principles plus continual improvement plus the service value chain plus practices, with the exam commonly testing the governance-chain-practices subset. Settled key B names exactly that structural trio. The other options list service-relationship roles, value components, or stakeholder results rather than SVS structural elements.

Why the others are wrong

  • A. Provision, consumption, and relationship management describe service relationships, not SVS structure.
  • C. Outcomes, utility, and warranty describe service value components, not system elements.
  • D. Customer and stakeholder value describe results, not the system that creates them.

ITILFND-V4 exam tip

SVS structure, recall governance plus chain plus practices as the core.

7What is an incident?
  • The planned removal of an item that might affect a service
  • A result enabled by one or more outputs
  • A possible future event that could cause harm
  • A service interruption resolved by the use of self-help tools
Answer: D

The short version

D — Foundation calls an incident a resolvable interruption. Planned removals are changes, enabled results are outcomes, and future harm is risk. The banked phrasing centers on interruption handled via self-help.

Key concepts in this question

  • Incident essence: unplanned interruption or reduction in service quality needing restoration.
  • Self-help path: modern incidents may resolve through scripts or user tools without desk touch.
  • Change contrast: planned removal with risk control is a change, not an incident.
  • Outcome contrast: result enabled by outputs defines an outcome, not an interruption.
  • Risk contrast: possible future harm defines risk, not a realized interruption.

Why D is correct

The banked definition for this row frames an incident as a service interruption resolved by self-help tools, emphasizing restoration even through user-driven recovery. That matches the ITIL 4 incident concept of restoring normal operation after an interruption, adapted to the self-help scenario in the stem. Settled key D is therefore the retained answer for this bank index, with distractors quoting change, outcome, and risk definitions.

Why the others are wrong

  • A. Planned removal that might affect service describes a change, not an incident.
  • B. Result enabled by outputs describes an outcome in the value model.
  • C. Possible future event causing harm describes risk, not a realized interruption.

ITILFND-V4 exam tip

Interruption plus restore equals incident, even when self-help resolves it.

8What is defined as a change of state that has significance for the management of an IT service?
  • Event
  • Incident
  • Problem
  • Known error
Answer: A

The short version

A — An event is a significant state change for IT management. Incidents are interruptions, problems are causes, and known errors are assessed problems. State-change significance defines event.

Key concepts in this question

  • Event definition: change of state significant to managing a service or configuration item.
  • Monitoring role: events trigger detection, correlation, and response workflows.
  • Incident contrast: interruption needing restoration is the result, not every state change.
  • Problem contrast: underlying cause of incidents, identified after analysis.
  • Known-error contrast: problem with assessed workaround and root-cause understanding.

Why A is correct

ITIL 4 defines an event as any change of state that has significance for managing a service, from a server crossing a threshold to a license approaching expiry. That significance test is what routes the state change into monitoring and response. Settled key A states that definition directly, while incident, problem, and known error describe downstream handling stages.

Why the others are wrong

  • B. Incident is an interruption requiring restoration, narrower than any significant state change.
  • C. Problem is the cause behind one or more incidents, not the state change itself.
  • D. Known error is a problem with documented workaround, a later analysis stage.

ITILFND-V4 exam tip

Significant state change, answer event before incident or problem.

9Which dimension includes the knowledge needed for the management of services?
  • Organizations and people
  • Information and technology
  • Partners and suppliers
  • Value streams and processes
Answer: B

The short version

B — Information and technology holds service-management knowledge. People covers roles and skills, partners covers suppliers, and streams covers workflows. Data, systems, and know-how sit in information-technology.

Key concepts in this question

  • Four dimensions: organizations-people, information-technology, partners-suppliers, streams-processes.
  • Information-technology scope: data, knowledge, automation, and tech platforms needed to deliver.
  • People contrast: culture, staffing, and competencies rather than knowledge artifacts.
  • Partners contrast: external relationships and contracts rather than internal know-how.
  • Streams contrast: activity flows and procedures rather than the knowledge they consume.

Why B is correct

ITIL 4 places the knowledge needed to manage services, including information assets, data models, and supporting technologies, in the information-and-technology dimension. That dimension governs availability, quality, and security of knowledge for delivery. Settled key B therefore correctly locates service-management knowledge, while the other dimensions cover people, suppliers, and process flows.

Why the others are wrong

  • A. Organizations and people covers roles, skills, and culture, not knowledge artifacts.
  • C. Partners and suppliers covers external dependencies and contracts.
  • D. Value streams and processes covers workflows and activity sequencing.

ITILFND-V4 exam tip

Knowledge plus tech for services, choose information and technology.

10What is the PRIMARY use of a change schedule?
  • To support the 'incident management' practice and improvement planning
  • To manage emergency changes
  • To plan changes and help avoid conflicts
  • To manage standard changes
Answer: C

The short version

C — Change schedule plans changes and avoids conflicts. Incident support is secondary, emergency and standard changes are subsets. The primary use is forward planning and collision avoidance.

Key concepts in this question

  • Change schedule: calendar of planned changes with windows, impacts, and dependencies.
  • Conflict avoidance: sequencing and overlap checks prevent outages from colliding changes.
  • Emergency handling: expedited path still recorded, but not the schedule primary purpose.
  • Standard-change handling: pre-authorized low-risk flow, also reflected but not the whole use.
  • Incident linkage: schedule informs incident triage, it does not exist for incidents alone.

Why C is correct

ITIL 4 positions the change schedule as the planning view that helps coordinate changes over time and surface conflicts before implementation. Teams consult it to sequence work, reserve windows, and assess collision risk. Settled key C states that primary planning-and-avoidance use, while the other options elevate secondary incident, emergency-only, or standard-only purposes.

Why the others are wrong

  • A. Incident plus improvement support is a consumer of the schedule, not its primary use.
  • B. Managing emergency changes is one trigger path, not the overall planning purpose.
  • D. Managing standard changes is a subset flow within the broader schedule.

ITILFND-V4 exam tip

Change schedule equals plan ahead and deconflict, all else is secondary.

Want the full bank of 347 questions for ITIL 4 Foundation? See all practice exams.