ITIL4F Flashcards — Free ITIL 4 Foundation Study Cards

Organizations and people, and information and technology

For a financial institution's new digital service, regulatory compliance and resilience are paramount. The 'information and technology' dimension is critical first because it governs the security, availability, and integrity of data (e.g., encryption standards like AES-256, access controls, and backup/recovery mechanisms) that underpin compliance with regulations such as PCI DSS or SOX. The 'organizations and people' dimension is equally critical to ensure staff are trained on compliance procedures and that roles (e.g., Data Protection Officer) are clearly defined to enforce these technical controls.

Focus on value

The 'Focus on value' guiding principle is the correct first step because the service owner must define what value means for the CRM system's customers and stakeholders before any design or implementation begins. In ITIL 4, value is co-created with customers, and all other activities—such as iterative progress, simplification, or leveraging existing assets—must be aligned to that value definition. Without first establishing the desired outcomes and value, subsequent decisions risk delivering a technically sound service that fails to meet business needs.

Governance

Governance is the component of the Service Value System (SVS) that ensures organizational activities, including new service deployments, are aligned with business strategy and policies. It provides the framework for decision-making, accountability, and oversight, making it the correct mechanism to govern strategic alignment before deployment.

Focus on value

The team is violating the 'Focus on value' principle because they are adding staff without first understanding the root cause of slow incident resolution. This wastes resources on a solution that may not address the actual value drivers for users, such as inefficient processes or tooling issues, rather than improving the service outcome.

Organization and People

The question describes a scenario where the project team is focusing on technology and processes but neglecting to define clear roles and responsibilities for the service desk and system administrators. This directly relates to the 'Organization and People' dimension of service management, which ensures that roles, responsibilities, skills, and culture are properly defined to support the service value system. Without clear roles, the new CRM system will lack the necessary human governance and operational ownership, leading to confusion and inefficiency.

Change enablement

Change enablement is the correct practice because it specifically governs the lifecycle of changes to IT services, ensuring that all changes are assessed, authorized, and implemented in a controlled manner. This practice balances the need for rapid service evolution with the imperative to minimize risk by using standardized procedures, change models, and authorization policies (e.g., pre-approved standard changes, normal changes requiring CAB approval, emergency changes with expedited review).

Create a known error record in Problem Management and provide a workaround

Option B is correct because Problem Management aims to identify the root cause of incidents and provide workarounds or permanent solutions. In this scenario, creating a known error record and providing a workaround directly reduces the impact of the known bug. Option A is incorrect because Service Level Management focuses on setting and managing service level targets, not on addressing the technical problem. Option C is incorrect because Incident Management is about restoring service quickly after an incident occurs, but it does not proactively address the underlying known error. Option D is incorrect because Change Enablement manages the lifecycle of changes, but replacing the software may not be feasible or immediate, and it is not the practice specifically designed to handle known errors.

Change enablement

Change enablement is the ITIL practice that ensures all changes to the production environment are properly assessed, authorized, and controlled before implementation. By enforcing a standardized change management process—including change requests, approvals, and review boards—this practice directly prevents unauthorized modifications that cause service outages.