ITIL4-CDS ITIL 4 Specialist Create Deliver and Support Practice Questions

Infrastructure as Code (IaC) is the most direct and foundational solution to the problem. By defining the infrastructure (servers, load balancers, configuration) in version-controlled code, SwiftCart can eliminate the manual checklist. IaC allows them to create consistent, repeatable environments automatically, which is a prerequisite for reliable, frequent deployments and a core principle of DevOps.

A fundamental principle of good service design is to hide the underlying complexity from the consumer. The customer does not need to know about the replication, data centers, or failover mechanisms. They are consuming a simple 'storage' service. This abstraction makes the service easier to use and understand, allowing the consumer to focus on the value they receive.

The statement is false. While the service desk is the entry point and provides a channel for users to report incidents and make requests, its role is broader. The service desk acts as the empathetic and informed link between the service provider and its users. It captures demand, provides communication during outages, and plays a crucial role in the overall user experience, contributing to many value chain activities beyond just these two practices.

'Shift-left' means moving activities like testing earlier in the development lifecycle (to the left on a typical project timeline). A developer running performance tests locally is a perfect example. Instead of waiting for a dedicated performance testing phase late in the cycle, potential issues are identified and fixed at the earliest possible moment, when the cost of remediation is lowest.

The purpose of the Change Enablement practice is to maximize the number of successful service and product changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule. The 'Risk & Impact Assessment' step is a core activity of this practice.

Value stream mapping is the most effective first step. It provides a holistic view of the entire process from concept to delivery, making bottlenecks, delays, and handoff issues (like the cadence mismatch) visible. This allows the organization to collaboratively identify and address the specific constraints hindering the flow of value, which is the core issue described.

By categorizing incidents and tracking the KPI for each category, the company can set realistic targets and gain actionable insights into the performance of different support teams and technologies. This allows for targeted improvements, such as better software patching processes or more efficient hardware maintenance, which would be impossible with a single, blended metric.

Automating testing is a core tenet of continuous delivery and a 'shift-left' approach. By integrating automated tests into the pipeline, potential issues are caught early, reducing risk and providing the confidence needed to deploy changes rapidly.

In a high-velocity environment, centralizing all change authority is a bottleneck. Delegating authority for pre-approved, standard changes (often verified by automation) empowers teams and speeds up the delivery process, which is a key goal of modern change enablement.

Swarming is a collaborative approach where multiple stakeholders, including specialists (like L2/L3 engineers), work on an incident simultaneously from the beginning. This model is specifically designed to eliminate the delays and information loss associated with tiered escalations by bringing the right expertise to the problem immediately, which directly addresses the issue described.

The statement is false. The core purpose of SIAM is the opposite: to integrate the services from multiple suppliers into a single, seamless, end-to-end service for the business. It achieves this by coordinating suppliers within a unified governance framework and ensuring they work together to deliver value through a common value stream, not by isolating them.