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

ITIL 4 Release Management practice questions

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

First 50 of 200 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 1Release Management

In ITIL 4, which definition best describes a release?

  1. A routine change implemented by a self-organizing team without approval
  2. A temporary organization created to deliver a defined output
  3. A documented description of a service designed to meet agreed requirements
  4. A version of a service or other configuration item, or a collection of configuration items, made available for use Correct answer.

Explanation

ITIL 4 defines a release as a version of a service or other configuration item, or a collection of configuration items, made available for use. A release may include infrastructure, software, documentation and configuration, and it becomes meaningful only when it is made available to users.

Question 2Release Management

What is the primary purpose of the release management practice in ITIL 4?

  1. To restore normal service operation after an incident
  2. To negotiate and agree service targets with customers
  3. To make new and changed services and features available for use Correct answer.
  4. To control financial spend on IT assets and services

Explanation

The purpose of release management is to make new and changed services and features available for use. It focuses on the effective deployment of releases into the live environment so that value can be realized by users.

Question 3Release Management

Which practice is most directly responsible for moving new or changed components into the live environment?

  1. Service catalogue management
  2. Problem management
  3. Deployment management Correct answer.
  4. Supplier management

Explanation

Deployment management is concerned with moving new or changed hardware, software, documentation, processes or other components to live environments. Release management then makes the assembled release available for use, so the two practices are closely related but distinct.

Question 4Release Management

What is a release unit?

  1. The components of a service that are normally released together Correct answer.
  2. The approval body that authorizes a release to go live
  3. The number of users who receive a release at the same time
  4. The environment in which a release is tested before deployment

Explanation

A release unit is the set of components of a service that are normally released together. Defining release units helps balance the effort of packaging and testing against the benefit of delivering changes in manageable chunks.

Question 5Release Management

A service provider wants to deliver a release to a small pilot group before exposing it to all users. Which release approach does this describe?

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

Explanation

A phased approach delivers the release to a subset of users or locations first, then expands to the rest. This limits the blast radius of defects and allows learning before full exposure.

Question 6Release Management

Which statement correctly distinguishes release management from deployment management?

  1. Deployment management only applies to hardware, while release management only applies to software.
  2. Release management and deployment management are the same practice under two names.
  3. Release management makes services available for use; deployment management moves components into environments. Correct answer.
  4. Release management moves components to live; deployment management makes them available to users.

Explanation

Release management makes new and changed services and features available for use, while deployment management moves components into environments. The two practices cooperate but have different scopes and outcomes.

Question 7Release Management

Why should release plans be aligned with the change enablement practice?

  1. Because releases are only permitted during major incidents
  2. Because releases typically require authorization before they are deployed into live environments Correct answer.
  3. Because change enablement owns the release budget
  4. Because change enablement defines the service catalogue entries

Explanation

Releases usually involve changes to live services, so they need authorization through change enablement. Aligning release plans with change schedules and authorities prevents unauthorized or conflicting deployments.

Question 8Release Management

What is the main purpose of a release note?

  1. To record the root cause of a major incident
  2. To define the service level targets for the release
  3. To authorize the release on behalf of the change authority
  4. To communicate what is included in a release and any known issues or actions required Correct answer.

Explanation

Release notes inform users and support staff about the content of a release, including features, fixes, known errors and required actions. Clear release notes reduce confusion and support calls after deployment.

Question 9Release Management

An organization runs a critical payment service. The release manager wants to minimize the impact of a failed release on all customers. Which approach best supports this goal?

  1. Deploy the release to a limited group first and expand after validation Correct answer.
  2. Skip testing to reduce the time the service is at risk
  3. Deploy the release without release notes to avoid alarming customers
  4. Deploy the release to all customers simultaneously to shorten the change window

Explanation

A phased rollout to a limited group lets the organization validate the release in production with reduced impact before expanding. This contains the blast radius if defects appear and allows rollback with fewer affected users.

Question 10Release Management

A team wants to decouple deployment from release so that code can be deployed to production frequently while features are activated only when business-ready. Which technique supports this?

  1. Manual regression testing
  2. Big bang cutover
  3. Feature toggles Correct answer.
  4. Change freeze windows

Explanation

Feature toggles allow code to be deployed while controlling whether the associated functionality is visible to users. This decouples technical deployment from business release timing and supports lower-risk, incremental delivery.

Question 11Release Management

What is the primary role of a release policy?

  1. To describe each individual change request in detail
  2. To set the rules and responsibilities governing how releases are planned, built, tested and deployed Correct answer.
  3. To list the names of all users authorized to access production
  4. To record the outcome of every incident linked to a release

Explanation

A release policy defines the rules, roles, responsibilities and criteria for how releases are managed across the organization. It provides consistent governance so that individual releases do not each invent their own approach.

Question 12Release Management

Which metric best indicates whether release management is achieving its purpose?

  1. The number of change requests rejected by the change authority
  2. The number of configuration items recorded in the CMDB
  3. The average time to resolve supplier disputes
  4. The percentage of releases delivered successfully without causing incidents Correct answer.

Explanation

Release management aims to make services and features available for use effectively, so successful release delivery without causing incidents is a direct indicator. Metrics should reflect release outcomes and their effect on live services.

Question 13Release Management

A release includes a database schema change that cannot be easily reversed. What should the release plan include before deployment?

  1. A commitment to deploy the release during peak business hours
  2. A plan to notify customers only after the release fails
  3. An agreement to skip the change authorization step
  4. A documented rollback or rollback mitigation plan and tested backup and recovery steps Correct answer.

Explanation

When a release cannot be cleanly reversed, the plan must define how to recover, such as restoring backups or applying forward-fix mitigations. Testing these steps before deployment reduces the risk of prolonged outage.

Question 14Release Management

Which statement best describes a pull-based release approach?

  1. The release is deployed only during a declared major incident
  2. Users choose when to adopt the release, often within a supported window Correct answer.
  3. The release is deployed without any communication to users
  4. The provider pushes the release to all users at a fixed date

Explanation

In a pull approach, users decide when to take up the release, typically within a defined support window. This can reduce disruption for user communities but requires the provider to maintain multiple supported versions.

Question 15Release Management

Why does release management depend on configuration management?

  1. Because accurate configuration data identifies the components, versions and dependencies included in a release Correct answer.
  2. Because configuration management resolves incidents caused by releases
  3. Because configuration management authorizes releases on behalf of the change authority
  4. Because configuration management negotiates service level targets for releases

Explanation

Release planning needs reliable information about which configuration items and versions make up the release and how they depend on one another. Configuration management provides that accurate baseline, which supports impact assessment and rollback.

Question 16Release Management

What is the main benefit of defining clear release units?

  1. It removes the need for change authorization
  2. It guarantees that no release will ever cause an incident
  3. It balances packaging and testing effort against the benefit of delivering changes together Correct answer.
  4. It eliminates the need for testing before deployment

Explanation

Choosing release units involves a trade-off between the effort of packaging and testing and the value of delivering related changes together. Well-defined units make releases manageable without excessive overhead.

Question 17Release Management

A release fails validation in the pre-production environment. What is the most appropriate immediate action for the release manager?

  1. Hold the release, record the failure and route the defect for correction before re-validation Correct answer.
  2. Cancel the release permanently and close all related change records
  3. Notify customers that the release has been delivered successfully
  4. Deploy to production anyway and monitor for issues

Explanation

A failed validation should stop the release from progressing and trigger correction and re-testing. Recording the failure and routing the defect preserves traceability and prevents a known-bad release from reaching production.

Question 18Release Management

Which practice combination most directly supports an integrated release pipeline from build to live?

  1. Problem management and knowledge management
  2. Service financial management and demand management
  3. Release management, deployment management and change enablement Correct answer.
  4. Capacity and performance management and availability management

Explanation

Release management coordinates making services available, deployment management moves components into environments, and change enablement authorizes changes to live services. Together they form the governance and execution chain for releases.

Question 19Release Management

What is the purpose of a release calendar?

  1. To coordinate planned releases and avoid conflicting changes to shared services and environments Correct answer.
  2. To record the working hours of release team members
  3. To record supplier contract renewal dates
  4. To list all configuration items in the CMDB

Explanation

A release calendar coordinates planned releases so that teams avoid collisions in shared services and environments. It supports planning, communication and conflict avoidance across multiple release streams.

Question 20Release Management

An organization wants to increase release frequency while maintaining stability. Which combination of practices is most relevant?

  1. Incident management with problem management only
  2. Release management with automated testing and deployment pipelines Correct answer.
  3. Service financial management with demand management
  4. Access management with service catalogue management

Explanation

Higher release frequency with stability depends on release management supported by automated testing and deployment pipelines. Automation reduces manual error and shortens feedback cycles, enabling smaller and safer releases.

Question 21Release Management

A release manager is told that a release must go live during a company-wide change freeze. What is the most appropriate response?

  1. Escalate for an exception decision through change enablement and document the justification Correct answer.
  2. Deploy the release quietly without informing the change authority
  3. Cancel the release and delete all related records
  4. Deploy the release as planned because release plans override change freezes

Explanation

Change freezes are governance controls managed through change enablement, so any exception must be authorized through that route with documented justification. Proceeding without authorization undermines the control and creates unmanaged risk.

Question 22Release Management

An organization operates a multi-tenant SaaS platform where tenants receive releases on different schedules. Which consideration is most important for the release manager?

  1. Deploying each tenant release without testing to save time
  2. Preventing tenants from ever receiving release notes
  3. Ensuring all tenants are always on the same version to simplify support
  4. Managing version support windows and compatibility across tenant versions Correct answer.

Explanation

When tenants receive releases on different schedules, the provider must manage which versions remain supported and ensure compatibility across them. This requires clear support windows, documentation and testing across versions.

Question 23Release Management

A critical release must be deployed outside normal hours to restore a degraded service. Which change type and release consideration apply?

  1. A standard change with a pre-approved template and no post-implementation review
  2. A normal change that can wait for the next scheduled change advisory board meeting
  3. No change authorization is needed because service is already degraded
  4. An emergency change authorized through the emergency change process with a defined rollback plan Correct answer.

Explanation

Restoring a degraded service urgently typically requires an emergency change, authorized through the emergency change process. The release should still include a rollback plan and post-implementation review to manage and learn from the risk.

Question 24Release Management

A release introduces a change that affects a service consumed by multiple internal teams with different risk tolerances. How should the release manager decide the rollout strategy?

  1. Use a big bang deployment because it is the simplest to administer
  2. Deploy to all groups without communication to avoid debate
  3. Assess impact and risk per consumer group and agree a phased approach with appropriate communication Correct answer.
  4. Apply the strategy preferred by the team with the loudest objection

Explanation

Where consumers have differing risk tolerances, the release manager should assess impact and risk for each group and agree a phased approach. Tailored communication and sequencing address the concerns of each group while maintaining overall delivery.

Question 25Release Management

Which statement best explains why release management should be integrated with continual improvement?

  1. Because release outcomes and post-implementation reviews provide evidence to refine release processes and reduce future risk Correct answer.
  2. Because releases are the only source of improvement opportunities in an organization
  3. Because continual improvement eliminates the need to test releases
  4. Because continual improvement replaces the need for change authorization

Explanation

Post-implementation reviews and release outcome data reveal where release processes can be improved, such as testing gaps or communication failures. Feeding these findings into continual improvement reduces risk and increases the effectiveness of future releases.

Question 26Release Management

In ITIL 4, which definition best captures the scope of the release management practice?

  1. Building and testing components before they are handed over
  2. Making new and changed services and features available for use Correct answer.
  3. Recording and reporting the financial value of services
  4. Negotiating service level agreements with customers

Explanation

Release management is defined as the practice of making new and changed services and features available for use. It focuses on the act of making something available to users, not on constructing it or on commercial and financial administration.

Question 27Release Management

Which practice is responsible for moving new or changed components into a live environment?

  1. Service validation and testing
  2. Release management
  3. Deployment management Correct answer.
  4. Incident management

Explanation

Deployment management concerns moving new or changed hardware, software, documentation, processes or other components to live environments. Release management then makes those deployed components available for use, so the two practices are related but distinct.

Question 28Release Management

What does a release unit describe?

  1. The number of users allowed to access a new feature
  2. The team that approves emergency changes
  3. The maximum time a release may remain in testing
  4. The set of components that are released together as a single package Correct answer.

Explanation

A release unit is the set of components that are released together, chosen according to how the service is structured and how much change can be absorbed at once. Defining release units helps balance release frequency against risk and effort.

Question 29Release Management

Which statement reflects a push-based approach to release?

  1. Users decide when to adopt each new version from a repository
  2. New versions are made available to users at a time chosen by the provider Correct answer.
  3. Releases are triggered automatically by monitoring alerts
  4. Releases are only performed when a user raises a request

Explanation

In a push-based approach the provider decides when to make the release available, so users receive the new version on the provider's schedule. A pull-based approach instead lets users choose when to take the new version.

Question 30Release Management

What is the purpose of a release note?

  1. To inform users about the content, timing and impact of a release Correct answer.
  2. To define the service level targets for the coming year
  3. To record the approval history of every change request
  4. To list the individual staff members who built the release

Explanation

Release notes communicate to users and support staff what is included in a release, when it becomes available and what impact it may have. They support adoption and reduce avoidable incidents caused by unexpected changes.

Question 31Release Management

Which item is typically recorded in a release record?

  1. The marketing budget for the service
  2. The salary band of the release manager
  3. The release unit, the components included and the planned date Correct answer.
  4. The personal contact details of every user

Explanation

A release record identifies what is being released, which components form the release unit and when the release is planned. It provides the traceable link between the release and the configuration items it contains.

Question 32Release Management

Why is a release calendar useful to an organization?

  1. It stores the source code for each release
  2. It guarantees that no release will ever fail
  3. It shows planned releases so that dependencies and conflicts can be coordinated Correct answer.
  4. It replaces the need for change authorization

Explanation

A release calendar gives visibility of upcoming releases, allowing teams to coordinate dependencies, avoid clashes and align with other activities such as change windows. It supports planning rather than guaranteeing outcomes or replacing other controls.

Question 33Release Management

Which pair of practices most directly enables a release to be made available to users in a controlled way?

  1. Supplier management and service financial management
  2. Release management and change enablement Correct answer.
  3. Knowledge management and relationship management
  4. Capacity and performance management and workforce planning

Explanation

Release management makes services available, while change enablement authorizes the changes that releases introduce. Together they ensure releases happen with proper assessment and approval.

Question 34Release Management

A service provider wants users to adopt a new client application only after their own internal testing is complete. Which release approach fits this requirement?

  1. A pull-based release where users take the new version when ready Correct answer.
  2. A push-based release that forces the update on a fixed date
  3. A release that is never announced to users
  4. A release performed only during major incidents

Explanation

A pull-based approach lets users decide when to adopt the new version, which suits customers who need to test before rollout. A push-based approach would impose the provider's timing on them and conflict with their internal validation.

Question 35Release Management

A release manager must decide how to package changes to a large monolithic application so that risk is limited. What is the most appropriate action?

  1. Bundle all pending changes into one annual release
  2. Delegate the decision entirely to end users
  3. Release every change individually regardless of dependencies
  4. Define release units that group components with similar risk and dependencies Correct answer.

Explanation

Release units should be defined so that components with similar risk, dependencies and change cadence travel together, which limits blast radius while keeping coordination manageable. Releasing everything at once or in isolation ignores dependency and risk factors.

Question 36Release Management

During a release, a feature is deployed to production but must remain hidden from users until a marketing launch date. Which approach supports this?

  1. Ask users to avoid the feature until launch
  2. Deploy the feature to a test environment only
  3. Delay the deployment until the launch date
  4. Decouple deployment from release using a feature toggle Correct answer.

Explanation

Decoupling deployment from release allows code to be deployed while availability to users is controlled separately, for example with a feature toggle. This lets the organization deploy early and release at the chosen moment without redeploying.

Question 37Release Management

A release plan shows that a new version depends on an interface change owned by another team. What should the release manager do first?

  1. Remove the dependency from the plan without consultation
  2. Confirm the dependency and its delivery date with the owning team Correct answer.
  3. Cancel the release permanently
  4. Proceed with the release and fix the interface afterwards

Explanation

Dependencies between release components must be validated with the teams that own them so that dates and interfaces align. Confirming the dependency early prevents a failed release caused by an unavailable prerequisite.

Question 38Release Management

A release includes a database migration that cannot be rolled back quickly. What should the release plan provide before go-live?

  1. A promise that the migration will succeed
  2. A tested recovery or restore approach and a defined decision point Correct answer.
  3. A shortened testing window to save time
  4. An instruction to ignore backups during the release

Explanation

When a change cannot be easily reversed, the plan must include a tested recovery path and a clear decision point for invoking it. This limits the impact of failure and gives approvers the information they need.

Question 39Release Management

A team releases frequently but users report that they are surprised by changes. Which release management improvement addresses this most directly?

  1. Increase the number of deployments per day
  2. Reduce testing to speed up releases
  3. Publish clear release notes and a visible release schedule Correct answer.
  4. Remove change authorization for all releases

Explanation

Surprise among users indicates a communication gap, so clearer release notes and a visible schedule address the root cause. Increasing deployment volume or weakening controls would not improve user awareness and could increase disruption.

Question 40Release Management

An organization wants to release a multi-tenant SaaS platform where tenants have different contractual upgrade windows. What should the release approach support?

  1. Scheduling availability of the same release per tenant Correct answer.
  2. Manual rebuilds of the platform for each tenant
  3. A single global release date for all tenants
  4. Permanent divergence of the codebase per tenant

Explanation

When tenants have different contractual windows, the release approach must schedule availability of the same release per tenant rather than forcing one global date. This preserves a common codebase while honoring contractual timing.

Question 41Release Management

A release introduces a change that several internal teams consume with different risk tolerances. How should the release manager proceed?

  1. Agree a staged rollout with each consumer team and confirm acceptance criteria Correct answer.
  2. Let the most risk-averse team block the release indefinitely
  3. Release to all teams simultaneously without consultation
  4. Release only to the team with the lowest risk tolerance

Explanation

Where consumers differ in risk tolerance, a staged rollout with agreed acceptance criteria balances delivery speed against each team's tolerance. Simultaneous release ignores those differences, while indefinite blocking or releasing to only one team fails the others.

Question 42Release Management

What distinguishes a release from a deployment in ITIL 4 terms?

  1. A release makes a service available for use, while a deployment moves components to a live environment Correct answer.
  2. A release moves components to live, while a deployment makes them available for use
  3. A release is always larger in scope than a deployment
  4. A release requires no change authorization, while a deployment does

Explanation

Deployment is the movement of components into a live environment, whereas release is the act of making the resulting service or feature available for use. The two can occur together or be separated, for example by feature toggles.

Question 43Release Management

A release manager notices that releases are frequently delayed because environments are unavailable. Which action best addresses the underlying cause?

  1. Shorten release notes to save time
  2. Add more approvers to the change process
  3. Increase the number of release candidates
  4. Agree environment booking and readiness as part of release planning Correct answer.

Explanation

Delays caused by unavailable environments point to a planning gap, so agreeing environment booking and readiness during release planning addresses the cause. Adding approvers or release candidates would add overhead without fixing availability.

Question 44Release Management

Which statement explains why release management should be integrated with continual improvement?

  1. Release management should only improve after a major outage
  2. Release outcomes and feedback should feed improvements to the release approach itself Correct answer.
  3. Continual improvement removes the need for release planning
  4. Continual improvement replaces release management over time

Explanation

Continual improvement uses feedback and measurement to refine how work is done, so release outcomes should inform improvements to the release approach. This creates a learning loop that raises release quality over time.

Question 45Release Management

A release must be deployed outside normal hours to restore a degraded critical service. Which combination is most appropriate?

  1. An emergency change authorized through change enablement with an expedited release Correct answer.
  2. A normal change scheduled for the next quarterly window
  3. A standard change pre-approved for routine low-risk work
  4. No change record, because the release is urgent

Explanation

Restoring a degraded critical service calls for an emergency change authorized through the change enablement practice, with the release expedited to match. Standard change is for pre-authorized low-risk work, and a quarterly window is too slow for a degraded service.

Question 46Release Management

An organization wants to increase release frequency while keeping stability. Which measure best supports this goal?

  1. Require manual approval for every individual deployment step
  2. Reduce the number of environments to simplify coordination
  3. Increase automated testing and deployment automation so smaller releases can be validated quickly Correct answer.
  4. Remove release notes to shorten the release cycle

Explanation

Higher frequency with maintained stability depends on fast, reliable validation, which automation of testing and deployment provides. Fewer environments, less communication or more manual gates would add risk or delay rather than enable safe frequent releases.

Question 47Release Management

A release fails validation in the pre-production environment shortly before the planned go-live. What is the most appropriate immediate action?

  1. Hold the release, record the failure and assess options with the release authority Correct answer.
  2. Proceed to production and monitor for the same failure
  3. Silently postpone the release without informing stakeholders
  4. Roll back the pre-production environment and declare success

Explanation

A validation failure means the release has not met its exit criteria, so it should be held while the failure is recorded and options are assessed with the release authority. Proceeding to production would carry a known defect into live service.

Question 48Release Management

A release manager is asked to release during a company-wide change freeze. What is the most appropriate response?

  1. Ignore the freeze and document it afterwards
  2. Escalate the request for an explicit exception decision by the change authority Correct answer.
  3. Cancel all releases for the rest of the year
  4. Quietly proceed because release management outranks change enablement

Explanation

A change freeze is a control set by the change authority, so any exception must be decided explicitly by that authority with the associated risk understood. Proceeding quietly or ignoring the freeze undermines the control, while cancelling all releases for the year is disproportionate.

Question 49Release Management

A release manager must choose a release model for a service used by regulated customers who require documented, auditable changes. Which consideration should drive the choice?

  1. The assumption that regulation never affects release timing
  2. The preference for the fastest possible release cadence regardless of evidence
  3. The desire to avoid recording release decisions
  4. The need for traceable evidence and formal acceptance at each release stage Correct answer.

Explanation

For regulated customers, the release model must produce traceable evidence and formal acceptance at each stage so that compliance can be demonstrated. Prioritizing speed without evidence or avoiding records would create compliance and audit risk.

Question 50Release Management

In ITIL 4 release management, what does the term 'release' specifically refer to?

  1. A version of a service or other configuration item made available for use Correct answer.
  2. The automated build of source code into deployable artefacts
  3. The approval of a request for change by the change authority
  4. The physical transfer of infrastructure into a data centre

Explanation

ITIL 4 defines a release as a version of a service or other configuration item, or a collection of configuration items, made available for use. Deployment moves components into the live environment, but a release is what becomes usable by the consumer. This distinction underpins how release management plans visibility and adoption.