Are flashcards effective for the ITIL 4 Foundation exam?

Yes. Flashcards use active recall — retrieving an answer from memory — which research shows is one of the most effective study methods, especially in short, spaced sessions. ITIL Foundation leans heavily on definitions and practice purposes, which is exactly what flashcards train.

What topics do the ITIL 4 Foundation flashcards cover?

The full syllabus: key concepts (service, value, utility, warranty, outcomes), the four dimensions, the seven guiding principles, the service value system and the six value chain activities, and the 34 management practices — including the seven examined in detail (incident, problem, change enablement, service request, service desk, service level management, continual improvement).

How should I study with these ITIL 4 Foundation flashcards?

Lead with the practices — they are 24 of the 40 marks — then the guiding principles and key concepts. Mix the modes: flip to learn, type to test recall, match for speed, and quiz to check yourself before a full practice test.

Are the ITIL 4 Foundation flashcards free?

Yes — 100% free, all four study modes, no paywall and no sign-up.

Do these flashcards match the current ITIL 4 Foundation syllabus?

Yes. The cards are organized to the current ITIL 4 Foundation candidate syllabus from PeopleCert/AXELOS, covering all seven learning outcomes in their official proportions.

What are the 7 ITIL guiding principles?

Focus on value; Start where you are; Progress iteratively with feedback; Collaborate and promote visibility; Think and work holistically; Keep it simple and practical; Optimize and automate.

What is a service in ITIL 4?

A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.

What is service management?

A set of specialized organizational capabilities for enabling value for customers in the form of services.

What is value in ITIL 4?

The perceived benefits, usefulness, and importance of something. Value is subjective, co-created, and depends on the perspective of the stakeholder.

Why is value 'co-created'?

Value is no longer delivered one-way by a provider; it emerges from an active collaboration between providers and consumers (and other stakeholders).

What is an organization?

A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.

What is a service provider?

A role an organization takes when it provides services to consumers.

What is a service consumer?

A generic role used to define the roles of customer, user, and sponsor — the organization that receives or uses services.

Customer vs user vs sponsor

Customer: defines requirements and is responsible for outcomes. User: uses the service. Sponsor: authorizes the budget for service consumption.

What is a customer (service consumer role)?

A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.

What is a sponsor (service consumer role)?

A person who authorizes the budget for service consumption.

A result for a stakeholder enabled by one or more outputs. Outcomes are what the consumer wants; outputs are the deliverables.

A tangible or intangible deliverable of an activity. Outputs help achieve outcomes but are not the outcomes themselves.

An output is a deliverable (e.g., a report). An outcome is the result the stakeholder wants enabled by that output (e.g., a faster decision).

What is cost in ITIL 4?

The amount of money spent on a specific activity or resource. Services can remove costs from a consumer or impose costs on a consumer.

A possible event that could cause harm or loss, or make it more difficult to achieve objectives. Services can remove or impose risks on a consumer.

The functionality offered by a product or service to meet a particular need — 'what the service does' (fitness for purpose).

Assurance that a product or service will meet agreed requirements — 'how the service performs' (fitness for use), covering availability, capacity, security, and continuity.

Utility = fit for purpose (what it does); warranty = fit for use (how well it performs). Both are required for a service to be valuable.

What is a service offering?

A description of one or more services designed to address the needs of a target consumer group, including goods, access to resources, and service actions.

Three components of a service offering

Goods (supplied to the consumer), access to resources (granted under agreed conditions), and service actions (performed to address consumer needs).

What is a service relationship?

A cooperation between a service provider and service consumer, including service provision, service consumption, and service relationship management.

What is service provision?

Activities performed by an organization to provide services: managing resources, providing access, fulfilling agreed actions, and managing service performance.

What is service consumption?

Activities performed by an organization to consume services: using resources, performing actions, and receiving (acquiring) goods.

What is service relationship management?

Joint activities performed by a provider and a consumer to ensure continual value co-creation based on agreed and available service offerings.

How does a service relieve costs and risks?

A provider takes on specified costs and risks on the consumer's behalf, letting the consumer focus on its desired outcomes.

Can a service impose costs and risks?

Yes. A service can also impose new costs or risks on the consumer (e.g., training, downtime), which must be weighed against the value gained.

What is a product in ITIL 4?

A configuration of an organization's resources designed to offer value for a consumer. Products are typically not consumed directly; service offerings are based on products.

What is a stakeholder?

A person or organization that has an interest in an activity, project, or organization — including customers, users, sponsors, employees, suppliers, and partners.

What are the four dimensions of service management?

Organizations and people; Information and technology; Partners and suppliers; Value streams and processes.

Why do the four dimensions matter?

All four must be considered for every service so it remains effective and balanced; ignoring a dimension can degrade or fail the service.

Dimension 1: Organizations and people

Covers structures, roles, responsibilities, culture, skills, and competencies needed to create and deliver value.

Dimension 2: Information and technology

Covers the information, knowledge, and technologies (applications, databases, AI, cloud, etc.) used to manage and deliver services.

Dimension 3: Partners and suppliers

Covers an organization's relationships with other organizations involved in designing, developing, deploying, delivering, supporting, or improving services.

Dimension 4: Value streams and processes

Covers how the various parts of the organization work together (the activities, workflows, controls, and procedures) to enable value creation.

What is a value stream?

A series of steps an organization undertakes to create and deliver products and services to a service consumer.

A set of interrelated activities that transform inputs into outputs; a process defines the sequence of actions and their dependencies.

What are the external (PESTLE) factors?

Political, Economic, Social, Technological, Legal, and Environmental factors that constrain or influence how the four dimensions are addressed.

What does PESTLE stand for?

Political, Economic, Social, Technological, Legal, Environmental — the external factors affecting service management.

What is a sourcing strategy?

An organization's approach to partners and suppliers, ranging from insourcing to outsourcing to a service integration (SIAM) model.

What is service integration and management (SIAM)?

An approach to managing multiple suppliers and integrating them to deliver a single, business-facing service.

How do the four dimensions relate to the SVS?

The four dimensions apply to the entire service value system and to every component within it; each dimension is relevant to all SVS activities.

Guiding principle: Focus on value

Everything the organization does should map, directly or indirectly, to value for stakeholders. Know who is being served and what their desired outcomes are.

Guiding principle: Start where you are

Do not start from scratch; assess and reuse what already exists (services, processes, people, tools). Measure the current state with objective data.

Your FREE ITIL 4 Foundation Flashcards 2026 – 250+ Cards

Realistic, ITIL 4 Foundation exam-style flashcards across the whole syllabus — flip, match, type, and quiz yourself.

Master cards to boost your scoreMaster cards to raise your exam readiness score

How well do you know them?

ITIL 4 Foundation Flashcards

What are the 7 ITIL guiding principles?: Focus on value; Start where you are; Progress iteratively with feedback; Collaborate and promote visibility; Think and work holistically; Keep it simple and practical; Optimize and automate.
What is a service in ITIL 4?: A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
What is service management?: A set of specialized organizational capabilities for enabling value for customers in the form of services.
What is value in ITIL 4?: The perceived benefits, usefulness, and importance of something. Value is subjective, co-created, and depends on the perspective of the stakeholder.
Why is value 'co-created'?: Value is no longer delivered one-way by a provider; it emerges from an active collaboration between providers and consumers (and other stakeholders).
What is an organization?: A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.
What is a service provider?: A role an organization takes when it provides services to consumers.
What is a service consumer?: A generic role used to define the roles of customer, user, and sponsor — the organization that receives or uses services.
Customer vs user vs sponsor: Customer: defines requirements and is responsible for outcomes. User: uses the service. Sponsor: authorizes the budget for service consumption.
What is a customer (service consumer role)?: A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
What is a user (service consumer role)?: A person who uses services.
What is a sponsor (service consumer role)?: A person who authorizes the budget for service consumption.
What is an outcome?: A result for a stakeholder enabled by one or more outputs. Outcomes are what the consumer wants; outputs are the deliverables.
What is an output?: A tangible or intangible deliverable of an activity. Outputs help achieve outcomes but are not the outcomes themselves.
Output vs outcome: An output is a deliverable (e.g., a report). An outcome is the result the stakeholder wants enabled by that output (e.g., a faster decision).
What is cost in ITIL 4?: The amount of money spent on a specific activity or resource. Services can remove costs from a consumer or impose costs on a consumer.
What is a risk?: A possible event that could cause harm or loss, or make it more difficult to achieve objectives. Services can remove or impose risks on a consumer.
What is utility?: The functionality offered by a product or service to meet a particular need — 'what the service does' (fitness for purpose).
What is warranty?: Assurance that a product or service will meet agreed requirements — 'how the service performs' (fitness for use), covering availability, capacity, security, and continuity.
Utility vs warranty: Utility = fit for purpose (what it does); warranty = fit for use (how well it performs). Both are required for a service to be valuable.
What is a service offering?: A description of one or more services designed to address the needs of a target consumer group, including goods, access to resources, and service actions.
Three components of a service offering: Goods (supplied to the consumer), access to resources (granted under agreed conditions), and service actions (performed to address consumer needs).
What is a service relationship?: A cooperation between a service provider and service consumer, including service provision, service consumption, and service relationship management.
What is service provision?: Activities performed by an organization to provide services: managing resources, providing access, fulfilling agreed actions, and managing service performance.
What is service consumption?: Activities performed by an organization to consume services: using resources, performing actions, and receiving (acquiring) goods.
What is service relationship management?: Joint activities performed by a provider and a consumer to ensure continual value co-creation based on agreed and available service offerings.
How does a service relieve costs and risks?: A provider takes on specified costs and risks on the consumer's behalf, letting the consumer focus on its desired outcomes.
Can a service impose costs and risks?: Yes. A service can also impose new costs or risks on the consumer (e.g., training, downtime), which must be weighed against the value gained.
What is a product in ITIL 4?: A configuration of an organization's resources designed to offer value for a consumer. Products are typically not consumed directly; service offerings are based on products.
What is a stakeholder?: A person or organization that has an interest in an activity, project, or organization — including customers, users, sponsors, employees, suppliers, and partners.
What are the four dimensions of service management?: Organizations and people; Information and technology; Partners and suppliers; Value streams and processes.
Why do the four dimensions matter?: All four must be considered for every service so it remains effective and balanced; ignoring a dimension can degrade or fail the service.
Dimension 1: Organizations and people: Covers structures, roles, responsibilities, culture, skills, and competencies needed to create and deliver value.
Dimension 2: Information and technology: Covers the information, knowledge, and technologies (applications, databases, AI, cloud, etc.) used to manage and deliver services.
Dimension 3: Partners and suppliers: Covers an organization's relationships with other organizations involved in designing, developing, deploying, delivering, supporting, or improving services.
Dimension 4: Value streams and processes: Covers how the various parts of the organization work together (the activities, workflows, controls, and procedures) to enable value creation.
What is a value stream?: A series of steps an organization undertakes to create and deliver products and services to a service consumer.
What is a process?: A set of interrelated activities that transform inputs into outputs; a process defines the sequence of actions and their dependencies.
What are the external (PESTLE) factors?: Political, Economic, Social, Technological, Legal, and Environmental factors that constrain or influence how the four dimensions are addressed.
What does PESTLE stand for?: Political, Economic, Social, Technological, Legal, Environmental — the external factors affecting service management.
What is a sourcing strategy?: An organization's approach to partners and suppliers, ranging from insourcing to outsourcing to a service integration (SIAM) model.
What is service integration and management (SIAM)?: An approach to managing multiple suppliers and integrating them to deliver a single, business-facing service.
How do the four dimensions relate to the SVS?: The four dimensions apply to the entire service value system and to every component within it; each dimension is relevant to all SVS activities.
Guiding principle: Focus on value: Everything the organization does should map, directly or indirectly, to value for stakeholders. Know who is being served and what their desired outcomes are.
Guiding principle: Start where you are: Do not start from scratch; assess and reuse what already exists (services, processes, people, tools). Measure the current state with objective data.
Guiding principle: Progress iteratively with feedback: Organize work into smaller, manageable sections that can be executed and completed in a timely manner; use feedback before, during, and after each iteration.
Guiding principle: Collaborate and promote visibility: Working together across boundaries produces better buy-in, relevance, and success. Making work visible reduces the cost of poor information and builds trust.
Guiding principle: Think and work holistically: No service, practice, process, or component stands alone. Take an integrated, end-to-end view; outcomes suffer when parts are managed in isolation.
Guiding principle: Keep it simple and practical: Use the minimum number of steps needed to accomplish an objective. Eliminate anything that does not add value; design for outcomes.
Guiding principle: Optimize and automate: Optimize work before automating it; do not automate a flawed process. Use technology to do what it can, freeing people for complex decision-making.
What is a guiding principle?: A recommendation that guides an organization in all circumstances, regardless of changes in goals, strategies, type of work, or management structure.
Are the guiding principles universal?: Yes — they are universal and enduring. They apply to virtually any initiative and to all relationships with stakeholders.
Which principle says don't reinvent the wheel?: Start where you are — assess and reuse existing services, processes, and tools rather than building from scratch.
Which principle covers active feedback loops?: Progress iteratively with feedback — small iterations with feedback before, during, and after each step.
Which principle warns against premature automation?: Optimize and automate — optimize the process first; automating an inefficient process just makes it fail faster.
Which principle stresses end-to-end thinking?: Think and work holistically — services and their parts work together as a system, not in silos.
Which principle reduces wasteful steps?: Keep it simple and practical — use the fewest steps necessary and remove anything that does not contribute to value.
How do principles relate in practice?: Organizations should not use just one or two; consider the relevance of each principle and how they apply together to a given situation.
What is the Service Value System (SVS)?: A model showing how all the components and activities of an organization work together to facilitate value creation through IT-enabled services.
What are the components of the SVS?: Guiding principles, governance, the service value chain, practices, and continual improvement.
What are the inputs and outputs of the SVS?: Input: opportunity and demand. Output: value. The SVS converts demand and opportunity into value.
What is opportunity vs demand?: Opportunity represents options to add value for stakeholders or improve the organization; demand is the need or desire for products and services.
What is governance in the SVS?: The means by which an organization is directed and controlled — evaluating, directing, and monitoring activities and performance.
What is continual improvement (in the SVS)?: A recurring organizational activity performed at all levels to ensure performance continually meets stakeholder expectations; it surrounds the whole SVS.
What is the service value chain (SVC)?: An operating model within the SVS — a set of six interconnected activities an organization performs to create value through products and services.
What are the six service value chain activities?: Plan; Improve; Engage; Design and transition; Obtain/build; Deliver and support.
SVC activity: Plan: Ensures a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services.
SVC activity: Improve: Ensures continual improvement of products, services, and practices across all value-chain activities and the four dimensions.
SVC activity: Engage: Provides a good understanding of stakeholder needs, transparency, and continual engagement with all stakeholders.
SVC activity: Design and transition: Ensures products and services continually meet stakeholder expectations for quality, costs, and time to market.
SVC activity: Obtain/build: Ensures service components are available when and where they are needed and meet agreed specifications.
SVC activity: Deliver and support: Ensures services are delivered and supported according to agreed specifications and stakeholders' expectations.
Are the value chain activities a fixed sequence?: No. The six activities combine in many different sequences to form value streams; their order depends on the work being done.
What is a value stream (in the SVC)?: A specific combination of value-chain activities and practices designed for a particular scenario, converting demand into value.
How do practices relate to the value chain?: Each value-chain activity draws on a different combination of the 34 ITIL practices to perform its work; practices are sets of resources for doing work.
What is an ITIL practice?: A set of organizational resources designed for performing work or accomplishing an objective. ITIL 4 defines 34 management practices.
What is the four-dimensions relationship to the SVC?: The four dimensions are relevant to and apply across all six service value chain activities.
How is the SVS resilient to disruption?: Its flexible structure (principles, governance, value chain, practices, improvement) lets organizations respond to changing demand and opportunities in many ways.
How many ITIL 4 management practices are there?: 34 practices, grouped into three categories: general management (14), service management (17), and technical management (3).
What are the three practice categories?: General management practices (14), service management practices (17), and technical management practices (3).
What is continual improvement (practice)?: Aligns the organization's practices and services with changing business needs through ongoing improvement of products, services, and practices. One of the 7 deep-dive practices.
What is the continual improvement model?: A 7-step approach: 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?
What is the continual improvement register (CIR)?: A database or structured document used to track and manage improvement ideas from identification through to action.
Who is responsible for continual improvement?: Everyone. Continual improvement is everyone's responsibility, though a dedicated team may coordinate and embed it.
What is information security management?: Protects the information needed by the organization to conduct its business — confidentiality, integrity, and availability (CIA), plus authentication and non-repudiation.
What is relationship management?: Establishes and nurtures links between the organization and its stakeholders at strategic and tactical levels.
What is supplier management?: Ensures the organization's suppliers and their performance are managed appropriately to support seamless, quality products and services.
What is the purpose of supplier management?: To get value for money from suppliers, create closer relationships, and manage risk through the supplier lifecycle (evaluation, contracting, performance, renewal).
What is service financial management?: Supports decision-making by ensuring the organization's financial resources and investments are used effectively (budgeting, accounting, charging).
What is workforce and talent management?: Ensures the organization has the right people with the right skills and knowledge, in the right roles, to support its objectives.
What is the general management practice of architecture management?: Provides an understanding of all the different elements that make up an organization and how they interrelate (business, service, information, technology, environment architectures).
What is project management (practice)?: Ensures that all of an organization's projects are successfully delivered, balancing scope, schedule, cost, quality, resources, and risk.
What is risk management (practice)?: Ensures the organization understands and effectively handles risk; risk is essential to but must be balanced against value.
What is portfolio management (practice)?: Ensures the organization has the right mix of programs, projects, products, and services to execute its strategy within funding and resource constraints.
What is knowledge management (practice)?: Maintains and improves the effective, efficient, and convenient use of information and knowledge across the organization.
What is measurement and reporting (practice)?: Supports good decision-making and continual improvement by decreasing uncertainty through the collection of relevant data and its assessment.
What is organizational change management (practice)?: Ensures that changes in an organization are smoothly and successfully implemented, and that lasting benefits are achieved by managing the human aspects of change.
What is strategy management (practice)?: Formulates the goals of an organization and adopts the courses of action and allocation of resources necessary to achieve them.
What is service desk vs information security?: Service desk is a service management practice (capturing demand for incidents/requests); information security is a general management practice (protecting information).
What is the service desk practice?: Captures demand for incident resolution and service requests; it is the single, central point of contact between the provider and its users. One of the 7 deep-dive practices.
What is the value of the service desk?: Provides a clear path for users to report issues, ask questions, and make requests; it has a major impact on user experience and satisfaction.
Does the service desk need deep technical skill?: Increasingly, no — it needs strong empathy, communication, and incident-triage skills; the practical/emotional intelligence matters as much as technical knowledge.
What is incident management?: Minimizes the negative impact of incidents by restoring normal service operation as quickly as possible. One of the 7 deep-dive practices.
What is an incident?: An unplanned interruption to a service, or reduction in the quality of a service.
How are incidents prioritized?: By impact and urgency, often using a priority matrix; the highest-impact, most-urgent incidents are resolved first, frequently via target resolution times.
What is a major incident?: An incident with significant business impact requiring a coordinated, often separate, resolution procedure and faster timescales.
What is problem management?: Reduces the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. One of the 7 deep-dive practices.
What is a problem?: A cause, or potential cause, of one or more incidents.
What is a known error?: A problem that has been analyzed but not resolved. Documenting known errors and workarounds speeds future incident resolution.
What is a workaround?: A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available.
Three phases of problem management: Problem identification, problem control (analysis, documenting known errors/workarounds), and error control (managing known errors and possible permanent fixes).
Incident vs problem: An incident is the interruption itself; a problem is the underlying cause of one or more incidents.
What is service request management?: Supports the agreed quality of a service by handling all predefined, user-initiated service requests effectively and user-friendly. One of the 7 deep-dive practices.
What is a service request?: A request from a user (or their authorized representative) that initiates a service action which has been agreed as a normal part of service delivery.
Service request vs incident: A service request is a normal, predefined, planned part of service delivery; an incident is an unplanned interruption or quality reduction.
Why standardize and automate service requests?: Requests are predefined and repeatable, so they should be standardized and automated to the greatest degree possible for speed and consistency.
What is change enablement?: Maximizes the number of successful service and product changes by ensuring risks are properly assessed, changes are authorized, and the schedule is managed. One of the 7 deep-dive practices.
What is a change in ITIL 4?: The addition, modification, or removal of anything that could have a direct or indirect effect on services.
What are the three types of change?: Standard changes (low-risk, pre-authorized), normal changes (assessed/authorized via a change schedule), and emergency changes (must be implemented as soon as possible).
What is a standard change?: A low-risk, pre-authorized change that is well understood and fully documented and can be implemented without additional authorization.
What is a normal change?: A change that must be scheduled, assessed, and authorized following a standard process; ranges from minor to major.
What is an emergency change?: A change that must be implemented as soon as possible (e.g., to resolve an incident or apply a security patch); assessment may be expedited.
What is the change authority?: The person or group that authorizes a change. ITIL 4 de-emphasizes a single change advisory board (CAB) in favor of appropriate, often decentralized, change authorities.
What is service level management (SLM)?: Sets clear, business-based targets for service performance so that delivery can be properly assessed, monitored, and managed against them. One of the 7 deep-dive practices.
What is a service level agreement (SLA)?: A documented agreement between a service provider and a customer that identifies both the services required and the expected level of service.
What makes a good SLA?: It relates to a defined service, reflects an agreement (engagement and discussion), is simply written and easy to understand, and uses outcome-based metrics.
What is the 'watermelon SLA' effect?: When SLA metrics look green on the outside but the customer experience is red inside — a sign metrics don't reflect real outcomes.
What is service catalogue management?: Provides a single source of consistent information on all services and service offerings, available to the relevant audience.
What is service configuration management?: Ensures accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where needed.
What is a configuration item (CI)?: Any component that needs to be managed in order to deliver an IT service.
What is a configuration management database (CMDB)?: A database used to store configuration records (CIs) and their relationships throughout their lifecycle.
What is the service request fulfilment value?: Effective handling of predefined requests improves user satisfaction and frees specialized resources to focus on complex incidents and problems.
What is availability management?: Ensures that services deliver agreed levels of availability to meet the needs of customers and users.
What is capacity and performance management?: Ensures that services achieve agreed and expected performance, cost-effectively satisfying current and future demand.
What is service continuity management?: Ensures that the availability and performance of a service are maintained at a sufficient level in case of a disaster (business continuity / disaster recovery).
What is monitoring and event management?: Systematically observes services and CIs, records and reports selected changes of state (events), and identifies and prioritizes those that require action.
What is an event?: Any change of state that has significance for the management of a service or other configuration item.
What is release management?: Makes new and changed services and features available for use. A release can be planned, scheduled, and controlled.
What is a release?: A version of a service or other configuration item, or a collection of configuration items, that is made available for use.
What is service validation and testing?: Ensures that new or changed products and services meet defined requirements for both utility and warranty.
What is service design (practice)?: Designs products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.
What is business analysis (practice)?: Analyzes a business or some element of it, defines its needs, and recommends solutions that deliver value to stakeholders.
Which practices are the 7 deep-dive (Foundation) practices?: Continual improvement, Change enablement, Incident management, Problem management, Service request management, Service desk, and Service level management.
Release vs deployment: Release management makes features available for use; deployment management moves new/changed components into live (or other) environments.
What are the 3 technical management practices?: Deployment management; Infrastructure and platform management; Software development and management.
What is deployment management?: Moves new or changed hardware, software, documentation, processes, or any other component to live (or other) environments.
What are common deployment approaches?: Phased deployment, continuous delivery, big bang deployment, and pull deployment — chosen based on risk, speed, and environment.
What is infrastructure and platform management?: Oversees the infrastructure and platforms used by an organization, enabling the monitoring of technology solutions including cloud.
What is software development and management?: Ensures applications meet stakeholder needs in terms of functionality, reliability, maintainability, compliance, and auditability.
Deployment vs release management: Deployment management moves components into an environment; release management controls when functionality is made available to users. They often work together.
How does deployment relate to change enablement?: Deployments are usually authorized through change enablement; deployment management performs the technical move once the change is approved.
Why separate deployment from release?: It lets organizations deploy code to production without exposing the feature to users (e.g., feature flags), supporting modern continuous-delivery practices.
What is value co-creation?: The idea that value is not delivered one-directionally but emerges through the active collaboration of providers, consumers, and other stakeholders in a service relationship.
What is an IT asset?: Any financially valuable component that can contribute to the delivery of an IT product or service. (One of the 7 syllabus key terms.)
What is a configuration item (CI)? (key term): Any component that needs to be managed in order to deliver an IT service. (One of the 7 syllabus key terms.)
What is a change? (key term): The addition, modification, or removal of anything that could have a direct or indirect effect on services. (One of the 7 syllabus key terms.)
What is an incident? (key term): An unplanned interruption to a service, or a reduction in the quality of a service. (One of the 7 syllabus key terms.)
What is a problem? (key term): A cause, or potential cause, of one or more incidents. (One of the 7 syllabus key terms.)
What is a known error? (key term): A problem that has been analyzed but has not been resolved. (One of the 7 syllabus key terms.)
What is an event? (key term): Any change of state that has significance for the management of a service or other configuration item. (One of the 7 syllabus key terms.)
Two types of cost in a service: Costs removed from the consumer by the service (part of the value), and costs imposed on the consumer by the service (a trade-off against the value).
Two types of risk in a service: Risks removed from the consumer by the service (part of the value), and risks imposed on the consumer by the service.
Is value objective or subjective?: Subjective — value depends on the perception and desired outcomes of the stakeholder, so the same output can represent different value to different consumers.
How do utility and warranty combine?: A service is only valuable (fit for use) when it has BOTH adequate utility (it does what's needed) AND adequate warranty (it performs reliably enough).
What is a service action?: An action performed by a provider to address a consumer's need, performed according to an agreement with the consumer (part of a service offering).
Access to resources (service offering component): Granting a consumer agreed access to resources such as networks, storage, or computing power under defined terms and conditions.
Goods (service offering component): Items supplied to the consumer where ownership is transferred and the consumer takes responsibility for their future use.
Why does ITIL use a generic 'consumer' role?: Because a single person or organization can be customer, user, and sponsor at once, or these can be different parties — the generic role keeps the model flexible.
What can happen if a dimension is ignored?: Service delivery becomes unbalanced and may fail — e.g., great technology with no skilled people, or a good process with an unmanaged supplier.
Which dimension covers organizational culture?: Organizations and people — it includes structures, roles, responsibilities, leadership, and the culture and competencies of staff.
Which dimension covers data, knowledge, and tech?: Information and technology — the information and knowledge needed, plus the technologies (and their relationships) used to deliver and manage services.
Which dimension covers contracts and the supply chain?: Partners and suppliers — relationships with other organizations involved in designing, deploying, delivering, supporting, or improving services.
Which dimension covers workflows and activities?: Value streams and processes — how the parts of the organization work together in a coordinated way to enable value through products and services.
Can the four dimensions overlap?: Yes — they are interconnected and overlapping; each must be considered together for any service, alongside the external PESTLE factors.
How many guiding principles are there?: Seven — focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, and optimize and automate.
Which principle anchors everything else?: Focus on value — every activity should map, directly or indirectly, to value for a stakeholder.
What is the recommended optimize-then-automate order?: First understand and agree the context and objectives, then optimize the work (make it effective and useful), and only then automate — never automate a poor process.
What does 'collaborate and promote visibility' improve?: Buy-in, relevance to objectives, and the likelihood of long-term success; reducing hidden work lowers the cost of poor information and improves trust.
Why progress iteratively rather than all at once?: Smaller iterations are easier to manage, deliver value sooner, allow feedback to keep work relevant, and reduce the risk of large-scale failure.
What should you do before discarding existing assets?: Start where you are — observe and measure the current state directly, because much of what already exists can often be reused and built upon.
What surrounds and applies to the whole SVS?: The guiding principles and continual improvement apply across the entire service value system and every component within it.
What converts demand into value?: The service value chain — the central operating model of the SVS — using practices and the guiding principles, under governance.
What is the purpose of governance in the SVS?: To evaluate, direct, and monitor the organization's activities, ensuring they align with policies, objectives, and stakeholder needs.
Where do practices fit in the SVS?: Practices are SVS components — sets of resources that the service value chain activities draw on to perform work.
Are value chain activities done in a fixed order?: No. The six activities are flexible and combine in different sequences to form value streams suited to particular scenarios.
What is a value stream made of?: A specific sequence of service value chain activities and the practices they use, designed to convert demand or opportunity into value.
Which value chain activity handles stakeholder relationships?: Engage — it ensures understanding of stakeholder needs, transparency, and continual relationships with all stakeholders.
Which value chain activity makes components available?: Obtain/build — it ensures service components are available where and when needed and meet agreed specifications.
Which value chain activity runs and supports live services?: Deliver and support — it ensures services are delivered and supported to agreed specifications and stakeholder expectations.
What are the steps of the continual improvement model?: (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?
What does the CIA triad stand for?: Confidentiality, Integrity, Availability — the core objectives of information security management (often extended with authentication and non-repudiation).
Purpose of information security management: To protect the information the organization needs to conduct its business — its confidentiality, integrity, and availability.
Purpose of relationship management: To establish and nurture the links between the organization and its stakeholders at strategic and tactical levels.
Purpose of supplier management: To ensure suppliers and their performance are managed appropriately to support the seamless provision of quality products and services.
Which general practices are in LO6's 15?: Information security management, relationship management, and supplier management (the three general management practices examined at purpose level on Foundation).
Why is continual improvement everyone's job?: Because improvement opportunities arise everywhere; a small central team coordinates and embeds the practice, but all staff are expected to contribute.
What is the difference between a practice and a process?: A practice is a set of organizational resources (people, info, tools, value streams) for doing work; a process is a set of activities transforming inputs to outputs — practices may include processes.
Purpose of IT asset management: To plan and manage the full lifecycle of all IT assets, helping maximize value, control costs, manage risks, and support decision-making about reuse and disposal.
Purpose of monitoring and event management: To systematically observe services and CIs, and record and report selected changes of state identified as events.
Three event types (informational/warning/exception): Informational events (no action needed), warning events (something approaching a threshold), and exception events (a breach requiring action).
Purpose of release management: To make new and changed services and features available for use.
Purpose of service configuration management: To ensure that accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where it is needed.
Which service practices are LO7 deep-dive?: Change enablement, incident management, problem management, service request management, service desk, and service level management (plus continual improvement, a general practice).
Purpose of change enablement: To maximize the number of successful service and product changes by ensuring risks are assessed, changes authorized, and the change schedule managed.
Purpose of incident management: To minimize the negative impact of incidents by restoring normal service operation as quickly as possible.
Purpose of problem management: To reduce the likelihood and impact of incidents by identifying actual and potential causes and managing workarounds and known errors.
Purpose of service request management: To support the agreed quality of a service by handling all predefined, user-initiated service requests effectively and in a user-friendly manner.
Purpose of the service desk: To capture demand for incident resolution and service requests; it is the entry point and single point of contact for users.
Purpose of service level management: To set clear, business-based targets for service performance so delivery can be properly assessed, monitored, and managed against them.
How should low-risk frequent incidents be handled?: Through standardized, often automated, models or known-error records, freeing skilled staff to focus on complex or high-impact incidents.
What is incident swarming?: A collaborative technique where multiple stakeholders work together on an incident until it's clear who is best placed to continue, then the rest disengage.
Purpose of availability management: To ensure that services deliver agreed levels of availability to meet the needs of customers and users.
Purpose of capacity and performance management: To ensure services achieve agreed and expected performance, satisfying current and future demand cost-effectively.
Purpose of service continuity management: To ensure availability and performance are maintained at sufficient levels in case of a disaster, supporting overall business continuity.
Purpose of service catalogue management: To provide a single source of consistent information on all services and service offerings, available to the relevant audience.
Purpose of service design (practice): To design products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.
Purpose of business analysis: To analyze a business or element of it, define associated needs, and recommend solutions that enable the organization to add value to stakeholders.
Purpose of service validation and testing: To ensure new or changed products and services meet defined requirements for utility and warranty.
What is a service-level target?: A measurable commitment within an SLA, ideally outcome-based and tied to the user experience, against which performance is judged.
Why avoid relying on a single metric for SLAs?: A single technical metric (e.g., uptime) can look healthy while user experience is poor — the 'watermelon' effect. Use a balanced set of outcome-based metrics.
Which technical practice is in LO6's 15?: Deployment management — the technical management practice examined at purpose level on Foundation.
Phased deployment: Releasing to part of the production environment or user base at a time, then expanding in stages to control risk.
Big bang deployment: Deploying the new or changed component to all targets at once; higher risk but sometimes necessary.
Pull deployment: Making new/changed software available in a controlled repository, and letting users or devices download (pull) it when ready.
Continuous delivery deployment: An automated approach where changes are deployed frequently and reliably through an integrated pipeline.
Purpose of infrastructure and platform management: To oversee the infrastructure and platforms used by an organization, enabling monitoring of technology solutions, including those of external and cloud services.
Purpose of software development and management: To ensure applications meet internal and external stakeholder needs for functionality, reliability, maintainability, compliance, and auditability.
Service consumption vs service provision: Provision = the provider's activities to supply a service (resources, access, actions, levels). Consumption = the consumer's activities to use it (using resources, requesting actions, receiving goods).
What is fitness for purpose?: Another name for utility — the service does what is needed, supporting performance or removing a constraint for the consumer.
What is fitness for use?: Another name for warranty — the service performs reliably enough, covering availability, capacity, security, and continuity.
Does a consumer always manage the costs/risks?: No — the defining feature of a service is that the provider takes on specified costs and risks so the consumer can focus on its outcomes.
Who owns the outcomes of service consumption?: The customer — the role that defines requirements and takes responsibility for the outcomes of service consumption.
Mnemonic for the four dimensions: Often remembered as O-I-P-V: Organizations & people, Information & technology, Partners & suppliers, Value streams & processes.
Are PESTLE factors inside or outside the org?: Outside — PESTLE factors are external; the organization cannot fully control them and must respond to them across all four dimensions.
Mnemonic order of the 7 guiding principles: Value, Start, Iterate, Collaborate, Holistic, Simple, Automate — focus on value; start where you are; progress iteratively; collaborate & promote visibility; think holistically; keep it simple; optimize & automate.
Which principle says 'don't lose what works'?: Start where you are — assess the current state objectively and reuse existing services, processes, people, and tools where possible.
Name the SVS components in order: Guiding principles, governance, the service value chain, practices, and continual improvement — together converting opportunity/demand into value.
First and last value chain activities (typical flow): There is no fixed first/last — but Plan sets direction and Improve runs continuously; Engage often starts demand and Deliver & support runs the live service.
How do guiding principles relate to the SVS?: They guide decision-making throughout the SVS and apply to every component and activity within it.
Purpose of architecture management: To provide an understanding of all the different elements that make up an organization and how they interrelate.
Purpose of knowledge management: To maintain and improve the effective, efficient, and convenient use of information and knowledge across the organization.
Purpose of measurement and reporting: To support good decision-making and continual improvement by decreasing uncertainty through the collection and assessment of relevant data.
Purpose of organizational change management: To ensure changes in an organization are smoothly and successfully implemented, and lasting benefits achieved by managing the people side of change.
Purpose of portfolio management: To ensure the organization has the right mix of programs, projects, products, and services to execute its strategy within funding and resource constraints.
Purpose of project management (practice): To ensure all of an organization's projects are successfully delivered.
Purpose of risk management (practice): To ensure the organization understands and effectively handles risk.
Purpose of service financial management: To support strategies and plans for service management by ensuring financial resources and investments are used effectively.
Purpose of strategy management: To formulate the goals of the organization and adopt the courses of action and allocation of resources necessary to achieve those goals.
Purpose of workforce and talent management: To ensure the organization has the right people with the appropriate skills and knowledge in the correct roles.
Why optimize a process before automating it?: Automation locks in a process; if the process is wasteful, automating it just produces poor results faster and at scale.
Is the continual improvement register a tool or a step?: A tool — the CIR is a database/structured document used to capture and track improvement ideas; it is not a step of the improvement model.
How does ITIL 4 treat the change advisory board (CAB)?: It de-emphasizes a single, heavyweight CAB in favor of appropriate, often decentralized change authorities suited to the change type and risk.
Standard vs normal vs emergency change: Standard = low-risk, pre-authorized, repeatable. Normal = scheduled, assessed, and authorized via a process. Emergency = must be done ASAP, with expedited assessment.
What initiates a service request?: A user (or authorized representative) requesting something predefined and agreed as a normal part of service delivery — not an interruption.
Why are workarounds documented?: So they can be reused to restore service quickly for future incidents caused by the same problem, even before a permanent fix exists.
Problem identification vs control vs error control: Identification = finding/logging problems. Problem control = analysis and documenting known errors/workarounds. Error control = managing known errors and assessing permanent fixes.
What is the single point of contact?: The service desk — the central channel through which users report incidents, ask questions, and make service requests.
Should the service desk only resolve issues?: No — it also captures demand, coordinates with other practices, communicates with users, and shapes the user experience and perception of the provider.
What does an SLA require to be meaningful?: Engagement and agreement with the customer, a defined service, simple clear language, and metrics that reflect the actual customer/user experience.
Why monitor before managing events?: Monitoring observes states continuously; event management then filters and prioritizes the significant changes of state (events) that require a response.
Major incident vs normal incident: A major incident has significant business impact and uses a separate, coordinated, faster procedure; a normal incident follows the standard incident process.
Relationship between incident and problem management: Incident management restores service fast (often via workarounds); problem management investigates underlying causes to prevent recurrence — they work closely together.
Why automate and standardize service requests?: Because requests are predefined and repeatable, standardization and automation improve speed, consistency, and user satisfaction while freeing specialist staff.
How does deployment relate to release in ITIL 4?: They are distinct: deployment moves components into an environment; release controls when functionality becomes available to users. Modern practice deliberately decouples them.
Which deployment approach lowers risk by stages?: Phased deployment — rolling out to part of the environment or user base first, then expanding once it proves stable.

To find us again, just search “Career Employer ITIL 4 Foundation”

By Career EmployerUpdated Jun 19, 2026

250+ free ITIL 4 Foundation flashcards — 4 ways to study

ITIL 4 Foundation Flashcard of the DayNew daily

The classic card. Do you know this one?

Click Study Flashcards above to open the flashcard hub — hundreds of ITIL 4 Foundation cards you can flip, match, type, or quiz yourself on. Every card is drawn from the official ITIL 4 Foundation syllabus, so you study exactly what the exam tests.^[1] Pair them with our free practice test and study guide.

ITIL 4 Foundation Flashcard Study Modes

Most flashcard sites give you one thing: a card to flip. Ours has four modes so you can both learn the material and prove you know it — the difference between recognizing an answer and recalling it under exam pressure.

Flip (Study) — the classic card. Flip term ↔ definition, shuffle the deck, and mark each card “Got it” or “Still learning.”
Match (Game) — a timed game: pair each term to its definition as fast as you can. Great for cementing ITIL definitions and practice purposes.
Type (Recall) — read the definition and type the term. Typing forces true active recall instead of passive recognition.
Quiz (Test) — multiple-choice questions generated from the cards, so you self-test exactly like exam day.

Free ITIL 4 Foundation flashcards from Career Employer — active recall for the ITIL 4 Foundation exam

Why Flashcards Work for the ITIL 4 Foundation Exam

Flashcards aren’t busywork — they’re built on active recall: pulling an answer out of memory strengthens it far more than re-reading notes. Pair that with spacing — short sessions across several days rather than one cram — and you retain more in less time.

ITIL 4 Foundation is dense with definitions — the exact wording of service, utility, and warranty, the seven guiding principles, the six value chain activities, and the purpose of dozens of practices.^[1] Spaced flashcards are the most efficient way to keep it all fresh. Used alongside our practice test and study guide, they turn review time into measurable progress.

ITIL 4 Foundation Flashcards by Topic

The cards are organized by the syllabus areas. Lead with the practices — understanding seven in detail (17 marks) plus the purpose of 15 (7 marks) is 24 of the 40 marks:^[1]

ITIL 4 Foundation flashcards by topic and exam weight
Topic	Exam weight (of 40 marks)
Key concepts of service management	5 marks
The seven guiding principles	6 marks
The four dimensions	2 marks
The service value system & value chain	3 marks
The 34 practices (purpose + 7 in detail)	24 marks

How to Get the Most Out of These Flashcards

Lead with the practices. They are 24 of 40 marks — drill the seven deep-dive practices (incident, problem, change enablement, service request, service desk, service level management, continual improvement) hardest.
Use Type and Quiz, not just Flip. Recognizing the right answer is easy; recalling and choosing it is the real test.
Drill your weakest topic. Pick a single topic deck and grind it until the Match time drops and the Quiz score climbs.
Then prove it. When the cards feel easy, confirm with a full practice test — aim comfortably above the 65% pass mark before exam day.

ITIL 4 Foundation Flashcards FAQ

Hundreds of free ITIL 4 Foundation flashcards, organized across the whole syllabus — key concepts, the four dimensions, the seven guiding principles, the service value system and value chain, and the 34 ITIL practices. They're free with no account required.

References

1.AXELOS. “ITIL 4 Foundation Candidate Syllabus.” axelos.com. ↑
2.PeopleCert. “ITIL 4 Foundation — Certification.” peoplecert.org. ↑
3.AXELOS. “ITIL Glossary of Terms and Definitions.” axelos.com. ↑

Career Employer

Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.

All Posts

Career Employer’s Editorial Process

Here at Career Employer, we focus a lot on providing factually accurate information that is always up to date. We strive to provide correct information using strict editorial processes, article editing, and fact-checking for all of the information found on our website. We only utilize trustworthy and relevant resources. To find out more, make sure to read our full editorial process page here.