ServiceNow Certified Implementation Specialist - IT Service Management (CIS-ITSM) (CIS-ITSM) CIS-ITSM Questions 226–300 | Page 4/5

226

Multi-Selectmedium

Which TWO components can be used to notify a user about an incident update?

Select 2 answers

A.Customer Comments

B.Assignment Rule

C.Work Notes

D.UI Policy

E.Email Notification

AnswersA, E

Comments trigger notification events for the end user.

Why this answer

Customer Comments (A) are correct because they are visible to the caller/end user on the incident record and, when added, can trigger outbound communication such as an email notification to the user, thereby notifying them of an update. Email Notification (E) is correct because it is the mechanism that actually sends an email to the user (for example, via a notification configured on the incident table when a comment is added or the record is updated). Assignment Rule (B) is not correct because it only automatically sets fields such as assignment group or assigned user during insert/update and does not notify users.

Work Notes (C) are not correct because they are internal-only and are not visible to the end user. UI Policy (D) is not correct because it only dynamically changes form field behavior (visible, mandatory, read-only) on the client side and does not send notifications.

Exam trap

CIS-ITSM often tests the visibility distinction between Customer Comments and Work Notes — the trap is assuming Work Notes notify the user, when they are internal-only.

Full explanation →

227

MCQeasy

An administrator needs to group several catalog items into a logical category on the Service Portal homepage. What should be created to achieve this categorization?

A.Assignment Group

B.Catalog Definition

C.Catalog Category

D.Knowledge Base

AnswerC

Catalog Categories provide the logical grouping container that catalog items are assigned to, and the Service Portal homepage renders these categories as browsable sections. Creating one satisfies the stem's requirement to categorise several items together, since items reference a category rather than being grouped individually on the portal.

Why this answer

Catalog Category is the correct answer because it is the native ServiceNow construct used to group catalog items into logical categories for display on the Service Portal. When you assign a catalog item to a category, the portal renders that category as a section or tile, allowing users to browse related items together. This is the standard method for organizing the service catalog without custom code.

Exam trap

CIS-ITSM often tests the distinction between catalog organization (categories) and assignment routing (assignment groups), causing candidates to confuse grouping with support team assignment.

How to eliminate wrong answers

Option A is wrong because Assignment Groups are used for routing incidents, tasks, and approvals to the correct support teams, not for organizing catalog items on the portal. Option B is wrong because a Catalog Definition (or Catalog) is the top-level container that holds categories and items; it does not provide the logical grouping within the portal homepage. Option D is wrong because Knowledge Base is for storing articles and documentation, not for categorizing catalog items.

Full explanation →

228

Multi-Selecteasy

Which TWO of the following are primary benefits of implementing Service Portfolio Management (SPM) in ServiceNow? (Choose two.)

Select 2 answers

A.Aligns IT service offerings directly with business goals and organizational strategies

B.Automatically provisions virtual machines in VMware vCenter

C.Automates hardware patch deployment across Linux servers

D.Replaces the Incident Management workflow engine entirely

E.Provides clear visibility into service costs, performance, and business value

AnswersA, E

Service Portfolio Management maintains the complete lifecycle view of services, letting IT map each offering to business outcomes and strategic objectives. This directly satisfies the stem's requirement of aligning service offerings with business goals, rather than merely tracking operational incidents or catalog items.

Why this answer

Option A is correct because Service Portfolio Management in ServiceNow is designed to manage the full lifecycle of services and explicitly map them to business strategy, ensuring IT investments and offerings support organizational goals. Option E is correct because SPM delivers a service-centric view that surfaces cost, performance, demand, and value data (often via the Service Portfolio and related dashboards), enabling informed investment and retirement decisions. The unmarked options do not belong: B (VMware vCenter VM provisioning) is an orchestration/automation capability, not an SPM benefit; C (Linux patch deployment) is configuration/patch management automation; and D is false because SPM complements rather than replaces the Incident Management workflow engine.

Exam trap

CIS-ITSM often tests the confusion between strategic Service Portfolio Management and operational fulfillment features like orchestration or patching, tempting candidates to pick automation capabilities as SPM benefits.

Full explanation →

229

MCQeasy

What is the difference between 'Work Notes' and 'Comments' in an incident?

A.Work notes are mandatory; Comments are optional

B.Work notes are visible to the caller; Comments are internal

C.Work notes are internal; Comments are visible to the caller

D.None

E.Both are visible to everyone

AnswerC

Work notes are restricted to internal IT staff and never surface in the customer portal, while additional comments are customer-visible and notify the caller. This visibility split satisfies the stem's distinction, letting technicians document diagnostics privately while communicating updates externally.

Why this answer

In ServiceNow Incident records, 'Work Notes' are internal and visible only to users with appropriate roles (such as ITIL), while 'Comments' (also called Additional Comments) are visible to the caller and external parties. This distinction is fundamental to incident communication.

Exam trap

CIS-ITSM often tests the visibility distinction between Work Notes and Comments, and candidates sometimes confuse which is internal and which is external.

How to eliminate wrong answers

Option A is wrong because neither Work Notes nor Comments are mandatory by default; mandatory status is controlled by UI Policies or Data Policies. Option B is wrong because it reverses the visibility: Work Notes are internal, Comments are visible to the caller. Option D is wrong because there is a clear difference.

Option E is wrong because Work Notes are not visible to everyone; they are restricted to internal users with roles.

Full explanation →

230

MCQhard

An organization uses Domain Separation in ServiceNow. Problem records must be segregated by region. Where must an administrator verify domain separation configurations to ensure proper record visibility and visibility rules for Problem tasks?

A.System Security > Access Control Lists exclusively

B.Table dictionary attributes ensuring 'no_domain' is disabled and domain pathing is active on problem and problem_task

C.System Definition > Tables for problem and problem_task with Domain separation set to 'Edge'

D.Service Portal > Pages configuration

AnswerB

Domain separation depends on the table's dictionary attributes: the 'no_domain' flag must be disabled and domain pathing active so records inherit the correct domain. Verifying these on problem and problem_task ensures visibility rules segregate records by region correctly.

Why this answer

For Domain Separation to work on Problem and Problem Task, the tables must be domain-separated: the 'no_domain' dictionary attribute must be disabled (so records carry a domain) and domain pathing must be active. Administrators verify these dictionary attributes on the problem and problem_task tables to ensure records are segregated and visibility rules apply.

Exam trap

CIS-ITSM often tests the belief that ACLs alone provide domain separation — candidates pick ACL-only answers, missing that domain stamping and pathing on the table dictionary are the foundational controls.

How to eliminate wrong answers

Option A is wrong because ACLs alone do not implement domain separation; domain visibility is enforced by the domain field and domain pathing, with ACLs as a supplementary layer. Option C is wrong because there is no 'Edge' domain separation setting on tables — domain separation is enabled via the 'Domain Separated' table attribute and the no_domain dictionary attribute, not an 'Edge' value. Option D is wrong because Service Portal page configuration controls UI layout, not record-level domain segregation or visibility rules.

Full explanation →

231

MCQmedium

An administrator needs to apply a set of UI policies across multiple catalog items without recreating them for each item. Which feature should be utilized?

A.Order Guide UI Policy Mapping

B.Catalog Data Policy Global Template

C.Catalog UI Policy associated with a Variable Set

D.Global Catalog Client Script Collection

AnswerC

A catalog UI policy attached to a variable set applies its conditions and actions to every catalog item that includes that set, avoiding per-item recreation. This satisfies the requirement to enforce consistent UI behaviour across multiple catalog items efficiently.

Why this answer

Catalog UI Policies can be attached to a Variable Set, and that Variable Set can then be included in multiple catalog items. This means the UI policy logic is defined once and inherited by every catalog item that uses the Variable Set, avoiding the need to recreate the policies per item. This is the standard ServiceNow pattern for reusing catalog UI policies across many items.

Exam trap

CIS-ITSM often tests whether candidates confuse Variable Sets (the reuse container for variables and their UI Policies) with unrelated constructs like Data Policies or Client Scripts, causing them to pick a plausible-sounding but nonexistent feature.

How to eliminate wrong answers

Option A is wrong because 'Order Guide UI Policy Mapping' is not a real ServiceNow feature — order guides orchestrate multiple catalog items but do not provide a UI policy mapping mechanism. Option B is wrong because 'Catalog Data Policy Global Template' does not exist; Data Policies are a separate platform feature used for mandatory/read-only enforcement at the data layer, not a global catalog template. Option D is wrong because 'Global Catalog Client Script Collection' is a fabricated term — client scripts are attached individually or via Variable Sets, not through a 'collection' construct.

Full explanation →

232

MCQmedium

A Change Manager wants to customize the columns displayed in the CAB Workbench agenda view. Where are these agenda column settings configured?

A.UI Policy on the wm_agenda table

B.Report Designer properties

C.CAB Definition record / CAB Workbench settings

D.List Layout of the change_request table

AnswerC

Agenda column settings live on the CAB Definition record, under CAB Workbench settings, where the Change Manager defines which fields appear in the agenda view. This satisfies the stem's constraint: customising displayed columns for the CAB Workbench agenda specifically, rather than global list layouts or personal user preferences.

Why this answer

The CAB Workbench agenda view columns are configured in the CAB Definition record, which is part of the CAB Workbench settings. The CAB Definition record includes fields for specifying the agenda columns, meeting schedule, and other workbench preferences. This allows change managers to customize what information is displayed during CAB meetings without modifying the underlying table layout.

Exam trap

The trap here is confusing the CAB Workbench agenda column configuration with standard list layout or UI policy configurations, as candidates might assume that any column display is controlled by the table's list layout.

How to eliminate wrong answers

Option A is wrong because UI Policies on the wm_agenda table control field behavior (mandatory, read-only, etc.) on the agenda form, not the columns displayed in the agenda view. Option B is wrong because Report Designer properties are used for creating reports, not for configuring the CAB Workbench agenda. Option D is wrong because the List Layout of the change_request table controls the columns shown in the standard change request list, not the CAB Workbench agenda view.

Full explanation →

233

MCQeasy

What is the primary benefit of linking multiple recurring Incidents to a single Problem record?

A.It allows tracking the underlying root cause and enables bulk updates or closure once resolved

B.It converts all linked incidents into emergency change requests

C.It bypasses the need for Service Level Agreements on the incidents

D.It automatically increases the user satisfaction score (CSAT) for all affected callers

AnswerA

Linking many recurring Incidents to one Problem record consolidates their symptoms under a single root-cause investigation. This satisfies the stem's need for a primary benefit: analysts avoid duplicated diagnosis, and resolving the Problem lets them bulk-update or close all associated Incidents together.

Why this answer

Linking multiple recurring incidents to a single problem record allows the organization to track the underlying root cause across all affected incidents and, once the problem is resolved, perform bulk updates or closure on the linked incidents. This consolidation prevents duplicate investigation efforts and ensures all related incidents are addressed when the permanent fix is deployed. It is the core value of the problem-incident relationship in ITIL.

Exam trap

CIS-ITSM often tests the purpose of the problem-incident relationship — candidates incorrectly assume linking triggers automatic changes (like SLA bypass or change creation) when it only provides association and bulk-update capability.

How to eliminate wrong answers

Option B is wrong because linking incidents to a problem does not convert them into emergency change requests — change requests are separate records created through Change Management, and linking does not trigger that conversion. Option C is wrong because linking incidents to a problem does not bypass SLAs — SLAs continue to apply to the incidents independently, and linking has no effect on SLA clocks or compliance. Option D is wrong because linking incidents to a problem does not automatically increase CSAT scores — CSAT is based on user survey responses, and linking has no direct impact on survey results.

Full explanation →

234

Multi-Selecthard

Which THREE of the following are valid types of catalog items available in the ServiceNow Service Catalog? (Choose three.)

Select 3 answers

A.Database View Item

B.Workflow Template

C.Catalog Item

D.Record Producer

E.Order Guide

AnswersC, D, E

A Catalog Item is the fundamental ServiceNow Service Catalog record type, defining a requestable offering with variables, pricing and fulfilment workflow. This satisfies the stem's requirement by naming the baseline item type from which other catalog offerings such as order guides are constructed.

Why this answer

In the ServiceNow Service Catalog, a Catalog Item (C) is the fundamental item type that end users order, such as a laptop or software request, and it drives a defined fulfillment process. A Record Producer (D) is also a valid catalog item type; it lets users create a record on a target table (for example, an incident or case) directly from the catalog rather than ordering a tangible item. An Order Guide (E) is likewise a valid catalog item type that groups multiple catalog items into a single guided ordering experience, often with conditional logic to show or hide items.

By contrast, Database View Item (A) is not a catalog item type — database views are used for reporting and data aggregation, not ordering — and Workflow Template (B) is not a catalog item type either; workflows are fulfillment automation artifacts, not items users can request from the catalog.

Exam trap

CIS-ITSM often tests catalog item types by including non-catalog constructs like 'Workflow Template' and 'Database View Item', so candidates must know the actual sc_cat_item type values rather than assuming any ServiceNow artifact can be a catalog item.

Full explanation →

235

Multi-Selectmedium

Which TWO fields are used in the default Incident Priority calculation?

Select 2 answers

A.Impact

B.Priority

C.Configuration Item

D.Assignment Group

E.Urgency

AnswersA, E

Impact is the second axis in ServiceNow's default priority lookup, quantifying how broadly the incident affects users or services. Combined with urgency in the priority matrix, it produces the priority value the stem's calculation requires, making it one of the two fields used.

Why this answer

In the default Incident Priority calculation, the two fields used are Impact (option A) and Urgency (option E). Priority is derived from a lookup matrix that maps the combination of Impact and Urgency values to a Priority value, so both fields must be populated for the calculation to work. Impact reflects how broadly the incident affects the business, while Urgency reflects how quickly the incident needs resolution, and together they determine the resulting Priority.

Options B, C, and D are not inputs to the calculation: Priority is the output, and Configuration Item and Assignment Group are unrelated to the default Priority matrix.

Exam trap

CIS-ITSM often tests the confusion between inputs and outputs of the priority calculation — candidates may select Priority itself or unrelated fields like Configuration Item, forgetting that only Impact and Urgency are used.

Full explanation →

236

MCQmedium

An organization notices that manual updates made by technicians to the 'Assigned to' field on server CIs are frequently being overwritten by automated nightly imports. What is the best way to prevent this without disabling the import entirely?

A.Modify the transform map to ignore the 'Assigned to' field during every import.

B.Configure a Reconciliation Rule giving priority to the 'UI / Manual' data source over the import data source for the 'Assigned to' attribute.

C.Write a Business Rule on the cmdb_ci table to abort updates to 'Assigned to'.

D.Lock the 'Assigned to' field dictionary attribute.

AnswerB

A reconciliation rule resolves conflicting values for the same attribute by ranking data sources, so the 'UI / Manual' source outranks the import for 'Assigned to'. This satisfies the constraint of preserving technician edits while the nightly import continues running, since precedence is applied per attribute rather than disabling the import entirely.

Why this answer

Configuring a Reconciliation Rule that gives priority to the 'UI / Manual' data source over the import data source for the 'Assigned to' attribute ensures that manual updates are not overwritten by automated imports. This rule allows the import to update other fields while preserving the manually assigned value.

Exam trap

CIS-ITSM often tests the misconception that transform maps or business rules are the best way to handle data conflicts, but reconciliation rules are specifically designed for this purpose in CMDB.

How to eliminate wrong answers

Option A is wrong because modifying the transform map to ignore the 'Assigned to' field would prevent the import from updating that field at all, even when manual updates are not present, which may not be desired. Option C is wrong because a Business Rule to abort updates would block all updates, including legitimate ones, and is too broad. Option D is wrong because locking the dictionary attribute would prevent all updates to the field, including manual ones, which is not the goal.

Full explanation →

237

MCQhard

A user reports that a variable is not appearing on a Catalog Item form, even though the variable is active and associated with the item. Which troubleshooting step should be performed first?

A.Rebuild the Catalog Item cache

B.Verify the Catalog Item workflow

C.Inspect Catalog UI Policies and Catalog Client Scripts for visibility logic

D.Check the Variable Set order

AnswerC

Catalog UI Policies and Catalog Client Scripts commonly hide or show variables dynamically, so a variable that is active and correctly associated can still be invisible at runtime. Inspecting their visibility conditions first identifies whether client-side logic is suppressing the field.

Why this answer

When a variable is active and associated with a catalog item but still not visible, the most common cause is client-side visibility logic — Catalog UI Policies or Catalog Client Scripts that hide the variable based on conditions. Inspecting these first is the fastest diagnostic because they execute at form render time and can override the variable's active state.

Exam trap

CIS-ITSM often tests the tendency to jump to cache rebuilds or workflow checks for visibility issues — the trap is overlooking client-side UI Policies and Client Scripts, which are the actual render-time gatekeepers.

How to eliminate wrong answers

Option A is wrong because rebuilding the catalog cache addresses stale catalog metadata (items, categories, variable sets) but does not fix conditional visibility logic — and it is a heavier operation than needed for a single-variable issue. Option B is wrong because workflows execute after submission, not during form rendering, so they cannot hide a variable on the form. Option D is wrong because variable set order affects the sequence in which variables appear, not whether a specific variable is visible at all — a hidden variable would still be hidden regardless of order.

Full explanation →

238

Multi-Selectmedium

When creating variables in the Service Catalog, which TWO of the following variable types support choices or reference lookups? (Choose two.)

Select 2 answers

A.Single Line Text

B.Label

C.Select Box

D.Container Begin

E.Reference

AnswersC, E

A Select Box renders a predefined list of choices as a dropdown, storing the chosen value against the question. This directly satisfies the stem's requirement for a variable type supporting choices, unlike Single Line Text or Multi Line Text.

Why this answer

The Select Box variable type (C) is correct because it is specifically designed to present a predefined list of choices to the user, allowing them to pick one option from a dropdown menu. The Reference variable type (E) is correct because it performs a reference lookup against a table (such as sys_user or cmdb_ci), letting the user select a record from that table rather than typing a free-form value. Single Line Text (A) is incorrect because it only accepts free-form alphanumeric input and has no built-in choice list or lookup mechanism.

Label (B) is incorrect because it is a read-only display element used to show static text or instructions, not to capture a selection. Container Begin (D) is incorrect because it is a layout/UI element that groups other variables together and does not itself support choices or reference lookups.

Exam trap

CIS-ITSM often tests variable types, and candidates may mistakenly think that Single Line Text can have choices or that Label is an input type.

Full explanation →

239

Multi-Selecteasy

Which TWO types of services are explicitly recognized in the ServiceNow CSDM framework? (Choose two.)

Select 2 answers

A.Desktop Wallpaper Service

B.Technical Service

C.Physical Hardware Service

D.Business Service

E.Network Cable Service

AnswersB, D

Technical Service is one of the CSDM service types, describing a service consumed by other services or applications rather than directly by end users. It sits alongside Business Service in the framework's service taxonomy, satisfying the stem's requirement for an explicitly recognised service type.

Why this answer

The ServiceNow CSDM (Common Service Data Model) framework explicitly recognizes Business Service (option D) and Technical Service (option B) as its two core service types. A Business Service represents a service offered to customers or business users that directly supports business outcomes, while a Technical Service represents the underlying technical capabilities (often mapped to applications, infrastructure, or CI groups) that support one or more business services. These two are the formally defined service classes in CSDM's service taxonomy, with Technical Services typically consumed by Business Services in the model's layering.

Options A, C, and E are not CSDM service types; 'Desktop Wallpaper Service,' 'Physical Hardware Service,' and 'Network Cable Service' are fabricated or overly granular labels that do not correspond to any recognized CSDM service classification.

Exam trap

CIS-ITSM often tests CSDM vocabulary — candidates pick plausible-sounding but non-existent service types (like 'Physical Hardware Service') instead of the officially defined Business and Technical Service categories.

Full explanation →

240

MCQmedium

A service owner manages the 'Payroll Processing' business service in ServiceNow. The service has three service offerings: 'Standard Payroll', 'Executive Payroll', and 'Contractor Payroll'. The service owner needs to add a new offering called 'International Payroll' that will use the same parent business service but have its own SLAs and pricing. Which record should the service owner create to meet this requirement?

A.A new Service Portfolio record containing the new offering

B.A new Service Category record for international payroll

C.A new Service Offering record with 'Payroll Processing' as the parent

D.A new Business Service record under the same portfolio

AnswerC

Service Offerings are designed to be child records of a Business Service, allowing different SLAs, pricing, and delivery commitments for variants of the same service. Creating 'International Payroll' as a Service Offering under 'Payroll Processing' preserves the hierarchy, enables distinct SLAs and pricing, and aligns with the CSDM. This is the correct approach for adding a new variant of an existing business service.

Why this answer

Service Offerings are the correct vehicle for defining variants of a business service that require their own SLAs, pricing, and delivery commitments. Because 'International Payroll' is a variant of the existing 'Payroll Processing' business service rather than a separate service, it should be created as a Service Offering with that business service as its parent. This preserves the CSDM hierarchy and enables independent management of the offering's commitments.

Exam trap

The trap here is assuming that a new variant of a service requires a new Business Service record rather than a Service Offering under the existing business service.

Full explanation →

241

MCQeasy

Which tab on the Incident form is typically used to track communication with the caller?

A.Notes

B.Activity

C.SLA

D.Related Records

AnswerB

The Activity tab records the full interaction history, including outbound notifications, work notes and emails exchanged with the caller. It provides the chronological audit trail needed to track communication, which the question specifically asks for.

Why this answer

The Activity tab on the Incident form is the standard location for tracking all communication with the caller, including outbound emails, inbound replies, comments, and work notes. It provides a chronological feed of all interactions, making it the primary tab for reviewing the communication history with the user.

Exam trap

CIS-ITSM often tests whether candidates confuse the Activity tab (full communication history) with the Notes field (internal work notes) or Related Records, so they pick the wrong tab for caller communication tracking.

How to eliminate wrong answers

Option A is wrong because the Notes tab (or field) is used for internal work notes and additional comments but does not aggregate the full communication thread; it is a field, not the tab that tracks caller communication. Option C is wrong because the SLA tab displays service level agreement milestones and breach times, not communication. Option D is wrong because Related Records shows linked records such as problems, changes, or tasks, not the communication history.

Full explanation →

242

MCQhard

A company uses ServiceNow Domain Separation. A global Problem record needs to be visible across child domains while allowing child domains to create local problem tasks. How should domain scoping be configured on the Problem Task table?

A.Ensure domain visibility and reference cascading are configured properly for parent-child domain hierarchies

B.Disable domain separation entirely on the task table

C.Create duplicate problem records in every child domain manually

D.Use Access Control Lists with domain bypass scripts

AnswerA

Problem Task sits below Problem in the domain hierarchy, so enabling domain visibility and reference cascading lets a global Problem be seen across child domains while child domains still create their own local tasks. This satisfies both the global visibility and local task creation constraints.

Why this answer

For a global Problem record to be visible across child domains while allowing child domains to create local Problem Tasks, the Problem Task table must have proper domain visibility and reference cascading configured for the parent-child domain hierarchy. This ensures the global problem is readable in child domains and that tasks created in a child domain inherit the correct domain.

Exam trap

CIS-ITSM often tests domain separation by offering 'disable it' or 'duplicate records' as shortcuts — candidates pick these instead of understanding that visibility and reference cascading must be configured on the table for parent-child hierarchies.

How to eliminate wrong answers

Option B is wrong because disabling domain separation on the task table breaks the domain model and can expose data across domains inappropriately. Option C is wrong because manually duplicating problem records in every child domain creates data redundancy, breaks the single global record, and defeats the purpose of domain separation. Option D is wrong because ACLs with domain bypass scripts are a security anti-pattern that circumvents the domain model rather than configuring it correctly.

Full explanation →

243

MCQeasy

What is the primary purpose of defining a 'Business Criticality' value on a Business Service record in ServiceNow?

A.To automatically calculate the monthly subscription cost of the service offering

B.To restrict user access to the service portal catalog items

C.To establish the technical monitoring parameters in Event Management

D.To determine priority and impact assessment during incident and change management

AnswerD

Business Criticality drives the priority and impact calculations applied to incidents and changes affecting the service, satisfying the stem's requirement for a defined criticality value. ServiceNow maps this field into impact assessment logic, so higher criticality services escalate faster and receive stricter change scrutiny.

Why this answer

Business Criticality on a Business Service record is used to indicate how important the service is to the organization, which directly informs impact assessment and priority calculation during incident and change management processes. It feeds into ServiceNow's impact/urgency matrix to determine incident priority and helps change managers assess risk.

Exam trap

The trap is confusing Business Criticality with access control or monitoring configuration — candidates may pick the answer that sounds like a security or technical control, but Business Criticality is fundamentally about business impact and prioritization.

How to eliminate wrong answers

Option A is wrong because subscription cost calculation is not a function of Business Criticality — cost data lives in financial management or service costing modules, not the criticality field. Option B is wrong because restricting user access to catalog items is handled by User Criteria and ACLs, not by Business Criticality. Option C is wrong because technical monitoring parameters in Event Management are configured through monitoring tools, CI relationships, and alert rules, not through the Business Service's criticality value.

Full explanation →

244

MCQhard

A company implements proactive Problem Management. They want to automatically generate a Problem record when more than 5 incidents with the exact same Configuration Item and Category are logged within a 2-hour window. Which ServiceNow feature should be configured to achieve this automation?

A.A Dictionary Data Policy

B.An Email Notification template

C.Flow Designer with a scheduled trigger or table trigger combined with aggregate queries

D.A UI Action script

AnswerC

Flow Designer supports table triggers and scheduled triggers, and can run aggregate queries against the Incident table. Grouping by Configuration Item and Category over a two-hour window lets it detect the threshold of five matching incidents and automatically create the Problem record.

Why this answer

Flow Designer can be configured with a scheduled trigger that runs periodically (for example, every 15 minutes) and uses an aggregate query (via a Look Up Records or custom action) to count incidents matching the same CI and Category within a 2-hour window. If the count exceeds 5, the flow creates a Problem record. This is the native, low-code automation approach for proactive problem management.

Exam trap

CIS-ITSM often tests whether candidates know that proactive problem creation requires aggregation over time, which rules out simple table triggers or client-side scripts — the trap is picking a UI Action or Data Policy because it sounds like automation.

How to eliminate wrong answers

Option A is wrong because a Dictionary Data Policy enforces field-level validation or defaulting on a table — it cannot aggregate incidents over a time window or create Problem records. Option B is wrong because an Email Notification template only formats and sends email; it has no logic to query incidents or create problems. Option D is wrong because a UI Action script runs only when a user clicks a button on a form, so it cannot run automatically on a schedule or in response to incident creation.

Full explanation →

245

MCQhard

A service catalog manager needs a single catalog item that, when ordered, creates three separate catalog tasks assigned to different fulfillment groups, each with its own short description and due date. The manager wants no approval and no user interaction after submission. Which approach should the manager use?

A.Create three separate catalog items and rely on the user to order all three.

B.Build a Flow Designer flow triggered on the requested item that uses three Create Catalog Task actions with distinct assignments and due dates.

C.Configure a Record Producer that inserts three records into the sc_task table directly.

D.Use a single Create Task workflow activity that creates one task and rely on the assignment group to split it manually.

AnswerB

Flow Designer supports a catalog trigger and a Create Catalog Task action that can set assignment group, short description, and due date per task. Three such actions in one flow produce the required tasks after submission without approvals or user input, matching the stated requirement precisely.

Why this answer

Flow Designer is the current orchestration tool for catalog fulfillment and can create multiple catalog tasks from one requested item, each with its own assignment group, description, and due date. Triggering the flow on the requested item and using repeated Create Catalog Task actions satisfies the no-approval, no-interaction requirement in a single maintainable definition.

Exam trap

The trap here is treating a single Create Task activity or a Record Producer as capable of generating multiple independently assigned catalog tasks, when multi-task fulfillment belongs to Flow Designer actions.

Full explanation →

246

MCQmedium

A Change Manager at a financial services company needs to configure the system so that changes affecting the core banking platform cannot be scheduled during a defined month-end freeze window. The freeze recurs every month on the last two business days. Which native ServiceNow Change Management capability should the Change Manager configure to enforce this restriction?

A.A CAB agenda rule that automatically rejects any change submitted during the last two business days

B.A Change Management maintenance schedule applied to the core banking CI

C.A scheduled job that sets affected Change Requests to the Unauthorized state at month-end

D.Change Management blackout window defined on the Change schedule with a recurring monthly schedule

AnswerD

Blackout windows are native Change Management records that block change scheduling in defined periods. By attaching a recurring monthly schedule to the blackout window, the Change Manager enforces the freeze automatically for the last two business days, and conflict detection flags any change that violates it. This is exactly the intended use of blackout windows on the Change schedule.

Why this answer

Blackout windows are the native Change Management mechanism for prohibiting change activity during specified periods such as month-end freezes. Because they integrate with conflict detection, any change scheduled inside the window is flagged before approval. Recurring monthly schedules let the Change Manager define the freeze once and have it repeat without manual intervention.

Exam trap

The trap here is confusing maintenance schedules, which describe permitted change periods for a CI, with blackout windows, which prohibit changes during specified dates.

Full explanation →

247

MCQmedium

An organization wants to require 'Work Notes' whenever an incident is set to 'Pending'. How do you configure this?

A.Use a Client Script on the state field.

B.Modify the Form Layout.

C.Use a UI Policy with a condition.

D.Use a Business Rule to check for null notes.

AnswerC

A UI Policy applies client-side logic that can make the Work Notes field mandatory when the State changes to Pending, enforcing completion before submission. This satisfies the requirement to require Work Notes specifically on that state transition.

Why this answer

A UI Policy with a condition is the correct approach because UI Policies are designed to dynamically enforce field-level behavior (mandatory, visible, read-only) on the client side based on form conditions. By setting a condition on the State field (State = Pending), the UI Policy can make the Work Notes field mandatory exactly when the incident enters the Pending state, without writing custom code. This is the declarative, maintainable way ServiceNow intends for this requirement.

Exam trap

CIS-ITSM often tests the confusion between client-side declarative controls (UI Policies) and server-side enforcement (Business Rules/Data Policies), tricking candidates into choosing a Business Rule when the question emphasizes the user-facing form behavior.

How to eliminate wrong answers

Option A is wrong because a Client Script requires custom JavaScript (onChange or onSubmit) and is more error-prone and harder to maintain than a declarative UI Policy for a simple mandatory-field rule. Option B is wrong because modifying the Form Layout only controls which fields appear on the form; it cannot conditionally enforce that a field is mandatory based on another field's value. Option D is wrong because a Business Rule runs server-side and can only validate after submission (or on update), which produces a poor user experience and does not prevent the user from submitting the form with empty Work Notes in the first place.

Full explanation →

248

MCQeasy

An ITIL process owner wants to review the effectiveness of problem resolution by analyzing how often problems are reopened after being closed. Which field on the Problem record should be used to track the number of times a problem has been reopened?

A.Resolution count

B.Problem state changes

C.Reassignment count

D.Reopen count

AnswerD

The 'Reopen count' field on the Problem record increments each time a problem is reopened after being closed. This provides a direct metric for how often problems are not fully resolved. The field is automatically updated by the system when the state changes from Closed to an active state, making it the correct choice for tracking reopen frequency.

Why this answer

The 'Reopen count' field is a standard field on the Problem table that automatically increments each time a problem is reopened. It is the correct metric to analyze how often problems are not permanently fixed. Other fields like reassignment count do not capture reopen events.

Exam trap

The trap here is assuming that reassignment count or state change history indicates reopens, when the explicit 'Reopen count' field is the correct one.

Full explanation →

249

MCQhard

An incident manager wants to ensure that when an incident is escalated to a major incident, the 'Major Incident' field is set to true and a notification is sent to the major incident management team. The escalation can happen via a UI Action or automatically via a business rule. Which configuration should be used to meet this requirement?

A.Create a Business Rule that runs after update on the Incident table, checks if the 'Major Incident' field changed to true, and if so, triggers an event that sends a notification to the major incident management team.

B.Create a UI Action that sets the 'Major Incident' field to true and sends a notification directly using the 'gs.eventQueue' method.

C.Create a Notification with a condition that the 'Major Incident' field is true, and set it to send when the record is updated.

D.Create a Business Rule that runs before update on the Incident table, checks if the 'Major Incident' field changes to true, and if so, sends a notification using the 'event' mechanism.

AnswerA

An after update business rule runs after the record is saved, ensuring the change is committed. Triggering an event at this point is the standard way to send notifications asynchronously. The event can be tied to a notification that targets the major incident management team. This approach works regardless of whether the escalation was manual or automatic, as it reacts to the field change.

Why this answer

The requirement is to set the Major Incident field and send a notification when escalation occurs, whether manual or automatic. An after update business rule can detect the change to true and trigger an event, which the notification engine uses to send the email. This ensures the notification is sent only when the field actually changes, and it works regardless of how the escalation was initiated.

A before rule is too early, a UI Action only handles manual, and a simple notification condition lacks change detection.

Exam trap

The trap here is using a before update rule or a UI Action, which either sends notifications prematurely or only works for manual escalations, missing the need for a robust, event-driven approach.

Full explanation →

250

MCQeasy

Where can users view all scheduled changes across the infrastructure?

A.Dashboard

B.Configuration Item list

C.Change Schedule

D.Service Portal

E.CAB Workbench

AnswerC

The Change Schedule provides a consolidated calendar view of all planned changes across the infrastructure, satisfying the requirement to see every scheduled change in one place. Unlike individual change records or the CAB workbench, it aggregates approved and upcoming changes by planned start and end dates, giving users the complete forward-looking picture.

Why this answer

The Change Schedule in ServiceNow provides a calendar view showing all scheduled changes across the infrastructure, allowing users to visualize planned maintenance windows, identify overlaps, and coordinate changes. It aggregates change requests by their planned start and end dates and can be filtered by CI, group, or other criteria. This is the primary interface for viewing scheduled changes.

Exam trap

CIS-ITSM often tests the distinction between change-related interfaces — candidates confuse the Change Schedule (enterprise-wide calendar) with CAB Workbench (meeting management) or dashboards (custom reports), picking the wrong tool for viewing all scheduled changes.

How to eliminate wrong answers

Option A is wrong because a Dashboard is a configurable collection of widgets and reports — it can display change data if configured, but it is not the dedicated view for all scheduled changes. Option B is wrong because the Configuration Item list shows CI records, not their associated change schedules — it does not present a calendar of changes. Option D is wrong because the Service Portal is a self-service interface for end users and does not provide the comprehensive change schedule view that the Change Schedule module offers.

Option E is wrong because CAB Workbench is for managing CAB meetings and agendas, not for viewing the full enterprise change schedule — it shows only changes relevant to a specific meeting.

Full explanation →

251

Multi-Selectmedium

A problem manager is configuring the Problem Management process and needs to define how known errors are managed. Which TWO statements accurately describe the 'Known Error' functionality in ServiceNow ITSM? (Choose two.)

Select 2 answers

A.A known error is a problem that has a documented root cause and a workaround.

B.A known error record automatically closes the associated problem record.

C.The Known Error Database (KEDB) is a repository that stores known errors and their workarounds.

D.Known errors can be created directly from an incident record without an associated problem.

E.Known errors are only accessible to users with the problem_manager role.

AnswersA, C

In ITIL and ServiceNow, a known error represents a problem where the root cause is identified and a workaround is available. This allows IT to provide temporary solutions to users while a permanent fix is developed. The known error record is typically created from a problem and includes details of the root cause and workaround, making this statement accurate.

Why this answer

A known error is a problem with a documented root cause and workaround, and the KEDB is the repository for these records. These two statements correctly describe the functionality. Known errors are not created directly from incidents, do not auto-close problems, and are accessible to multiple roles for effective incident resolution.

Exam trap

The trap here is assuming that known errors can be created from incidents or that they automatically close problems, when they are derived from problems and remain open until a permanent fix.

Full explanation →

252

MCQhard

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?

A.A Data Lookup definition on the task table

B.A Business Rule on the Change Request table that evaluates state changes and updates linked Problem records

C.A Client Script on the Problem table checking parent change status

D.A UI Policy on the Change form

AnswerB

A Business Rule on the Change Request table fires on state changes, so when the change is cancelled it can query and update the linked Problem records, setting state to Assess and triggering notification to the assignee. This automates the cross-table transition the stakeholder requires.

Why this answer

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.

Exam trap

The trap is choosing a client-side or presentation-layer control (Client Script or UI Policy) for a server-side automation requirement; ServiceNow exams expect candidates to match the mechanism to the execution context and the need to update related records.

How to eliminate wrong answers

Option A is wrong because a Data Lookup definition maps data between tables for display or reference; it does not execute logic or trigger state transitions. Option C is wrong because a Client Script runs in the browser and cannot reliably update related records or fire notifications on the server. Option D is wrong because a UI Policy only controls field visibility, mandatory, and read-only behavior on the form; it cannot transition a Problem record or send notifications.

Full explanation →

253

MCQmedium

An IT manager wants to report on the average time it takes problems to move from the 'Assess' state to 'Root Cause Analysis'. Which reporting feature in ServiceNow should be used to track this stage duration?

A.Data Archiving rules

B.Sys_audit table queries in standard List View

C.Metric Definitions / Metric Instance table

D.Service Level Agreements (SLAs) on the incident table

AnswerC

Metric Definitions create Metric Instances that record the duration a record spends in each state, such as Assess to Root Cause Analysis. This satisfies the stem's need to report average stage duration, which standard field-based reporting on the Problem table cannot calculate.

Why this answer

Metric Definitions and the Metric Instance table are designed to track duration and state transition timing on records, making them the correct feature for measuring how long problems spend in a specific state such as 'Assess' to 'Root Cause Analysis.' Metric Definitions define what to measure (e.g., time in state), and Metric Instances store the calculated values per record. This is the standard ServiceNow mechanism for stage duration reporting.

Exam trap

CIS-ITSM often tests the difference between SLAs (external service commitments on incidents) and Metrics (internal duration/state tracking) — candidates incorrectly pick SLAs for measuring internal problem stage durations.

How to eliminate wrong answers

Option A is wrong because Data Archiving rules move old records to archive tables to manage database size — they have nothing to do with measuring stage durations. Option B is wrong because querying the sys_audit table in a standard List View shows field-level change history but does not provide aggregated duration metrics or a reporting-friendly structure for stage timing. Option C is correct.

Option D is wrong because SLAs on the incident table measure service level compliance (response/resolution targets) on incidents, not problem state transition durations — SLAs are not designed for internal problem lifecycle stage measurement.

Full explanation →

254

Multi-Selecthard

When designing complex request fulfillment processes, which THREE mechanisms are available in ServiceNow to handle approvals? (Choose three.)

Select 3 answers

A.Catalog Client Script 'approve()' function

B.Approval - Group workflow activity

C.Approval - User workflow activity

D.Flow Designer 'Ask for Approvals' action

E.Dictionary Policy approval rules

AnswersB, C, D

The Approval - Group workflow activity routes a request to a specified group, where any eligible member can approve, rather than targeting named individuals. This satisfies the stem's complex fulfilment requirement for approvals that survive personnel changes without editing the workflow.

Why this answer

Option B (Approval - Group workflow activity) is correct because the legacy Workflow Editor provides a dedicated 'Approval - Group' activity that routes an approval record to a specified group, generating sysapproval_approver records for its members. Option C (Approval - User workflow activity) is correct because the Workflow Editor also offers an 'Approval - User' activity that creates an approval for a specific user, letting the workflow pause until that user approves or rejects. Option D (Flow Designer 'Ask for Approvals' action) is correct because Flow Designer includes the built-in 'Ask for Approval' action, which creates approval records and waits for the designated approvers, making it the modern mechanism for handling approvals in flows.

Option A is incorrect because 'approve()' is not a Catalog Client Script function; client scripts run in the browser and cannot create or process approval records server-side. Option E is incorrect because Dictionary Policies enforce data rules (mandatory, read-only, default values) on records and do not generate or manage approval requests.

Exam trap

CIS-ITSM often tests the misconception that approvals can be triggered from client scripts or dictionary policies, when the legitimate mechanisms are workflow activities and Flow Designer actions.

Full explanation →

255

MCQeasy

What is the primary function of the 'Workarounds' field on a Problem record?

A.To document temporary solutions that can be shared with service desk agents to resolve related incidents

B.To log the exact times the server experienced packet loss

C.To store the final approved code for software deployment

D.To record the financial cost of the problem

AnswerA

The Workarounds field holds temporary mitigations that restore service without resolving the underlying root cause, letting service desk agents apply them to related incidents while permanent problem resolution proceeds. This matches the stem's requirement to document temporary solutions shared with agents for resolving linked incidents.

Why this answer

The 'Workarounds' field on a Problem record is specifically designed to capture temporary fixes or alternative solutions that can be used to restore service or resolve incidents while the underlying root cause is still being investigated. These workarounds are often shared with service desk agents to help them quickly resolve related incidents, reducing downtime and improving user productivity. This aligns with ITIL's Problem Management practice, where workarounds are a key output of problem investigation and are documented for reuse.

Exam trap

CIS-ITSM often tests the distinction between temporary workarounds and permanent fixes, so candidates must remember that the Workarounds field is for interim solutions, not final resolutions or unrelated data.

How to eliminate wrong answers

Option B is wrong because logging exact times of server packet loss is a monitoring or event management activity, not the purpose of the Workarounds field; such data would typically be recorded in incident or event records, not as a workaround. Option C is wrong because storing final approved code for software deployment is a release and deployment management function, not a workaround; workarounds are temporary and not necessarily code-based. Option D is wrong because recording the financial cost of a problem is related to cost tracking or financial management, not workarounds; workarounds focus on technical or procedural solutions, not cost accounting.

Full explanation →

256

MCQeasy

Which table stores individual Change Tasks (such as Post-Implementation Testing or Implementation tasks) associated with a Change Request?

A.incident_task

B.change_task

C.wm_task

D.sc_task

AnswerB

The change_task table stores the individual task records that decompose a change request, including Implementation and Post-Implementation Testing tasks. Each row references its parent change request, so querying change_task returns exactly the associated tasks the stem describes.

Why this answer

The change_task table stores individual Change Tasks associated with a Change Request in ServiceNow. Change Tasks represent the granular work items such as implementation, testing, or review tasks that roll up to the parent Change. This is the correct table because it is specifically designed for Change Management task records.

Exam trap

CIS-ITSM often tests whether candidates confuse the various task tables (incident_task, change_task, sc_task, wm_task) and their parent record types, so memorizing the table-to-process mapping is critical.

How to eliminate wrong answers

Option A is wrong because incident_task stores tasks associated with Incidents, not Changes. Option C is wrong because wm_task is used by Work Management (or legacy Project Management) and is not the table for Change Tasks. Option D is wrong because sc_task stores tasks associated with Service Catalog requests (Requested Items), not Change Requests.

Full explanation →

257

MCQeasy

Which action should a problem coordinator take when a permanent fix has been successfully deployed and verified?

A.Change the priority to 1 - Critical

B.Delete the problem record immediately to save database storage

C.Transition the Problem state to Resolved / Closed

D.Reassign the problem to the Service Desk as a new incident

AnswerC

Once the permanent fix is deployed and verified, the Problem no longer requires investigation, so its state moves to Resolved and then Closed. This satisfies the stem's condition that the fix has been successfully deployed and verified.

Why this answer

When a permanent fix has been deployed and verified, the problem coordinator should transition the Problem record to Resolved, and then typically to Closed after a verification period. This reflects that the root cause has been eliminated and no further investigation is needed, while preserving the record for audit and knowledge management.

Exam trap

CIS-ITSM often tests whether candidates know that problem records are transitioned to Resolved/Closed rather than deleted or converted, so options implying record destruction or incident reassignment are the trap.

How to eliminate wrong answers

Option A is wrong because changing priority to Critical is unrelated to fix completion — priority reflects business impact and urgency, not lifecycle state, and escalating priority after resolution is nonsensical. Option B is wrong because deleting the problem record destroys the audit trail and the knowledge gained from root cause analysis, violating ITIL knowledge management practices; problems are closed, not deleted. Option D is wrong because reassigning the problem as a new incident confuses the two record types — incidents are unplanned interruptions, while problems are the underlying causes; converting a resolved problem into an incident would duplicate work and corrupt reporting.

Full explanation →

258

MCQeasy

When designing a catalog item, what is the purpose of adding 'Help Text' to a variable?

A.To log errors in the system log when the variable is empty

B.To define default database values for the variable

C.To restrict the user role required to view the variable

D.To provide additional instructions or guidance to users filling out the form

AnswerD

Help Text supplies contextual guidance beside a variable, clarifying expected input format or meaning without enforcing validation. This satisfies the design requirement of reducing user confusion and submission errors when completing catalog item forms, improving data quality and lowering abandonment rates during request submission.

Why this answer

Help Text on a variable provides additional instructions, context, or guidance to the user filling out the catalog form. It appears as supplementary text near the variable and does not affect data storage, validation, or access control. Its sole purpose is to improve the user experience by clarifying what is expected.

Exam trap

CIS-ITSM often tests the distinction between Help Text and other variable attributes like Default Value, Instructions, and Tooltip — the trap is confusing a UX guidance feature with a data or security control.

How to eliminate wrong answers

Option A is wrong because Help Text does not log errors — logging is handled by business rules, script includes, or system logs, not by variable help text. Option B is wrong because default values are set via the variable's 'Default Value' field or a script default, not Help Text. Option C is wrong because role-based visibility is controlled by User Criteria, ACLs, or UI Policies, not by Help Text.

Full explanation →

259

MCQmedium

An analyst opens an incident and needs to populate several fields quickly with predefined standard text for a VPN connectivity issue. Which ServiceNow feature should the analyst use?

A.Quick Messages

B.Data Policies

C.Incident Templates

D.Catalog Client Scripts

AnswerC

Incident Templates store predefined field values, letting the analyst populate multiple fields with standard VPN text in one action. This directly satisfies the requirement to fill several fields quickly with predefined standard text, avoiding manual re-entry and ensuring consistency across similar incidents.

Why this answer

Incident Templates in ServiceNow allow analysts to quickly populate multiple fields with predefined standard text for common issues like VPN connectivity. Templates can pre-fill short description, description, category, assignment group, and other fields, saving time and ensuring consistency.

Exam trap

The trap is confusing Templates with Quick Messages — candidates may pick Quick Messages because they think of predefined text, but the question specifies populating several fields, which requires Templates.

How to eliminate wrong answers

Option A is wrong because Quick Messages are used for inserting predefined text into a single field (like additional comments or work notes), not for populating multiple fields on a form. Option B is wrong because Data Policies enforce field requirements and read-only behavior, not pre-populate standard text. Option D is wrong because Catalog Client Scripts are used in Service Catalog items to dynamically change form behavior, not for incident field population.

Full explanation →

260

MCQeasy

What is the primary purpose of a Standard Change template?

A.To handle major incident swarming

B.To automate emergency change approvals

C.To define the risk assessment questions for normal changes

D.To provide a repeatable, pre-approved method for implementing a low-risk change

AnswerD

Standard Change templates deliver repeatable, pre-approved execution for low-risk changes, eliminating the need for individual Change Advisory Board review each time. This directly satisfies the stem's requirement for a primary purpose: streamlining routine changes through a defined, authorised procedure that maintains control whilst reducing administrative overhead and approval delays.

Why this answer

A Standard Change template provides a pre-approved, repeatable method for implementing low-risk, routine changes. Because the change is pre-approved by the CAB, it bypasses the normal approval workflow, reducing administrative overhead and enabling faster execution of common tasks like password resets or minor software installs.

Exam trap

CIS-ITSM often tests the distinction between standard, normal, and emergency changes, and candidates may incorrectly associate standard templates with emergency approval automation.

How to eliminate wrong answers

Option A is wrong because major incident swarming is an incident management practice for collaborative resolution, not a change management function. Option B is wrong because emergency changes follow an expedited but still reviewed approval path — they are not automated by Standard Change templates, which are specifically for pre-approved low-risk changes. Option C is wrong because risk assessment questions for normal changes are defined in the Risk Assessment questionnaire, not in Standard Change templates.

Full explanation →

261

MCQeasy

An incident record has been closed, and a user calls in reporting the exact same issue is still occurring. What is the recommended ITIL and ServiceNow best practice?

A.Use the Reopen UI action if permitted by system properties and workflow.

B.Delete the closed incident and create a new one.

C.Convert the closed incident into a change request.

D.Modify the closed record state directly via database XML export.

AnswerA

Reopening preserves the original incident's timeline, assignment and audit trail, which ITIL and ServiceNow treat as preferable to raising a duplicate. The Reopen UI action restores the record to an active state, subject to system properties and workflow rules governing whether reopening is permitted.

Why this answer

ITIL and ServiceNow best practice is to reopen the closed incident using the Reopen UI action, which is governed by system properties (such as glide.incident.reopen or the incident state model) and workflow conditions. Reopening preserves the incident's history, SLA data, and relationships, which is essential for accurate reporting and problem management.

Exam trap

CIS-ITSM often tests the misconception that a closed incident should be deleted or recreated, when the correct ITIL-aligned action is to reopen it (subject to system properties and workflow).

How to eliminate wrong answers

Option B is wrong because deleting a closed incident destroys audit history, SLA records, and any linked problem, change, or knowledge articles — and ServiceNow generally restricts deletion of task records for compliance reasons. Option C is wrong because converting an incident to a change request is a different process used when the resolution requires a controlled change, not when a user reports the same unresolved issue. Option D is wrong because modifying a closed record directly via XML export/import bypasses audit trails, business rules, and state model validation, and is explicitly discouraged in ServiceNow administration.

Full explanation →

262

Multi-Selectmedium

Which TWO of the following are recommended best practices when configuring identification rules in the CMDB? (Choose two.)

Select 2 answers

A.Create identification rules directly on the global cmdb table for all custom classes.

B.Use attributes that uniquely and reliably identify the CI, such as serial numbers or MAC addresses.

C.Disable all out-of-the-box identification rules to improve payload processing speed.

D.Include volatile attributes like IP addresses as the sole criteria in identification rules.

E.Test identification rules thoroughly in a sub-production instance before deploying payloads in production.

AnswersB, E

Serial numbers and MAC addresses are globally unique, stable hardware identifiers, so they reliably distinguish CIs of the same class. This satisfies the uniqueness constraint identification rules demand, preventing duplicate CI records that weaker attributes such as name or IP address would produce.

Why this answer

Option B is correct because effective identification rules must rely on attributes that uniquely and reliably distinguish a CI, such as serial numbers or MAC addresses, so that incoming payloads match the right existing record instead of creating duplicates. Option E is correct because identification rules should always be validated in a sub-production instance first; this lets you confirm that payloads reconcile to the intended CIs and catch unintended inserts or merges before they corrupt production CMDB data. Option A is not recommended because identification rules should be defined on the appropriate class (or the class hierarchy where they apply), not indiscriminately on the global cmdb table for all custom classes, which can cause incorrect matching across unrelated CI types.

Option C is wrong because disabling all out-of-the-box identification rules does not improve processing speed in a recommended way and would break standard CI class reconciliation. Option D is wrong because volatile attributes like IP addresses change frequently and must not be the sole criteria, since that would cause unstable or duplicate CI identification.

Exam trap

CIS-ITSM often tests the misconception that identification rules belong on the global cmdb table or that any unique-looking attribute (like IP) is acceptable, when in fact rules must be class-scoped and use stable, non-volatile identifiers.

Full explanation →

263

MCQeasy

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?

A.Emergency Change

B.Standard Change

C.Normal Change

D.Template Change

E.Minor Change

AnswerB

Standard Change is a pre-approved Change Model for low-risk, routine changes, so it bypasses the full approval workflow. This matches the requirement for minimal approval on a frequent change, unlike Normal Change, which requires assessment and authorisation.

Why this answer

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.

Exam trap

CIS-ITSM often tests the confusion between Change Model types, tempting candidates toward 'Normal' or invented types like 'Minor' when the scenario describes pre-approved, low-risk, repeatable work.

How to eliminate wrong answers

Option A is wrong because Emergency Changes are for urgent, high-impact situations requiring expedited approval, not routine low-risk work. Option C is wrong because Normal Changes require full assessment and approval through the change process. Option D is wrong because 'Template Change' is not a Change Model type in ServiceNow.

Option E is wrong because 'Minor Change' is not a standard Change Model category in the platform.

Full explanation →

264

MCQeasy

What is the purpose of the 'No quantity' checkbox on a Service Catalog item form?

A.It sets the default inventory stock count to zero.

B.It disables checkout for bulk orders exceeding 10 items.

C.It prevents the item from being added to the shopping cart.

D.It hides the quantity selector on the item form, forcing the quantity to be 1.

AnswerD

Selecting 'No quantity' removes the quantity field from the catalogue item form, so the request is submitted with a fixed quantity of one. This suits items ordered as single units, preventing users from requesting multiples.

Why this answer

The 'No quantity' checkbox on a catalog item form removes the quantity selector from the item's order form, effectively forcing the quantity to 1. This is used for items where ordering multiples doesn't make sense, such as a single laptop assignment or a software license tied to one user. It is a UI-level restriction on the catalog item definition.

Exam trap

The trap is confusing 'No quantity' with 'No cart' or 'Cannot be ordered' — candidates often assume it blocks ordering entirely rather than just hiding the quantity selector.

How to eliminate wrong answers

Option A is wrong because the checkbox has nothing to do with inventory stock counts — inventory is managed separately via the Inventory module and stock rules. Option B is wrong because there is no built-in 'bulk order limit of 10' tied to this checkbox; order limits are configured via max quantity rules, not this flag. Option C is wrong because preventing cart addition is controlled by the 'Cannot be ordered' or 'Hidden' flags, not 'No quantity' — items with 'No quantity' can still be added to the cart, just with quantity fixed at 1.

Full explanation →

265

MCQeasy

Which table stores the individual requested items (RITMs) created when a user checks out a cart from the Service Catalog?

A.sc_cat_item

B.sc_request

C.incident

D.sc_req_item

AnswerD

The sc_req_item table holds each individual requested item generated when a catalog cart is submitted, one record per line item. The parent request record lives in sc_request, so sc_req_item satisfies the requirement for storing the individual RITMs.

Why this answer

The sc_req_item table stores individual Requested Items (RITMs) — one record per catalog item checked out in a cart. When a user submits a cart, ServiceNow creates one sc_request record and one sc_req_item record per distinct catalog item, making sc_req_item the correct answer.

Exam trap

CIS-ITSM often tests the confusion between sc_request (the parent REQ) and sc_req_item (the RITM line item), causing candidates to pick sc_request when asked about individual requested items.

How to eliminate wrong answers

Option A is wrong because sc_cat_item is the catalog item definition table (the template), not the transactional record. Option B is wrong because sc_request stores the parent request header, not the individual line items. Option C is wrong because incident is the ITSM incident table, unrelated to catalog checkout.

Full explanation →

266

Multi-Selecthard

A problem manager needs to ensure that when a problem is closed, the resolution information is captured and can be reused for future incidents. Which TWO actions should be taken to meet this requirement? (Choose two.)

Select 2 answers

A.Attach the original incident records to the problem record.

B.Enable the 'Known error' field on the problem record.

C.Require the 'Resolution code' and 'Resolution notes' fields to be filled before the problem can be closed.

D.Create a knowledge article from the problem record upon closure.

E.Set the problem state to 'Closed' automatically after 7 days of inactivity.

AnswersC, D

Mandating resolution code and notes ensures that the root cause and fix are documented. This information is essential for building the Known Error Database (KEDB) and for future reference. Without these fields, the resolution would be lost, and the problem record would lack the details needed to help resolve similar incidents quickly.

Why this answer

To capture resolution information for future reuse, the problem record must enforce documentation of resolution details and ideally convert that into a knowledge article. Requiring resolution code and notes ensures the data is entered, while creating a knowledge article makes it accessible to support staff. Together, these actions populate the KEDB and enable faster incident resolution.

Exam trap

The trap here is assuming that simply marking a problem as a known error or attaching incidents automatically captures resolution details; the actual capture requires mandatory fields and knowledge creation.

Full explanation →

267

MCQeasy

An organization wants to ensure that when an incident is resolved, the Caller receives an email notification with a survey link. Which baseline module manages the triggering of this survey?

A.Incident Properties

B.Event Registry

C.SLA Definitions

D.Assessment and Surveys (Assessment Metric Types)

AnswerD

The Assessment and Surveys module holds survey definitions and the assessment metric types that drive them. Configuring a survey there and attaching it to incident resolution triggers the notification email containing the survey link to the Caller.

Why this answer

The Assessment and Surveys module (specifically Assessment Metric Types) manages survey definitions, triggers, and metric types used to generate surveys. When an incident is resolved, a survey can be triggered based on a metric type, and the notification with the survey link is part of that configuration.

Exam trap

The trap is confusing survey triggering with notifications or events — candidates may pick Event Registry because it triggers emails, but the survey definition itself lives in the Assessment and Surveys module.

How to eliminate wrong answers

Option A is wrong because Incident Properties control default field values and behaviors on the incident table, not survey triggering. Option B is wrong because Event Registry defines events that can trigger notifications or scripts, but it does not manage survey definitions or metric types. Option C is wrong because SLA Definitions define service level agreements and their workflows, not surveys.

Full explanation →

268

MCQmedium

A ServiceNow implementation specialist is designing a Catalog Item where the visibility of a custom variable named 'server_os' must dynamically change depending on the selection of another variable named 'request_type'. Which configuration tool is best suited for this requirement?

A.Data Policy

B.Business Rule

C.Catalog Client Script

D.Catalog UI Policy

AnswerD

Catalog UI Policies run client-side logic that shows, hides, or makes mandatory variables based on another variable's value, which is exactly the dynamic dependency between request_type and server_os. They act on the catalogue form without altering stored data.

Why this answer

Catalog UI Policies are specifically designed to dynamically control the visibility, mandatory, and read-only state of catalog item variables based on the values of other variables on the form, all without requiring a server round-trip. They execute client-side and are the native, declarative tool for this exact requirement. Since the requirement is to change visibility of 'server_os' based on 'request_type', a Catalog UI Policy is the correct and most efficient choice.

Exam trap

CIS-ITSM often tests the confusion between client scripts and UI policies, where candidates might choose a client script for dynamic visibility because they think scripting is always needed, but the exam expects knowledge of declarative UI Policies as the best-suited tool for simple show/hide requirements.

How to eliminate wrong answers

Option A is wrong because Data Policies are server-side rules that enforce mandatory, read-only, and default values on task records (like incident or change), not on catalog item variables, and they cannot dynamically show/hide variables on a catalog form. Option B is wrong because Business Rules run on the server and are used for database operations, record manipulation, and server-side logic; they cannot directly control client-side variable visibility in real time without additional scripting and are not the intended tool for this UI behavior. Option C is wrong because Catalog Client Scripts are used for custom client-side scripting (e.g., onChange, onLoad, onSubmit) and while they can achieve visibility changes, they require custom code and are not the best-suited declarative tool for simple visibility toggles; UI Policies are preferred for such requirements.

Full explanation →

269

MCQmedium

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?

A.Client Script onLoad calculation

B.Data Lookup Definitions and Matchers

C.Dictionary Overrides for Priority

D.UI Policy Action matrix

AnswerB

Data Lookup Definitions and Matchers let ServiceNow derive a field value, such as Problem priority, by matching Impact and Urgency against a configured matrix table. This directly satisfies the requirement for automatic priority calculation on Problem record creation.

Why this answer

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.

Exam trap

CIS-ITSM often tests the difference between client-side scripts, UI policies, and server-side data lookups, luring candidates into choosing UI-centric options when the requirement is for a server-side matrix calculation.

How to eliminate wrong answers

Option A is wrong because a Client Script onLoad runs in the browser when a form loads and is not suited for server-side, matrix-based priority calculation; it also cannot easily reference a data lookup matrix. Option C is wrong because Dictionary Overrides change field behavior (e.g., making a field mandatory or read-only) but do not perform value lookups or calculations. Option D is wrong because a UI Policy Action matrix controls field visibility or mandatory state on the form, not the calculation of field values like Priority.

Full explanation →

270

MCQeasy

Which module allows problem managers to review unassigned problems that require triage and assignment?

A.Closed Problems

B.Known Errors

C.My Work

D.Open - Unassigned

AnswerD

The Open - Unassigned module filters problems that are open yet have no assigned owner, giving problem managers the triage queue they need. It directly satisfies the requirement to review unassigned problems awaiting triage and assignment, unlike assigned or closed views.

Why this answer

The 'Open - Unassigned' module in ServiceNow Problem Management is a default list view that filters problems with a state of Open and no assigned user, specifically designed for problem managers to perform triage and assign resources. It provides a centralized queue of new or unassigned problems that require immediate attention. This module is part of the standard Problem Management application and is essential for managing the problem lifecycle.

Exam trap

CIS-ITSM often tests the distinction between modules that show unassigned problems versus those that show assigned or closed problems, so candidates must remember that 'Open - Unassigned' is specifically for triage.

How to eliminate wrong answers

Option A is wrong because 'Closed Problems' displays problems that have been resolved and closed, not those needing triage. Option B is wrong because 'Known Errors' lists problems that have a known root cause and workaround, typically after analysis, not unassigned ones. Option C is wrong because 'My Work' shows records assigned to the current user, not unassigned problems.

Full explanation →

271

MCQhard

An administrator created a Multi-Row Variable Set (MRVS) and wants to populate a field on the target task using the data collected in the MRVS rows. Since MRVS stores data as a JSON string, what is the best way to extract and process this data in a workflow script?

A.Dot-walk directly to current.variables.mrvs_name.column_name in the task activity.

B.Use a Record Producer script to flatten the MRVS into custom table rows automatically.

C.Configure a Catalog UI Policy to export MRVS rows to the sys_variable_value table.

D.Parse the JSON string using JSON.parse(current.variables.mrvs_name) in a Run Script activity and iterate through the resulting array.

AnswerD

MRVS values are stored as a JSON string, so JSON.parse converts it into an array of row objects. A Run Script activity can then iterate that array to read each row's fields and write the required value onto the target task record.

Why this answer

The MRVS stores its collected row data as a JSON string in the variable value, so the only reliable way to access individual columns is to parse that string into a JavaScript object/array. JSON.parse(current.variables.mrvs_name) converts the serialized rows into an array of objects, which a Run Script workflow activity can then iterate over to read each row's column values and write them to the target task fields. Direct dot-walking (Option A) does not work because the MRVS is not a true related list of child records — it is a single variable holding a JSON payload, so there are no column-level fields to traverse.

Exam trap

CIS-ITSM often tests the misconception that MRVS variables behave like related lists or child records that can be dot-walked directly, when in fact they are JSON strings requiring explicit parsing.

How to eliminate wrong answers

Option A is wrong because dot-walking assumes the MRVS is backed by child records with addressable column fields, but it is actually a single variable containing a JSON string, so current.variables.mrvs_name.column_name resolves to nothing. Option B is wrong because a Record Producer script is used to create records from a catalog item submission, not to flatten an existing MRVS into custom table rows during a workflow; it also does not address the JSON parsing requirement. Option C is wrong because a Catalog UI Policy controls form field behavior on the catalog form (visibility, mandatory, read-only) and cannot export MRVS rows to sys_variable_value; the MRVS data is already stored as a variable value, not as separate rows to export.

Full explanation →

272

MCQeasy

What is the primary benefit of using Variable Sets in the ServiceNow Service Catalog?

A.To create reusable collections of variables that can be shared across multiple catalog items

B.To enforce database-level table normalization

C.To automatically close requests upon creation

D.To replace the need for workflows entirely

AnswerA

Variable Sets let you define one collection of variable definitions and attach it to many catalog items, so updates propagate everywhere. This directly satisfies the stem's reusability constraint, eliminating duplicated maintenance across items and keeping question sets consistent without rebuilding them per item.

Why this answer

Variable Sets are reusable containers of variable definitions (questions) that can be attached to multiple catalog items, eliminating the need to recreate identical questions on each item. When a variable set is updated, the change propagates to every catalog item that references it, ensuring consistency across the catalog. This is the core design intent: define once, reuse everywhere.

Exam trap

CIS-ITSM often tests whether candidates confuse Variable Sets (reusable variable containers) with UI Policies, Data Policies, or workflows — the trap is picking an answer that describes a control mechanism rather than a reuse mechanism.

How to eliminate wrong answers

Option B is wrong because Variable Sets have nothing to do with database table normalization — normalization is a schema design concern handled via table relationships and dictionary configuration, not catalog variables. Option C is wrong because automatically closing requests upon creation is a workflow/flow or business rule behavior, not a function of Variable Sets. Option D is wrong because Variable Sets only supply variable definitions; workflows, flows, and approval engines are still required to drive fulfillment and task orchestration.

Full explanation →

273

MCQmedium

An administrator needs to ensure that a set of variables appears on multiple Catalog Items without having to recreate them individually for each item. Which feature should the administrator configure?

A.Catalog Client Script Template

B.Record Producer

C.Variable Set

D.Order Guide

AnswerC

A Variable Set is a reusable collection of variables that can be attached to many Catalog Items, so the administrator defines the variables once and references the set rather than recreating them per item. This satisfies the requirement to surface identical variables across multiple items.

Why this answer

A Variable Set is a reusable container of variables that can be attached to multiple Catalog Items, so the administrator defines the variables once and references the set on each item. This avoids duplicating variable definitions across items and keeps them synchronized when changes are needed.

Exam trap

CIS-ITSM often tests whether candidates confuse Variable Sets (reusable variable containers) with Order Guides (bundled item ordering) or Record Producers (direct record creation) — the key differentiator is 'reuse variables across items.'

How to eliminate wrong answers

Option A is wrong because a Catalog Client Script Template is not a ServiceNow feature for sharing variables — client scripts are attached individually to items or via UI policies, not templated for variable reuse. Option B is wrong because a Record Producer creates records on a target table; it does not share variables across catalog items. Option D is wrong because an Order Guide groups multiple catalog items into a single ordering flow, not a mechanism for reusing variable definitions.

Full explanation →

274

Multi-Selectmedium

Which TWO of the following are true about 'Incident Tasks'?

Select 2 answers

A.Closing an incident task automatically closes the parent.

B.They allow for granular work tracking.

C.They are automatically assigned to the same user as the parent.

D.They can only be created by admins.

E.They are child tasks of the incident.

AnswersB, E

Incident Tasks decompose an incident into discrete, assignable units of work, each with its own state, assignment and short description. This granularity lets teams track individual activities separately from the parent incident, satisfying the requirement for detailed, item-level progress visibility across the resolution effort.

Why this answer

Option B is correct because Incident Tasks exist specifically to break an incident down into smaller, individually trackable units of work, giving teams granular visibility into progress on each piece of the resolution effort. Option E is correct because an Incident Task is by definition a child record of the parent incident, inheriting its context and rolling up under it rather than standing alone. Closing a task does not close the parent incident (A), since the parent's state is managed independently and typically requires all work plus resolution to be complete.

Tasks are not automatically assigned to the parent's assignee (C); assignment is set explicitly or by assignment rules. And they are not admin-only (D), as fulfillers and other roles with the appropriate role permissions can create them.

Exam trap

CIS-ITSM often tests the assumption that child task state changes cascade to the parent record — candidates incorrectly pick 'closing a task closes the incident' because that pattern exists in some other ITSM tools.

Full explanation →

275

MCQmedium

A problem manager notices that many problem records are created from incident records but the link between the incident and the problem is not automatically established. The manager wants to ensure that whenever an incident is promoted to a problem, the incident is automatically associated with the new problem record. Which action should be taken?

A.Use the 'Promote to Problem' UI action on the Incident form.

B.Enable the 'Create Problem from Incident' UI action.

C.Configure the 'Problem' related list on the Incident form to auto-populate.

D.Create a business rule that inserts a problem record and updates the incident's problem field.

AnswerA

The 'Promote to Problem' UI action on the Incident form creates a new problem record and automatically associates the incident with it. This action is designed to streamline the process by copying relevant incident details and establishing the link. It ensures that the incident is directly tied to the problem, fulfilling the manager's requirement without manual intervention.

Why this answer

The 'Promote to Problem' UI action is the standard ServiceNow feature that creates a problem from an incident and automatically links the two records. It copies key fields and establishes the relationship, ensuring traceability. Custom solutions or manual actions are not required and may not provide the same seamless integration.

Exam trap

The trap here is assuming that any UI action or related list automatically creates the link, when only the specific 'Promote to Problem' UI action does so.

Full explanation →

276

MCQeasy

Which state indicates that a Problem has completed root cause analysis and investigation, and a fix is currently being implemented via Change Management?

A.Closed

B.Root Cause Analysis

C.Fix In Progress

D.Assess

AnswerC

Fix In Progress is the Problem state recorded once root cause analysis and investigation are complete and a Change is actively implementing the remediation. It satisfies the stem's condition that a fix is currently being deployed through Change Management.

Why this answer

The 'Fix In Progress' state in Problem Management indicates that root cause analysis is complete and a fix is being implemented, typically through a Change request. This state bridges Problem and Change Management, ensuring the fix is tracked and applied. It is the correct state when a fix is actively being deployed.

Exam trap

CIS-ITSM often tests the distinction between 'Root Cause Analysis' and 'Fix in Progress', causing candidates to select the former when a fix is already being implemented.

How to eliminate wrong answers

Option A is wrong because 'Closed' means the problem is resolved and no further action is needed. Option B is wrong because 'Root Cause Analysis' is the state where investigation is ongoing, not yet complete. Option D is wrong because 'Assess' is an early state for evaluating the problem, before root cause analysis.

Full explanation →

277

MCQmedium

What is the primary function of the 'Incident State' field choices?

A.To determine SLA priority

B.To define user visibility

C.To track the lifecycle stage of an incident

D.To trigger the assignment rule

AnswerC

Incident State records where an incident sits in its lifecycle — New, In Progress, On Hold, Resolved, Closed — driving workflow transitions and reporting. It is distinct from Priority or Assignment Group, which classify urgency and ownership rather than progression.

Why this answer

The Incident State field tracks the lifecycle stage of an incident — values like New, In Progress, On Hold, Resolved, and Closed represent where the incident is in its workflow. It is the primary indicator of progress and drives reporting, SLA pause logic, and closure requirements. It does not itself set priority or assignment.

Exam trap

CIS-ITSM often tests whether candidates confuse State (lifecycle stage) with Priority (SLA urgency) or Assignment (routing), causing them to pick a field that drives a different process.

How to eliminate wrong answers

Option A is wrong because SLA priority is determined by the Priority field (impact × urgency) and SLA definitions, not by State. Option B is wrong because user visibility is controlled by ACLs and the 'opened by'/'caller' relationships, not by the State value. Option D is wrong because assignment rules run based on fields like Category, Subcategory, and Assignment Group, not on State — State changes after assignment typically.

Full explanation →

278

MCQeasy

Which field on an incident is used to indicate the severity of the business impact?

A.Impact

B.Priority

C.Urgency

D.Severity

AnswerA

Impact records how extensively the incident affects business operations or users, which is the severity of business impact. Urgency measures how quickly resolution is needed; priority is derived from combining impact and urgency, so it is not the impact field itself.

Why this answer

On a ServiceNow incident, the Impact field indicates the severity of the business impact — how broadly the issue affects users or business operations (e.g., 1 - High, 2 - Medium, 3 - Low). Impact is one of the two inputs (along with Urgency) that the system uses to calculate Priority via the priority lookup matrix.

Exam trap

CIS-ITSM often tests the confusion between Impact, Urgency, and Priority — candidates pick Priority thinking it indicates business impact, when Priority is actually the derived output of Impact and Urgency.

How to eliminate wrong answers

Option B is wrong because Priority is a derived value calculated from Impact and Urgency, not the field that indicates business impact severity itself; it represents the overall urgency ranking for resolution. Option C is wrong because Urgency describes how quickly the issue needs resolution from the user's or business's perspective (time sensitivity), not the breadth or severity of business impact. Option D is wrong because 'Severity' is not a standard field on the ServiceNow incident table — it is a distractor term borrowed from other ITSM tools; ServiceNow uses Impact and Urgency to derive Priority.

Full explanation →

279

MCQmedium

A service desk analyst wants to assign an unassigned incident to themselves with a single click. Which UI Action provides this functionality out of the box?

A.Claim Incident

B.Assign to me

C.Self-Assign

D.Take Ownership

AnswerB

The Assign to me UI Action is shipped out of the box on incident records; it sets the Assigned to field to the current user and saves the record in one click, satisfying the analyst's single-click self-assignment requirement without customisation.

Why this answer

ServiceNow ships an out-of-the-box UI Action named 'Assign to me' on the Incident table that sets the Assigned to field to the current user in a single click. It is a form button visible when the incident is unassigned (or reassignable) and is the standard mechanism analysts use to claim work.

Exam trap

CIS-ITSM often tests whether candidates know the exact out-of-the-box UI Action name — 'Assign to me' — versus plausible but non-existent labels like 'Claim Incident' or 'Self-Assign'.

How to eliminate wrong answers

Option A is wrong because 'Claim Incident' is not a standard out-of-the-box UI Action name on the Incident table — claiming is accomplished via 'Assign to me' or assignment group logic. Option C is wrong because 'Self-Assign' is not a shipped UI Action; it is a plausible-sounding but fabricated label. Option D is wrong because 'Take Ownership' is not a base-system UI Action on Incident; ownership concepts exist in other modules but not as this button.

Full explanation →

280

Multi-Selecthard

An organization is implementing Change Management and needs to configure Maintenance and Blackout schedules. Which THREE characteristics apply to cmn_schedule records used in this context? (Choose three.)

Select 3 answers

A.Schedules are automatically generated by ITOM Discovery based on server reboots

B.Schedules can be referenced by conflict detection to identify blackout violations

C.Schedules can define recurring windows of time (such as weekly maintenance windows)

D.Schedules can include time zone considerations for global organizations

E.Schedules are strictly limited to single-day events and cannot span multiple days

AnswersB, C, D

Conflict detection evaluates change requests against defined schedules, so cmn_schedule records must be referenceable by that engine. Linking a blackout schedule to conflict detection lets the system flag or block changes falling inside prohibited windows, which is precisely the enforcement behaviour the scenario requires.

Why this answer

Option B is correct because cmn_schedule records are referenced by Change Management conflict detection to determine whether a change falls within a blackout window and thus violates it. Option C is correct because cmn_schedule supports recurring schedules, including repeating maintenance windows such as weekly or monthly intervals, via schedule entries and repeating spans. Option D is correct because cmn_schedule records store a time zone, allowing global organizations to define windows that are evaluated correctly across regions.

Option A is not correct because schedules are not auto-generated by ITOM Discovery from server reboots; they are defined by administrators or processes. Option E is not correct because cmn_schedule entries can span multiple days and are not limited to single-day events.

Exam trap

The trap is assuming schedules are auto-generated or limited to single-day events, when in fact they are manually configured, support recurrence, and can span multiple days with time zone awareness.

Full explanation →

281

MCQhard

A Problem task is assigned to a vendor group. The vendor updates the task via an inbound email action. The administrator wants to ensure that the inbound email sender is validated against the vendor company record before updating the task. Where should this validation be implemented?

A.In a Client Script running on the Email form

B.In the Dictionary entry for email body

C.In the script of the Inbound Email Action record

D.In a UI Policy Action

AnswerC

The Inbound Email Action script executes before the record update, giving access to the sender address and the ability to query the vendor company record. Validating there blocks unauthorised senders from modifying the task, satisfying the stem's requirement to check the sender against the vendor company.

Why this answer

Inbound Email Actions in ServiceNow contain a script field where you can inspect the sender (email.from) and validate it against the vendor company record before allowing the task update. This is the correct place because the Inbound Email Action is the processing logic that runs when the email is received and decides whether to update the target record.

Exam trap

CIS-ITSM often tests the misconception that client-side or dictionary-level logic can validate inbound email senders, when only the server-side Inbound Email Action script executes during email processing.

How to eliminate wrong answers

Option A is wrong because Client Scripts run in the browser on form load/change and cannot execute during server-side inbound email processing. Option B is wrong because a Dictionary entry defines field attributes (type, default, etc.) and cannot contain validation logic for email senders. Option D is wrong because UI Policies control form field visibility/read-only behavior in the UI and have no role in inbound email processing.

Full explanation →

282

MCQhard

What is the correct order of operations when an incident meets criteria for both a standard SLA and an SLA pause condition?

A.The latest SLA created always takes priority

B.Conditions are evaluated based on defined order

C.Only one SLA can be active at a time

D.Pause conditions take precedence over start conditions

AnswerB

When an incident satisfies both a standard SLA and a pause condition, the platform applies the configured evaluation order to determine precedence, so the defined sequence governs which SLA applies and when pausing takes effect rather than either rule overriding arbitrarily.

Why this answer

When an incident qualifies for multiple SLAs, ServiceNow evaluates SLA definitions in a defined order (typically the order field on the SLA definition, or the order in which they are processed). Pause conditions are evaluated as part of the SLA lifecycle, but the overall processing follows the configured order rather than a fixed rule like 'pause always wins'.

Exam trap

CIS-ITSM often tests the misconception that pause conditions always override start conditions or that only one SLA can be active — candidates miss that multiple SLAs can run concurrently and are evaluated in a defined order.

How to eliminate wrong answers

Option A is wrong because the latest-created SLA does not automatically take priority; priority is determined by the SLA definition's order or the processing sequence, not creation timestamp. Option C is wrong because multiple SLAs can be active on a single incident simultaneously (e.g., response and resolution SLAs, or SLAs from different SLA definitions). Option D is wrong because pause conditions do not inherently take precedence over start conditions — both are evaluated according to the SLA engine's processing order and the SLA's own configuration.

Full explanation →

283

MCQhard

An administrator is troubleshooting why conflict detection is not running when changes are updated via a REST API integration. Which condition in the conflict detection business rule might prevent execution during API calls?

A.Conflict detection requires an interactive web browser session

B.The business rule checks if the update modifies schedule-related fields (like planned start/end or CI) and runs accordingly

C.REST APIs inherently disable all database business rules globally

D.Integration accounts lack read access to the cmdb_ci table

AnswerB

Conflict detection only fires when the update touches the schedule-related fields the rule inspects, so REST API changes altering other fields bypass it. This condition directly explains why detection does not run during those API calls.

Why this answer

The conflict detection business rule in ServiceNow checks whether the update modifies schedule-related fields such as planned start/end dates or CI relationships, and only runs conflict detection when those fields change. When updates come via REST API, if the payload does not modify those specific fields, the business rule condition evaluates false and conflict detection does not execute. This is the correct answer because it describes the actual conditional logic in the OOB conflict detection business rule.

Exam trap

CIS-ITSM often tests whether candidates understand that business rules have conditions that may not be met during API calls, leading them to incorrectly blame ACLs or API limitations instead of the business rule's field-change condition.

How to eliminate wrong answers

Option A is wrong because conflict detection does not require an interactive web browser session; it runs server-side on database operations regardless of client type. Option C is wrong because REST APIs do not globally disable business rules; business rules execute on API calls unless explicitly bypassed via sysparm_suppress or similar mechanisms. Option D is wrong because integration accounts lacking read access to cmdb_ci would cause a different error (ACL failure), not prevent conflict detection from running due to a business rule condition.

Full explanation →

284

MCQeasy

Which user role is required by default to create, manage, and close incident records within the standard ServiceNow IT Service Management application?

A.snc_read

B.sn_incident_write

C.admin

D.itil

AnswerD

The itil role grants the baseline permissions needed to create, update, and close incident records in ServiceNow ITSM. It satisfies the stem's requirement for default incident management capability, since this role is assigned to fulfil ITIL process tasks without requiring elevated admin rights.

Why this answer

The 'itil' role is the standard user role required to create, manage, and close incident records in ServiceNow ITSM. It grants the necessary permissions to perform these actions without granting full administrative privileges. The other roles either provide read-only access or are too broad.

Exam trap

CIS-ITSM often tests the default roles required for specific actions. Candidates might choose 'sn_incident_write' because it sounds specific to incidents, but the 'itil' role is the standard role that encompasses incident management capabilities.

How to eliminate wrong answers

Option A is wrong because 'snc_read' is a read-only role that allows viewing records but not creating or modifying them. Option B is wrong because 'sn_incident_write' is a role that grants write access to incident records, but it is not the standard role assigned to ITIL users; it is often included as part of the 'itil' role. Option C is wrong because 'admin' has full access but is not the default role for typical incident management; using admin for routine tasks violates the principle of least privilege.

Full explanation →

285

MCQhard

A change coordinator needs to schedule a change that requires a maintenance window. The change must not overlap with any other change affecting the same configuration item (CI). The coordinator runs conflict detection and receives a conflict warning. Which action should the coordinator take to resolve the conflict while preserving the change record?

A.Adjust the planned start and end times of the change to a window that does not overlap with the conflicting change.

B.Ignore the conflict and proceed, because conflict detection is only advisory and does not block scheduling.

C.Remove the CI from the change request so that conflict detection no longer considers it.

D.Cancel the conflicting change and reschedule it for a later date.

AnswerA

Rescheduling the change to a non-overlapping window directly resolves the conflict. This preserves the change record and its details while ensuring the maintenance activities do not collide with other changes on the same CI. It is the most straightforward and policy-compliant resolution.

Why this answer

The correct resolution is to reschedule the change to a maintenance window that does not overlap with the other change on the same CI. This addresses the conflict at its source, keeps the change record intact, and aligns with change management best practices of coordinating schedules to avoid collisions.

Exam trap

The trap here is thinking that conflict detection warnings can be dismissed without consequence or that removing the CI is an acceptable workaround.

Full explanation →

286

MCQhard

An organization requires that when a user submits an order guide, the fulfillment workflow needs to evaluate rules to determine which catalog items are included based on user input. Where are these rules defined?

A.Order Guide Item Mappings

B.Rule Base

C.Catalog Client Scripts

D.Workflow Canvas

AnswerB

The Rule Base holds the decision logic that the fulfilment workflow evaluates against user input to determine which catalog items an order guide includes. Rules are authored there, so it is where inclusion criteria are defined and executed during submission.

Why this answer

The Rule Base is the component within an Order Guide that defines the conditional logic (rules) used to evaluate user input and determine which catalog items are dynamically included in the order. It contains the conditions and associated catalog items that get added when those conditions are met. This is the core mechanism for dynamic item selection in Order Guides.

Exam trap

CIS-ITSM often tests the confusion between the Rule Base (which controls item inclusion) and Item Mappings (which control variable cascading), so candidates must distinguish between these two Order Guide components.

How to eliminate wrong answers

Option A is wrong because Order Guide Item Mappings are used to map variables between the order guide and child items, not to define inclusion rules. Option C is wrong because Catalog Client Scripts run client-side JavaScript for form behavior (e.g., showing/hiding fields) and do not control which items are included in an order guide. Option D is wrong because Workflow Canvas is the graphical workflow editor for process automation, not for defining order guide inclusion rules.

Full explanation →

287

Multi-Selecteasy

Which TWO are common types of changes in ServiceNow?

Select 2 answers

A.Risk-based

B.Scheduled

C.Emergency

D.Normal

E.Routine

AnswersC, D

Emergency changes address unplanned outages or severe incidents and follow an expedited approval path rather than the standard change model. ServiceNow recognises emergency as a distinct change type alongside normal and standard, satisfying the question's requirement for a common change category.

Why this answer

In ServiceNow Change Management, the standard change types are Normal, Standard, and Emergency, so option D (Normal) is correct because it represents the default change type used for changes that require assessment, authorization, and approval through the full change lifecycle. Option C (Emergency) is also correct because it is a recognized change type used for changes that must be implemented immediately, typically to restore service or address a critical issue, and it often bypasses parts of the normal approval process. Options A (Risk-based), B (Scheduled), and E (Routine) are not ServiceNow change types; while risk and scheduling are attributes or characteristics of changes, and 'routine' is not a defined type, they are not among the standard change type values in ServiceNow.

Exam trap

CIS-ITSM often tests the confusion between change types and change attributes, where candidates might select 'Scheduled' or 'Routine' as types, but they are not standard ServiceNow change types.

Full explanation →

288

MCQhard

A change manager notices that a high-risk change was implemented without a post-implementation review, and the change record still shows the state as “Review”. The change manager needs to ensure that a post-implementation review is completed before the change is closed. Which action should the change manager take to enforce this requirement for all future high-risk changes?

A.Send a notification to the change manager when a high-risk change is implemented.

B.Add a mandatory field on the change form for the post-implementation review date.

C.Create a business rule that prevents the change from moving to Closed until the post-implementation review task is closed.

D.Configure a UI policy to make the post-implementation review field read-only after the change is implemented.

AnswerC

A business rule can enforce that the change cannot be closed until the associated post-implementation review task is complete. This ensures the review is not skipped. By applying it to high-risk changes, the manager meets the requirement for future changes.

Why this answer

A business rule that blocks closure until the post-implementation review task is closed enforces the requirement. It ensures that high-risk changes cannot be closed without the review, providing a hard control. This is the most effective way to guarantee compliance for all future high-risk changes.

Exam trap

The trap here is thinking that a notification or a mandatory field is sufficient to enforce a process step, when only a business rule can actively prevent state transition.

Full explanation →

289

Multi-Selectmedium

Which THREE fields on a Problem record are typically editable when the problem is in the 'Assess' state, prior to root cause analysis? (Choose three.)

Select 3 answers

A.Short description

B.Assignment group

C.Sys_created_on timestamp

D.Configuration item

E.System sys_id (read-only system identifier)

AnswersA, B, D

Short description remains editable during 'Assess' because it captures the reported symptom, which staff refine as understanding grows. Root cause analysis has not begun, so this descriptive field is not yet locked by the later 'Root Cause Analysis' state's mandatory-field and read-only constraints.

Why this answer

In the 'Assess' state of a Problem record, the team is still triaging and scoping the issue before formal root cause analysis begins, so the Short description (A) remains editable to refine the problem statement as understanding improves. The Assignment group (B) is also editable because ownership often shifts during assessment as the problem is routed to the correct resolver group. The Configuration item (D) is editable as well, since identifying or correcting the affected CI is part of the assessment and scoping work.

The Sys_created_on timestamp (C) is a system-maintained audit field set at record creation and is never user-editable, and the sys_id (E) is a read-only unique system identifier that cannot be modified.

Exam trap

The trap is assuming that state transitions lock all fields — candidates may think Assess is read-only, or fail to recognize that sys_created_on and sys_id are system fields that are never editable regardless of state.

Full explanation →

290

Multi-Selecthard

Which THREE of the following are benefits of using CI Class Manager? (Choose three.)

Select 3 answers

A.Automatic execution of incident management triage workflows for failed discoveries.

B.Direct editing of system-level Java source code for Discovery patterns.

C.Centralized viewing and editing of class-specific identification rules.

D.Ability to add, modify, and delete attributes for specific CI classes within the hierarchy.

E.Centralized management of reconciliation rules for classes and attributes.

AnswersC, D, E

Class-specific identification rules normally live scattered across individual class records, so editing them one by one is slow and error-prone. CI Class Manager consolidates these rules into a single interface, letting administrators view and edit identification logic for any class centrally, satisfying the benefit of streamlined, consistent configuration.

Why this answer

Option C is correct because CI Class Manager provides a single, centralized console where administrators can view and edit the identification rules that determine how CIs of a given class are uniquely identified and matched during discovery and import. Option D is correct because CI Class Manager allows you to add, modify, and delete attributes on specific CI classes within the CMDB class hierarchy, extending the schema without direct table manipulation. Option E is correct because CI Class Manager centralizes the management of reconciliation rules at both the class and attribute level, controlling how duplicate or conflicting CI records are merged.

Option A is not a CI Class Manager benefit; incident triage workflows for failed discoveries are handled through Discovery/Service Mapping health and error handling, not class administration. Option B is not correct because CI Class Manager does not provide direct editing of system-level Java source code for Discovery patterns; pattern customization is done through the Pattern Designer and related tooling.

Exam trap

The trap here is confusing CI Class Manager's administrative scope (class hierarchy, identification, reconciliation) with Discovery pattern editing or workflow execution, which belong to different tools.

Full explanation →

291

MCQmedium

Which field must be populated to allow the 'Resolution' tab to be visible or actionable?

A.Incident State

B.Caller

C.Assignment Group

D.Category

AnswerA

The Resolution tab only becomes visible and editable once the incident's State field is populated with a value such as Resolved, since resolution information is captured as part of closing the record. Populating State satisfies the stem's requirement for the tab to be actionable.

Why this answer

In ServiceNow Incident Management, the Resolution tab (or Resolution Information section) becomes visible and actionable only when the Incident State is set to 'Resolved' (or 'Closed'). The State field drives the form's UI behavior, so it must be populated correctly to expose resolution fields like Resolution code and Resolution notes.

Exam trap

CIS-ITSM often tests which field gates the Resolution tab — candidates assume Assignment Group or Category drives form behavior, but it is the Incident State field that controls resolution visibility.

How to eliminate wrong answers

Option B is wrong because Caller identifies who reported the incident but has no bearing on whether the Resolution tab appears. Option C is wrong because Assignment Group determines who works the incident, not the form's resolution visibility. Option D is wrong because Category classifies the incident type but does not control the Resolution tab's visibility or actionability.

Full explanation →

292

MCQhard

A fulfillment team requires a workflow to dynamically branch based on the value of a choice variable selected in a Catalog Item. Which activity should be placed in the Flow Designer flow to evaluate this condition?

A.If

B.Wait for Condition

C.Switch Case

D.Ask for Approval

AnswerA

The If flow logic activity evaluates a condition and branches the flow down different paths based on the outcome. Referencing the catalog item's choice variable in its condition lets the workflow dynamically route according to the selected value.

Why this answer

The 'If' activity in Flow Designer is used to evaluate a condition and branch the flow based on the result. It directly supports dynamic branching based on any variable or data available in the flow, including a choice variable from a catalog item. This is the standard way to implement conditional logic in Flow Designer.

Exam trap

CIS-ITSM often tests the difference between 'If' and 'Switch Case' in Flow Designer, and candidates may overcomplicate by choosing 'Switch Case' when a simple condition is needed.

How to eliminate wrong answers

Option B is wrong because 'Wait for Condition' pauses the flow until a condition is met, but it does not branch; it simply waits, which is not suitable for immediate branching based on a variable value. Option C is wrong because 'Switch Case' is used for multi-branch logic based on a single value, but the question asks for evaluating a condition (likely a simple true/false or specific value) and the 'If' activity is the direct equivalent for conditional branching. Option D is wrong because 'Ask for Approval' is used to request approval, not to evaluate a variable and branch.

Full explanation →

293

MCQhard

An enterprise uses custom change states. Where must an administrator define these new states to ensure proper integration with the Change State Model framework?

A.Change State Model records and state transition rules

B.Workflow Designer transition lines only

C.System Dictionary choices on the state field only

D.UI Actions script bodies

AnswerA

Custom change states must be defined on Change State Model records together with state transition rules, because that framework governs which states exist and the permitted transitions between them. Defining states elsewhere leaves the model unaware of them, breaking lifecycle enforcement.

Why this answer

Custom change states must be defined in the Change State Model records along with the state transition rules, because the Change State Model framework governs which states exist and how a change can move between them. Defining states only in the dictionary or UI does not integrate with the model's transition logic.

Exam trap

CIS-ITSM often tests where custom states must be defined — the trap is assuming dictionary choices alone are sufficient, when the Change State Model and its transition rules are the authoritative source.

How to eliminate wrong answers

Option B is wrong because Workflow Designer transition lines control workflow execution, not the authoritative definition of change states in the state model. Option C is wrong because adding choices to the state field's dictionary alone does not register the states with the Change State Model framework or its transition rules. Option D is wrong because UI Actions only control button/UI behavior, not state model definitions.

Full explanation →

294

MCQeasy

An administrator needs to review the overall CMDB health scores for Completeness, Correctness, and Compliance across all classes. Which application and module should they navigate to?

A.CI Class Manager > Overview

B.System Definition > Health Log

C.Configuration > CMDB Dashboard

D.Discovery > Health Metrics

AnswerC

The CMDB Dashboard module opens the comprehensive health dashboard tracking core CMDB health metrics.

Why this answer

The CMDB Dashboard (Configuration > CMDB Dashboard) is the application module that surfaces the overall CMDB health scores for Completeness, Correctness, and Compliance across all classes. It aggregates the health metrics computed by the CMDB Health engine and presents them in a single view for administrators. This is the correct navigation path for reviewing enterprise-wide CMDB health.

Exam trap

CIS-ITSM often tests the distinction between the CMDB Dashboard (aggregated health KPIs) and CI Class Manager (per-class configuration), catching candidates who assume class-level views show enterprise health scores.

How to eliminate wrong answers

Option A is wrong because CI Class Manager > Overview shows class-level details and identification/reconciliation configuration, not the aggregated enterprise health scores for all three KPIs. Option B is wrong because System Definition > Health Log is for system/job health logging, not CMDB data health scores. Option D is wrong because Discovery > Health Metrics relates to Discovery scheduling and MID Server health, not CMDB Completeness/Correctness/Compliance scoring.

Full explanation →

295

MCQhard

A team uses Problem Tasks to divide root cause investigations. A requirement states that a Problem record cannot be moved to 'Fix In Progress' until all child Problem Tasks are in either 'Closed Complete' or 'Closed Skipped' state. How should an administrator configure this validation?

A.An Access Control List (ACL) with script execution

B.A Before Update Business Rule on the Problem table checking active child task counts

C.A Dictionary Override on the State field

D.A UI Policy with an advanced script condition

AnswerB

A server-side Before Business Rule can query related problem tasks and abort the transaction if open tasks exist.

Why this answer

A Before Update Business Rule on the Problem table is the correct approach because it can query the child Problem Tasks via the task relationship and block the state transition when any task is not in 'Closed Complete' or 'Closed Skipped'. Business Rules execute server-side on the database operation, so they enforce the rule regardless of whether the update comes from the UI, an import, or a REST API call. The script can use GlideAggregate to count active child tasks and call current.setAbortAction(true) with a message when the count is greater than zero.

Exam trap

CIS-ITSM often tests whether candidates confuse client-side UI Policies with server-side Business Rules — the trap is picking a UI Policy because it 'looks' like it enforces mandatory behavior, when only a Business Rule can block a database update from any source.

How to eliminate wrong answers

Option A is wrong because an ACL controls field/record read, write, create, and delete access — it cannot evaluate child task states or conditionally block a state transition based on related records. Option C is wrong because a Dictionary Override only changes which field or value is used when the same field name exists on parent and child tables; it has no logic for validating related task states. Option D is wrong because a UI Policy only affects the client-side form (making fields mandatory, read-only, or visible) and is bypassed by background updates, imports, and API calls, so it cannot reliably enforce a state-transition rule.

Full explanation →

296

MCQhard

You are designing an integration where incidents are created via an API. How do you ensure that 'Assignment Rules' are triggered?

A.Ensure the API user has the 'itil' role.

B.Set the 'auto_assignment' flag to true.

C.Enable the 'Run Assignment Rules' checkbox in the API call.

D.Leave the assignment fields empty in the API payload.

AnswerD

Assignment rules execute only when the assignment fields arrive empty, letting the engine evaluate and populate them. Supplying values in the API payload bypasses rule evaluation entirely, so leaving those fields blank ensures the configured assignment logic fires.

Why this answer

Assignment Rules in ServiceNow run automatically on incident insert/update only when the assignment fields (assignment_group, assigned_to) are empty. If the API payload leaves these fields blank, the rules execute and assign the incident. If the payload sets them, the rules are skipped.

Exam trap

The trap is inventing API flags like 'auto_assignment' or checkboxes — ServiceNow assignment rules are triggered by the absence of assignment values, not by an explicit toggle.

How to eliminate wrong answers

Option A is wrong because the 'itil' role grants access to the incident table but does not trigger assignment rules — rules run based on field values, not user roles. Option B is wrong because there is no 'auto_assignment' flag in the incident API; assignment rules are controlled by the emptiness of assignment fields. Option C is wrong because there is no 'Run Assignment Rules' checkbox in the API — this is a fabricated option.

Full explanation →

297

Multi-Selecthard

Which THREE of the following statements are true regarding Identification and Reconciliation Engine (IRE) processing? (Choose three.)

Select 3 answers

A.IRE relies solely on the sys_id attribute to match and update existing Configuration Items.

B.IRE automatically deletes any CI that has not been updated within 30 days.

C.IRE processing can be invoked via script using the CMDBEngine API or JSON payloads.

D.IRE ensures that duplicate CIs are not created when multiple data sources report the same physical item.

E.Reconciliation rules determine which data sources are authorized to update specific CI attributes.

AnswersC, D, E

IRE processing is not limited to scheduled or UI-driven runs; it can be triggered programmatically through the CMDBEngine API or by submitting JSON payloads. This satisfies the stem's requirement that IRE processing be invocable via script.

Why this answer

Option C is correct because IRE processing can be triggered programmatically through the CMDBEngine API (e.g., sn_cmdb.IRE or CMDBEngine) or by submitting JSON payloads to the IRE endpoint, allowing integrations and scripts to run identification and reconciliation on demand. Option D is correct because one of IRE's core purposes is de-duplication: it identifies incoming records against existing CIs using identifiers and reconciliation rules so that multiple data sources reporting the same physical item update one CI rather than creating duplicates. Option E is correct because reconciliation rules (and the related data source precedence/authoritative source configuration) define which data source is allowed to update which CI attributes, resolving conflicts when sources disagree.

Option A is not correct because IRE matches on identifiers such as serial number, name, MAC address, and other identifier entries, not solely on sys_id; sys_id is a unique record key, not a matching attribute. Option B is not correct because IRE does not automatically delete CIs based on a 30-day inactivity threshold; CI lifecycle and retirement are handled by separate CMDB data management/health policies, not by IRE processing itself.

Exam trap

CIS-ITSM often tests misconceptions about IRE, such as believing it relies solely on sys_id or that it auto-deletes stale CIs, when in fact it uses sophisticated identification and reconciliation rules.

Full explanation →

298

MCQeasy

Where do you configure the email notification that is sent to the 'Caller' when an incident is resolved?

A.Business Rule > Email

B.System Notification > Email > Notifications

C.Incident Form Layout

D.Service Portal Configuration

AnswerB

Caller resolution notifications are defined under System Notification > Email > Notifications, where the notification record for the incident resolved event is configured. Editing that record controls the email dispatched to the caller when the incident reaches the resolved state.

Why this answer

Email notifications in ServiceNow are configured in System Notification > Email > Notifications, where you define the notification trigger (e.g., incident resolved), recipients (e.g., Caller), and email template. This is the baseline module for all outbound notification rules.

Exam trap

The trap is thinking a Business Rule is needed to send email — candidates often pick Business Rule because it's scriptable, but the exam expects the standard notification module for out-of-the-box email configuration.

How to eliminate wrong answers

Option A is wrong because Business Rules are server-side scripts that run on database operations; while a business rule can send an email via gs.eventQueue or GlideEmailOutbound, it is not the configuration module for notifications. Option C is wrong because the Incident Form Layout controls which fields appear on the form, not email behavior. Option D is wrong because Service Portal Configuration manages the portal UI and widgets, not email notifications.

Full explanation →

299

MCQeasy

Which user role is required by default to create, manage, and close Problem records in ServiceNow?

A.change_manager

B.itil

C.problem

D.major_incident_manager

AnswerC

The "problem" role grants the baseline permissions needed to create, manage, and close Problem records in ServiceNow. Unlike itil, which covers broader incident and change tasks, this dedicated role satisfies the stem's default requirement for full Problem lifecycle management without relying on elevated admin rights.

Why this answer

The 'problem' role is specifically designed for managing Problem records in ServiceNow. It grants the necessary permissions to create, read, update, and delete problem records. This role is typically assigned to problem managers and problem coordinators.

Exam trap

CIS-ITSM often tests the specific roles required for problem management, and candidates may confuse the 'itil' role with the 'problem' role, not realizing that 'itil' does not grant full problem management capabilities.

How to eliminate wrong answers

Option A is wrong because change_manager is for managing change records, not problems. Option B is wrong because itil is a broad role that includes many ITIL processes but does not specifically grant full problem management rights; it may allow reading and some updates but not full management. Option D is wrong because major_incident_manager is for managing major incidents, not problems.

Full explanation →

300

MCQhard

An organization wants to ensure that whenever a Normal Change is set to 'Assess', an automatic risk assessment questionnaire is sent to the change assignee. Which mechanism triggers this assessment out of the box?

A.Scheduled jobs running nightly

B.Assessment trigger rules (asmt_metric_type / risk assessment triggers)

C.Email notifications with mail scripts

D.Client scripts on the change request form

AnswerB

Assessment trigger rules fire automatically when a Normal Change enters the 'Assess' state, dispatching the risk questionnaire to the assignee without custom scripting. Configured against the assessment metric type, they satisfy the stem's out-of-the-box requirement for state-driven, assignee-targeted assessment delivery.

Why this answer

Out of the box, ServiceNow uses Assessment trigger rules (configured on the asmt_metric_type and related trigger condition records) to automatically generate assessment instances when a record meets defined conditions — such as a Normal Change entering the 'Assess' state. These trigger rules evaluate the change record and, when matched, create an asmt_assessment_instance that sends the questionnaire to the designated recipient (the assignee). This is the native, declarative mechanism for assessment automation.

Exam trap

CIS-ITSM often tests the misconception that notifications or client scripts can drive assessment generation, when in fact only Assessment trigger rules (asmt_metric_type triggers) create assessment instances out of the box.

How to eliminate wrong answers

Option A is wrong because scheduled jobs run on a time interval and cannot react to a state transition like 'Assess' in real time; they are used for batch or periodic processing, not event-driven assessments. Option C is wrong because email notifications with mail scripts only send messages — they do not create assessment instances or evaluate trigger conditions, so no questionnaire would be generated. Option D is wrong because client scripts run in the browser on the form and are used for UI behavior (field visibility, validation), not for server-side generation of assessment instances.

Full explanation →

ServiceNow Certified Implementation Specialist - IT Service Management (CIS-ITSM) (CIS-ITSM) (CIS-ITSM) — Questions 226–300