CIS-ITSM · Question #91
Where can a change manager define the interval frequency for unauthorized change detection?
The correct answer is C. Unauthorized Change Properties module. The interval frequency for unauthorized change detection is configured through the Unauthorized Change Properties module, which centralizes the scheduling settings for this automated detection process.
Question
Where can a change manager define the interval frequency for unauthorized change detection?
Options
- AThe ci.change unplanned business rule
- BEvent Processing Properties module
- CUnauthorized Change Properties module
- DUnauthorized change flow
How the community answered
(32 responses)- A3% (1)
- C94% (30)
- D3% (1)
Why each option
The interval frequency for unauthorized change detection is configured through the Unauthorized Change Properties module, which centralizes the scheduling settings for this automated detection process.
The ci.change_unplanned business rule triggers detection logic but does not expose a configurable interval frequency setting for administrators to adjust.
Event Processing Properties module manages event-related settings broadly and is not specifically designed for unauthorized change detection interval configuration.
The Unauthorized Change Properties module provides a dedicated interface where a change manager can set the detection interval, specifying how frequently the system scans for CI changes that lack an associated authorized change record. Centralizing this setting in a properties module allows administrators to adjust detection frequency without modifying business rules or flows directly.
The unauthorized change flow defines the process steps taken after detection occurs, not the scheduling interval for how often detection runs.
Concept tested: Unauthorized change detection interval configuration in ServiceNow
Source: https://docs.servicenow.com/bundle/washingtondc-it-service-management/page/product/change-management/concept/unauthorized-change-detection.html
Topics
Community Discussion
No community discussion yet for this question.