CIS-ITSM · Question #81
What are key relationships between Changes and Incidents? Choose 2 answers
The correct answer is B. Incidents can be caused by a Change C. A Change can resolve Incidents. Changes and Incidents are related in ServiceNow because a Change can cause Incidents through unintended side effects, and a Change can also be the mechanism for resolving existing Incidents.
Question
What are key relationships between Changes and Incidents? Choose 2 answers
Options
- AIncident owners are part of the change approval workflow
- BIncidents can be caused by a Change
- CA Change can resolve Incidents
- DIncidents autoclose upon closure of a related Change
How the community answered
(25 responses)- A4% (1)
- B92% (23)
- D4% (1)
Why each option
Changes and Incidents are related in ServiceNow because a Change can cause Incidents through unintended side effects, and a Change can also be the mechanism for resolving existing Incidents.
Incident owners do not participate in the Change approval workflow; change approvals are handled by CAB members and designated approvers defined on the change record.
Incidents can be caused by a Change when a change implementation introduces unintended consequences or breaks existing functionality. ServiceNow supports linking incidents to the causative change record for root cause tracking and post-implementation review.
A Change can resolve one or more Incidents by implementing a permanent fix, and ServiceNow allows changes to be associated with the incidents they are intended to close, creating a traceable link between problem resolution and change activity.
Incidents do not automatically close when a related Change closes; incident resolution requires its own separate closure process and is not triggered by change state changes.
Concept tested: ServiceNow Change and Incident relationship management
Source: https://docs.servicenow.com/bundle/washingtondc-it-service-management/page/product/change-management/concept/change-management-overview.html
Topics
Community Discussion
No community discussion yet for this question.