ITIL 4 defines capability level 3 for a practice as achieving integration across the organization, where the practice is embedded into broader workflows and understood by related practices. For deployment management, an indication of reaching capability level 3 is when employees from other practices understand how deployment activities are integrated into relevant workflows (Option B). This demonstrates cross-functional alignment and maturity, showing that deployment management is not siloed but part of the organization's value streams.
Option A (The deployment management team regularly suggests and implements improvement opportunities): Incorrect, as continual improvement is characteristic of higher capability levels (e.g., level 4), not the defining feature of level 3.
Option B (Employees from other practices understand how deployment activities are integrated into relevant workflows): Correct, as level 3 focuses on integration and collaboration across practices, per ITIL 4's capability framework.
Option C (The deployment manager is able to report on the effectiveness of the deployment management practice): Incorrect, as reporting effectiveness is a general management task, not specific to level 3 maturity.
Option D (Deployment models are developed and implemented): Incorrect, as model development occurs at lower capability levels (e.g., level 1 or 2), not a hallmark of level 3.

ITIL 4 emphasizes that value streams are designed to deliver specific outcomes by integrating relevant management practices tailored to the context of services or products. For a large organization, creating several value streams that incorporate practices like change enablement, deployment management, and continual improvement (Option D) is the most effective approach. This allows flexibility to address different services or workflows while ensuring practices are embedded where needed, aligning with ITIL 4's value-driven and context-specific principles.
Option A (Create a separate value stream for each management practice): Incorrect, as this fragments processes and contradicts ITIL 4's holistic approach, where practices work together within value streams to deliver outcomes, not in isolation.
Option B (Create one combined value stream for change enablement and deployment management): Incorrect, as limiting to a single value stream for only two practices may not account for other necessary practices or varying service needs, reducing flexibility.
Option C (Create a single value stream that includes change enablement, deployment management, and other practices such as continual improvement): Incorrect, as a single value stream for all practices may become overly complex and fail to address diverse service requirements in a large organization.
Option D (Create several value streams that include change enablement, deployment management, and other practices such as continual improvement): Correct, as it reflects ITIL 4's guidance to design multiple value streams tailored to specific services or products, integrating relevant practices to optimize value delivery.

ITIL 4 emphasizes continual improvement in deployment management, which includes identifying and addressing inefficiencies in deployment models to enhance performance, reliability, and value delivery. Option D directly aligns with this principle by focusing on streamlining inefficient processes during model updates.
Option A (The impact of deployed software should not be considered when designing these models): Incorrect, as ITIL 4 stresses that the impact of deployments on services, users, and the organization is a critical consideration to ensure value and minimize disruption.
Option B (User resistance to updates is not a relevant factor to consider when designing deployment models): Incorrect, as user experience and acceptance are key factors in ITIL 4's value co-creation model, and resistance must be addressed to ensure successful deployments.
Option C (The same deployment approach should be used for deployments of similar size): Incorrect, as ITIL 4 advocates for context-specific deployment models tailored to the unique needs of each service or environment, not a one-size-fits-all approach.
Option D (Deployment model updates should consider inefficient processes): Correct, as improving deployment models involves analyzing current processes, identifying bottlenecks or waste, and optimizing workflows to deliver greater value.