🇬🇧 ITIL Foundation · subject

ITIL Foundation Key Practices Examined in Detail Syllabus

The Key Practices Examined in Detail syllabus for ITIL Foundation in full: 5 chapters, 16 topics and 27 sub-topics, every one listed below, plus 50 Key Practices Examined in Detail flashcards with answers.

5Chapters
16Topics
27Sub-topics
50Flashcards

Key Practices Examined in Detail syllabus: all 5 chapters

Expand any chapter to see its topics and sub-topics.

  1. General Management Practices in Detail

    4 topics
    • Continual improvement practice
      • Purpose and activities of the practice
      • Methods, the CIR and improvement culture
    • Information security management (purpose)
      • Protecting information across CIA
    • Relationship management (purpose)
      • Establishing and nurturing stakeholder links
    • Supplier management (purpose)
      • Ensuring suppliers and their performance meet needs
  2. The Service Desk Practice

    3 topics
    • Purpose of the service desk
      • Single point of contact between provider and users
    • Key principles of the service desk
      • Empathy, communication and user experience
      • Centralised and virtual service desk models
    • Channels and technology supporting the desk
      • Phone, portals, chat, self-service and automation
  3. Incident and Problem Management

    3 topics
    • Incident management practice
      • Purpose: restoring normal service as quickly as possible
      • Prioritisation, escalation and major incidents
      • Swarming and collaboration techniques
    • Problem management practice
      • Purpose: reducing likelihood and impact of incidents
      • Problem identification, control and error control
      • Known errors and workarounds
    • Relationship between incidents and problems
      • Distinguishing root cause from symptom restoration
  4. Service Request and Change Management

    3 topics
    • Service request management practice
      • Purpose: handling predefined user-initiated requests
      • Standardisation, fulfilment and approval policies
    • Change enablement practice
      • Purpose: maximising successful changes while managing risk
      • Standard, normal and emergency change types
      • The change authority and change schedule
    • Balancing speed and risk in changes
      • Assessment, authorisation and the change schedule
  5. Service Level Management

    3 topics
    • Purpose of service level management
      • Setting clear targets and monitoring service performance
    • Service level agreements (SLAs)
      • Characteristics of effective SLAs
      • The watermelon SLA effect
    • Metrics, measurement and engagement
      • Customer-focused outcome metrics
      • Operational and business reporting

ITIL Foundation Key Practices Examined in Detail flashcards — 50 questions with answers

  1. What is the purpose of the continual improvement practice in ITIL 4?

    To align an organisation's practices and services with changing business needs through ongoing identification and improvement of services, components, and anything involved in the management of products and services.

  2. What are the steps of the ITIL continual improvement model (in order)?

    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?

  3. In continual improvement, what is the role of the 'continual improvement register' (CIR)?

    A structured database or document used to track and manage improvement ideas from identification through to action, capturing, assessing and prioritising improvement opportunities.

  4. Whose responsibility is continual improvement in ITIL 4?

    Everyone's. It is the responsibility of every person in the organisation, though a dedicated team may coordinate and promote the practice.

  5. What is the purpose of the information security management practice?

    To protect the information needed by the organisation to conduct its business, including managing the risks to the confidentiality, integrity and availability of information, as well as authentication and non-repudiation.

  6. Name the key elements protected by information security management (the CIA triad plus two).

    Confidentiality, Integrity and Availability (CIA), plus Authentication (verifying identity) and Non-repudiation (ensuring an action cannot later be denied).

  7. In information security management, what is the difference between confidentiality and integrity?

    Confidentiality means information is observed or disclosed only to those who have a right to know; integrity means information is complete, accurate, and protected against unauthorised modification.

  8. What balance must information security management maintain?

    A balance between prevention (stopping incidents), detection (spotting incidents quickly) and correction (recovering from incidents), and between protecting the organisation and allowing it to remain effective and accessible.

  9. What is the purpose of the relationship management practice?

    To establish and nurture the links between the organisation and its stakeholders at strategic and tactical levels, including identification, analysis, monitoring and continual improvement of relationships.

  10. What outcomes does effective relationship management aim to deliver?

    Stakeholders' needs prioritised and balanced, conflicting requirements mediated, customer satisfaction high, and a constructive relationship between the organisation and stakeholders established and maintained.

  11. What is the purpose of the supplier management practice?

    To ensure that the organisation's suppliers and their performance are managed appropriately to support the seamless provision of quality products and services.

  12. What are common supplier relationship types/activities managed by supplier management?

    Creating a single point of visibility and control, building close relationships, managing risks, governing contracts, negotiating and agreeing terms, and managing performance against agreements.

  13. In supplier management, what is the difference between insourcing, outsourcing and a partnership/co-source arrangement?

    Insourcing uses internal resources; outsourcing uses an external third party to provide products/services; partnership/co-sourcing combines internal and external resources working together to achieve shared goals.

  14. What is the purpose of the service desk practice?

    To capture demand for incident resolution and service requests; it is the entry point and single point of contact for the service provider with all of its users.

  15. What is a key principle of the service desk regarding its value?

    The service desk has a major influence on user experience and how the service provider is perceived; its real value is in providing a clear path for users and supporting the people and business, not just fixing technical issues.

  16. What does it mean that the service desk should be the 'single point of contact'?

    All user demand (incidents and service requests) is captured and coordinated through one consistent point, giving users a clear, consistent path and the provider a single view of demand.

  17. What practical and empathetic skills does a modern service desk require?

    Excellent customer service skills such as empathy, incident analysis and prioritisation, effective communication, emotional intelligence, and the ability to fully understand a business issue in the user's terms.

  18. Why might service desk staff increasingly not need deep technical skills for every interaction?

    Because automation, self-service, AI/chatbots and increased centralisation handle routine work, allowing the desk to focus on excellent customer experience and coordinating support across teams.

  19. What are the main channels and technologies that support the modern service desk?

    Phone calls, service portals and mobile apps, live chat and chatbots, email, walk-in/physical desks, plus supporting technology such as intelligent telephony, knowledge bases, AI/machine learning, workflow systems and remote access tools.

  20. What is the difference between a centralised, local (distributed), and virtual service desk?

    Centralised: a single desk location serving the whole organisation; Local/distributed: physical desks near user locations; Virtual: staff in multiple/remote locations appearing as one desk through technology.

Show the other 30 Key Practices Examined in Detail flashcards
  1. What is the purpose of the incident management practice?

    To minimise the negative impact of incidents by restoring normal service operation as quickly as possible.

  2. How does ITIL 4 define an incident?

    An unplanned interruption to a service, or a reduction in the quality of a service.

  3. How are incidents typically prioritised in incident management?

    Based on a combination of impact (how widely/severely the business is affected) and urgency (how quickly resolution is needed), often using an impact/urgency priority matrix.

  4. What is swarming in the context of incident management?

    A collaborative technique where many stakeholders work together on an incident until it becomes clear which of them is best placed to continue, then the others move on.

  5. What is the purpose of the problem management practice?

    To reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.

  6. How does ITIL 4 define a problem?

    A cause, or potential cause, of one or more incidents.

  7. How does ITIL 4 define a known error?

    A problem that has been analysed but has not been resolved, i.e. one for which the cause is understood and (often) a workaround exists.

  8. What is a workaround in problem management?

    A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available; some workarounds become permanent if resolving the problem is not viable.

  9. What are the three phases of the problem management practice?

    Problem identification, problem control (analysis and documenting workarounds/known errors), and error control (managing known errors and potential permanent solutions, often via change enablement).

  10. What is the key relationship between incidents and problems?

    Incidents are unplanned interruptions or quality reductions experienced by users; problems are the underlying causes of those incidents. Problem management addresses causes, while incident management restores service from the symptoms.

  11. Why are incident management and problem management kept as separate practices despite being closely related?

    Because they have different goals: incident management focuses on rapid restoration of service (speed), while problem management focuses on understanding and removing root causes to prevent recurrence (analysis), which require different timeframes and skills.

  12. What is the purpose of the service request management practice?

    To support the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner.

  13. How does ITIL 4 define a service request?

    A request from a user or user's authorised representative that initiates a service action which has been agreed as a normal part of service delivery.

  14. How do service requests differ from incidents?

    Service requests are predefined, planned parts of normal service delivery (e.g. a password reset, access request, or information), whereas incidents are unplanned interruptions or quality reductions; requests are not failures.

  15. What are key guidelines for fulfilling service requests effectively?

    Standardise and automate requests as far as possible, establish workflows and self-service, set expectations for fulfilment times, and identify opportunities for improvement; policies should allow streamlined fulfilment with minimal approvals.

  16. What is the purpose of the change enablement practice?

    To maximise the number of successful service and product changes by ensuring that risks are properly assessed, authorising changes to proceed, and managing the change schedule.

  17. How does ITIL 4 define a change?

    The addition, modification, or removal of anything that could have a direct or indirect effect on services.

  18. What are the three types of change in change enablement?

    Standard changes (low-risk, pre-authorised, well understood, often automated); Normal changes (scheduled, assessed and authorised following a process); and Emergency changes (must be implemented as soon as possible, e.g. to resolve a major incident).

  19. What is a standard change and who authorises it?

    A low-risk, pre-authorised change that is well understood and fully documented; it can be implemented without additional authorisation because the authorisation is given once when the procedure is created.

  20. What is an emergency change and how is its assessment handled?

    A change that must be implemented as soon as possible (e.g. to fix a major incident or apply a security patch); assessment and authorisation are expedited, sometimes with a separate emergency change authority (ECAB), and documentation may be completed afterwards.

  21. What is a change authority in change enablement?

    The person or group that authorises a change; ITIL 4 recommends decentralising change authorisation to the appropriate level to balance speed and control, rather than relying on a single central body.

  22. How does change enablement balance speed and risk?

    By matching the level of control to the risk of the change: low-risk standard changes are pre-authorised and automated for speed, while higher-risk normal/emergency changes get more rigorous assessment and authorisation to control risk without unnecessarily slowing the business.

  23. Why should change enablement avoid being overly bureaucratic?

    Because excessive control slows the flow of changes and can push people to bypass the process; the practice must balance the need to make beneficial changes quickly against the need to protect customers and users from adverse effects.

  24. What is the purpose of the service level management practice?

    To set clear business-based targets for service performance, so that the delivery of a service can be properly assessed, monitored and managed against these targets.

  25. How does ITIL 4 define 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.

  26. What are the key requirements for an SLA to be effective in ITIL 4?

    It must relate to a defined service, relate to defined outcomes (not just operational metrics), reflect an agreement between provider and customer, and be written simply and easy to understand and use for all parties.

  27. What is the 'watermelon SLA' problem in service level management?

    When SLA reports show all green (targets met) on the outside but the customer is unhappy (red) on the inside, because the metrics measured do not reflect the actual customer experience or business outcomes.

  28. What sources should service level management use to understand service performance beyond simple metrics?

    Customer engagement (listening and discussing with customers), customer feedback (surveys, key business-related measures), operational metrics, and business metrics, to gain a balanced and realistic view of performance.

  29. In SLA metrics, what is the difference between an output/operational metric and an outcome/business metric?

    An operational metric measures a single, technical aspect of delivery (e.g. uptime percentage), whereas an outcome/business metric reflects the actual result the customer cares about (e.g. ability to complete transactions); good SLAs focus on outcomes.

  30. Why is ongoing engagement, not just measurement, central to service level management?

    Because targets and metrics alone can hide dissatisfaction; regular listening, business-focused conversation and feedback ensure the service is measured against what the customer actually values and allow continual improvement.

ITIL Foundation Key Practices Examined in Detail FAQ

What is in the ITIL Foundation Key Practices Examined in Detail syllabus?

ITIL Foundation Key Practices Examined in Detail is split into 5 chapters: General Management Practices in Detail, The Service Desk Practice, Incident and Problem Management, Service Request and Change Management and Service Level Management. Together they contain 16 topics and 27 sub-topics.

How many chapters are in ITIL Foundation Key Practices Examined in Detail?

5 chapters, containing 16 topics and 27 sub-topics. The largest chapter is General Management Practices in Detail, with 4 topics.

Are there flashcards for ITIL Foundation Key Practices Examined in Detail?

Yes — a 50-card Key Practices Examined in Detail deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.