nerdexam
PeopleCert

ITIL-4-CDS · Question #17

A service provider is redesigning its service management system using value stream management and mapping. The service management team is reviewing the role of practices in various value streams…

The correct answer is C. Deployment management plays an important role in any value stream requiring transition of. Option C is correct because in ITIL 4, Deployment Management's core purpose is moving any component (software, hardware, documentation, processes) to a target environment - this applies across multiple value streams, not just new service creation. Wherever a transition to an…

Understand how relevant ITIL practices contribute to creation, delivery and support across the SVS and value streams

Question

A service provider is redesigning its service management system using value stream management and mapping. The service management team is reviewing the role of practices in various value streams. There is an argument about the role of deployment management as software development and service management teams see its role differently. What is the BEST approach to define the role of deployment management practice in value streams?

Options

  • ADeployment management plays an important role in creation of new and changed services; it does
  • BDeployment management plays an important role only in creation of new services developed
  • CDeployment management plays an important role in any value stream requiring transition of
  • DDeployment management does not play any role in the incident resolution value stream

How the community answered

(31 responses)
  • A
    16% (5)
  • B
    6% (2)
  • C
    74% (23)
  • D
    3% (1)

Explanation

Option C is correct because in ITIL 4, Deployment Management's core purpose is moving any component (software, hardware, documentation, processes) to a target environment - this applies across multiple value streams, not just new service creation. Wherever a transition to an environment is needed - whether building a new service, releasing a change, or deploying an emergency hotfix during incident resolution - Deployment Management is relevant.

Why the distractors fail:

  • A is wrong because it artificially limits deployment management to "new and changed services," implying it has no role in incident resolution - but deploying a hotfix to resolve an incident is a classic deployment activity.
  • B is even more restrictive, limiting the practice to new services only, which excludes changes, patches, and emergency fixes entirely.
  • D is the most dangerous trap - it flatly denies any role in incident resolution, but emergency deployments (e.g., pushing a fix to production) are a direct example of deployment management supporting incident resolution.

Memory tip: Think of Deployment Management as the "logistics team" - any time something needs to be moved into an environment, they're involved, regardless of whether the reason is a new release, a change, or an emergency fix. If it crosses the boundary into a live (or test) environment, deployment management has a hand in it.

Topics

#deployment management#value streams#service transition#practice roles

Community Discussion

No community discussion yet for this question.

Full ITIL-4-CDS Practice