CIS-ITSM Practice Test 4 — 10 Questions

Question 1

You are investigating why an incident was not auto-assigned. You check the Assignment Rules but notice the 'Match Conditions' are met. What is another common reason?

Accepted Answer

The Assignment Rule is not active.. A common reason an incident is not auto-assigned despite matching Assignment Rule conditions is that the Assignment Rule itself is inactive. ServiceNow only evaluates active assignment rules; an inactive rule is skipped entirely during incident creation, regardless of whether its match conditions are satisfied. Checking the 'Active' checkbox on the rule is a standard troubleshooting step.

Answer

The 'Assigned to' field is already populated.

Answer

The incident is in a closed state.

Answer

The incident was created via an Email Inbound Action.

Question 2

A fulfillment workflow needs to dynamically assign a Catalog Task to the manager of the user specified in a catalog variable named 'target_employee'. How can this be accomplished in a workflow?

Accepted Answer

Configure the Catalog Task activity assignment to use script/dot-walking to reach current.variables.target_employee.manager.. The Catalog Task activity in a workflow supports dynamic assignment via scripting. By using dot-walking on the current.variables object, you can directly reference the manager field of the user stored in the 'target_employee' variable. This approach leverages the workflow's access to the current record's variables and the referenced user's manager relationship, eliminating the need for external rules or manual group assignments.

Answer

Write a standalone Business Rule on the sys_user table.

Answer

Modify the Order Guide rule base to evaluate manager hierarchy.

Answer

Use the Assignment group field in the Catalog Task activity configuration directly.

Question 3

Which module allows administrators to configure categories and subcategories to organize Service Catalog items for end users?

Accepted Answer

Maintain Categories. The Maintain Categories module is the administrative interface in ServiceNow Service Catalog where admins create and organize the category/subcategory hierarchy that end users see when browsing the catalog. Categories defined here drive the catalog's navigation tree and can be assigned to catalog items via the Catalogs/Categories related lists. This is distinct from Maintain Items, which is where the individual catalog items themselves are created and edited.

Answer

Maintain Items

Answer

Order Guides

Answer

Catalog Definitions

Question 4

Which module allows administrators to view and manage all submitted Service Catalog Requests across the organization?

Accepted Answer

Service Catalog > Requests. The Service Catalog > Requests module in ServiceNow lists all submitted catalog requests (sc_request records) across the organization, allowing administrators to view and manage them. This is the central place to track request states, approvals, and fulfillment. It is distinct from catalog item definitions and incident management.

Answer

Service Catalog > Catalog Items

Answer

Incident > Open

Answer

Request Management > Active Cart

Question 5

A change manager needs to review the history of a change request, including all state transitions and approval decisions. Which related list on the Change Request form provides this audit trail?

Accepted Answer

Approval History / Activity Stream. The Approval History related list (and the Activity Stream) on the Change Request form records all approval decisions, state transitions, and comments, providing the audit trail the change manager needs. Approval History shows who approved or rejected and when, while the Activity Stream captures field changes and work notes. Together they satisfy the requirement to review the full history of the change.

Answer

Outages

Answer

Configuration Items

Answer

Catalog Tasks

Question 6

A Problem record is associated with a Change Request via the 'Caused by change' field. When the Change Request is cancelled, a stakeholder wants the linked Problem record to automatically transition back to the 'Assess' state and notify the problem assignee. How should this be configured?

Accepted Answer

A Business Rule on the Change Request table that evaluates state changes and updates linked Problem records. A Business Rule on the Change Request table is the correct mechanism because it runs server-side on state changes and can query and update related Problem records. This ensures the transition to Assess and the notification to the problem assignee happen automatically when the change is cancelled.

Answer

A Data Lookup definition on the task table

Answer

A Client Script on the Problem table checking parent change status

Answer

A UI Policy on the Change form

Question 7

Which TWO features are supported by Multi-Row Variable Sets (MRVS) in ServiceNow Service Catalog? (Choose two.)

Accepted Answer

Supporting Catalog UI Policies and Catalog Client Scripts. Option B is correct because Multi-Row Variable Sets (MRVS) fully support Catalog UI Policies and Catalog Client Scripts, allowing dynamic show/hide, mandatory, and read-only behavior on the grid's fields and rows. Option D is correct because the core purpose of an MRVS is to let a user enter tabular, multi-row data collections (a grid of repeated field sets) within a single catalog item, with the collected rows stored as a JSON array in the variable's value. The unmarked options do not belong: A is wrong because MRVS does not auto-create an incident per row (that would require custom scripting or Flow Designer logic), C is wrong because MRVS data is held as JSON in the variable value rather than written directly to permanent custom table columns at cart checkout, and E is wrong because MRVS neither replaces workflows nor performs spreadsheet imports.

Answer

Automatically generating a separate incident record for each row submitted

Answer

Storing data directly in permanent custom table columns during initial cart checkout

Answer

Replacing standard workflows with spreadsheet imports

Question 8

An organization wants to ensure that when a Problem record is created, its priority is automatically calculated based on Impact and Urgency using a data lookup matrix. Which ServiceNow feature provides this capability?

Accepted Answer

Data Lookup Definitions and Matchers. Data Lookup Definitions and Matchers in ServiceNow allow administrators to define a matrix that maps input values (Impact and Urgency) to an output value (Priority). This is the standard feature for automatically calculating Priority based on a lookup table, and it is commonly used in Problem, Incident, and Change Management. The lookup executes on the server side when the record is created or updated, ensuring consistent priority assignment.

Answer

Client Script onLoad calculation

Answer

Dictionary Overrides for Priority

Answer

UI Policy Action matrix

Question 9

What is the primary function of the 'Review' state in the change lifecycle?

Accepted Answer

Conducting Post Implementation Review (PIR) and assessing success. The 'Review' state in the change lifecycle is used to conduct the Post Implementation Review (PIR) after a change has been implemented. During this state, the change manager and stakeholders assess whether the change was successful, if it met its objectives, and if any follow-up actions are needed. This is a distinct phase that occurs after implementation and before closure.

Answer

Approving standard change proposals

Answer

Running automated risk assessments

Answer

Performing initial conflict detection checks

Question 10

When configuring a CAB meeting definition, what does the 'Duration' field specify?

Accepted Answer

The planned length of time for the CAB meeting session. In ServiceNow Change Management, the 'Duration' field on a CAB meeting definition specifies the planned length of the meeting session itself. This value is used to schedule the meeting on the CAB's calendar and to determine the meeting's start and end times. It does not control change state timings, conflict detection, or lead times.

Answer

The maximum allowable time a change request can stay in the Authorize state

Answer

The window of time for conflict detection lookahead

Answer

The lead time required before submitting a normal change