I85PREP
⌘ K
ITIL 4 Deployment Management study materials
ITIL 4 Deployment Management study resources

ITIL 4 Deployment Management practice questions

One question at a time. Build your ITIL 4 Deployment Management understanding.

First 50 of 199 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Deployment management concepts and scope

In ITIL 4, what is the primary purpose of the deployment management practice?

  1. To forecast future demand and plan capacity for services
  2. To move new or changed components into live environments and make them available to users Correct answer.
  3. To record and manage the financial value of IT assets
  4. To define and agree on service targets with customers through negotiation

Explanation

Deployment management focuses specifically on moving new or changed hardware, software, documentation, and other components into live environments, including production. It sits alongside release management, which controls the availability of features to users rather than the physical movement of components.

Question 2Deployment management concepts and scope

How does deployment management differ from release management in ITIL 4?

  1. Deployment management moves components into live environments, while release management makes features available to users Correct answer.
  2. Deployment management applies only to software, while release management applies only to hardware
  3. Deployment management controls when features become available to users, while release management moves components
  4. Deployment management is performed by external suppliers, while release management is performed internally

Explanation

The two practices are closely related but distinct: deployment is the technical act of moving components into an environment, whereas release is about making functionality available to users, which may happen at a different time. A single release can involve several deployments, and a deployment can occur without a release to users.

Question 3Deployment management concepts and scope

Which statement best describes a 'deployment environment' as used in deployment management?

  1. Any location where users physically work with the service
  2. The set of suppliers that provide infrastructure components
  3. A controlled area into which components are placed and where they are configured and tested Correct answer.
  4. The documentation describing the service catalogue

Explanation

Deployment environments are the controlled areas, such as test, staging, or production, into which components are deployed and where they are configured and validated. They are managed as part of the deployment management practice so that changes reach the right place in a controlled way.

Question 4Deployment management concepts and scope

A team deploys a new application version to a staging environment for testing before moving it to production. Which deployment approach pattern does this illustrate?

  1. A rollback of a failed release
  2. A big bang deployment into production
  3. A continuous deployment directly to users
  4. A phased deployment across multiple environments Correct answer.

Explanation

Moving components through successive environments such as staging and then production is a phased deployment pattern, where deployment occurs in stages rather than all at once. This reduces risk by allowing validation before components reach the live environment.

Question 5Deployment management concepts and scope

What is a 'big bang' deployment?

  1. Deploying components incrementally to a small pilot group first
  2. Deploying all components to the target environment at the same time Correct answer.
  3. Deploying components to a test environment only
  4. Deploying only documentation changes without software

Explanation

A big bang deployment moves all the relevant components into the target environment simultaneously rather than in stages. It is faster but carries higher risk because there is no gradual validation with a subset of components or users.

Question 6Deployment management concepts and scope

Why might an organization choose a phased deployment over a big bang deployment?

  1. To reduce the risk of a widespread failure by validating changes gradually Correct answer.
  2. To eliminate the need for any testing before production
  3. To guarantee that no users are affected by the change
  4. To avoid documenting the deployment plan

Explanation

Phased deployment limits the blast radius of a failure by exposing a subset of components or users first and validating before wider rollout. This gradual approach supports risk management and faster containment of issues.

Question 7Deployment management concepts and scope

What does 'rollback' mean in the context of deployment management?

  1. Transferring deployment tasks to a supplier
  2. Releasing a feature to a wider group of users
  3. Restoring the previous known-good state after a deployment problem Correct answer.
  4. Permanently removing a service from the catalogue

Explanation

Rollback is the planned reversal of a deployment, returning the environment to its last known-good state when the new components cause problems. Deployment plans typically include rollback or remediation steps so that service can be restored quickly.

Question 8Deployment management concepts and scope

Which item is most clearly within the scope of deployment management?

  1. Negotiating the service level agreement with a customer
  2. Deploying a patched database component into the production environment Correct answer.
  3. Auditing the financial accounts of the IT department
  4. Prioritizing a backlog of user stories

Explanation

Deployment management covers moving components such as patched software into live environments in a controlled manner. Activities like agreement negotiation, backlog prioritization, and financial auditing belong to other practices.

Question 9Deployment management concepts and scope

A deployment plan specifies the order in which components are installed and the checks performed after each step. Which concept does this best represent?

  1. A deployment procedure or plan that guides the controlled movement of components Correct answer.
  2. A service level objective for availability
  3. A risk register entry for supplier failure
  4. A capacity forecast for the coming year

Explanation

Deployment management relies on documented procedures and plans that define sequencing, checks, and responsibilities for moving components into an environment. This gives the deployment a controlled, repeatable path rather than an ad hoc action.

Question 10Deployment management concepts and scope

In ITIL 4, which practice works most closely with deployment management to ensure that new functionality is made available to users at the right time?

  1. Continual improvement
  2. Release management Correct answer.
  3. Problem management
  4. Supplier management

Explanation

Release management and deployment management are complementary: deployment moves components into environments, and release management coordinates making the resulting functionality available to users. The two are typically planned together so that technical readiness and user availability align.

Question 11Deployment management concepts and scope

What is the role of a 'known-good' baseline in deployment management?

  1. It records the training needs of deployment staff
  2. It defines the maximum number of users allowed on a service
  3. It lists the suppliers approved to deliver components
  4. It provides a reference state to which an environment can be restored if a deployment fails Correct answer.

Explanation

A known-good baseline captures a validated state of an environment or component set so that rollback can restore it if a deployment goes wrong. Having this reference reduces recovery time and uncertainty during remediation.

Question 12Deployment management concepts and scope

A deployment to production fails partway through and the service is degraded. According to good deployment management, what should happen next?

  1. Disable monitoring so that further alerts are not raised
  2. Execute the planned rollback or remediation steps to restore the known-good state Correct answer.
  3. Wait for the next scheduled release window before taking any action
  4. Continue deploying the remaining components to complete the change

Explanation

Deployment plans should include rollback or remediation actions so that a failed deployment can be reversed or corrected promptly. Continuing an unsuccessful deployment or delaying action increases the impact on users.

Question 13Deployment management concepts and scope

Which statement correctly describes the relationship between deployment and the change enablement practice?

  1. Change enablement authorizes changes, while deployment management executes the movement of components Correct answer.
  2. Deployment management authorizes changes, while change enablement executes them
  3. The two practices are identical and can be merged without distinction
  4. Deployment management replaces change enablement for all standard changes

Explanation

Change enablement assesses and authorizes changes, while deployment management carries out the physical or logical movement of components that the change requires. Keeping the authorization and execution roles distinct supports control and accountability.

Question 14Deployment management concepts and scope

What is a 'pilot' deployment?

  1. Deploying to a small, representative group before wider rollout Correct answer.
  2. Deploying without any prior testing
  3. Deploying only to the disaster recovery site
  4. Deploying to every user at once

Explanation

A pilot deployment introduces components to a limited, representative group so that behavior can be observed before a wider rollout. This pattern helps validate assumptions and reduce risk before full deployment.

Question 15Deployment management concepts and scope

Why is automation commonly used in deployment management?

  1. To ensure that changes never require authorization
  2. To eliminate the need for environments other than production
  3. To make deployments repeatable, consistent, and faster while reducing human error Correct answer.
  4. To remove the need for any deployment plan

Explanation

Automation supports deployment management by making the movement of components repeatable and consistent, which reduces manual error and speeds up delivery. It complements, rather than replaces, planning and authorization.

Question 16Deployment management concepts and scope

Which of the following best describes a 'deployment unit'?

  1. The person responsible for approving a change
  2. The group of components that are deployed together as a single coordinated action Correct answer.
  3. The budget allocated to a deployment project
  4. The environment in which users consume the service

Explanation

A deployment unit is the set of components deployed together in one coordinated action, which may span software, configuration, and documentation. Defining deployment units helps plan sequencing and rollback.

Question 17Deployment management concepts and scope

An organization wants to deploy a change to a critical service with minimal disruption during business hours. Which consideration is most relevant?

  1. The number of suppliers in the supply chain
  2. The deployment window and the impact on live users Correct answer.
  3. The historical revenue of the organization
  4. The colour scheme of the deployment dashboard

Explanation

Timing a deployment to minimize disruption involves selecting an appropriate deployment window and understanding the impact on live users. This is a core planning consideration in deployment management for critical services.

Question 18Deployment management concepts and scope

What distinguishes a deployment from a release in a scenario where code is installed on servers but the feature remains hidden behind a toggle?

  1. Neither a deployment nor a release has occurred
  2. The deployment has occurred, but the release to users has not yet happened Correct answer.
  3. The release has occurred, but the deployment has not yet happened
  4. Both deployment and release occur simultaneously by definition

Explanation

Installing the code is the deployment, while controlling whether users can access the feature is the release. Feature toggles allow deployment to proceed without immediately releasing functionality to users.

Question 19Deployment management concepts and scope

Which statement about deployment environments is most accurate?

  1. Each component must have its own dedicated environment
  2. Environments are irrelevant once automation is introduced
  3. Environments should be managed and controlled so that components reach the right place with the right configuration Correct answer.
  4. Production is the only environment relevant to deployment management

Explanation

Deployment management treats environments as controlled assets, ensuring components are placed and configured correctly in each. Multiple environments such as test, staging, and production are typically managed, and automation does not remove the need for that control.

Question 20Deployment management concepts and scope

What is the main benefit of maintaining a deployment record or log?

  1. It guarantees that deployments will never fail
  2. It replaces the need for change authorization
  3. It provides traceability of what was deployed, where, and when for audit and troubleshooting Correct answer.
  4. It removes the need to test components

Explanation

Deployment records give traceability, showing which components were deployed to which environments and when, which supports auditing and troubleshooting. They do not substitute for authorization, testing, or guarantee success.

Question 21Deployment management concepts and scope

A team uses a canary pattern where a small percentage of traffic is routed to the new version before full rollout. Which deployment objective does this primarily support?

  1. Eliminating the need for rollback plans
  2. Maximizing the number of users exposed as quickly as possible
  3. Avoiding the use of monitoring tools
  4. Reducing risk by observing behavior on a limited scale before wider exposure Correct answer.

Explanation

A canary pattern limits exposure to a small portion of traffic so that behavior can be observed before the change reaches everyone. This is a risk-reduction technique consistent with phased deployment thinking.

Question 22Deployment management concepts and scope

Which of these activities belongs to deployment management rather than to infrastructure and platform management?

  1. Provisioning a new physical server in the data centre
  2. Managing the lifecycle of the hypervisor platform
  3. Moving a configured application package into the production environment Correct answer.
  4. Monitoring the health of storage arrays

Explanation

Deployment management is concerned with moving components such as application packages into environments. Provisioning hardware, managing platform lifecycles, and monitoring infrastructure health are infrastructure and platform management activities.

Question 23Deployment management concepts and scope

Which factor most strongly influences the choice between big bang and phased deployment?

  1. The acceptable level of risk and the ability to validate changes incrementally Correct answer.
  2. The colour of the release packaging
  3. The number of pages in the deployment documentation
  4. The seniority of the deployment team leader

Explanation

The decision hinges on risk tolerance and whether the organization can validate changes in stages before full exposure. Higher risk and greater need for validation favor phased approaches, while low-risk, well-understood changes may suit big bang.

Question 24Deployment management concepts and scope

What does 'deployment management' typically NOT include?

  1. Planning rollback actions for failed deployments
  2. Coordinating the movement of components between environments
  3. Deciding the strategic direction of the organization Correct answer.
  4. Verifying that components are correctly placed and configured

Explanation

Deployment management covers coordinating component movement, verifying correct placement and configuration, and planning rollback. Setting the strategic direction of the organization is a governance and strategy activity outside its scope.

Question 25Deployment management concepts and scope

Which statement best captures why deployment management is important to service value?

  1. It guarantees that every change will improve service performance
  2. It ensures that changes reach live environments reliably, supporting service availability and user outcomes Correct answer.
  3. It removes the need for service level agreements
  4. It replaces the need for continual improvement

Explanation

Reliable deployment ensures that new or changed components reach live environments as intended, which underpins availability and the value users receive. It supports, but does not guarantee, performance improvement and does not replace other practices.

Question 26Deployment management concepts and scope

In ITIL 4, which statement best describes the purpose of the deployment management practice?

  1. To authorize changes and assess their risk before work begins
  2. To negotiate and agree service levels with customers
  3. To make new or changed services, components, and related artefacts available in the live environment Correct answer.
  4. To manage the financial value of IT services across their lifecycle

Explanation

Deployment management exists to move services, components, and artefacts into the target environments, including live, so that they can be used. It focuses on the mechanics of placement and verification rather than on authorization or commercial agreements.

Question 27Deployment management concepts and scope

A service provider installs and configures an updated payment component on production servers but leaves the related customer-facing feature switched off. Which statement is correct?

  1. The component has been neither deployed nor released
  2. The component has been both deployed and released
  3. The component has been deployed but not released to users Correct answer.
  4. The component has been released but not deployed

Explanation

Deployment concerns placing components into an environment, while release concerns making functionality available for use. Installing the component but keeping the feature disabled separates the two activities clearly.

Question 28Deployment management concepts and scope

Which outcome is the strongest evidence that deployment management is contributing to value creation?

  1. The organization holds fewer change advisory board meetings each quarter
  2. Individual engineers gain broader technical knowledge of the tooling
  3. Changes reach the live environment predictably, with fewer failed deployments and faster restoration when problems occur Correct answer.
  4. The number of documented policies in the service management system increases

Explanation

Deployment management adds value by making the movement of components into live environments reliable and recoverable. Predictable success rates and quick recovery from failed deployments are direct indicators of that contribution.

Question 29Deployment management concepts and scope

Which activity is normally performed as part of deployment management?

  1. Defining the utility and warranty requirements for a new service
  2. Transferring, installing, and configuring components in a target environment and verifying they work there Correct answer.
  3. Deciding whether a proposed change should be approved
  4. Resolving user incidents caused by a failed deployment

Explanation

Deployment management covers the transfer, installation, configuration, and verification of components in the intended environment. The other activities belong to different practices that interact with deployment but are not part of it.

Question 30Deployment management concepts and scope

An organization operates a highly regulated environment where every deployment step must be evidenced to auditors. Which deployment management consideration is most relevant?

  1. Delegating deployment decisions to the development team without documentation
  2. Ensuring deployment records capture each step, its result, and who performed it Correct answer.
  3. Shortening the deployment window by skipping post-deployment verification
  4. Reducing the number of environments to simplify the pipeline

Explanation

Where evidence is required, deployment management must produce records that show what was done, by whom, and with what result. Verification cannot be skipped because it is part of the evidence chain.

Question 31Deployment management concepts and scope

Which pair of practices most directly supplies deployment management with the artefacts and target environments it needs?

  1. Service desk and service request management
  2. Continual improvement and measurement and reporting
  3. Release management and infrastructure and platform management Correct answer.
  4. Supplier management and service financial management

Explanation

Release management defines what functionality is made available, and infrastructure and platform management provides and maintains the environments into which components are deployed. These two practices are the closest operational partners for deployment work.

Question 32Deployment management concepts and scope

What is the primary reason deployment management distinguishes between environments such as development, test, and production?

  1. Each environment must use a different deployment tool
  2. Environments exist to allow parallel versions of the service catalogue
  3. Each environment has different purposes, controls, and acceptable levels of risk Correct answer.
  4. Environments are only needed when an organization uses cloud hosting

Explanation

Separate environments let components be built, validated, and finally exposed to real users under controls suited to each stage of risk. The distinction is about purpose and control, not about tools or hosting model.

Question 33Deployment management concepts and scope

A deployment engineer discovers that the approved deployment plan omits a step needed to stop a dependent service before installation. What is the most appropriate action?

  1. Abandon the deployment and revert the change request to draft
  2. Continue the installation and document the missing step afterwards
  3. Improvise the missing step and note it in a personal log
  4. Pause, raise the discrepancy through the change and deployment governance route, and update the plan before continuing Correct answer.

Explanation

Deployment must follow the authorized plan; when reality diverges, the divergence is handled through the established governance route so that risk is assessed and the plan is corrected. Improvising silently removes the control the plan was meant to provide.

Question 34Deployment management concepts and scope

Which statement about the relationship between deployment management and continual improvement is most accurate?

  1. Improvement of deployment is only possible after a major incident
  2. Deployment data such as failure rates and lead times can feed improvement opportunities for the practice Correct answer.
  3. Deployment management cannot be improved because it is purely technical
  4. Continual improvement owns all deployment activities and directs engineers

Explanation

Deployment produces measurable data, and that data can be used to identify and prioritize improvements to the practice itself. Continual improvement provides the method, but deployment management remains accountable for its own activities.

Question 35Deployment management concepts and scope

Which of the following is most clearly outside the scope of deployment management?

  1. Moving a tested component into a staging environment
  2. Deciding the commercial terms under which a supplier will host a service Correct answer.
  3. Verifying that a deployed component starts correctly
  4. Recording the outcome of an installation step

Explanation

Deployment management is concerned with placing and verifying components in environments. Commercial negotiation with suppliers belongs to supplier management and related commercial practices.

Question 36Deployment management concepts and scope

A team deploys the same component to two regions, one after the other, with a verification gate between them. Which deployment characteristic does this illustrate?

  1. A big bang approach that completes in a single step
  2. A phased approach that limits the blast radius of a failure Correct answer.
  3. A release that makes functionality available to all users at once
  4. A rollback that restores the previous version

Explanation

Sequencing deployments across regions with checks in between is a phased approach, which contains the impact if something goes wrong. It is not a single-step rollout, and no reversion has occurred.

Question 37Deployment management concepts and scope

Which factor most strongly supports automating a deployment that runs several times a day?

  1. Automation guarantees that the deployed component has no defects
  2. Automation removes the need to authorize changes before deployment
  3. Automation eliminates the need for any post-deployment verification
  4. Repetition makes manual steps slow and prone to inconsistency, while automation gives repeatable results Correct answer.

Explanation

Frequent repetition magnifies the cost and variability of manual steps, so automation provides consistency and speed. It does not replace change authorization, remove defects, or make verification unnecessary.

Question 38Deployment management concepts and scope

An organization must deploy an urgent security fix to a service used around the clock. Which consideration should weigh most heavily in the deployment approach?

  1. The preference of the deployment tool vendor for big bang rollouts
  2. The number of people available to attend a deployment meeting
  3. The length of the deployment plan document
  4. The risk of the fix versus the risk of leaving the vulnerability unaddressed, given the service's availability needs Correct answer.

Explanation

Urgent fixes require balancing the exposure created by the vulnerability against the disruption a deployment may cause to a continuously used service. Staffing, vendor preferences, and document length are secondary to that risk trade-off.

Question 39Deployment management concepts and scope

What distinguishes a deployment package from a single component in deployment management terms?

  1. A deployment package is any component that has been tested at least once
  2. A deployment package is the document that authorizes a change
  3. A deployment package groups components that must be deployed together to deliver a coherent outcome Correct answer.
  4. A deployment package is the set of users who will receive a release

Explanation

A deployment package is a set of components that are deployed as a coordinated unit because they depend on each other. Testing history, user groups, and change authorization are separate concepts.

Question 40Deployment management concepts and scope

A deployment is planned for a component that has never been deployed to the target environment before. Which precaution is most defensible?

  1. Ask the service desk to handle any problems after the deployment
  2. Proceed directly to production because rehearsal delays the change
  3. Rehearse the deployment in a comparable non-production environment and confirm rollback works there Correct answer.
  4. Deploy without a rollback plan because the component is new

Explanation

A first-time deployment carries unknown behaviour, so rehearsing in a comparable environment and proving the rollback path reduces risk before live exposure. Skipping these steps transfers avoidable risk to users.

Question 41Deployment management processes and activities

Which statement best distinguishes deployment from release in ITIL 4?

  1. Deployment moves components into the live environment, while release makes the service available to users Correct answer.
  2. Deployment is a governance activity, while release is a technical activity performed by developers
  3. Deployment applies only to infrastructure, while release applies only to applications
  4. Deployment and release are synonyms and the terms may be used interchangeably

Explanation

Deployment concerns placing components into the live environment, whereas release concerns making the service and its features available for use by the consumer. A component can be deployed without being released, for example when it is installed but not yet enabled for users.

Question 42Deployment management processes and activities

A team installs a new version of an application onto production servers but keeps it disabled behind a feature flag so users cannot access it yet. Which statement describes this situation in ITIL 4 terms?

  1. The component has been released but not deployed
  2. The component has been neither deployed nor released
  3. The component has been both deployed and released
  4. The component has been deployed but not released Correct answer.

Explanation

Deployment places the component in the live environment, while release makes it available to users. Installing the software with the feature disabled is deployment without release, which is a common technique for decoupling the two practices.

Question 43Deployment management processes and activities

Which deployment approach involves moving all affected components to the new version at the same time and then switching users over together?

  1. Canary deployment
  2. Phased deployment
  3. Big bang deployment Correct answer.
  4. Continuous deployment

Explanation

A big bang deployment replaces everything at once and switches users over in a single step. It is simple to coordinate but carries high risk because there is no gradual exposure or easy partial rollback.

Question 44Deployment management processes and activities

An organization deploys a new service to a small group of users in one region, verifies stability, then extends it to further regions. Which deployment approach is being used?

  1. Pull deployment
  2. Phased deployment Correct answer.
  3. Blue/green deployment
  4. Big bang deployment

Explanation

Phased deployment introduces the change in stages, for example by user group, location or component, so that issues are detected before wider exposure. It reduces risk compared with an all-at-once switch but lengthens the overall transition.

Question 45Deployment management processes and activities

What is the defining characteristic of a blue/green deployment pattern?

  1. Deployment is performed manually by the service desk on request
  2. All users are moved to the new version simultaneously with no fallback environment
  3. Components are installed only when the user requests them from a repository
  4. Two identical environments are maintained and traffic is switched from one to the other Correct answer.

Explanation

Blue/green deployment keeps two production-like environments so that the new version can be prepared and tested in one while the other serves users. Traffic is then switched, and if problems arise it can be switched back quickly.

Question 46Deployment management processes and activities

Which deployment pattern delivers the change to a small subset of users or traffic before widening it to the whole population?

  1. Big bang deployment
  2. Manual deployment
  3. Phased deployment by component
  4. Canary deployment Correct answer.

Explanation

Canary deployment exposes only a small, controlled portion of users or traffic to the new version so that behaviour can be observed before full rollout. It limits blast radius and supports fast reversal if metrics degrade.

Question 47Deployment management processes and activities

Why does ITIL 4 recommend that deployment be automated through a pipeline where possible?

  1. It eliminates the need for a configuration management database
  2. It guarantees that no deployment will ever fail
  3. It improves repeatability and speed while reducing the chance of human error Correct answer.
  4. It removes the need for any change enablement authorization

Explanation

Automation makes deployments repeatable, faster and less error-prone, and it produces consistent evidence of what was deployed. It supports, but does not replace, change authorization or configuration record keeping.

Question 48Deployment management processes and activities

A deployment fails during execution and the team restores the previous version of the component. What is this activity called?

  1. Continual improvement
  2. Backout plan approval
  3. Rollback Correct answer.
  4. Release

Explanation

Rollback restores the previous known-good state after a failed deployment. It should be planned in advance, together with the criteria that trigger it, so that recovery is fast and predictable.

Question 49Deployment management processes and activities

What should be defined before a deployment proceeds so that a failed change can be reversed safely?

  1. A revised organizational chart for the operations team
  2. A backout or rollback plan with defined trigger criteria Correct answer.
  3. A marketing communication plan for end users
  4. A new service level agreement for the changed component

Explanation

A backout plan describes how to return to the previous state and the conditions that trigger it. Defining trigger criteria in advance prevents indecision during an incident and keeps recovery within agreed timeframes.

Question 50Deployment management processes and activities

Which item is a typical input to the deployment management practice?

  1. Approved change requests and the release plan Correct answer.
  2. The organization's recruitment plan
  3. The service catalogue entry for an unrelated service
  4. Customer satisfaction survey results

Explanation

Deployment work is triggered by authorized changes and coordinated with the release plan so that components are placed into the live environment at the right time. Other inputs include configuration information and deployment specifications.