CIS-ITSM · Question #90
How are Releases related to Changes?
The correct answer is B. Releases are comprised of one or more Changes. In ITSM, a Release is a higher-level container that groups one or more Changes together for coordinated deployment, making Changes the constituent components of a Release.
Question
How are Releases related to Changes?
Options
- AReleases are implemented prior lo Changes
- BReleases are comprised of one or more Changes
- CChanges are implemented prior to Releases
- DChanges are comprised of one or more Release
How the community answered
(47 responses)- A4% (2)
- B89% (42)
- C2% (1)
- D4% (2)
Why each option
In ITSM, a Release is a higher-level container that groups one or more Changes together for coordinated deployment, making Changes the constituent components of a Release.
Releases are not implemented prior to Changes - Changes are the individual units of work and are contained within a Release, not the other way around.
A Release record in ServiceNow aggregates multiple related Change requests that must be deployed together as a single logical unit. This relationship allows organizations to coordinate testing, scheduling, and approval of bundled changes, with the Release serving as the parent and individual Changes as its child components.
Changes are not implemented prior to Releases as a structural rule - they are implemented as part of a Release, not independently before it in this relationship.
Changes are not comprised of Releases - the hierarchy flows from Release down to Change, not from Change down to Release.
Concept tested: Release and Change Management hierarchical relationship
Source: https://docs.servicenow.com/bundle/washingtondc-it-service-management/page/product/release-management/concept/c_ReleaseManagement.html
Topics
Community Discussion
No community discussion yet for this question.