A release manager has decided on a policy of not allowing users to choose to accept software updates. What is this an example of?
Correct Answer: B
Explanation:
The ITIL® 4 Practitioner: Release Management document explains the difference between push and pull approaches in release management: "In a push approach, updates are deployed to users without giving them a choice, often to ensure compliance or security. In a pull approach, users can choose when to adopt updates" (Section 3.2.3). Option A (A ‘pull’ approach) is incorrect because a pull approach allows users to choose when to accept updates, which contradicts the scenario. Option B (A ‘push’ approach) is correct, as the policy of not allowing users to choose means the updates are automatically deployed to them, fitting the definition of a push approach. Option C (Continuous delivery) and Option D (Continuous integration) are development practices, not release deployment strategies. Continuous delivery involves making releases available frequently, but it doesn’t specify whether users must accept them (push) or can choose (pull). The scenario describes a push approach, making B the correct answer. [Reference: ITIL® 4 Practitioner: Release Management , Section 3.2.3: Release Execution., , , ]
Question 2
[RM 2: The processes of the practice]
What is a description of a release?
Correct Answer: A
Explanation:
In ITIL 4, a release is defined as the output of the release management practice that is made available to
users. TheITIL® 4 Practitioner: Release Managementdocument states:"A release is a version of a service
or a set of service components that is made available for use. It often includes new or changed features
that deliver value to users"(Section 2.2).
Option A (A set of new service features that will benefit users) aligns with the definition, as a release
typically includes new or changed features intended to provide value to users.
Option B (The repeated building and testing of code) describes a development process (e.g., continuous
integration), not the release itself.
Option C (All updated service versions that are mandatory for users) is incorrect because releases are not
always mandatory; ITIL 4 allows for push or pull approaches.
Option D (Guidelines for collating changes) describes a process or policy, not the release itself.
The correct description of a release is a set of features or components made available for use, making A
the correct answer.
[Reference: ITIL® 4 Practitioner: Release Management , Section 2.2: Concepts and Definitions.]
Question 3
[RM 1: The purpose of the practice]
An organization invested in the development and adoption of a common approach to release management.
Which metric will help the organization to understand if this initiative has been successful?
Correct Answer: B
Explanation:
A common approach to release management aims to improve the reliability and stability of releases.
TheITIL® 4 Practitioner: Release Managementdocument highlights key metrics for evaluating the
success of release management:"Key metrics for release management often include the percentage of
releases that do not result in incidents, as this indicates the stability and reliability of the release
process"(Section 5.3).
Option A (Alignment with suppliers) is a process improvement metric but doesn’t directly measure the
success of the release outcomes.
Option B (The percentage of releases that do not result in incidents) directly measures the effectiveness of
the release process by assessing its impact on service stability, aligning with the goal of a common
approach to reduce errors and disruptions.
Option C (Satisfaction rating) is a valuable metric but is more subjective and less directly tied to the
operational success of a common approach.
Option D (Number of delayed releases) measures timeliness but not the quality or stability of the releases.
The best metric to assess the success of a standardized release management approach is the reduction in
incidents, making B the correct answer.
[Reference: ITIL® 4 Practitioner: Release Management , Section 5.3: Key Metrics for Release
Management.]
Demo Practice Mode
You are viewing only the questions marked as Demo.