CIS-ITSM Change Management Practice Test 8 — 15 Questions

Question 1

Which TWO fields on a Change Request form help determine whether a schedule conflict exists? (Choose two.)

Accepted Answer

Planned end date. The Planned start date (D) and Planned end date (A) are the two fields that define the time window during which a change will be implemented, so comparing these dates against other changes' windows is exactly how a schedule conflict (overlapping maintenance windows) is detected. If another approved change's planned start/end overlaps with these dates, a conflict exists; without both boundaries you cannot determine overlap. Assignment group (B) only identifies who will perform the work and does not convey timing. Category (C) classifies the type of change (e.g., hardware, software) and has no temporal information. Short description (E) is a free-text summary of the change and does not provide structured scheduling data.

Answer

Assignment group

Answer

Category

Answer

Short description

Question 2

Which TWO actions happen when a conflict is detected during the change scheduling process? (Choose two.)

Accepted Answer

Conflict status indicators provide visibility into soft or hard conflicts. Option A is correct because conflict status indicators are the mechanism that surfaces whether a detected scheduling clash is a soft conflict (a warning that can often be resolved by rescheduling) or a hard conflict (a genuine overlap that must be addressed before the change can proceed), giving change managers the visibility needed to act. Option E is correct because when the scheduling process detects a conflict, it creates conflict records that are stored and shown in the Conflicts related list on the change request, providing an auditable, actionable record of the clash. The remaining options do not belong: B is wrong because conflict detection does not trigger a company-wide email broadcast, C is wrong because a scheduling conflict never automatically retires the affected configuration item from service, and D is wrong because the change request is not deleted from the database — it is retained and flagged so the conflict can be resolved.

Answer

An automated email is broadcast to all company employees

Answer

The configuration item is automatically retired from service

Answer

The change request is automatically deleted from the database

Question 3

An administrator is troubleshooting why conflict detection is not evaluating custom CI relationship types. Which THREE components control how CI relationships are traversed during conflict detection? (Choose three.)

Accepted Answer

CI relationship type definitions (cmdb_rel_type) specifying upstream/downstream semantics. Option B is correct because CI relationship type definitions in the cmdb_rel_type table specify the parent/child (upstream/downstream) semantics that conflict detection uses to determine how related CIs are traversed; if a custom relationship type is not properly defined there, traversal will not evaluate it. Option C is correct because conflict detection system properties (such as those controlling whether relationship traversal is enabled and which relationship types are considered) govern whether and how the engine walks CI relationships during evaluation. Option E is correct because script includes like ConflictFinderSNC contain the actual traversal query logic that builds and executes the relationship queries, so custom relationship types must be handled by that logic to be evaluated. Option A is not relevant because Service Catalog workflow versioning rules govern catalog item workflow versions, not CMDB relationship traversal. Option D is not relevant because incident priority lookup tables map impact/urgency to priority and have no role in how CI relationships are traversed during conflict detection.

Answer

Service Catalog workflow versioning rules

Answer

Incident management priority lookup tables

Question 4

During the review of a scheduled Normal Change, the Change Management conflict engine flags an overlap. The conflict is detected against another change record that targets a different CI, but both CIs depend on the same parent business service. How does the conflict engine identify this relationship?

Accepted Answer

By evaluating upstream and downstream relationships in the cmdb_rel_ci table linked to shared dependent CIs or business services.. The conflict engine in ServiceNow Change Management identifies overlaps by analyzing the CMDB relationship table (cmdb_rel_ci) to trace dependencies between configuration items (CIs). When two changes target different CIs that both depend on the same parent business service, the engine detects this shared dependency through upstream and downstream relationships, flagging a potential conflict. This ensures that changes affecting interconnected components are coordinated even if they don't directly share a CI.

Answer

By comparing the assignment groups of the tasks to see if they share the same manager.

Answer

By checking if both change records reference the same parent service portfolio offering in Service Portfolio Management.

Answer

Through the Change Schedule map view overlapping boundaries calculated exclusively by the location field.

Question 5

An IT organization wants to ensure that Emergency Changes bypass standard multi-tier CAB reviews while still capturing post-implementation reviews. Which configuration component natively supports this requirement in ServiceNow ITSM?

Accepted Answer

Change Models. Change Models in ServiceNow natively support defining different process flows for different change types, including Emergency changes that bypass standard multi-tier CAB reviews while still enforcing post-implementation review. A Change Model can specify the workflow/flow, approval policy, and state transitions appropriate for emergency changes, making it the correct configuration component.

Answer

Assignment Rules

Answer

Change Schedule conflict rules

Answer

Change Risk Calculator properties

Question 6

Where can a change manager view a graphical representation of planned changes, maintenance windows, and blackouts to identify potential scheduling conflicts?

Accepted Answer

Change Schedule calendar workspace. The Change Schedule calendar workspace in ServiceNow provides a visual timeline view of planned changes, maintenance windows, and blackout periods, enabling change managers to spot scheduling conflicts at a glance. It aggregates change requests and their associated schedules into a single graphical interface, highlighting overlaps and potential collisions. This is the designated tool for proactive conflict identification in the change management process.

Answer

CMDB Health Dashboard

Answer

Service Portfolio Management dashboard

Answer

CAB Workbench

Question 7

During Change Conflict Detection, which THREE types of conflicts can the ServiceNow conflict engine automatically identify and report on a change record? (Choose three.)

Accepted Answer

Conflicts where another change targets the exact same Configuration Item (CI) during an overlapping time window.. The ServiceNow change conflict engine automatically detects three conflict types on a change record. Option A is correct because it identifies direct CI conflicts, where another change targets the exact same Configuration Item during an overlapping time window, which is the classic scheduling collision the engine checks via the change CI relations. Option B is correct because the engine also evaluates related CI conflicts, where a change's target CI is related (through CI relationships) to another CI being changed in a conflicting window, catching downstream or dependency impacts. Option E is correct because the engine checks blackout schedules, flagging changes scheduled during a defined Blackout Schedule window as conflicts. Options C and D are not conflict types the engine reports: approval delegation limits and cost center budget thresholds are governance/financial controls handled by approval rules and budget workflows, not by change conflict detection.

Answer

Conflicts where the change request submitter lacks the required approval delegation limits.

Answer

Conflicts where the estimated cost of the change exceeds the assigned cost center budget threshold.

Question 8

A change manager needs to create a template for a frequent, low-risk change that requires minimal approval. Which Change Model type should be configured?

Accepted Answer

Standard Change. A Standard Change is a pre-approved, low-risk, repeatable change that follows a defined Change Model with minimal or no additional approval. Change managers create Standard Change templates (Change Models) so requesters can submit them without CAB review.

Answer

Emergency Change

Answer

Normal Change

Answer

Template Change

Answer

Minor Change

Question 9

To prevent overlapping outages, you are configuring Conflict Detection. Which table contains the criteria used to identify conflicts?

Accepted Answer

Change Conflict Definition [change_conflict_definition]. The Change Conflict Definition [change_conflict_definition] table contains the criteria used to identify conflicts between changes. It defines the conditions under which changes are considered conflicting, such as overlapping schedules or shared configuration items.

Answer

Change Request [change_request]

Answer

CAB Definition [cab_definition]

Answer

Change Schedule [cmn_schedule]

Answer

Change Conflict [change_conflict]

Question 10

A technician is unable to see the 'CAB Workbench' module. Which role is required to access the CAB Workbench interface?

Accepted Answer

sn_change_cab.cab_manager. Access to the CAB Workbench module requires the sn_change_cab.cab_manager role, which is purpose-built to grant CAB managers the ability to view and run CAB meetings through the Workbench interface. Without this role, the module is hidden from the navigation menu.

Answer

admin

Answer

itil

Answer

cab_analyst

Answer

change_manager

Question 11

Which field on the Change Request form identifies the specific configuration item being modified?

Accepted Answer

Configuration item. The Configuration item field on the Change Request form directly references the specific CI (e.g., server, application, database) that the change will modify. This field creates a relationship between the change record and the CMDB, enabling impact analysis and ensuring that the correct asset is targeted. Other fields like Service or Assignment group provide context but do not identify the exact CI.

Answer

Priority

Answer

Service

Answer

Assignment group

Answer

Short description

Question 12

When using the CAB Workbench, how is a meeting agenda created?

Accepted Answer

Generated automatically by the CAB Definition.. The CAB Workbench agenda is driven by the CAB Definition record, which specifies the meeting schedule, related change filters, and agenda item sources. When a CAB meeting is opened in the Workbench, the system automatically populates the agenda with changes that match the CAB Definition's criteria (such as changes in the 'Assess' or 'Authorize' state assigned to that CAB). This means the agenda is generated automatically rather than assembled by hand.

Answer

Defined in the Change Request form.

Answer

Manually add each change.

Answer

Set by the CAB manager in the meeting.

Answer

Imported via Excel.

Question 13

A change request is currently in the 'New' state. You want to automate the transition to 'Assess'. Where do you define this logic in a Change Model?

Accepted Answer

Change Model Flow. In ServiceNow Change Management, the Change Model Flow (also called Change Model workflow) defines the states and transitions for a change request, including automated transitions like moving from 'New' to 'Assess'. This is where you configure the logic that drives the state model.

Answer

UI Action on change_request

Answer

State transition table

Answer

Business Rule on change_request

Answer

Workflow properties

Question 14

What is the function of the 'CAB Required' flag on a Change Request?

Accepted Answer

It forces CAB approval.. The 'CAB Required' flag on a Change Request, when set to true, forces the change to go through CAB (Change Advisory Board) approval as part of its approval workflow. It ensures that the CAB reviews and approves the change before implementation.

Answer

It bypasses all approvals.

Answer

It sets the risk to high.

Answer

It automatically generates a CAB meeting.

Answer

It alerts the CAB manager.

Question 15

If you perform a 'Mass Update' on multiple Change Requests, which feature ensures that risk assessments are recalculated for every record?

Accepted Answer

Business Rule. When performing a Mass Update on multiple Change Requests, a Business Rule ensures that risk assessments are recalculated for every record. Business Rules run on the server for each record during the mass update, allowing the system to recalculate risk based on the updated data. This is the standard mechanism for enforcing logic across multiple records.

Answer

Scheduled Job

Answer

Flow Designer

Answer

UI Policy

Answer

Client Script