Free ITIL-4-CDS Practice Test

Topic-based forums are specifically designed to facilitate structured, two-way communication. They allow users to post specific questions and provide detailed feedback in organized threads. This format enables product teams to directly engage in conversations, answer questions, ask for clarification, and build a community around the product. This method is superior to other options as it creates a persistent, searchable, and collaborative environment for dialogue, directly meeting the requirement for enabling two-way communication between users and the product team.

A. Event surveys: Surveys are primarily a one-way feedback collection mechanism. They do not facilitate the back-and-forth dialogue required for two-way communication.
C. Self-service portals: These are designed to provide users with information and transactional capabilities (e.g., logging a ticket) to reduce direct contact, not to foster open, two-way community dialogue.
D. Social media: While enabling two-way communication, social media is often unstructured and not ideal for tracking specific, technical product questions or detailed feedback threads effectively.

AXELOS, ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office), 2020.

Section 4.1.5 'Channels': This section discusses various communication channels. It explicitly states, "Online forums and communities are a good way of facilitating communication between users and with the service provider." This directly supports the use of forums for the scenario described.

Section 5.1.5 'Feedback': This section discusses feedback mechanisms. While it mentions surveys as a tool, the context is data gathering, not dialogue. The emphasis on understanding user experience points towards more interactive channels like forums for qualitative feedback and questions.

Section 4.1.5 'Channels': This section also describes self-service portals as a way for users to "find information and log and manage their own incidents and requests," which is a transactional function rather than a conversational one.

Robotic Process Automation (RPA) uses software 'robots' to automate repetitive, rule-based tasks that humans typically perform through a user interface. The primary goals and benefits of implementing RPA are to improve efficiency by streamlining business operations, reduce operational expenses by lowering the need for manual human effort (staffing costs), and enhance quality by minimizing the human errors inherent in repetitive tasks. RPA achieves this by executing processes consistently and accurately, leading to more reliable outcomes.

B. RPA is designed to automate high-volume, repetitive, and rule-based tasks, not "unique and singular" ones, which would not provide a return on the automation investment.
C. RPA operates on structured or semi-structured data in a highly consistent and predictable, rule-based manner. Inconsistency and unpredictability are characteristics of processes unsuitable for RPA.
D. Compared to other forms of automation that require deep system integration, RPA is often considered a relatively low-cost and faster-to-implement solution, as it works at the user interface level.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office).

Section 5.2.7.2, Robotic process automation (RPA): "RPA is a potential way for organizations to streamline business operations, lower staffing costs, and reduce errors." This statement directly validates option A. The section also clarifies that RPA is used for "repetitive, rule-based tasks" (refuting B), can be "implemented quickly and cheaply" (refuting D), and works with "structured data" (refuting C).

A value proposition is a strategic statement that clearly articulates the benefits a customer will receive from a product or service. It is the promise of value to be delivered. Therefore, defining the expected benefits at a strategic level in exchange for customer loyalty is the core activity of creating a value proposition. This step is fundamental to a customer-oriented strategy as it sets the customer's expectations and frames the entire service relationship.

B. This describes managing the customer journey and user experience (UX) through touchpoints, which is a separate, subsequent step in a customer-oriented strategy, not the creation of the value proposition itself.
C. This focuses on developing staff competencies and soft skills. While essential for delivering on the value proposition, it is about enabling the workforce, not defining the strategic promise to the customer.
D. This describes the organizational culture and leadership style (servant leadership) that supports customer orientation. It is a foundational element but is distinct from the act of creating the value proposition.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office).

Section 2.2.1, Customer orientation: This section outlines the steps for a customer-oriented strategy. The first step listed is "Create a value proposition (VP) that sells the organization and its services. It should define, at a strategic level, the expected benefits the customer is being promised in return for their loyalty." This directly supports answer A. The same section lists understanding touchpoints (B), developing skills (C), and fostering a supportive culture (D) as other distinct steps.

The question describes the negative consequences of designing support structures around the mechanics of ticketing systems (data entry, ticket transfers) rather than focusing on the user's journey and value creation. Option 4 is a direct and powerful example of this negative impact. When a customer's single requirement is fragmented into several tickets, forcing them to re-enter the same information, it demonstrates a process designed around internal silos and ticket transfers, not customer experience. This creates inefficiency and frustration, which are key negative impacts that modern service management approaches, like value stream mapping, aim to eliminate.

A (Item 3): This is also a valid negative impact mentioned in the ITIL CDS publication. However, it focuses more on the agent's immediate task of data entry rather than the broader workflow design issue of ticket transfers and process fragmentation, which is central to the question's premise and best illustrated by option D. B (Item 2): While this is used as an analogy in the official ITIL text, it is an example from the hospitality industry, not directly from the IT service management context that is the primary focus of the question. C (Item 1): This is incorrect. The denial of a change due to a moratorium is the result of a governing policy, not a flaw in the workflow design related to data manipulation or ticket transfer. The ticketing system merely records and communicates this policy-based decision.

AXELOS, ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office), 2020.

Section 4.2.1, ‘Managing queues and backlogs’, explicitly lists the scenarios in options 2, 3, and 4 as examples of negative impacts of ticket-centric design. The text states: "Negative impacts are common and include, for example: telephone support agents having to pause the conversation while they complete on-screen forms; customers being asked to enter the same details on consecutive forms because their specific requirements necessitate several tickets; hotel check-in procedures involving lengthy typing by a front-desk employee." This directly supports that D is a correct answer and C is incorrect as it is not mentioned.

A 'job' is a formal position within an organization's structure assigned to an individual. The ITIL framework distinguishes this from a 'role'. A single person holding one job title, such as 'IT Operations Analyst', may be required to perform several different roles as part of their duties. For example, they might act in the role of an incident resolver, a change implementer, and a problem analyst at different times. This distinction is crucial for building flexible and effective teams where responsibilities are clearly understood beyond just a job title.

A. This describes a historical trend in IT job design, focusing on technical silos, rather than defining what a job is in the modern, role-based context of ITIL 4.
B. This is the official ITIL 4 definition of a 'role', which is a set of responsibilities and authorizations, not a 'job'. A person in one job can have many roles.
D. This statement is conceptually confused. A value stream or service is contributed to by several departments; a job is a position typically held by one person within a department.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office).

Section 4.1.2.1 'Jobs and roles': "A job is a position within an organization that is assigned to a specific person. As part of their job, a single person may fulfil many different roles." This directly supports option C.

Section 4.1.2.1 'Jobs and roles': "A role is a set of responsibilities, activities, and authorizations granted to a person or team, in a specific context." This directly refutes option B by defining it as a 'role'.

Section 4.1.2.2 'Competencies': Discusses the shift from purely technical competencies (I-shaped) to broader skills (T-shaped), showing that option A is an outdated model, not a core definition.

The ITIL 4 framework specifies that a successful continual improvement culture is built upon specific organizational behaviors and values. The official 'Create, Deliver and Support' publication explicitly identifies 'Management by example', 'Building trust', and 'Transparency' as the key elements. These foster an environment of psychological safety and collaboration, which is essential for identifying and implementing improvements. While 'Mitigating risks' is a crucial activity often addressed through improvement, it is considered an outcome or a related practice, not a foundational element of the culture itself.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office). Section 2.4.3, "Continual improvement culture", Page 31. This section states, "The key elements of a continual improvement culture are: Management by example; Building trust; Transparency."

Understanding a role’s competency profile is a fundamental component of workforce and talent management. The official ITIL 4 guidance specifies that its benefits include identifying the best candidates for a role, defining job requirements, identifying skill gaps to plan professional development, and aligning the organization’s talent strategy with industry models. The option concerning collaboration with leaders for risk management describes a risk management activity. While having competent personnel is crucial for managing risks, the collaborative process of identifying and managing risks is a separate practice and not a direct purpose or outcome of understanding a competency profile itself.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office). Section 2.2.2, "Professional IT and service management skills and competencies". This section explicitly lists the benefits of understanding a competency profile, which correspond to the other three options.

2. Campion, M. A., Fink, A. A., Ruggeberg, B. J., Carr, L., Phillips, G. M., & Odman, R. B. (2011). Doing competencies well: Best practices in competency modeling. Personnel Psychology, 64(1), 225–262. This academic review outlines the primary applications of competency modeling, such as selection, training, and performance management, which align with the correct uses listed in the question, but does not include collaborative risk management as a direct application. (https://doi.org/10.1111/j.1744-6570.2010.01207.x)

The description provided is a textbook definition of a functional organizational structure. This model groups employees based on their specific skills, expertise, and business functions, such as IT, finance, or human resources. Key characteristics include a clear hierarchical arrangement, specialized departments, and defined lines of authority within each function. The structure is designed to promote efficiency and deep expertise within these specialized areas, which aligns perfectly with the scenario described.

B. Divisional: This structure organizes teams around products, services, or geographical regions, not by specialized business functions as described.
C. Matrix: This is a hybrid model where employees report to both a functional manager and a project/product manager, which is not mentioned.
D. Flat: This structure has minimal or no middle management, contradicting the description of "hierarchical arrangements" and "different levels."

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office).

Section 2.2.1.1, Functional structure: "These are typically hierarchical arrangements based on organizational control, lines of authority, or technical domain... The organization may be divided into internal groups based on functional areas, such as HR, IT, finance, marketing, etc." This text directly matches the question's description.

Section 2.2.1, Organizational structures: This section provides context and definitions for the different structures, contrasting the functional model with matrix, divisional, and flat structures.

The scenario describes a flat organizational structure. This model is characterized by having few or no levels of middle management between staff and executives. The primary purpose is to reduce bureaucracy and remove hierarchical barriers, thereby accelerating communication and decision-making. The statement that these structures become a challenge to maintain as an organization grows is a well-documented limitation of the flat model, as the lack of management layers can lead to a loss of control and a broad span of control for senior leaders.

A. Matrix: This structure involves dual reporting lines (e.g., to a functional and a project manager), which often increases complexity rather than reducing hierarchy.
C. Functional: This is a traditional, hierarchical structure where the organization is divided by specialty or function, which is the type of model the described approach seeks to change.
D. Divisional: This structure organizes by product, service, or geography, and while it decentralizes some authority, it typically retains a traditional hierarchy within each division.

1. AXELOS. (2020). ITIL® 4 Specialist: Create, Deliver and Support. TSO (The Stationery Office).

Section 2.2.1, Organizational structures: This section states, "Traditional hierarchical structures are often seen as a barrier to the fast and efficient flow of work... As a result, many organizations are moving towards flatter, more dynamic structures that are better suited to the modern digital environment." This directly supports the rationale presented in the question for adopting a structure with reduced hierarchy.

2. Ghiselli, E. E., & Siegel, J. P. (1972). Leadership and Managerial Success in Tall and Flat Organization Structures. Personnel Psychology, 25(4), 617–624.

Page 617: The article discusses the core differences, noting that flat organizations are characterized by "a minimum of supervisory levels" and are intended to improve communication and decision-making speed, contrasting with taller, more hierarchical structures.

3. Burton, R. M., & Obel, B. (2018). The science of organizational design: A research-based perspective. In The Oxford Handbook of Management.

This academic text explains that flat structures aim to "reduce the length of the scalar chain" to increase responsiveness and employee empowerment, but notes the scalability challenges mentioned in the question.

The decision to buy a product instead of building it is a strategic sourcing choice. An organization may choose to buy if its internal product development processes are immature, as this mitigates the risk of project failure, delays, and poor quality. Sourcing from a supplier with mature processes and proven expertise provides a more reliable outcome. Additionally, when compliance with specific standards and policies is essential, buying a pre-certified product from a specialized vendor is often a prudent strategy. This leverages the supplier's expertise, reduces the significant risk and effort of achieving and maintaining compliance in-house, and can accelerate time-to-market for the service.

2 - Predictable and repetitive product development tasks: While this can be a factor (suggesting a commodity product), it can also be an argument for building in-house, as the predictability may allow for efficient internal development or automation. 3 - Product development relying on internal knowledge: This is a primary reason to build a product in-house, not buy it. Outsourcing development that requires proprietary or unique internal knowledge would be inefficient and risky.

1. AXELOS, ITIL® 4 Specialist: Create, Deliver and Support, 2020.

Section 4.3.1 Sourcing options: This section outlines the key factors in a build-versus-buy decision. It states, "Does the organization have the required skills and knowledge, or does it need to source them externally?" This directly supports reason 1 (Organization's immature product development processes) as a driver for buying.

Section 4.3.1 Sourcing options: The same section lists "Risks" as a key factor, explicitly mentioning "compliance risks." It notes that suppliers may have "specialist skills and knowledge." This supports reason 4 (Essential compliance to standards and policies), as buying from a specialist vendor is a key strategy to mitigate compliance risks.