nerdexam
PeopleCert

ITIL-FOUNDATION · Question #168

Which of the following would NOT be contained in a release policy?

The correct answer is D. The risk register for the release. A release policy is a governance document that sets standards applicable across all releases, while a risk register is a separate artifact tracking risks for an individual release. The risk register is therefore not a component of the policy itself.

Know the purpose of the ITIL practices

Question

Which of the following would NOT be contained in a release policy?

Options

  • ANaming and numbering conventions
  • BEntry and exit criteria of the release into testing
  • CRoles and responsibilities for the release
  • DThe risk register for the release

How the community answered

(47 responses)
  • A
    4% (2)
  • B
    17% (8)
  • C
    9% (4)
  • D
    70% (33)

Why each option

A release policy is a governance document that sets standards applicable across all releases, while a risk register is a separate artifact tracking risks for an individual release. The risk register is therefore not a component of the policy itself.

ANaming and numbering conventions

Naming and numbering conventions are explicitly included in a release policy to ensure releases are consistently identified and tracked across the organization.

BEntry and exit criteria of the release into testing

Entry and exit criteria for testing are a standard release policy element that defines the quality gates a release must satisfy before progressing.

CRoles and responsibilities for the release

Roles and responsibilities are a core part of any release policy, clarifying ownership and accountability for each stage of the release lifecycle.

DThe risk register for the releaseCorrect

A risk register is a project-level document used to identify, assess, and track risks specific to a given release, but it is created and maintained as part of release execution, not as part of the overarching release policy. The release policy defines standing rules - such as naming conventions, quality gates, and role assignments - that apply consistently to every release rather than recording risks for a single instance.

Concept tested: ITIL release policy components and scope

Source: https://www.axelos.com/certifications/itil-service-management

Topics

#release management#release policy#release planning#release control

Community Discussion

No community discussion yet for this question.

Full ITIL-FOUNDATION Practice