CIS-ITSM Practice Test 8 — 10 Questions

Question 1

When designing a Record Producer that maps user input to the Incident table, an administrator notices that the 'Caller' field on Incident is not populating correctly even though the variable is mapped to 'caller_id'. What is the most likely reason?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The variable type is set to Single Line Text instead of Reference pointing to the sys_user table.. For a Record Producer to correctly populate a reference field like Caller on the Incident table, the variable mapped to that field must be of type Reference and point to the sys_user table. A Single Line Text variable, even if named 'caller_id', will store a string value that cannot be resolved to a valid user sys_id, resulting in an empty or incorrect Caller field. The mapping process relies on the variable's type to determine how to transfer data to the target field.

Answer

The variable name must exactly match 'sys_id' to populate reference fields.

Answer

Record producers cannot map fields to the Incident table due to security restrictions.

Answer

The Incident table requires an active Business Rule to accept record producer inputs.

Question 2

When creating a Catalog Client Script, what is the purpose of selecting 'Mobile / Service Portal' as the UI type?

Accepted Answer

It ensures the script executes correctly in Service Portal and mobile interfaces where DOM manipulation is restricted.. Selecting 'Mobile / Service Portal' as the UI type in a Catalog Client Script ensures the script is compatible with the Service Portal and mobile interfaces, which use AngularJS instead of the classic Jelly/Prototype-based UI. In these environments, direct DOM manipulation (e.g., using $j or document.getElementById) is restricted or behaves differently, so the script must use the client-side API (g_form, g_user, etc.) that abstracts the UI. This option correctly identifies that the script executes properly in those interfaces by adhering to their constraints.

Answer

It restricts the script to run exclusively on native iOS and Android mobile apps.

Answer

It bypasses client-side caching for catalog item variables.

Answer

It automatically converts jQuery syntax into AngularJS directives.

Question 3

A catalog administrator needs to create a collection of variables that can be reused across multiple catalog items. Which feature should they use?

Accepted Answer

Variable Sets. Variable Sets are reusable collections of variables that can be attached to multiple catalog items, allowing administrators to define a set of variables once and include it wherever needed. This promotes consistency and reduces duplication across catalog items.

Answer

Variable Templates

Answer

Variable Collections

Answer

Catalog Item Groups

Question 4

An administrator wants to add a custom field called 'Root Cause Category' to the Problem table. What is the recommended best practice for naming the column name in ServiceNow?

Accepted Answer

The system automatically prefixes custom fields with 'u_' (e.g., u_root_cause_category). ServiceNow automatically prefixes custom fields created on any table with 'u_' to distinguish them from out-of-box (OOB) system fields. This convention prevents naming collisions with future platform upgrades and makes it easy to identify customizations during cloning or upgrade reviews. So a custom field named 'Root Cause Category' becomes 'u_root_cause_category' on the Problem table.

Answer

It must match an existing incident table column exactly

Answer

It must contain uppercase spaces for readability

Answer

It must start with 'sys_' to ensure system privileges

Question 5

What is the definition of a 'Known Error' in ITIL and ServiceNow Problem Management?

Accepted Answer

A problem that has a documented root cause and a temporary workaround, but no permanent fix yet. A Known Error in ITIL and ServiceNow Problem Management is a problem whose root cause has been identified and documented, and for which a workaround exists, but a permanent fix has not yet been implemented. This state is reached after the problem investigation phase confirms the underlying cause. It is distinct from a resolved problem, which has a permanent fix applied.

Answer

A software bug that has been successfully patched and deployed to production

Answer

An expired knowledge base article

Answer

An incident that has been rejected by the service desk three times

Question 6

Which TWO of the following are primary benefits of utilizing Standard Changes in ServiceNow? (Choose two.)

Accepted Answer

They bypass traditional CAB approval because they are pre-approved. Option C is correct because Standard Changes are pre-approved by the Change Management process, so they do not require individual CAB review or approval each time they are executed, which speeds up delivery. Option E is correct because Standard Changes follow a documented, repeatable procedure for frequent, low-risk changes, ensuring consistency and reducing administrative overhead. Option A is incorrect because Standard Changes are low-risk and pre-authorized, so mandatory manual risk assessment questionnaires for every execution are not a primary benefit and would defeat their purpose. Option B is incorrect because emergency incident swarming is associated with major incidents or emergency changes, not routine Standard Changes. Option D is incorrect because Standard Changes are intended for low-risk, routine changes, whereas major, high-risk infrastructure overhauls would typically follow Normal or Emergency Change processes.

Answer

They require mandatory manual risk assessment questionnaires for every execution

Answer

They automatically trigger emergency incident swarming

Answer

They are designed for major, high-risk infrastructure overhauls

Question 7

A customized Problem workflow utilizes legacy workflow engine. During testing, a workflow timer activity fails to resume after a server restart. What is the most likely cause related to workflow engine execution?

Accepted Answer

The system scheduler (sys_trigger) or workflow event queue processing encountered an issue. Legacy workflow timers in ServiceNow are driven by the system scheduler (sys_trigger) and the workflow event queue. If a timer activity fails to resume after a server restart, the most likely cause is that the scheduler or event queue processing was interrupted or not properly restored. This prevents the timer from firing and resuming the workflow.

Answer

The browser cache needs clearing

Answer

The user session expired

Answer

The Problem form layout was modified

Question 8

Which TWO actions can a Catalog UI Policy perform on catalog item variables without writing code? (Choose two.)

Accepted Answer

Make variables mandatory or optional. Catalog UI Policies are no-code configuration records in ServiceNow that dynamically control the behavior of catalog item variables on the form. Option A is correct because a Catalog UI Policy can set a variable's Mandatory field to true or false, forcing or removing the requirement that the user supply a value before submission. Option E is correct because the same policy can toggle a variable's Visible field, showing or hiding it based on conditions such as the value of another variable. The remaining options are incorrect: compiling Java source code (B) is a development activity unrelated to UI policies, deleting user profile records (C) is a data operation performed by users or scripts, and creating new database tables (D) is a schema change done through table administration, none of which a Catalog UI Policy can do.

Answer

Automatically compile Java source code

Answer

Delete user profile records

Answer

Create new database tables

Question 9

An administrator needs to create a variable that is shared across multiple catalog items in ServiceNow. Which feature should the administrator use to achieve this efficiently without recreating the variables each time?

Accepted Answer

Variable Set. A Variable Set is a reusable container of variables that can be attached to multiple catalog items, record producers, or other variable sets. This allows the administrator to define variables once and share them across items without recreating them, which is exactly the requirement.

Answer

Order Guide

Answer

Catalog UI Policy

Answer

Record Producer

Question 10

When utilizing Flow Designer to fulfill a Service Catalog request, how should the flow access the variables submitted by the user on the catalog item?

Accepted Answer

Through the 'Requested Item' record data pill, accessing the 'Variables' section. In Flow Designer, catalog item variables submitted by the user are accessible through the 'Requested Item' record data pill, which exposes a 'Variables' section containing all the variable values. This is the standard, supported way to reference catalog variables within a flow.

Answer

By calling a client-side script from the flow action

Answer

Using a legacy GlideRecord query on sc_item_option_mtom

Answer

Using system properties configured in the flow inputs