ITIL 4 Foundation (ITIL4F) — Questions 826–900

Options B and D are correct. The seven guiding principles are: 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. 'Plan' is a value chain activity, and 'Incident Management' is a practice.

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

A is correct because the ITIL 4 Service Value System (SVS) is explicitly defined to include the Guiding Principles as one of its five core components. These principles, such as 'Focus on Value' and 'Start Where You Are,' provide universal guidance that shapes all SVS activities and decision-making, ensuring alignment with business objectives.

The SVS includes Governance and Service value chain. Incident management is a practice, and SLAs are not a component.

The first action when a user reports an inability to access the CRM system is to log an incident record and categorize it. This aligns with the ITIL 4 incident management practice, which prioritizes restoring normal service operation as quickly as possible. Logging the incident captures essential details like the affected service, user impact, and symptoms, enabling a structured response before any escalation or deeper investigation.

The issue stems from a disconnect between the defined change management process and actual deployment activities, where developers bypass the process to speed up releases. This is fundamentally a process design and workflow integration problem, not a technology or partner issue. Reviewing the 'Value Streams and Processes' dimension first ensures that the change management workflow is aligned with deployment practices, eliminating bottlenecks that cause bypassing.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations. This ensures that service availability and quality are maintained, aligning with ITIL 4's focus on value co-creation and business continuity. The practice prioritizes speed of recovery over root cause analysis, which is handled by Problem Management.

Standard and emergency are two of the three change types; normal is the third. Standard is pre-approved, emergency is urgent.

Neglecting Information and Technology can lead to poor data quality, security breaches, and outdated tools. Lack of skilled staff is Organizations and People; poor supplier relationships is Partners and Suppliers.

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

Culture and roles are part of Organisations and People. Data and contracts belong to other dimensions.

Outputs are tangible deliverables, such as a report. Outcomes are results for stakeholders.

Option A is correct because the 'Progress iteratively with feedback' guiding principle emphasizes breaking changes into smaller, manageable increments and incorporating continuous feedback. This approach allows the retail company to deliver value more frequently while reducing the risk of large-scale disruptions, as each iteration can be tested and adjusted before proceeding.

Uptime is about availability, which is part of warranty (fit for use).

A standard change is a pre-approved, low-risk, well-known procedure that follows a defined workflow without requiring additional authorization. Applying a routine security patch to a server fits this definition because it is a common, documented activity with a known risk profile and a pre-established change model, such as a monthly patch cycle governed by an organizational patch management policy.

The output (software) was delivered, but the desired outcome (improved sales efficiency) was not achieved because the system was not adopted. This highlights the difference between output and outcome.

The decision to use a third-party vendor directly involves the Partners and Suppliers dimension, which covers relationships, contracts, and sourcing.

Warranty is the assurance that a service will meet agreed conditions such as availability, capacity, continuity, and security. Uptime guarantees and disaster recovery are warranty aspects.

Option A is correct because 'Keep it simple and practical' is one of the seven ITIL 4 guiding principles, emphasizing that processes should be streamlined and avoid unnecessary complexity to achieve effective service management. Option E is correct because 'Focus on value' is also a core guiding principle, ensuring that all activities directly contribute to delivering value to stakeholders and customers.

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

The reliance on a single supplier points to a risk in the Partners and Suppliers dimension. Diversity in suppliers could mitigate the risk.

The 'Obtain/build' activity ensures that service components are procured or developed and made available according to agreed specifications. Option D is correct. 'Design & transition' focuses on designing and transitioning services. 'Deliver & support' focuses on delivery and support. 'Engage' is about stakeholder relationships.

An emergency change is required when a change must be implemented urgently to prevent a major impact.

PESTLE factors are external. New regulations are a Legal factor under PESTLE.

In ITIL 4, an 'output' is the tangible or intangible deliverable produced directly by an activity (e.g., a completed service request form), while an 'outcome' is the result for the stakeholder, such as restored business functionality or improved user satisfaction. Option A correctly distinguishes these two concepts, which is a core distinction in service value system design.

The four dimensions are integral to the SVS; they must be considered in the design and management of all SVS components.

Value co-creation requires active participation from both the service provider and the consumer. The consumer provides resources (clean data) that are essential for the service to deliver value.

The team is starting by reviewing current process documentation and interviewing staff to understand existing workflows before making changes. This directly applies the 'Start where you are' guiding principle, which emphasizes basing improvements on the current state rather than designing from scratch or assuming a new process is needed.

Supplier Management is responsible for supplier contracts, which are typically documented as Underpinning Contracts (UCs). SLAs are agreements between the provider and customer, and OLAs are internal agreements.

Change Enablement involves assessing, authorizing, and scheduling changes. Option B is not specific to Change Enablement; options A and C are not standard activities.

The current recovery plan fails to meet the RTO of 2 hours (restore takes 3 hours) and the RPO of 15 minutes (hourly backups). Synchronous replication writes data to both data centers simultaneously, ensuring zero data loss (RPO=0) and enabling near-instant failover, which can achieve the 2-hour RTO. The 10 ms latency is acceptable for most trading applications and is a trade-off for meeting the critical recovery objectives.

The 'Focus on value' guiding principle is most directly applied because the initiative explicitly aims to minimize waste and focus on value. In incident management, this means prioritizing activities that restore service quickly and reduce business impact, rather than performing unnecessary steps or documentation that do not contribute to the resolution. By designing the process around what delivers value to the customer and the business, the team ensures every activity has a clear purpose.

Optimise and automate focuses on eliminating manual work and using technology to improve efficiency.

In a service relationship, the consumer may transfer certain risks and costs to the provider. For example, the provider takes on the risk of staffing, technical failures, etc.

Service Level Management (SLM) negotiates, agrees, and monitors SLAs.

IT asset management starts with strategy, then acquisition, tracking, maintenance, and disposal.

A new laptop for a user is typically a pre-approved service request, not an incident (unplanned disruption).

Service requests are predefined and pre-approved, often for standard changes like software installation. Incidents are unplanned disruptions.

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

Value Streams and Processes dimension is concerned with how work is organised and executed.

IT Asset Management manages the lifecycle of assets from acquisition to disposal.

Value co-creation means that value is co-created by both the provider and consumer through their interaction and relationship.

Option A is correct because 'Start where you are' is one of the seven ITIL 4 guiding principles. It emphasizes leveraging existing services, processes, and capabilities as a foundation for improvement, avoiding unnecessary rework or investment.

The 'Warranty' aspect of a service addresses whether the service is 'fit for use' (availability, capacity, continuity, security). Governance provides the overall direction and monitoring to ensure requirements are met.

An outcome is a result for a stakeholder enabled by one or more outputs. Here, the reduced time is a positive outcome for sales staff. Output would be the CRM system itself or a report.

These are the six activities of the service value chain.

The ITIL 4 Service Value System (SVS) is designed as an overarching model that describes how all components and activities of an organization work together to facilitate value co-creation. Its primary purpose is to enable value co-creation through service management by integrating the guiding principles, governance, service value chain, practices, and continual improvement into a cohesive system, rather than focusing on a single component like the value chain or practices.

Focus on value, Start where you are, and Keep it simple and practical are correct. 'Reduce silos' and 'Automate everything' are not guiding principles.

Problem Management is the ITIL 4 practice focused on identifying the root cause of incidents to prevent recurrence. While Incident Management restores normal service operation, Problem Management conducts root cause analysis (RCA) to eliminate underlying defects, aligning with the ITIL 4 Service Value System's objective of continual improvement.

Value co-creation recognizes that value is created jointly by the provider and consumer through their interactions and activities.

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

Option B (Improve) is correct because the ITIL Service Value Chain defines six core activities: Plan, Improve, Engage, Design & Transition, Obtain/Build, and Deliver & Support. 'Improve' is the activity responsible for continual improvement of products, services, and practices across the entire value chain, ensuring alignment with changing business needs.

An event that indicates a threshold has been exceeded and may require action is a warning event. Option B is correct. Option A is informational; Option C is exception; Option D is not an event classification.

Outcomes are results for stakeholders. Reduced operational risk and improved employee satisfaction are outcomes. Processed transactions and reports are outputs.

Option A is correct because the problem manager's role is to analyze incidents linked to a problem record to identify the underlying root cause, not just resolve individual incidents. Restarting the mail server resolved the symptoms (the high-priority incident), but the problem record shows three related incidents, indicating a recurring underlying issue that requires root cause analysis (RCA) to prevent future occurrences. Defining a workaround is a standard interim step before a permanent solution is implemented, aligning with ITIL 4's problem management practice.

An SLA is an agreement between the service provider and the customer, while an OLA is between internal teams.

Continual improvement is a key ITIL 4 component.

The four dimensions ensure a holistic approach to service management.

The Partners and Suppliers dimension is specifically concerned with managing relationships with external entities that provide services or components. Since the question involves an outsourced provider, this dimension directly addresses how to integrate, govern, and collaborate with that third party to ensure service quality and alignment with organizational goals.

Continual Improvement aims to align services with changing business needs by identifying and implementing improvements.

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

Outcomes are the results achieved by the consumer from using the service. Utility and warranty enable outcomes.

The Service Value Chain is the core component of the ITIL Service Value System that defines the key activities required to respond to demand and facilitate value creation through the creation, delivery, and improvement of services. By focusing on the value chain, the organization can map and integrate the workflows of different teams (e.g., incident management, change enablement, service desk) into a single end-to-end delivery model, directly breaking down silos by forcing cross-functional handoffs and shared accountability for outcomes.

The 'Plan' activity aligns improvement with strategy and objectives.