Free Practice Questions for the ITIL Practitioner Level ITIL-4-Practitioner-Release-Management Exam (2026 Updated)

Automating the verification of release success involves tracking the performance and stability of the released services. The ITIL® 4 Practitioner: Release Management document notes: "Monitoring and event management tools can automate the verification of release success by tracking system performance and detecting anomalies post-release, ensuring the release meets its objectives" (Section 4.2).

Option A (Monitoring and event management tools) is correct, as these tools can automatically check system health and performance after a release, replacing manual checks.

Option B (Workflow management and collaboration tools) focuses on process coordination, not post-release verification.

Option C (Enterprise architecture tools) is used for dependency mapping, not release verification.

Option D (Analysis and reporting tools) provides retrospective insights but doesn’t automate real-time verification.

The correct answer is A, as monitoring tools are best suited for automating release verification.

Third parties, such as suppliers or vendors, often play a role in the execution of releases, especially when they provide components or services involved in the release. The ITIL® 4 Practitioner: Release Management document states: "Performing a release according to an agreed model often involves dependencies on third parties, such as suppliers providing software updates, infrastructure, or support services, which need to be integrated during the release execution" (Section 3.4).

Option A (Release management alignment with other practices) is an internal coordination activity, less likely to directly involve third parties.

Option B (Identifying an applicable model) is a planning activity typically handled internally by the release manager.

Option C (Performing a release according to an agreed model) directly involves executing the release, which often requires third-party components or services, creating a dependency.

Option D (Verifying a release) may involve third-party tools but is less dependent on their active participation compared to execution.

The correct answer is C, as performing the release is the activity most likely to depend on third parties.

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.