ServiceNow Certified Implementation Specialist - IT Service Management (CIS-ITSM) (CIS-ITSM) CIS-ITSM Questions 76–150 | Page 2/5

MCQeasy

An IT administrator wants to ensure that a specific catalog item is only visible to members of the 'Database' group. Where should the administrator configure this restriction?

A.User Profile form

B.Catalog Properties module

C.Available For / Not Available related lists

D.Access Control Lists (ACLs) on sc_cat_item

AnswerC

The Available For / Not Available related lists on the catalog item control which users and groups can see it, so adding the 'Database' group to Available For restricts visibility to exactly those members, satisfying the requirement that only that group sees the item.

Why this answer

The 'Available For' and 'Not Available For' related lists on the catalog item record control which users, groups, or roles can see and order the item. Adding the 'Database' group to the 'Available For' list restricts visibility to members of that group, which is the standard, supported way to scope catalog item access.

Exam trap

The trap is over-engineering with ACLs — candidates with a security background often pick ACLs because they think access control always means ACLs, but ServiceNow's catalog visibility is declaratively managed via 'Available For' user criteria.

How to eliminate wrong answers

Option A is wrong because the User Profile form controls personal preferences and user attributes, not catalog item visibility. Option B is wrong because the Catalog Properties module configures global catalog behavior (e.g., search settings, cart options), not per-item visibility restrictions. Option D is wrong because while ACLs on sc_cat_item can technically restrict read access, they are a lower-level security mechanism and not the intended configuration point for catalog item visibility — the 'Available For' related list is the designed, declarative approach that also integrates with catalog search and the service portal.

Full explanation →

MCQhard

While reviewing the CMDB Correctness score, an administrator notices a high count of orphan CIs. What is the definition of an orphan CI in the context of CMDB Health Correctness?

A.A CI that has not been updated by any discovery source or manual import in over 90 days.

B.A CI record that shares the exact same serial number and name as another active CI record.

C.A CI whose assigned support group or managed-by user no longer exists in the sys_user table.

D.A CI that has no relationships defined where relationships are expected according to class configuration rules.

AnswerD

Orphan CIs are flagged when class configuration rules expect relationships but none exist, directly satisfying the Correctness metric's requirement to detect missing mandatory connections. This differs from duplicate or stale CIs, which belong to other CMDB Health KPIs. The high orphan count therefore reflects absent expected relationships, not merely unlinked records.

Why this answer

An orphan CI is a Configuration Item that belongs to a class that is expected to have relationships (such as containing or running on), but currently has no relationships defined.

Full explanation →

Multi-Selecteasy

Which TWO options are benefits of using Service Catalog Request Management in ServiceNow? (Choose two.)

Select 2 answers

A.Elimination of all network infrastructure errors

B.Automatic generation of source code repositories

C.Standardization and automation of service delivery processes

D.Mandatory replacement of all Incident Management processes

E.Improved tracking and visibility for end-users regarding their orders

AnswersC, E

Service Catalog Request Management enforces predefined catalogue items, workflows and approval paths, so delivery becomes repeatable and automated rather than ad hoc. This standardisation directly satisfies the stem's benefit requirement by reducing manual effort and inconsistent fulfilment across service requests.

Why this answer

Option C is correct because Service Catalog Request Management uses catalog items, workflows, and approval flows to standardize how services are requested and automate fulfillment, ensuring consistent and repeatable service delivery. Option E is correct because the ServiceNow Service Catalog provides requesters with a portal view and status tracking (e.g., 'My Requests' / 'Requests' module) showing order state, approvals, and fulfillment progress, improving visibility for end-users. Option A is incorrect because no ServiceNow catalog feature eliminates network infrastructure errors; that is outside its scope.

Option B is incorrect because the Service Catalog does not automatically generate source code repositories; it manages service requests, not software version control. Option D is incorrect because Request Management complements rather than mandatorily replaces Incident Management, which handles unplanned interruptions and failures.

Exam trap

The trap is selecting absolute-sounding options (eliminate all errors, mandatory replacement) — exam writers include these as distractors because they sound impressive but violate ITIL's complementary-process principle.

Full explanation →

Multi-Selecthard

Which THREE items are included in the Major Incident Workbench?

Select 3 answers

A.System Logs.

B.Incident Task list.

C.Communication history.

D.SLA Definition editor.

E.Timeline.

AnswersB, C, E

The Incident Task list tracks the individual action items assigned to responders during a major incident, showing ownership and completion status. It is a core component of the Major Incident Workbench for coordinating resolution work.

Why this answer

The Major Incident Workbench in ServiceNow is designed to give responders a single pane of glass for managing a major incident, and it includes the Incident Task list (B), which shows the child tasks created to resolve the incident and their states. It also includes the Communication history (C), which records all outbound notifications, emails, and updates sent to stakeholders during the incident. The Timeline (E) is likewise part of the workbench, providing a chronological view of key incident events, actions, and updates.

System Logs (A) are accessed through system diagnostics/log modules rather than the workbench, and the SLA Definition editor (D) is a separate configuration tool for creating and modifying SLA records, not a component of the Major Incident Workbench.

Exam trap

CIS-ITSM often tests the specific components of the Major Incident Workbench, and candidates may mistakenly include System Logs or SLA Definition editor, which are not part of it.

Full explanation →

MCQeasy

What is the name of the out-of-the-box workbench tool used to manage and conduct Change Advisory Board meetings?

A.Release Workbench

B.CAB Workbench

C.Major Incident Workbench

D.Change Management Console

AnswerB

CAB Workbench is the out-of-the-box ServiceNow tool that directly satisfies the requirement to manage and conduct Change Advisory Board meetings. It provides a dedicated agenda view, meeting scheduling, attendee management and change record review, letting CAB members assess and approve changes within a single interface rather than through standard change lists.

Why this answer

The CAB Workbench is the out-of-the-box ServiceNow tool specifically designed to manage and conduct Change Advisory Board meetings. It provides agenda management, attendee tracking, decision recording, and meeting minutes. No other workbench in the platform serves this governance function.

Exam trap

CIS-ITSM often tests exact OOB tool names, and candidates fall for plausible-sounding distractors like 'Change Management Console' instead of the real 'CAB Workbench'.

How to eliminate wrong answers

Option A is wrong because the Release Workbench manages release planning and readiness, not CAB meetings. Option C is wrong because the Major Incident Workbench is for coordinating major incident response and communications. Option D is wrong because 'Change Management Console' is not an actual OOB workbench tool — it's a distractor name that sounds plausible but doesn't exist as a named feature.

Full explanation →

MCQhard

A custom integration creates Problem records in ServiceNow via REST API. The integration payload occasionally omits the 'Assignment group', but company policy requires all problems to have an assignment group before reaching the 'Assess' state. Where should this default assignment logic be robustly implemented?

A.In a Service Portal Widget controller script

B.In a UI Policy Action

C.In an onLoad Client Script on the Problem form

D.In a Before Insert/Update Business Rule on the Problem table

AnswerD

A Before Insert/Update Business Rule runs server-side on the Problem table regardless of entry channel, so it applies the default assignment group before the record can reach Assess. This enforces policy for REST-created records, not just form submissions.

Why this answer

Implementing the default assignment logic in a Before Insert/Update Business Rule on the Problem table ensures that the assignment group is set regardless of how the record is created or updated, including via REST API, import sets, or UI. Business Rules run on the server side and are the most robust place for data integrity logic that must apply to all entry points.

Exam trap

CIS-ITSM often tests the appropriate use of Business Rules versus Client Scripts or UI Policies; candidates may choose client-side solutions that do not apply to API or background operations, leading to data integrity gaps.

How to eliminate wrong answers

Option A is wrong because a Service Portal Widget controller script only affects records created through that specific widget, not via REST API or other channels. Option B is wrong because a UI Policy Action only runs on the client side when the form is used, so it does not apply to API-created records. Option C is wrong because an onLoad Client Script only executes when the form loads in the browser, and it cannot enforce logic on API inserts or updates.

Full explanation →

MCQmedium

What is the purpose of the 'Parent Incident' field?

A.To link an incident to a problem

B.To link an incident to a user

C.To define the SLA group

D.To link child incidents to a master incident

AnswerD

The Parent Incident field establishes a hierarchical relationship, letting multiple child incidents be grouped under one master incident. This supports consolidated tracking and resolution when several related incidents stem from a single underlying cause or major outage.

Why this answer

The 'Parent Incident' field is used to link child incidents to a master incident, typically a major incident. When a major incident is created, related child incidents are associated with it via the Parent Incident field, creating a hierarchical relationship. This allows the major incident to serve as a coordination point, and child incidents inherit updates and share context with the parent.

Exam trap

CIS-ITSM often tests the purpose of the Parent Incident field — candidates confuse it with problem linking or user linking, but the correct answer is that it links child incidents to a master (major) incident.

How to eliminate wrong answers

Option A is wrong because linking an incident to a problem uses the 'Problem' field or the 'Problem ID' reference, not the Parent Incident field. Option B is wrong because linking an incident to a user is done via the 'Caller', 'Opened by', or 'Assigned to' fields, not Parent Incident. Option C is wrong because SLA groups are defined by SLA definitions and assignment rules, not by the Parent Incident field.

Full explanation →

Multi-Selecthard

When configuring advanced change authorization rules, which THREE records or features can be utilized in ServiceNow? (Choose three.)

Select 3 answers

A.Approval Definitions associated with change categories or models

B.Service Catalog variable sets

C.Change Approval Policies providing dynamic group assignments

D.Change Models defining specific process flows

E.Hardware asset reconciliation rules

AnswersA, C, D

Approval Definitions are reusable records that specify who must approve, and they attach to change categories or models. The authorisation engine consults the definition linked to the change's category or model to determine the required approvers, satisfying the stem's authorisation-rule requirement.

Why this answer

Option A is correct because Approval Definitions can be tied to change categories or change models, allowing authorization logic to be scoped to the type of change being requested. Option C is correct because Change Approval Policies enable dynamic approver group assignment based on conditions such as risk, category, or CI, rather than relying on static approver lists. Option D is correct because Change Models define the process flow a change follows, and the associated model determines which approval definitions and policies apply during the change lifecycle.

Options B and E are not part of advanced change authorization: Service Catalog variable sets are used to collect and organize catalog item inputs, and Hardware asset reconciliation rules are used for asset normalization and reconciliation, not for approving changes.

Exam trap

CIS-ITSM often tests the distinction between catalog/asset features (variable sets, reconciliation rules) and change governance features, tempting candidates to pick familiar-sounding but unrelated modules.

Full explanation →

Multi-Selecthard

Which THREE settings can be modified in an SLA Definition to control the SLA timer?

Select 3 answers

A.Duration type

B.Priority

C.Pause conditions

D.Incident State

E.Schedule

AnswersA, C, E

Duration type determines whether the SLA timer counts down to an end time or counts up from a start time. This directly governs how the timer is calculated against the SLA Definition, satisfying the requirement for a setting that controls the SLA timer.

Why this answer

In an SLA Definition, the Duration type (A) determines how the SLA timer's target is calculated — for example, whether it uses a relative duration from the task's creation/start or a percentage of a defined span — so it directly controls how the timer runs. Pause conditions (C) define the circumstances under which the SLA timer is paused (e.g., while the task is in an inactive state or awaiting a customer), which directly governs when the timer stops and resumes. The Schedule (E) specifies the business hours/calendar the SLA uses, so the timer only counts time within the defined schedule, directly controlling elapsed time.

The other options do not belong: Priority (B) is a task attribute used for routing/assignment rather than an SLA timer control, and Incident State (D) is a field on the incident record, not a timer setting in the SLA Definition (state-based behavior is handled through pause conditions or start/stop conditions, not by selecting a state as a timer setting).

Exam trap

CIS-ITSM often tests the distinction between fields on the incident record (Priority, State) and settings inside the SLA Definition (Duration type, Pause conditions, Schedule), catching candidates who conflate the two.

Full explanation →

MCQeasy

When migrating incidents from a legacy system, you need to ensure that the SLA duration is calculated based on the Business Calendar. Where is this configured?

A.SLA Definition record.

B.Incident Properties.

C.Workflow Activity.

D.Incident Business Rule.

AnswerA

The SLA Definition record holds the Business Calendar reference that drives duration calculation, so attaching the correct calendar there makes migrated incidents inherit business-hours timing. Without it, SLA durations would count continuous time rather than the defined schedule.

Why this answer

In ServiceNow, SLA duration calculations (including business calendar, schedule, and time zone) are configured on the SLA Definition record. The SLA Definition specifies the schedule (e.g., 8x5 business calendar) that determines when the SLA clock runs, so this is where business calendar-based duration is set.

Exam trap

CIS-ITSM often tests the misconception that SLA business calendars are configured in Incident Properties or Business Rules, when they are actually defined on the SLA Definition record via the Schedule field.

How to eliminate wrong answers

Option B is wrong because Incident Properties control system-wide incident behavior (e.g., auto-close, assignment) but not SLA duration or business calendar settings. Option C is wrong because Workflow Activities are steps in a workflow and do not configure SLA calendars. Option D is wrong because Incident Business Rules enforce record logic (e.g., state changes, field defaults) and do not define SLA business calendars.

Full explanation →

Multi-Selectmedium

Which TWO of the following actions can be performed using Catalog UI Policies? (Choose two.)

Select 2 answers

A.Automatically generate parent Request [sc_request] records upon form load

B.Make a catalog variable read-only or editable

C.Modify workflow execution paths directly during runtime

D.Make a catalog variable mandatory based on another variable's value

E.Write data directly to external third-party REST endpoints synchronously

AnswersB, D

Catalog UI Policies run client-side logic against catalog item variables, letting you set a variable's read-only or editable state dynamically. This satisfies the stem's action requirement by controlling whether the user can modify that variable's value on the form.

Why this answer

Catalog UI Policies in ServiceNow are client-side rules that dynamically control the behavior of catalog item variables on the catalog form, so option B is correct because they can set a variable to read-only or editable based on conditions evaluated on the form. Option D is also correct because Catalog UI Policies can make a variable mandatory (or not) depending on the value of another variable, which is a core use case for conditional variable requirements. Option A is incorrect because generating parent Request [sc_request] records is a server-side action typically handled by workflows, business rules, or script includes, not by client-side UI policies.

Option C is incorrect because workflow execution paths are determined by the workflow engine on the server, and UI policies cannot modify them at runtime. Option E is incorrect because UI policies run in the browser and cannot synchronously write data to external REST endpoints; that requires server-side scripting such as RESTMessageV2 or outbound REST integrations.

Exam trap

CIS-ITSM often tests the boundary between client-side UI Policies and server-side logic, trapping candidates who think UI Policies can create records or call external services.

Full explanation →

MCQmedium

What is the purpose of the 'Configuration Item' (CI) field on the Incident form?

A.To list the incident reporter

B.To define the SLA group

C.To store the resolution notes

D.To identify the affected asset

AnswerD

The CI field records the specific asset or service affected by the incident, linking the record to its entry in the CMDB. This satisfies the stem's requirement to identify what is broken, enabling impact assessment, correct assignment, and historical reporting against that configuration item.

Why this answer

The Configuration Item (CI) field on the Incident form identifies the specific asset, service, or infrastructure element affected by the incident, linking the incident to the CMDB. This linkage enables impact analysis, SLA targeting based on the CI's criticality, and root-cause correlation across incidents affecting the same CI. It is not used for reporter identity, SLA grouping, or resolution notes.

Exam trap

The trap is conflating the CI field with caller or SLA fields — candidates must remember CI is strictly the affected asset reference to the CMDB.

How to eliminate wrong answers

Option A is wrong because the incident reporter is captured in the 'Caller' or 'Opened by' field, not the CI field. Option B is wrong because SLA grouping is determined by SLA definitions and the task's SLA records, not by the CI field itself. Option C is wrong because resolution notes are stored in 'Close notes' or 'Resolution' fields, not the CI reference.

Full explanation →

MCQmedium

What is the 'Service Desk' group's primary role in Incident Management?

A.Managing service level agreements

B.Developing new applications

C.Fixing all hardware issues

D.Single Point of Contact for end users

AnswerD

Acting as the single point of contact satisfies the Service Desk's core Incident Management constraint: end users report every issue through one channel rather than contacting resolver groups directly. This centralised intake enables consistent logging, categorisation, initial diagnosis and ownership of incidents until resolution or escalation.

Why this answer

The Service Desk is defined in ITIL as the Single Point of Contact (SPOC) between the IT organization and users, handling all incident reports, service requests, and communications. Its primary role in Incident Management is to log, categorize, prioritize, and route incidents, and to keep users informed — not to own SLAs or fix every issue itself.

Exam trap

CIS-ITSM often tests the confusion between the Service Desk's SPOC/communication role and functional ownership of SLAs or technical fixes — candidates over-attribute responsibilities to the Service Desk that actually belong to other ITIL practices.

How to eliminate wrong answers

Option A is wrong because managing SLAs is the responsibility of Service Level Management, not the Service Desk — the Service Desk consumes SLA targets but does not define or manage them. Option B is wrong because developing new applications is an application development/DevOps function, entirely outside the Service Desk's scope. Option C is wrong because the Service Desk is not required to fix all hardware issues; it performs first-line diagnosis and escalates to second-line support groups when needed.

Full explanation →

MCQeasy

When configuring a Standard Change catalog, which table stores the actual Standard Change proposals before they are approved and published?

A.std_change_proposal

B.kb_knowledge

C.std_change_record_producer

D.change_request

AnswerA

The std_change_proposal table holds draft Standard Change proposals, including their template, category and approval state, until they are approved and published to the std_change_record table. It is therefore the staging table the question asks for.

Why this answer

The std_change_proposal table is the dedicated staging table where Standard Change proposals are created, reviewed, and stored before approval. Once a proposal is approved and published, it generates a std_change_record_producer record that produces actual change_request records. This separation allows governance over which standard changes are permitted before they become available in the catalog.

Exam trap

CIS-ITSM often tests the distinction between the three Standard Change tables (proposal, record producer, change_request), and candidates commonly pick change_request because it sounds like the 'real' change record.

How to eliminate wrong answers

Option B is wrong because kb_knowledge stores knowledge base articles, not change proposals. Option C is wrong because std_change_record_producer holds the approved/published template that generates change records, not the pre-approval proposals. Option D is wrong because change_request stores actual change tickets, not the catalog-level proposals that define what standard changes are available.

Full explanation →

MCQhard

An organization requires that certain catalog items require approval from the ordering user's cost center manager rather than their direct supervisor. How can this custom approval routing be implemented in a workflow?

A.Using Catalog UI Policies to force approval fields

B.Setting the system property 'glide.sc.approval.cost_center'

C.By modifying the base system 'approvals' business rule

D.Using an Approval - User activity in the workflow configured with a script that dots-walks from the user's cost center to the manager

AnswerD

ServiceNow's Approval - User activity accepts a dynamically resolved approver, so dot-walking from the ordering user's cost center record to its manager returns the correct approver rather than the direct supervisor, satisfying the cost centre routing requirement.

Why this answer

Using an Approval - User activity in the workflow with a script that dots-walks from the user's cost center to the manager allows dynamic approval routing based on the cost center, making option D correct.

Exam trap

CIS-ITSM often tests the misconception that system properties or UI policies can control approval routing, when in fact workflow scripting is required for dynamic approver selection.

How to eliminate wrong answers

Option A is wrong because Catalog UI Policies control field visibility and behavior on the form, not approval routing. Option B is wrong because there is no such system property 'glide.sc.approval.cost_center' by default; approval routing is not controlled by a simple property. Option C is wrong because modifying the base system 'approvals' business rule is not recommended and does not provide the flexibility to route based on cost center manager.

Full explanation →

MCQeasy

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

A.Configuration item

B.Priority

C.Service

D.Assignment group

E.Short description

AnswerA

The Configuration item field records which specific CI the change modifies, linking the request to the affected asset. This directly answers what identifies the configuration item being modified, distinguishing it from fields such as description or category.

Why this answer

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

Exam trap

CIS-ITSM often tests the distinction between Service and Configuration item, causing candidates to confuse the two when identifying the specific CI being modified.

How to eliminate wrong answers

Option B is wrong because Priority indicates the urgency and importance of the change, not the CI being modified. Option C is wrong because Service refers to the business service affected, which may encompass multiple CIs, but it does not pinpoint the specific CI. Option D is wrong because Assignment group identifies the team responsible for implementing the change, not the CI.

Option E is wrong because Short description is a brief text summary of the change, not a reference to a CI.

Full explanation →

MCQeasy

Which type of catalog design element allows users to create task records, such as Incident or Problem records, directly from the Service Catalog?

A.Catalog Item

B.Record Producer

C.Order Guide

D.Content Item

AnswerB

A Record Producer is a catalog item that generates task records, such as incidents or problems, on submission. It maps catalog variables onto the target table's fields, letting users create those records directly from the Service Catalog rather than through the standard form.

Why this answer

A Record Producer is a catalog design element that allows users to create task records (e.g., Incident, Problem, Change) directly from the Service Catalog. It presents a form-like interface and, upon submission, generates a record in the specified table. This is distinct from a Catalog Item, which creates a request (sc_req_item) and may generate tasks.

Exam trap

CIS-ITSM often tests the distinction between Catalog Items (create requests) and Record Producers (create task records directly), tricking candidates who assume all catalog elements create requests.

How to eliminate wrong answers

Option A is wrong because a Catalog Item creates a request item (sc_req_item) and typically involves fulfillment tasks, but it does not directly create Incident or Problem records unless configured with a workflow. Option C is wrong because an Order Guide groups multiple catalog items into a single order, but it does not directly create task records like Incidents. Option D is wrong because a Content Item is used to display static content (e.g., images, text) in the catalog, not to create records.

Full explanation →

MCQmedium

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

A.sn_change_cab.cab_manager

B.admin

C.itil

D.cab_analyst

E.change_manager

AnswerA

The sn_change_cab.cab_manager role grants access to the CAB Workbench module, which is scoped to the Change Management CAB application. Without it, the technician cannot see the module, satisfying the stem's requirement for the specific role needed.

Why this answer

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

Exam trap

CIS-ITSM often tests the assumption that admin or itil grants access to every module, when in fact scoped application roles like sn_change_cab.cab_manager are required for specific interfaces.

How to eliminate wrong answers

Option B is wrong because admin grants broad platform privileges but is not the specific role that surfaces the CAB Workbench module in the application menu. Option C is wrong because itil is a general ITIL user role that does not include CAB Workbench access. Option D is wrong because cab_analyst is not a valid out-of-box role for CAB Workbench access.

Option E is wrong because change_manager manages change records but does not by itself grant CAB Workbench module visibility.

Full explanation →

MCQhard

An IT administrator is configuring Service Level Agreements (SLAs) for a critical cloud infrastructure service. The requirement is that the SLA pause condition should trigger whenever a customer is actively providing requested information, but the time elapsed during the pause must be completely excluded from the duration calculation. Which SLA configuration element achieves this behavior in ServiceNow?

A.Retroactive Start calculation override

B.SLA Definition Pause Condition

C.SLA Workflow timer extension

D.Business Rule intercepting task state changes

AnswerB

The SLA Definition's pause condition specifies the state during which the task timer halts, and paused duration is excluded from elapsed time. Configuring the pause condition to trigger on 'awaiting customer information' state satisfies the requirement to exclude that time from the SLA duration.

Why this answer

The SLA Definition Pause Condition in ServiceNow allows you to specify conditions under which the SLA timer is paused. When the condition is met (e.g., customer is actively providing information), the timer stops, and the elapsed time during the pause is excluded from the SLA duration calculation. This directly achieves the required behavior.

Exam trap

CIS-ITSM often tests SLA configuration elements, and candidates may confuse pause conditions with other timer manipulations like retroactive start or workflow extensions, leading to incorrect selections.

How to eliminate wrong answers

Option A is wrong because Retroactive Start is used to set the SLA start time in the past, not to pause the timer. Option C is wrong because SLA Workflow timer extension is not a standard configuration element; workflows can manipulate timers but are not the primary mechanism for pause conditions. Option D is wrong because a Business Rule intercepting task state changes is a custom approach and not the standard SLA configuration element designed for pausing.

Full explanation →

MCQmedium

An administrator needs to restrict a catalog item so that it can only be ordered by managers. Which feature should be used to define this audience criteria?

A.Access Control List (ACL)

B.Workflow Approval Rule

C.Dictionary Privilege

D.User Criteria

AnswerD

User Criteria defines the audience conditions, such as role or department, that determine who may order a catalog item. Configuring it to require the manager role satisfies the requirement to restrict ordering to managers only.

Why this answer

User Criteria is the ServiceNow feature specifically designed to define who can view or order a catalog item based on user attributes, roles, groups, departments, or companies. It is applied directly on the Catalog Item record via the 'Available For' or 'Not Available For' related lists, making it the correct mechanism to restrict ordering to managers.

Exam trap

The trap here is confusing access control mechanisms (ACLs, dictionary privileges) with catalog audience targeting — candidates often pick ACL because it sounds like the 'security' answer, but catalog ordering eligibility is governed by User Criteria.

How to eliminate wrong answers

Option A is wrong because ACLs control record-level and field-level read/write/create/delete access at the database layer, not catalog ordering eligibility, and are not the intended tool for audience targeting on catalog items. Option B is wrong because Workflow Approval Rules define who must approve a request after it is submitted, not who is permitted to order the item in the first place. Option C is wrong because Dictionary Privileges govern who can read/write specific table columns and have no bearing on catalog item visibility or ordering rights.

Full explanation →

MCQeasy

An administrator wants to add an image and descriptive formatting to a catalog item form without capturing user input. Which variable type should be used?

A.Reference

B.Label

C.Checkbox

D.Single Line Text

AnswerB

A Label variable displays static text, images and rich formatting on a catalog item form without storing any user response, satisfying the requirement to present content without capturing input. Unlike other variable types, it holds no value and is excluded from submitted data, making it the appropriate choice for purely descriptive elements.

Why this answer

A Label variable is used to display static text, images, or formatted instructions on a catalog item form without capturing any user input. It is purely for presentation purposes, such as adding a descriptive header or an image. This matches the requirement to add an image and descriptive formatting without input.

Exam trap

CIS-ITSM often tests the distinction between input-capturing variables and display-only variables; candidates may choose 'Single Line Text' thinking it can display text, but it is an input field.

How to eliminate wrong answers

Option A is wrong because a Reference variable is used to select a record from another table, which captures user input. Option C is wrong because a Checkbox is a boolean input field, not for static content. Option D is wrong because Single Line Text is an input field for capturing text, not for displaying static images or formatting.

Full explanation →

Multi-Selecthard

When designing a complex Service Catalog request fulfillment process using Flow Designer, which THREE features are available to handle approvals and tasks? (Choose three.)

Select 3 answers

A.Direct execution of legacy graphical workflows inside the flow canvas

B.Ask for Approval flow action

C.Create Task flow action

D.Automatic roll-back to previous stages upon rejection

E.Wait for Condition flow logic

AnswersB, C, E

The Ask for Approval action pauses flow execution and generates approval records routed to specified users or groups, supporting the stem's approval requirement within Service Catalog fulfilment. Approvers act via the ServiceNow interface, and the flow resumes based on their decision.

Why this answer

Option B, the Ask for Approval flow action, is correct because Flow Designer provides this built-in action to generate approval records (sysapproval_approver) for users or groups and pause the flow until the approval is granted or rejected, which is essential for catalog request fulfillment. Option C, the Create Task flow action, is correct because it lets the flow instantiate task records (such as catalog tasks) that carry out the fulfillment work, and the flow can wait on their completion before proceeding. Option E, the Wait for Condition flow logic, is correct because Flow Designer supports waiting on a condition (for example, a record state or field value) to control sequencing and gating of approvals and tasks within the process.

Option A is not correct because legacy graphical workflows cannot be executed directly inside the flow canvas; they must be migrated or called via other integration means. Option D is not correct because Flow Designer does not automatically roll back to previous stages upon rejection; rejection handling must be explicitly modeled with branches or conditions.

Exam trap

CIS-ITSM often tests the misconception that Flow Designer can natively run legacy graphical workflows or auto-rollback stages, when in fact those require explicit actions or subflows.

Full explanation →

Multi-Selecthard

When configuring Problem Management properties (Problem Administration > Properties), which TWO behaviors can typically be controlled or enabled? (Choose two.)

Select 2 answers

A.Automatically provision AWS cloud infrastructure upon problem creation

B.Configure bi-weekly payroll deduction rates

C.Require root cause to be filled in before closing or resolving a problem

D.Force all end users to reset their Active Directory passwords

E.Enable automatic communication of workarounds to related active incidents

AnswersC, E

Requiring root cause completion before closure enforces data quality at the point of resolution, satisfying the stem's demand for a controllable Problem Administration property. ServiceNow's Problem Properties include a mandatory root cause field setting that blocks state transition to Closed or Resolved until populated, ensuring the investigation record is complete.

Why this answer

Option C is correct because Problem Management properties commonly include a setting that mandates the Root Cause field be populated before a problem can be resolved or closed, enforcing proper root cause analysis discipline. Option E is correct because these properties typically allow enabling automatic notification or communication of known workarounds to related active incidents, helping service desk agents apply interim fixes quickly. Option A is incorrect because provisioning AWS cloud infrastructure is an orchestration/automation task, not a Problem Management property.

Option B is incorrect because payroll deduction rates belong to HR/payroll systems, not Problem Administration. Option D is incorrect because forcing Active Directory password resets is an identity management function, unrelated to Problem Management configuration.

Exam trap

CIS-ITSM often tests the specific location and scope of Problem Management properties; candidates may confuse them with Incident or Change properties, or assume that all listed behaviors are configurable when some are not.

Full explanation →

MCQeasy

Which related list on a Problem form displays incidents that have been associated with that specific problem?

A.Problem Tasks

B.Child Incidents

C.Outages

D.Knowledge Articles

AnswerB

The Child Incidents related list on a Problem record shows incidents linked to that problem, providing the association the stem requests. It is populated when incidents are related to the problem, distinguishing it from lists such as Problem Tasks or Affected CIs.

Why this answer

The Child Incidents related list on a Problem record displays incidents that have been associated with that problem, either manually or through the problem's incident correlation process. This is the standard related list used to view and manage the incidents tied to a specific problem.

Exam trap

The trap is confusing the various related lists on the Problem form; candidates often pick Problem Tasks because it sounds like the work associated with the problem, but the question specifically asks for the incidents linked to it.

How to eliminate wrong answers

Option A is wrong because Problem Tasks are the work items created to investigate and resolve the problem, not the incidents linked to it. Option C is wrong because Outages records represent service outages and their impact, not the individual incidents associated with the problem. Option D is wrong because Knowledge Articles are the documented solutions and references attached to the problem, not the incidents it affects.

Full explanation →

100

MCQmedium

An administrator wants to ensure that a specific catalog item can only be ordered by users who possess the 'itil' role. How should this be configured without writing scripts?

A.Create a User Criteria specifying the 'itil' role and add it to the 'Available For' related list of the catalog item.

B.Configure an Order Guide rule base to restrict access based on user roles.

C.Assign the itil role to the 'Mandatory Roles' field on the catalog item form.

D.Add a Read Access Control (ACL) on the sc_cat_item table for the itil role.

AnswerA

A User Criteria record referencing the 'itil' role, attached to the catalog item's 'Available For' related list, restricts ordering to users holding that role. This is declarative configuration requiring no scripting, exactly satisfying the stem's no-script constraint while enforcing role-based catalog visibility.

Why this answer

User Criteria records define who can see or order a catalog item, and they can be built from roles, groups, companies, or departments without scripting. Adding a User Criteria that includes the 'itil' role to the catalog item's 'Available For' related list restricts ordering to users with that role.

Exam trap

CIS-ITSM often tests the misconception that ACLs are the only way to restrict catalog access — candidates pick Read ACLs, missing that User Criteria are the no-code, catalog-native mechanism for orderability.

How to eliminate wrong answers

Option B is wrong because Order Guide rules control the sequence and conditional display of catalog items within a guide, not who is authorized to order a standalone item. Option C is wrong because 'Mandatory Roles' is not a field on the catalog item form; role enforcement is done via User Criteria or ACLs, not a mandatory-roles field. Option D is wrong because a Read ACL on sc_cat_item controls record-level read access, not orderability, and ACLs are a lower-level security mechanism rather than the intended no-code catalog visibility control.

Full explanation →

101

MCQeasy

What is the primary role of the 'Configuration Item' (CI) field on a Problem record?

A.To schedule an automatic reboot of the CI upon problem creation

B.To automatically assign the problem to the vendor who manufactured the hardware

C.To lock the CI from being modified while investigations are ongoing

D.To identify the specific hardware, software, or service suspected of causing the failure

AnswerD

The CI field links the Problem record to the specific configuration item — hardware, software, or service — suspected of causing the failure, enabling impact analysis and root cause investigation. This directly satisfies the stem's requirement to identify what is failing rather than who reported it.

Why this answer

The CI field on a Problem record identifies the specific configuration item (hardware, software, or service) that is suspected of causing the failure. This helps in root cause analysis and linking the problem to the affected infrastructure.

Exam trap

The trap here is confusing the CI field's purpose with other automation features like reboots or locking, which are not inherent to the field.

How to eliminate wrong answers

Option A is wrong because the CI field does not trigger automatic reboots; that would require a workflow or orchestration. Option B is wrong because vendor assignment is not automatic based on CI; it would require assignment rules. Option C is wrong because the CI field does not lock the CI from modification; locking is controlled by other mechanisms like business rules or ACLs.

Full explanation →

102

Multi-Selecteasy

Which TWO of the following are valid variable types available in the ServiceNow Service Catalog? (Choose two.)

Select 2 answers

A.Workflow Canvas

B.Database View

C.Checkbox

D.Select Box

E.Access Control

AnswersC, D

Checkbox is a native ServiceNow Service Catalog variable type, presenting a true/false toggle that stores a boolean value. It satisfies the question's requirement by being one of the recognised catalog variable types available when building catalog items.

Why this answer

Checkbox (C) is a valid Service Catalog variable type that renders a single yes/no checkbox and stores a boolean value on the catalog item's variable set. Select Box (D) is also a valid variable type that presents a dropdown list of predefined choices, allowing the requester to pick one option. Both are standard catalog variable types configured under the Variable Types table (question_type).

Workflow Canvas (A) is a graphical workflow design interface, not a variable type. Database View (B) is a database construct for joining tables, not a catalog variable. Access Control (E) refers to ACL security rules, not a variable type.

Exam trap

CIS-ITSM often tests the confusion between platform objects (Workflow Canvas, Database View, ACL) and actual catalog variable types, causing candidates to select non-variable options.

Full explanation →

103

MCQeasy

Which field on the Change Request form designates the primary configuration item affected by the change?

A.Configuration item

B.Business Service

C.CI Class

D.Assignment group

AnswerA

The Configuration item field explicitly records the CI that the change primarily affects, linking the change record to the affected asset in the CMDB. This satisfies the stem's requirement for designating the primary configuration item, unlike fields such as Assignment group or Short description.

Why this answer

The 'Configuration item' field on the Change Request form is the designated field that identifies the primary CI affected by the change. This field references the cmdb_ci table and is used by conflict detection, risk assessment, and impact analysis to determine which CI the change targets. It is a direct reference field, not a classification or grouping field.

Exam trap

The trap here is confusing the primary CI reference field with related CI tracking or classification fields like CI Class and Business Service, which serve different purposes on the Change Request form.

How to eliminate wrong answers

Option B is wrong because Business Service is a separate reference field that identifies the business service impacted, not the primary CI. Option C is wrong because CI Class is a classification attribute (such as cmdb_ci_server) used for categorization, not the primary CI reference. Option D is wrong because Assignment group determines who works on the change, not which CI is affected.

Full explanation →

104

MCQeasy

What is the primary purpose of an Emergency Change?

A.To request new hardware purchases through procurement

B.To handle routine software upgrades with zero planning

C.To test experimental code in a development environment

D.To address an urgent business or technical disruption requiring immediate remediation

AnswerD

Emergency Changes exist to restore service or avert imminent harm when normal change control timescales cannot be met, so this option satisfies the stem's "urgent disruption" constraint. The Emergency Change Advisory Board reviews such changes retrospectively, prioritising speed of remediation over full pre-approval, which is precisely the immediate-remediation purpose described.

Why this answer

An Emergency Change exists to remediate an urgent business or technical disruption — for example, a critical outage, security breach, or service-down situation — where normal change lead times are unacceptable. It follows an expedited approval path (often a smaller Emergency CAB) so remediation can begin immediately while still retaining some governance. The key is that it addresses disruption, not routine work or procurement.

Exam trap

CIS-ITSM often tests the misconception that 'emergency' means 'no process' — the correct answer always ties Emergency Change to urgent disruption remediation with an expedited but still governed approval path.

How to eliminate wrong answers

Option A is wrong because hardware procurement is a request/fulfillment activity handled through the procurement or request process, not a change type. Option B is wrong because routine software upgrades with zero planning are the opposite of an Emergency Change — routine, low-risk, repeatable work is a Standard Change, and 'zero planning' is never acceptable. Option C is wrong because testing experimental code in a development environment is a development activity, not an emergency remediation of a production disruption.

Full explanation →

105

Multi-Selecthard

A CMDB administrator is configuring the CMDB Health Dashboard to monitor the health of the CMDB. The administrator needs to ensure that the dashboard includes metrics for the completeness of CI attributes. Which TWO of the following metrics are part of the Completeness pillar in the CMDB Health Dashboard? (Choose two.)

Select 2 answers

A.Orphan CIs

B.Audit results

C.Recommended fields

D.Required fields

E.Duplicate CIs

AnswersC, D

Recommended fields is a metric in the Completeness pillar that checks whether CIs have values for attributes that are recommended but not mandatory. It helps improve data quality by encouraging the population of important fields. This metric is part of the Completeness pillar.

Why this answer

The Completeness pillar in the CMDB Health Dashboard measures whether CIs have values for required and recommended attributes. Required fields and recommended fields are the two metrics that directly assess attribute completeness. Orphan CIs and duplicate CIs are part of the Correctness pillar, and audit results belong to the Compliance pillar.

Therefore, the correct selections are the metrics that evaluate the presence of data in CI attributes.

Exam trap

The trap here is mixing up metrics from the Correctness and Compliance pillars with those from the Completeness pillar, as they all relate to CMDB health but measure different aspects.

Full explanation →

106

Multi-Selecthard

Which THREE aspects must be considered when creating an SLA Definition for Incidents?

Select 3 answers

A.Assignment Group.

B.User locale.

C.Start Condition.

D.Stop Condition.

E.Duration (Schedule).

AnswersC, D, E

The start condition defines the trigger that begins SLA timing, such as when an incident is created or assigned. Without it, the SLA cannot determine when its clock starts, so this aspect is essential to any Incident SLA Definition.

Why this answer

When building an SLA Definition for Incidents, the Start Condition (C) is required because it defines the trigger event that begins the SLA timer, such as when an Incident is created or when its priority changes. The Stop Condition (D) is equally essential because it specifies the event that halts the SLA clock, for example when the Incident is resolved or closed. The Duration (E) is also mandatory since it establishes the target time, calculated against a Schedule, within which the task must be completed to meet the SLA.

Assignment Group (A) is not a required SLA Definition component—it is a field on the Incident record that may be referenced in conditions but is not itself an SLA aspect. User locale (B) is irrelevant to SLA timing and does not affect how an SLA Definition is configured.

Exam trap

The trap is selecting plausible-sounding but non-structural fields like Assignment Group or User locale — candidates must recognize that Start Condition, Stop Condition, and Duration/Schedule are the three mandatory pillars of any SLA Definition.

Full explanation →

107

MCQmedium

While working on a high-priority incident, an agent navigates away from the incident record without saving. The agent had changed the State to 'In Progress' and entered work notes. What happens to those unsaved changes?

A.The changes are saved to a temporary draft that can be recovered later from the 'My Drafts' module.

B.The changes are lost and the incident record remains unchanged.

C.The system automatically saves the changes to the incident record when the agent navigates away.

D.The system prompts the agent to save changes before navigating away.

AnswerB

In ServiceNow, unsaved form changes are not persisted when the user navigates away from the record. The incident remains in its previous state, and any entered work notes or state changes are discarded. This is standard behavior to avoid accidental updates. Agents must click Save or Update to commit changes.

Why this answer

ServiceNow does not auto-save or prompt to save when leaving an incident form. Any unsaved modifications are discarded, and the record remains as it was last saved. Agents must explicitly save their work.

This design prevents unintended updates but requires diligence.

Exam trap

The trap here is assuming that ServiceNow auto-saves or prompts to save when navigating away from a form.

Full explanation →

108

MCQeasy

A CMDB administrator needs to ensure that when a CI is retired, it is automatically removed from the CMDB after a specified period to maintain data hygiene. Which feature should the administrator use?

A.CMDB Health Dashboard

B.Identification and Reconciliation Engine

C.CMDB Data Manager

D.CI Class Manager

AnswerC

CMDB Data Manager allows administrators to create policies that automate the archiving and deletion of CIs based on conditions such as retirement date. It can be configured to remove CIs after a specified period, ensuring data hygiene. This is the correct tool for automating CI lifecycle management.

Why this answer

CMDB Data Manager is designed to automate the lifecycle management of CIs, including archiving and deletion based on policies. Administrators can create policies that target CIs based on conditions like operational status or retirement date, and schedule actions such as deletion after a grace period. This ensures that the CMDB remains clean and free of obsolete records without manual intervention.

Exam trap

The trap here is confusing the CMDB Health Dashboard, which monitors data quality, with CMDB Data Manager, which enforces data lifecycle policies.

Full explanation →

109

MCQmedium

A CMDB administrator needs to ensure that when a discovery source reports a server with the same serial number as an existing CI, the existing CI is updated rather than a duplicate being created. The administrator wants to apply this behavior only to the 'cmdb_ci_linux_server' class and its child classes. Which approach should the administrator take?

A.Create a business rule on the cmdb_ci_linux_server table that checks for existing serial numbers and updates the matching record.

B.Enable the 'Use serial number for identification' system property in the CMDB properties.

C.Create a custom identification rule for the Linux Server class with an entry using the serial_number attribute.

D.Modify the default identification rule for the Computer class to include serial_number as a matching attribute.

AnswerC

A custom identification rule for the Linux Server class with a serial_number entry ensures that IRE uses this attribute to match incoming CIs to existing ones, preventing duplicates. Because identification rules are class-specific and inherited by child classes, this approach applies only to Linux servers and their subclasses, satisfying the requirement.

Why this answer

The Identification and Reconciliation Engine (IRE) uses identification rules to determine whether an incoming CI matches an existing record. By creating a custom rule for the Linux Server class with a serial_number entry, the administrator ensures that only that class and its descendants use serial number for matching. This is the standard, supported method to achieve class-specific identification behavior without affecting other CI types.

Exam trap

The trap here is assuming that identification rules can be set globally via a system property or that a business rule can replace IRE functionality.

Full explanation →

110

MCQeasy

Which role is specifically required to create or modify 'SLA Definitions'?

A.itil

B.admin

C.sla_admin

D.incident_manager

AnswerC

The sla_admin role holds the elevated privileges needed to define and edit SLA Definitions, satisfying the stem's requirement for a role specifically authorised to create or modify them. Standard users and other admin roles cannot alter these records, so sla_admin is the only role granting that exact capability.

Why this answer

The 'sla_admin' role is specifically designed to create and modify SLA Definitions in ServiceNow. This role grants the necessary permissions to manage SLA records and their associated configurations. Other roles like 'admin' have broad privileges but are not specifically tailored for SLA management, and 'itil' or 'incident_manager' do not have the required rights to modify SLA definitions.

Exam trap

CIS-ITSM often tests the confusion between the broad 'admin' role and the specific 'sla_admin' role, leading candidates to choose 'admin' when a more precise role is required.

How to eliminate wrong answers

Option A is wrong because the 'itil' role is for ITIL process users and does not include permissions to create or modify SLA definitions. Option B is wrong because while 'admin' can do everything, the question asks for the role specifically required, and 'sla_admin' is the precise role for this task. Option D is wrong because 'incident_manager' manages incidents, not SLAs.

Full explanation →

111

Multi-Selecthard

A customized Problem workflow requires integrating with an external CMDB discovery tool. When a Problem is resolved, the integration must verify CI attributes via REST. Which TWO ServiceNow features support making outbound REST calls and parsing JSON responses? (Choose two.)

Select 2 answers

A.Dictionary Override checkbox attributes

B.Flow Designer with the 'REST Step' in IntegrationHub

C.Client-side alert() popups

D.RESTMessageV2 API inside a Script Include or Business Rule

E.UI Policy Action visibility toggles

AnswersB, D

The IntegrationHub REST step performs outbound REST calls declaratively within a flow, and its response can be parsed as JSON for downstream logic. This meets the stem's requirement to verify CI attributes against the external discovery tool on Problem resolution.

Why this answer

Option B is correct because Flow Designer with IntegrationHub's REST step provides a no-code/low-code way to make outbound REST calls and natively parse JSON responses into flow variables, which fits the requirement to verify CI attributes when a Problem is resolved. Option D is correct because the RESTMessageV2 API (in a Script Include or Business Rule) allows server-side outbound REST calls via methods like execute() and executeAsync(), and the returned response body can be parsed with JSON.parse() to read CI attributes. Option A is not correct because Dictionary Override checkbox attributes only control field-level behavior across extended tables and have nothing to do with outbound REST or JSON parsing.

Option C is not correct because client-side alert() popups only display browser messages and cannot perform server-side REST integrations. Option E is not correct because UI Policy Action visibility toggles only show or hide form fields and do not make REST calls or parse JSON.

Exam trap

CIS-ITSM often tests the confusion between client-side UI features and server-side integration capabilities, tricking candidates into selecting UI policies or client scripts when the requirement is for outbound REST calls and JSON parsing.

Full explanation →

112

MCQmedium

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

A.It bypasses all approvals.

B.It sets the risk to high.

C.It forces CAB approval.

D.It automatically generates a CAB meeting.

E.It alerts the CAB manager.

AnswerC

Ticking 'CAB Required' forces the change through the CAB approval process, ensuring the Change Advisory Board must review and approve before the change can proceed. This satisfies the stem's requirement by mandating CAB approval rather than leaving it optional.

Why this answer

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

Exam trap

CIS-ITSM often tests the function of the 'CAB Required' flag; candidates may think it automatically schedules a CAB meeting or alerts the CAB manager, but it only enforces CAB approval in the workflow.

How to eliminate wrong answers

Option A is wrong because the flag does not bypass approvals; it adds a required CAB approval step. Option B is wrong because it does not set the risk to high; risk is a separate field. Option D is wrong because it does not automatically generate a CAB meeting; it only requires CAB approval, which may occur asynchronously.

Option E is wrong because it does not alert the CAB manager; it simply enforces CAB approval in the workflow.

Full explanation →

113

MCQeasy

What is the primary function of the 'sc_request' table in the ServiceNow Service Catalog data model?

A.To act as the top-level container for a cart checkout containing one or more requested items

B.To define catalog item templates

C.To store individual task workflows

D.To store approval definitions

AnswerA

The sc_request table acts as the top-level container for a cart checkout, holding one or more requested items (sc_req_item) generated when the order is submitted. It groups the individual catalogue requests into a single purchasable transaction.

Why this answer

The sc_request table acts as the top-level container for a cart checkout, holding one or more sc_req_item records. It represents the overall request submitted by a user and is the parent in the request fulfillment hierarchy. This makes it the header record for reporting and approval at the request level.

Exam trap

CIS-ITSM often tests the confusion between sc_request (header) and sc_req_item (line item), tempting candidates to assign line-item or task-level functions to the request table.

How to eliminate wrong answers

Option B is wrong because catalog item templates are defined in the sc_cat_item table (and related template tables), not sc_request. Option C is wrong because individual task workflows are stored in sc_task (and workflow context tables), not sc_request. Option D is wrong because approval definitions are stored in approval-related tables like sysapproval_approver and workflow definitions, not sc_request.

Full explanation →

114

MCQmedium

When a Major Incident is created, a 'Major Incident Workbench' is available. What is its primary function?

A.Providing a central dashboard for communication and status.

B.Automating incident resolution.

C.Configuring SLA definitions.

D.Managing assignment rules.

AnswerA

The Major Incident Workbench supplies a single consolidated dashboard where responders view incident status, track assigned tasks and coordinate communications across teams. This directly satisfies the stem's requirement for a centralised coordination point during major incidents, eliminating scattered updates and giving stakeholders real-time visibility of resolution progress.

Why this answer

The Major Incident Workbench is a centralized dashboard in ServiceNow that aggregates all major incidents, their status, affected services, communication logs, and task assignments in one view. Its primary function is to give major incident managers a single pane of glass for communication and status tracking across the incident lifecycle.

Exam trap

CIS-ITSM often tests the distinction between the Workbench's monitoring/communication purpose and configuration functions like SLA or assignment rules — candidates pick options that sound operational but are actually configuration tasks.

How to eliminate wrong answers

Option B is wrong because automating incident resolution is not the Workbench's role — resolution is handled by workflows, business rules, and assignment logic, not the Workbench UI. Option C is wrong because SLA definitions are configured in the SLA module (Contract/SLA), not in the Major Incident Workbench. Option D is wrong because assignment rules are configured in assignment rule tables and workflows, not in the Workbench, which is a monitoring and communication interface.

Full explanation →

115

Multi-Selecthard

Which THREE types of metrics can be tracked using the baseline Incident Management SLA and Metric definitions? (Choose three.)

Select 3 answers

A.The exact GPS coordinates of the technician resolving the ticket.

B.Duration an incident spent in a specific assignment group.

C.The physical CPU utilization of the server hosting the database.

D.Time elapsed before an incident reaches the 'Resolved' state (SLA target).

E.Whether an SLA achieved its target or breached.

AnswersB, D, E

The baseline metric definitions capture time spent within assignment groups, so the duration an incident remained in a specific group is measurable. This satisfies the stem's request for trackable metric types by reporting group-level dwell time rather than resolution or attainment.

Why this answer

Option B is correct because baseline Incident Management SLA and Metric definitions in ServiceNow can measure the time an incident spends in a particular assignment group, using a metric definition with the Assignment group field as the condition. Option D is correct because SLA definitions track the elapsed time against a target, such as the time before an incident reaches the 'Resolved' state, which is a standard SLA target type. Option E is correct because SLA processing records whether the SLA achieved its target or breached, which is the core outcome reported by SLA metrics.

Option A is not correct because GPS coordinates of a technician are not part of baseline Incident Management SLA or metric definitions. Option C is not correct because physical CPU utilization of a database server is infrastructure monitoring data, not an incident SLA or metric definition.

Exam trap

CIS-ITSM often tests the distinction between SLA metrics (time-based, target-driven) and unrelated operational data (like GPS or CPU), so candidates may incorrectly assume any measurable data is part of the baseline SLA.

Full explanation →

116

MCQeasy

What is the primary purpose of the 'Known Error Article' integration with Knowledge Management?

A.To automatically order replacement hardware from vendors

B.To publish known errors and workarounds to a knowledge base for searchability and incident deflection

C.To generate annual financial audit reports

D.To reset user passwords automatically

AnswerB

Known Error Articles record the root cause and workaround for diagnosed errors, and publishing them into the knowledge base makes that content searchable by service desk staff and users. This enables incident deflection by resolving recurring issues without escalation, satisfying the integration's stated purpose.

Why this answer

The Known Error Article integration with Knowledge Management publishes documented known errors and their workarounds into the knowledge base so they are searchable and reusable. This supports incident deflection — users and agents can find the workaround without logging a new incident, and agents can attach the article to incidents. It is a knowledge-sharing mechanism, not an automation or procurement tool.

Exam trap

CIS-ITSM often tests whether candidates confuse knowledge management (documenting and sharing) with automation (executing fixes), leading them to pick an option that implies the article performs an action.

How to eliminate wrong answers

Option A is wrong because ordering replacement hardware is a procurement/asset workflow, not a function of knowledge articles. Option C is wrong because financial audit reports come from financial systems, not from known error knowledge articles. Option D is wrong because password resets are handled by identity/credential management tools or automated workflows, not by publishing a knowledge article.

Full explanation →

117

MCQeasy

What is the purpose of the 'Risk' field on a Change Request form?

A.To specify the cost of the change implementation

B.To automatically trigger major incident swarming

C.To indicate the evaluated potential danger or impact of failure associated with the change

D.To determine which user is assigned to test the change

AnswerC

The Risk field captures the evaluated potential danger or impact of failure for the change, informing approval routing and CAB review. It satisfies the need to quantify exposure, distinguishing high-risk changes requiring stricter scrutiny from routine low-risk ones.

Why this answer

The Risk field on a Change Request captures the evaluated potential danger or impact if the change fails — for example, whether it could cause an outage, data loss, or affect critical CIs. It is used to drive approval requirements, CAB review, and scheduling decisions, so higher-risk changes get more scrutiny. It is an assessment field, not a cost, assignment, or automation trigger.

Exam trap

The trap is conflating 'Risk' with cost or assignment — candidates often pick the cost option because both are numeric fields on the form, but Risk is about potential impact of failure.

How to eliminate wrong answers

Option A is wrong because cost of implementation is a financial/estimation attribute, not what the Risk field represents. Option B is wrong because major incident swarming is triggered by incident severity and assignment rules, not by the change Risk field. Option D is wrong because determining the tester is an assignment/approval activity handled by change tasks and assignment rules, not by the Risk field.

Full explanation →

118

MCQeasy

When a user submits a catalog item, what is the name of the task record generated for fulfillment teams to complete manual work steps specified in a workflow?

A.sc_task

B.incident

C.sc_req_item

D.change_request

AnswerA

The sc_task table stores individual fulfilment work items generated by a workflow's approval or task activities, letting assignment groups action manual steps. It satisfies the stem's requirement for the record created when a catalog item is submitted, distinct from sc_req_item, which holds the requested item itself.

Why this answer

When a catalog item is submitted, ServiceNow generates an sc_task record for each manual fulfillment step defined in the associated workflow. The sc_task table is the catalog task table used by fulfillment teams to track and complete work. This is distinct from the sc_req_item (the requested item) and sc_request (the parent request).

Exam trap

CIS-ITSM often tests the distinction between sc_request, sc_req_item, and sc_task — candidates frequently confuse the requested item with the fulfillment task.

How to eliminate wrong answers

Option B is wrong because 'incident' is the ITIL incident table, not a catalog fulfillment task — incidents are for unplanned interruptions, not catalog order fulfillment. Option C is wrong because sc_req_item is the requested item record that represents the line item ordered, not the individual fulfillment task assigned to a team. Option D is wrong because change_request is used for ITIL change management, not catalog task fulfillment.

Full explanation →

119

MCQeasy

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

A.Record Producer

B.Variable Set

C.Order Guide

D.Catalog Client Script

AnswerB

Variable Sets group variables once and attach them to many catalog items, so edits propagate everywhere. This directly satisfies the requirement for a variable shared across multiple catalog items, unlike item-specific variables, which must be recreated and maintained separately for each catalog item.

Why this answer

A Variable Set is a reusable collection of variables that can be attached to multiple catalog items, Record Producers, or other catalog entities. By defining variables once in a Variable Set and attaching it to multiple items, the administrator ensures consistency and reduces maintenance overhead. This is the standard ServiceNow mechanism for sharing variables across catalog items.

Exam trap

CIS-ITSM often tests Variable Sets by offering other catalog constructs (Record Producer, Order Guide, Catalog Client Script) that sound related but do not provide variable reuse, so candidates must know that Variable Sets are the only mechanism for sharing variables across catalog items.

How to eliminate wrong answers

Option A is wrong because a Record Producer is a catalog item type that creates records on a target table; it does not share variables across items. Option C is wrong because an Order Guide bundles multiple catalog items into a guided order but does not provide a shared variable definition mechanism. Option D is wrong because a Catalog Client Script is client-side JavaScript that runs on a catalog form; it can manipulate variables but does not define or share them across items.

Full explanation →

120

MCQmedium

An administrator is setting up a reference variable on a catalog item that should only display active users belonging to the 'Hardware' assignment group. How should this be achieved?

A.Modify the Cart Layout record.

B.Create a Catalog UI Policy setting the filter criteria.

C.Write a Business Rule on the sys_user table.

D.Configure a Reference Qualifier on the variable definition.

AnswerD

A Reference Qualifier on the variable definition filters the referenced records at query time. Setting it to return only active users in the 'Hardware' assignment group ensures the variable displays exactly those users, satisfying both conditions.

Why this answer

A Reference Qualifier on the variable definition is the correct way to filter the records that appear in a reference variable's lookup. By setting a reference qualifier, you can specify conditions such as 'active=true' and 'assignment group=Hardware' to restrict the displayed users. This is a built-in feature of reference variables.

Exam trap

CIS-ITSM often tests the difference between UI policies and reference qualifiers; candidates may choose UI Policy thinking it can filter reference fields, but it cannot.

How to eliminate wrong answers

Option A is wrong because modifying the Cart Layout record controls the layout of the catalog cart, not the filtering of reference variables. Option B is wrong because a Catalog UI Policy can set fields to mandatory or read-only, but it does not filter the records shown in a reference variable's lookup. Option C is wrong because a Business Rule on sys_user would affect all queries to the user table, not just the catalog item's reference variable, and it's not the appropriate mechanism for this requirement.

Full explanation →

121

MCQhard

If an organization wants to prevent an Incident from being closed unless certain fields are populated, which feature should be used?

A.Client Script

B.Data Policy

C.Assignment Rule

D.System Property

AnswerB

Data Policies enforce mandatory field completion before an Incident can be closed, directly satisfying the stem's constraint that closure must be blocked until specified fields are populated. Unlike UI Policies, which only control field visibility or read-only state on the form, Data Policies apply server-side validation regardless of how the record is saved.

Why this answer

Data Policies in ServiceNow enforce mandatory field requirements at the database level regardless of how a record is saved (UI, import, script, or API). They are the correct feature to prevent an Incident from being closed unless specified fields are populated, because they apply consistently across all entry points.

Exam trap

CIS-ITSM often tests the distinction between client-side enforcement (Client Scripts, UI Policies) and server-side enforcement (Data Policies), luring candidates toward UI-only features that can be bypassed.

How to eliminate wrong answers

Option A is wrong because Client Scripts run only in the browser UI and can be bypassed by imports, web services, or background scripts. Option C is wrong because Assignment Rules determine who a record is assigned to, not field validation. Option D is wrong because System Properties control global platform behavior, not per-record field enforcement on close.

Full explanation →

122

MCQmedium

When a Standard Change template is updated, how are existing active change requests created from that template affected?

A.They are automatically canceled and must be resubmitted

B.They trigger a new conflict detection run automatically

C.They remain unchanged, retaining the values from when the change was created

D.They are automatically updated with the new template values

AnswerC

Standard Change templates act as blueprints only at creation time; the resulting change records copy the template's values and are then independent. Updating the template therefore cannot retroactively alter active changes, which retain the field values captured when each was created.

Why this answer

When a Standard Change template is updated, existing active change requests created from that template retain the values they were created with and are not retroactively modified. The template only applies at creation time to populate the new change request. This ensures that in-flight changes are not unexpectedly altered mid-process.

Exam trap

The trap is assuming that template updates cascade to existing records, when in fact ServiceNow treats templates as creation-time blueprints that do not retroactively modify active change requests.

How to eliminate wrong answers

Option A is wrong because existing changes are not automatically canceled when a template is updated; they continue through their lifecycle. Option B is wrong because updating a template does not trigger conflict detection, which runs based on change scheduling and CI overlap, not template edits. Option D is wrong because changes are not automatically updated with new template values; the template is a creation-time blueprint only.

Full explanation →

123

MCQmedium

When creating an Incident from a Service Portal, which component defines the fields displayed to the user?

A.Incident Form

B.Catalog Item

C.Record Producer

D.Business Rule

AnswerC

A Record Producer defines which fields appear on a Service Portal form and maps submitted values onto the target Incident record. It satisfies the stem's constraint by controlling the portal-facing field set independently of the Incident table's dictionary, unlike catalogue items or UI policies, which govern catalogue ordering or client-side behaviour rather than portal field display.

Why this answer

A Record Producer is used to create records (like Incidents) from the Service Portal. It defines the fields that are displayed to the user by allowing you to select which variables to include and how they map to the target record. The Record Producer essentially acts as a form builder for record creation.

Exam trap

CIS-ITSM often tests the distinction between Record Producers and Catalog Items, and candidates may confuse the two when asked about incident creation from the portal.

How to eliminate wrong answers

Option A is wrong because the Incident Form is the backend form used by fulfillers, not the portal interface for end users. Option B is wrong because a Catalog Item is used for requesting items or services, not for creating incidents directly. Option D is wrong because a Business Rule is server-side logic that runs on database operations, not a UI component for field display.

Full explanation →

124

MCQeasy

When creating a Catalog Item, which table is the base table that all catalog items extend from?

A.Task [task]

B.Requested Item [sc_req_item]

C.Item [sc_cat_item]

D.Request [sc_request]

AnswerC

Item [sc_cat_item] is the base table from which all catalog item types extend, holding the shared fields every catalog item inherits. This satisfies the constraint that the answer must name the parent table, not a child type.

Why this answer

The base table for all catalog items in ServiceNow is sc_cat_item, which is labeled 'Item'. When you create a catalog item, it is stored as a record in this table, and all catalog item types (e.g., hardware, software, service) extend from it. This table defines the core fields and logic common to all catalog items, such as name, price, and category.

Options like sc_req_item and sc_request represent transactional records generated when items are ordered, not the definition of the item itself.

Exam trap

CIS-ITSM often tests the distinction between definition tables (like sc_cat_item) and transactional tables (like sc_req_item and sc_request), causing candidates to confuse the base table for catalog items with the tables that store order data.

How to eliminate wrong answers

Option A is wrong because Task [task] is the base table for all task-related records (e.g., incidents, problems, changes), not catalog items. Option B is wrong because Requested Item [sc_req_item] is a transactional table that stores individual items within a request after an order is placed; it does not define catalog items. Option D is wrong because Request [sc_request] is the transactional table that groups requested items into a request, not the base for catalog item definitions.

Full explanation →

125

Multi-Selectmedium

Which TWO methods can be used to initiate conflict detection in ServiceNow Change Management? (Choose two.)

Select 2 answers

A.By importing knowledge base articles

B.Manually by clicking a 'Run Conflict' UI action on the change request form

C.By running a daily hardware asset discovery scan

D.Automatically via business rules when schedule or CI fields are modified

E.By submitting an incident ticket via self-service portal

AnswersB, D

The 'Run Conflict' UI action on the change request form lets users trigger conflict detection on demand, satisfying the manual initiation method. It complements automatic detection by scanning the change against schedules and CI relationships when clicked.

Why this answer

Option B is correct because ServiceNow Change Management provides a 'Run Conflict' UI action on the change request form that lets a user manually trigger conflict detection against other changes, blackout/maintenance schedules, and related CIs. Option D is correct because conflict detection also runs automatically through business rules that fire when key fields such as the planned start/end dates (schedule) or the affected CI are modified, re-evaluating conflicts without user intervention. Option A is incorrect because importing knowledge base articles has no role in conflict detection, which evaluates change schedules and configuration items, not KB content.

Option C is incorrect because hardware asset discovery scans populate the CMDB and do not initiate change conflict detection. Option E is incorrect because submitting an incident through the self-service portal creates an incident record and does not trigger change conflict detection.

Exam trap

Candidates might confuse conflict detection triggers with other change management activities, such as risk assessment or approval, and may not realize that both manual and automatic methods are valid.

Full explanation →

126

Multi-Selecthard

Which THREE actions can be performed when utilizing the incident-to-problem workflow in ITSM? (Choose three.)

Select 3 answers

A.Associate multiple active incidents to a single Problem record.

B.Convert the incident table class directly into a problem table class via schema map manipulation.

C.Propagate workarounds from the Problem record to all associated Incidents.

D.Automatically generate a hardware purchase order from the problem investigation.

E.Create a new Problem record directly from an Incident form.

AnswersA, C, E

Associating multiple active incidents to one Problem record satisfies the workflow's core purpose: consolidating recurring or related incidents so root cause analysis occurs once. The incident-to-problem relationship is many-to-one, letting agents link each affected incident while tracking resolution progress centrally against the single Problem.

Why this answer

Option A is correct because the incident-to-problem workflow is designed to link many active incidents that share a common root cause to one Problem record, enabling consolidated root cause analysis. Option C is correct because once a workaround is documented on the Problem record, it can be propagated to all associated Incidents so affected users receive the interim fix. Option E is correct because the workflow allows an agent to create a new Problem record directly from an Incident form, establishing the parent-child relationship without leaving the incident context.

Option B is not part of the workflow; converting an incident table class into a problem table class via schema map manipulation is a database schema change, not an ITSM process action. Option D is not part of the workflow; automatically generating a hardware purchase order from a problem investigation is a procurement activity outside the incident-to-problem process.

Exam trap

The trap is including schema-level or procurement actions that sound plausible but are outside the supported incident-to-problem workflow — candidates must stick to the three documented actions.

Full explanation →

127

MCQmedium

A custom integration script is inserting records directly into the cmdb_ci_server table without invoking the Identification and Reconciliation Engine (IRE). What is the primary risk of this approach?

A.It causes ServiceNow to automatically reject all incoming records due to missing UI policies.

B.It bypasses identification rules and reconciliation rules, risking data duplication and unauthorized overwrites.

C.It prevents the CIs from ever being viewed in the Dependency View.

D.It triggers an infinite loop in the Discovery pattern engine.

AnswerB

Direct inserts skip the Identification and Reconciliation Engine entirely, so identification rules never match incoming records against existing CIs, and reconciliation rules never arbitrate conflicts. That produces duplicate server records and lets a source overwrite data it has no precedence for — precisely the governance the IRE enforces.

Why this answer

The primary risk is that bypassing the Identification and Reconciliation Engine (IRE) means identification rules and reconciliation rules are not applied. This can lead to duplicate CIs because the system cannot match incoming records to existing ones, and it can allow unauthorized overwrites of CI attributes because reconciliation rules that determine which data source wins are not enforced. This results in data integrity issues in the CMDB.

Exam trap

The trap is underestimating the importance of the IRE and assuming that direct inserts are acceptable. Candidates might think that UI policies or other mechanisms will catch issues, but the IRE is specifically designed for CMDB data integrity. The exam tests knowledge of CMDB best practices and the consequences of bypassing IRE.

How to eliminate wrong answers

Option A is wrong because ServiceNow does not automatically reject records due to missing UI policies; UI policies are client-side and do not affect direct database inserts. Option C is wrong because CIs can still be viewed in Dependency View even if inserted directly; the view relies on relationship data, not on how the CI was created. Option D is wrong because inserting records directly does not trigger Discovery patterns, so an infinite loop is not possible.

Full explanation →

128

MCQeasy

Which change type is characterized by low risk, high frequency, and pre-authorization?

A.Emergency Change

B.Standard Change

C.Major Change

D.Normal Change

AnswerB

Standard changes are pre-authorised, low-risk and routine, so they follow a documented procedure without individual CAB review. Their high frequency makes per-change approval impractical, and the pre-authorisation satisfies the low-risk, repeatable nature described in the stem.

Why this answer

A Standard Change is a pre-approved, low-risk, high-frequency change that follows a documented procedure and does not require CAB review each time. Because it is pre-authorized, it can be implemented quickly and repeatedly — examples include password resets, adding a user to a standard group, or routine patching. This matches the low risk, high frequency, pre-authorization profile exactly.

Exam trap

The trap is confusing 'Standard' with 'Normal' — candidates often pick Normal because it sounds like the default, but only Standard Change is pre-authorized, low-risk, and high-frequency.

How to eliminate wrong answers

Option A is wrong because Emergency Changes are high-urgency, unplanned, and require expedited approval — they are not low-risk, high-frequency, or pre-authorized. Option C is wrong because Major Changes are high-risk, high-impact changes requiring extensive CAB review and planning, the opposite of the described profile. Option D is wrong because Normal Changes require individual assessment and approval each time, so they are not pre-authorized even if they are routine.

Full explanation →

129

Multi-Selecthard

Which THREE components are configured when setting up a Service Level Agreement (SLA) Definition for Incident Management? (Choose three.)

Select 3 answers

A.Start condition

B.Workflow / Schedule

C.Stop condition

D.Assignment rule mapping

E.Data policy rule

AnswersA, B, C

The start condition defines the trigger criteria determining when the SLA timer begins, such as incident creation or a specific state change. It satisfies the stem by being one of the three required components configured in an SLA Definition.

Why this answer

In an SLA Definition for Incident Management, the three core components that must be configured are the Start condition (A), the Workflow/Schedule (B), and the Stop condition (C). The Start condition (A) defines the trigger criteria—such as when an incident is created or when a specific field changes—that begins the SLA timer. The Workflow/Schedule (B) specifies the SLA's timing behavior, including the schedule (e.g., 8x5 or 24x7), duration, and the workflow that drives the SLA stages and breach actions.

The Stop condition (C) defines the criteria that pause or end the SLA timer, such as when the incident is resolved or closed. Assignment rule mapping (D) and Data policy rule (E) are separate configuration elements used for routing and data validation, not for defining an SLA.

Exam trap

CIS-ITSM often tests the exact components of an SLA Definition — the trap is selecting adjacent configuration items like assignment rules or data policies that are configured elsewhere and are not part of the SLA Definition itself.

Full explanation →

130

MCQmedium

A service desk manager needs to ensure that Incidents assigned to the 'Hardware' group are automatically routed to a specific sub-group based on the 'Category' field. Which configuration should be used?

A.Flow Designer

B.Assignment Rules

C.Data Lookups

D.Business Rules

AnswerB

Assignment Rules evaluate conditions such as the Category field on an Incident record and automatically set the assignment group, satisfying the requirement to route Hardware Incidents to a specific sub-group. They run on record creation or update, so routing happens without agent intervention, unlike business rules or UI policies.

Why this answer

Assignment Rules in ServiceNow are designed to automatically assign records (like Incidents) to the appropriate assignment group or individual based on conditions such as Category. They are evaluated when a record is created or updated, and can route based on fields like Category. This is the standard configuration for such routing.

Exam trap

CIS-ITSM often tests the confusion between Assignment Rules and Business Rules, tempting candidates to choose Business Rules for simple routing, but Assignment Rules are the correct out-of-box feature.

How to eliminate wrong answers

Option A is wrong because Flow Designer is a broader automation tool; while it can perform assignments, it is not the specific configuration for simple routing based on Category. Option C is wrong because Data Lookups are used to populate field values from external tables, not for assignment routing. Option D is wrong because Business Rules are server-side scripts that can set assignments, but they are more complex and not the out-of-box configuration for this purpose; Assignment Rules are the intended feature.

Full explanation →

131

Multi-Selecthard

An administrator is configuring a Multi-Row Variable Set (MRVS). Which THREE of the following capabilities are true regarding MRVS behavior? (Choose three.)

Select 3 answers

A.It can be reused across multiple catalog items just like standard variable sets.

B.It allows users to enter tabular rows of variable data on a single catalog item form.

C.The submitted data is stored as a serialized JSON string in the variable value table.

D.It automatically creates separate Incident records for every row entered in the grid.

E.Standard Catalog UI Policies can dynamically hide individual columns inside an MRVS grid dynamically by column name.

AnswersA, B, C

MRVS is a type of variable set and supports reusability across items.

Why this answer

Option A is correct because a Multi-Row Variable Set is a reusable variable set type that, once created, can be attached to multiple catalog items just like a standard variable set, avoiding redefinition of the same row-based questions. Option B is correct because the defining behavior of an MRVS is to present a grid where users add multiple rows, each row containing the set of variables defined in the MRVS, all on a single catalog item form. Option C is correct because submitted MRVS data is stored as a serialized JSON string in the variable value table (e.g., the sc_item_option / question answer value), which is why it must be parsed to read individual row values.

Option D is not correct because an MRVS does not automatically create separate Incident records per row; any record creation would require custom scripting such as a business rule or flow, and it is not inherent MRVS behavior. Option E is not correct because standard Catalog UI Policies do not dynamically hide individual columns inside an MRVS grid by column name; column-level control in an MRVS requires client scripts or custom grid configuration rather than standard catalog UI policy column targeting.

Exam trap

CIS-ITSM often tests the misconception that MRVS automatically creates separate records (like Incidents) for each row, or that standard UI policies can control column-level visibility, leading candidates to select incorrect options.

Full explanation →

132

MCQmedium

A catalog item has a variable named 'software_version' that needs to be populated dynamically using a script. Which type of variable allows options to be populated dynamically via a lookup or script?

A.Lookup Select Box

B.Checkbox

C.Multi-Line Text

D.Single Line Text

AnswerA

Lookup Select Box variables pull their option list from a referenced table via a lookup configuration, or from a script, rather than storing static choices. This satisfies the stem's requirement that software_version be populated dynamically at runtime.

Why this answer

A Lookup Select Box variable type is designed to dynamically populate options from a lookup table or via a script. It allows administrators to define a lookup table and reference field, or use a script to generate choices dynamically. This makes it ideal for scenarios like populating software versions from a CMDB table or an external source.

Exam trap

CIS-ITSM often tests the misconception that any text variable can be dynamically populated, but only specific variable types like Lookup Select Box or Choice support dynamic options.

How to eliminate wrong answers

Option B is wrong because a Checkbox variable is a boolean input (true/false) and cannot hold dynamic options. Option C is wrong because a Multi-Line Text variable is for free-form text entry and does not support dynamic option population. Option D is wrong because a Single Line Text variable is for simple text input and cannot dynamically populate options; it is not a choice-based variable.

Full explanation →

133

MCQhard

When running conflict detection on a change request, ServiceNow evaluates 'Schedule Overlap' conflicts. What specific date/time fields on the change request are compared against other changes?

A.Start time and End time fields on associated change tasks

B.Opened and Closed dates

C.Due date and Effective date

D.Planned start date and Planned end date

AnswerD

Schedule Overlap detection compares the change's Planned start date and Planned end date against the same fields on other change records. Any intersection of those intervals flags a conflict, so these two fields define the window ServiceNow evaluates.

Why this answer

ServiceNow's Schedule Overlap conflict detection compares the Planned start date and Planned end date fields on the change request against the same fields on other change requests targeting the same CI. These are the authoritative scheduling fields used by ConflictFinderSNC to determine whether two changes occupy overlapping time windows. If the planned windows intersect, a Schedule Overlap conflict is raised.

Exam trap

CIS-ITSM often tests which specific fields drive conflict detection — candidates incorrectly assume change task dates or due dates are used, when only Planned start date and Planned end date are evaluated.

How to eliminate wrong answers

Option A is wrong because change task start/end times are execution-level fields and are not the fields evaluated by conflict detection — conflict detection operates at the change request level using planned dates. Option B is wrong because Opened and Closed dates are audit/record lifecycle timestamps, not scheduling fields, and have no bearing on conflict detection. Option C is wrong because Due date and Effective date are not the fields compared for overlap — Due date is a target completion date and Effective date is when the change takes effect, neither of which defines the planned maintenance window.

Full explanation →

134

Multi-Selecthard

When fulfilling a Catalog Request, ServiceNow generates a hierarchy of records. Which THREE of the following tables are part of this core request fulfillment data model? (Choose three.)

Select 3 answers

A.cmdb_ci

B.sc_req_item

C.sc_request

D.sc_task

E.incident

AnswersB, C, D

The `sc_req_item` table stores individual catalog items within a request, capturing quantity, price and fulfilment state per item. It sits directly beneath `sc_request` in the hierarchy, satisfying the stem's requirement for a core table in the request fulfilment data model.

Why this answer

The core ServiceNow catalog request fulfillment data model consists of three linked tables: sc_request (option C), which is the top-level Request record created when a user submits an order and which groups all items in that order; sc_req_item (option B), which represents each individual catalog item requested within the Request and holds the item's variables and approval/fulfillment state; and sc_task (option D), which is the task record generated to carry out the actual fulfillment work for a requested item. These three tables form the standard Request → Requested Item → Catalog Task hierarchy that ServiceNow generates when fulfilling a Catalog Request. Option A (cmdb_ci) is incorrect because it is the Configuration Item table used for CMDB asset/CI records, not part of the catalog request fulfillment chain.

Option E (incident) is incorrect because it is the ITIL incident table used for reporting and resolving service disruptions, unrelated to catalog request fulfillment.

Exam trap

CIS-ITSM often tests the confusion between the request fulfillment tables (sc_request, sc_req_item, sc_task) and unrelated tables like incident or cmdb_ci, tempting candidates to include operational or CMDB tables.

Full explanation →

135

MCQhard

An administrator is troubleshooting an Order Guide where Rule Base conditions evaluate to true, but the expected child catalog item is not being added to the cart. What is a valid troubleshooting step in this scenario?

A.Check the 'No cart' attribute on the order guide record itself.

B.Verify that the child catalog item is active and that the submitting user satisfies the child item's User Criteria.

C.Rewrite the rule base conditions using legacy javascript eval() statements.

D.Disable cascading variables on all child catalog items.

AnswerB

Rule Base conditions can evaluate true while the child item is still excluded, because inactive items or unmet User Criteria prevent addition. Confirming the child catalog item's active status and the submitting user's User Criteria eligibility isolates that cause.

Why this answer

When an Order Guide rule evaluates true but the child item is not added, the most common causes are that the child catalog item is inactive or that the submitting user does not satisfy the child item's User Criteria. Both conditions silently prevent the item from being included in the cart even though the rule fired correctly. Verifying item active status and User Criteria is therefore the correct diagnostic step.

Exam trap

CIS-ITSM often tests whether candidates know that Order Guide rule success does not guarantee cart inclusion — the trap is assuming the rule base is broken when the real cause is item-level visibility or active status.

How to eliminate wrong answers

Option A is wrong because the 'No cart' attribute on the Order Guide controls whether the guide bypasses the cart entirely and is unrelated to individual child items failing to be added. Option C is wrong because rewriting rule conditions with legacy eval() is neither a troubleshooting step nor a supported best practice — it introduces security and maintainability risks. Option D is wrong because disabling cascading variables affects variable propagation between items, not whether a child item is added to the cart by a rule.

Full explanation →

136

MCQmedium

A change practitioner is reviewing a Normal Change request and notices the Risk value is set to 'High'. What impact does a 'High' risk value typically have on the out-of-the-box change workflow?

A.It bypasses all conflict detection rules

B.It converts the normal change into a standard change automatically

C.It requires additional approvals, such as CAB review, before implementation

D.It automatically cancels the change request

AnswerC

A High risk value triggers the workflow's risk-based routing, inserting a mandatory CAB approval gate before the change can be authorised. This satisfies the stem's requirement that high-risk Normal Changes receive additional scrutiny rather than standard approval.

Why this answer

In the out-of-the-box ServiceNow Normal Change workflow, the Risk field drives the approval path. When Risk is set to 'High', the workflow routes the change through the Change Advisory Board (CAB) approval activity, requiring CAB review and additional authorization before the change can be scheduled and implemented. This ensures high-impact changes receive proper governance oversight.

Exam trap

CIS-ITSM often tests the assumption that Risk and Priority are interchangeable or that Risk only affects reporting — candidates forget that Risk directly drives the approval routing in the baseline Normal Change workflow.

How to eliminate wrong answers

Option A is wrong because conflict detection is controlled by the conflict detection properties and schedule, not by the Risk value; a High risk does not disable conflict checks. Option B is wrong because Standard changes are pre-approved templates with a fixed workflow — a Normal change can never be auto-converted to Standard by setting Risk to High. Option D is wrong because the workflow does not auto-cancel changes based on Risk; it only adds approval gates, and cancellation requires manual action or a rejection.

Full explanation →

137

MCQmedium

An administrator needs to hide a specific variable on a Catalog Item when another variable's value changes to 'Other'. Which tool should be used to achieve this without writing custom script logic?

A.Catalog UI Policy

B.Data Policy

C.Access Control List (ACL)

D.Catalog Client Script

AnswerA

A Catalog UI Policy applies client-side actions such as hide, show, or set mandatory on variables when another variable's value changes, configured declaratively without scripting. This satisfies the requirement to hide the variable when 'Other' is selected, avoiding custom client scripts or business rules.

Why this answer

A Catalog UI Policy can hide a variable based on another variable's value without writing custom script logic, making option A correct.

Exam trap

CIS-ITSM often tests the confusion between Catalog UI Policies and Catalog Client Scripts, where candidates might choose Client Script even when no custom script is desired.

How to eliminate wrong answers

Option B is wrong because Data Policies enforce data consistency on task records, not catalog item variables. Option C is wrong because ACLs control access to records and fields, not dynamic visibility based on variable values. Option D is wrong because Catalog Client Script requires writing custom script logic, which the administrator wants to avoid.

Full explanation →

138

MCQmedium

An administrator has created a new Variable Set containing five variables. They want to add this entire set to an existing catalog item. Where should the administrator navigate to accomplish this?

A.Modify the Order Guide rule base to include the variable set.

B.Open the Variable Set record and add the catalog item to the 'Target Items' related list.

C.Service Catalog > Administration > Variable Sets

D.Open the Catalog Item form and use the 'Variable Sets' related list to add the set.

AnswerD

Variable Sets are attached through the Catalog Item record's related list, which links the whole set to the item in one action. This satisfies the requirement to add all five variables together rather than recreating each variable individually on the form.

Why this answer

The correct approach is to open the Catalog Item form and use the 'Variable Sets' related list to add the set. In ServiceNow, Variable Sets are reusable collections of variables that can be attached to multiple catalog items. The Catalog Item form includes a related list called 'Variable Sets' where administrators can add existing variable sets, making all variables in the set available on that catalog item.

This is the standard method for associating a variable set with a catalog item.

Exam trap

CIS-ITSM often tests the direction of the relationship between catalog items and variable sets, causing candidates to incorrectly assume you add the catalog item to the variable set rather than the reverse.

How to eliminate wrong answers

Option A is wrong because Order Guides are used to group multiple catalog items into a single ordering process, not to attach variable sets to an individual catalog item. Option B is wrong because the Variable Set record does not have a 'Target Items' related list; variable sets are linked from the catalog item side, not the other way around. Option C is wrong because 'Service Catalog > Administration > Variable Sets' is the navigation path to manage variable sets themselves (create, edit, delete), not to attach them to a catalog item.

Full explanation →

139

MCQmedium

An administrator wants to ensure that when a user orders a specific software license item, the workflow checks if approval is needed based on the cost variable. Where should this conditional routing be built?

A.Inside the Variable Set definition.

B.Inside the workflow using an 'If' activity that evaluates the cost variable.

C.Inside the Catalog UI Policy configuration.

D.Inside the Cart Layout settings.

AnswerB

Conditional routing belongs inside the workflow itself, where an 'If' activity evaluates the cost variable and branches to an approval or auto-fulfilment path. Building it in the workflow keeps the decision logic with the process that acts on it.

Why this answer

The correct answer is B because conditional routing based on a catalog variable's value (like cost) is implemented within the workflow using an 'If' activity. The workflow engine evaluates the variable at runtime and directs the flow down the appropriate path—such as requiring approval or auto-approving. This is the standard ServiceNow mechanism for dynamic process branching in catalog item fulfillment.

Exam trap

CIS-ITSM often tests the confusion between UI policies (which control form behavior) and workflow activities (which control process flow), leading candidates to incorrectly choose UI Policy for backend routing.

How to eliminate wrong answers

Option A is wrong because a Variable Set definition only groups and defines variables; it does not contain workflow logic or conditional routing. Option C is wrong because a Catalog UI Policy controls the behavior and visibility of variables on the catalog form (client-side), not the backend approval routing. Option D is wrong because Cart Layout settings only affect the visual arrangement of the cart and checkout pages, not workflow decision logic.

Full explanation →

140

Multi-Selecthard

An administrator is designing a custom Flow Designer action to process Problem records. Which TWO types of inputs can be configured for a custom Flow Designer action? (Choose two.)

Select 2 answers

A.Live video streaming feed codec

B.Analog radio frequency wave capture

C.Record (referencing a specific table like Problem [problem])

D.Direct physical server motherboard circuit diagram binary

E.String (for text inputs like short descriptions or workarounds)

AnswersC, E

A Record input references a specific table, such as Problem [problem], passing a full record rather than a scalar value. This satisfies the stem's requirement for configurable input types by enabling the action to operate directly on Problem records.

Why this answer

Option C is correct because Flow Designer custom actions support a Record input type, which lets the action accept a reference to a specific table such as Problem [problem], enabling the action to operate on that record's fields and sys_id. Option E is correct because Flow Designer also supports the String input type, which is used for plain text values like short descriptions or workaround notes. These input types are defined in the action's input metadata and are surfaced as variables when the action is used in a flow.

The other options (A, B, and D) are not valid Flow Designer input types; they describe media codecs, radio signals, and hardware schematics, none of which are configurable inputs in the platform.

Exam trap

CIS-ITSM often tests the distinction between valid Flow Designer input types and unrelated technical concepts, causing candidates to overthink and select options that sound sophisticated but are not part of the platform.

Full explanation →

141

MCQhard

You are troubleshooting a scenario where an Incident SLA is not attaching to a ticket. What is the first place you should investigate?

A.SLA Definition Conditions

B.Incident State

C.System Dictionary

D.User Preferences

AnswerA

SLA definitions carry start, stop, pause and reset conditions that determine whether a record qualifies for attachment. If these conditions reference fields the ticket does not populate, or exclude its values, no SLA binds. Verifying them first satisfies the stem's requirement to find why attachment fails before checking workflows or schedules.

Why this answer

The first place to investigate when an Incident SLA is not attaching is the SLA Definition Conditions. SLA definitions in ServiceNow use start conditions, stop conditions, and pause conditions to determine when an SLA attaches to a task. If the conditions do not match the incident's field values (e.g., priority, category, assignment group), the SLA will not attach.

Checking the SLA Definition Conditions first confirms whether the incident meets the criteria for the SLA to be applied.

Exam trap

CIS-ITSM often tests SLA troubleshooting — candidates jump to incident state or user preferences, but the first and most logical place to check is the SLA definition's start conditions, which determine whether the SLA should attach at all.

How to eliminate wrong answers

Option B is wrong because the Incident State is a field value that may be part of the SLA conditions, but it is not the first place to investigate — the SLA definition itself defines which states trigger attachment. Option C is wrong because the System Dictionary defines table schema and field properties, not SLA attachment logic. Option D is wrong because User Preferences affect personal UI settings, not SLA attachment behavior.

Full explanation →

142

MCQmedium

A customer wants to make the 'Short Description' field mandatory only when the Incident state changes to 'Resolved'. Which approach is best?

A.Create a Business Rule with 'abortAction()'.

B.Use a UI Policy with the 'Mandatory' field set to 'True'.

C.Use a Data Policy on the field.

D.Create an OnChange Client Script.

AnswerB

A UI Policy with Mandatory set to True enforces the field only when its condition—state equals Resolved—is met, satisfying the stem's conditional requirement. A dictionary-level mandatory setting would apply unconditionally, making Short Description required at every state instead.

Why this answer

A UI Policy is the correct tool to make a field mandatory based on another field's value or state, because it operates on the client side and can dynamically set the 'Mandatory' attribute when the condition (state = Resolved) is met. UI Policies are designed exactly for this kind of conditional field behavior without writing code.

Exam trap

CIS-ITSM often tests the confusion between UI Policies (client-side, form behavior) and Data Policies (server-side, import/API enforcement), leading candidates to pick Data Policy for form-level mandatory logic.

How to eliminate wrong answers

Option A is wrong because a Business Rule with abortAction() runs server-side and would block the save entirely rather than conditionally making the field mandatory; it also does not provide the dynamic UI behavior expected. Option C is wrong because Data Policies are server-side and enforce mandatory/read-only rules on import and API, not dynamically on the form when a user changes state. Option D is wrong because an OnChange Client Script could set the mandatory flag, but it is more complex and less maintainable than a UI Policy, which is the standard declarative approach.

Full explanation →

143

Multi-Selecteasy

Which TWO benefits are gained by linking related Incidents to a Problem record? (Choose two.)

Select 2 answers

A.Immediate deletion of all server hard drives

B.Automatic conversion of incidents into physical paper mail

C.Ability to send bulk communications to all affected incident callers when a workaround is found

D.Accurate calculation of total business impact and affected user counts

E.Automatic promotion of all end users to IT administrators

AnswersC, D

Related incidents expose their caller contact details to the problem record, letting support staff issue one bulk notification to every affected caller once a workaround exists. This satisfies the requirement for efficient mass communication instead of contacting each caller individually.

Why this answer

Option C is correct because linking incidents to a Problem record lets support teams identify every caller tied to that problem and issue a single bulk notification (e.g., email or portal update) once a workaround or fix is available, rather than contacting each user individually. Option D is correct because the linked incident records aggregate data such as the number of affected users, sites, and services, enabling accurate calculation of the Problem's total business impact and user counts for prioritization and reporting. Options A, B, and E are incorrect because deleting hard drives, converting incidents to paper mail, and promoting users to administrators are not functions of incident-to-problem linking and have no basis in ITIL problem management practice.

Exam trap

CIS-ITSM often tests the misconception that linking Incidents to a Problem automatically resolves or closes the Incidents, or that it grants administrative privileges, when in fact the primary benefits are aggregated impact calculation and bulk communication.

Full explanation →

144

MCQeasy

Which ServiceNow table stores the individual requested items generated when a user submits a service catalog request?

A.sc_req_item

B.sc_request

C.sys_user

D.sc_task

AnswerA

Each requested item generated from a catalog request is stored as a record in sc_req_item, which holds individual item details such as quantity, variables and approval state. The parent request itself lives in sc_request, making sc_req_item the correct table for line items.

Why this answer

The sc_req_item table stores the individual requested items (RITMs) that are generated when a user submits a service catalog request. Each catalog item ordered creates one sc_req_item record, which tracks the item's fulfillment state, variables, and associated tasks. This is the correct table because it represents the line-item level of a request, distinct from the parent request record.

Exam trap

CIS-ITSM often tests the confusion between sc_request (parent request) and sc_req_item (individual requested item), so candidates who pick sc_request mistake the header record for the line-item record.

How to eliminate wrong answers

Option B is wrong because sc_request stores the parent request header (the 'request' record) that groups one or more requested items, not the individual line items. Option C is wrong because sys_user stores user records and has no role in catalog request fulfillment. Option D is wrong because sc_task stores the individual fulfillment tasks assigned to fulfillers, which are generated from a requested item, not the requested item itself.

Full explanation →

145

MCQhard

A custom workflow is designed for High Priority problems. When priority is 1 - Critical, the workflow must spawn a parallel set of problem tasks for Infrastructure, Security, and Database teams simultaneously. Which Flow Designer flow logic component accomplishes parallel execution?

A.For Each loop logic

B.Wait for condition activity

C.If / Else condition branches

D.Do in Parallel flow logic block

AnswerD

The Do in Parallel block branches execution into concurrent paths, so Infrastructure, Security, and Database problem tasks are created simultaneously rather than sequentially. This directly satisfies the stem's requirement for parallel task spawning when priority is 1 - Critical.

Why this answer

Flow Designer's 'Do in Parallel' flow logic block is specifically designed to execute multiple branches simultaneously, which is exactly what is needed to spawn Infrastructure, Security, and Database tasks at the same time. Each branch runs independently and the flow waits for all branches to complete before continuing. This is the native parallel execution primitive in Flow Designer.

Exam trap

CIS-ITSM often tests the difference between sequential iteration (For Each) and true parallel execution (Do in Parallel), catching candidates who assume any multi-branch logic runs concurrently.

How to eliminate wrong answers

Option A is wrong because a For Each loop iterates sequentially over a collection, executing one item at a time — it does not run branches concurrently. Option B is wrong because 'Wait for condition' pauses the flow until a condition is met; it does not create parallel execution paths. Option C is wrong because If/Else branches are mutually exclusive — only one path executes based on the condition, so it cannot spawn three simultaneous task sets.

Full explanation →

146

Multi-Selectmedium

Which THREE factors should an implementation specialist consider when designing the Service Portfolio hierarchy for a large enterprise? (Choose three.)

Select 3 answers

A.Alignment with the organization's CSDM framework and CMDB maturity

B.Governance, visibility, and access control requirements across departments

C.Business unit ownership and financial chargeback structures

D.Individual user password expiration policies

E.Local printer driver compatibility lists

AnswersA, B, C

Anchoring the Service Portfolio to the CSDM framework ensures service definitions map to CMDB CI classes and relationships, so portfolio tiers inherit accurate dependency data. This satisfies the large-enterprise constraint by keeping hierarchy consistent with existing configuration maturity rather than inventing parallel structures.

Why this answer

Option A is correct because the Service Portfolio hierarchy in ServiceNow must align with the Common Service Data Model (CSDM) and the organization's CMDB maturity level, since CSDM defines the standard layers (Business Service, Service Offering, Application Service, Technical Service) and mismatched maturity causes broken relationships and reporting. Option B is correct because governance, visibility, and access control requirements across departments determine how services are grouped and who can view or edit portfolio records, typically enforced through domain separation, user criteria, and role-based ACLs. Option C is correct because business unit ownership and financial chargeback structures dictate how services are mapped to cost centers and owners, enabling accurate showback/chargeback reporting and accountability in a large enterprise.

Option D is not relevant because individual user password expiration policies are identity and authentication settings, not factors in structuring the Service Portfolio hierarchy. Option E is not relevant because local printer driver compatibility lists are endpoint/device management details unrelated to portfolio hierarchy design.

Exam trap

CIS-ITSM often tests scope discipline — candidates pick operational IT details like password policies or printer drivers because they sound like 'implementation considerations,' missing that Service Portfolio design is about governance, ownership, and CSDM alignment.

Full explanation →

147

MCQeasy

A service desk agent receives a call about a widespread email outage. The agent needs to raise a change that will be implemented immediately by the on-call network team without waiting for the next CAB meeting, but the change must still be reviewed after implementation. Which Change Management model should the agent use?

A.Standard Change

B.Emergency Change

C.Unauthorized Change

D.Normal Change

AnswerB

Emergency Changes are designed for urgent situations where implementation cannot wait for a scheduled CAB meeting. They use an expedited approval path, often involving the Emergency Change Advisory Board or a designated approver, and are reviewed after implementation. This matches the agent's need to restore email service immediately while still capturing the change for post-implementation review.

Why this answer

Emergency Changes exist precisely for urgent work that cannot wait for a scheduled CAB review. They follow an expedited approval route and are reviewed after implementation, satisfying both the need to restore email service quickly and the need for governance. Standard and Normal Changes impose pre-implementation approval that the outage cannot accommodate.

Exam trap

The trap here is treating Emergency Change as a state rather than a Change model, or assuming any urgent change can simply skip governance entirely.

Full explanation →

148

MCQmedium

A change manager wants to ensure that changes affecting a specific mission-critical business service are automatically assigned a High risk score. How can this be accomplished?

A.Modifying the Business Service form layout

B.Configuring a Risk Condition matching that business service

C.Creating a Service Level Agreement (SLA) definition

D.Writing an Access Control List (ACL)

AnswerB

Risk Conditions evaluate change attributes, including affected business service, and assign a calculated risk score when matched. Configuring one against the mission-critical service satisfies the stem's requirement, automatically scoring any change affecting it as High.

Why this answer

Risk Conditions in Change Management allow you to define criteria that automatically set a risk score based on field values, such as the affected business service. By configuring a Risk Condition that matches the specific mission-critical business service, any change affecting that service will be assigned a High risk score without manual intervention. This is the standard, out-of-the-box method for dynamic risk assessment.

Exam trap

CIS-ITSM often tests the misconception that risk scoring is manually set or that form layout changes affect behavior. Candidates may confuse Risk Conditions with SLAs or ACLs, but only Risk Conditions directly control automatic risk assignment.

How to eliminate wrong answers

Option A is wrong because modifying the Business Service form layout only changes the visual arrangement of fields, not risk assignment logic. Option C is wrong because an SLA definition governs time-based commitments for incident, problem, or change resolution, not risk scoring. Option D is wrong because an ACL controls access to data, not risk calculation.

Full explanation →

149

MCQeasy

A service owner needs to define specific pricing, delivery commitments, and SLAs for a standard IT Service. In ServiceNow Service Portfolio Management, what is the correct term for this distinct level of a service?

A.Service Offering

B.Business Service Definition

C.Service Level Commitment (SLC)

D.Service Portfolio

AnswerA

A Service Offering is the specific level within a service that defines pricing, delivery commitments and SLAs for a particular consumer group. It sits beneath the overall service, giving the granular commercial detail the service owner needs.

Why this answer

A Service Offering is the correct term because it represents a specific, sellable or deliverable variant of a parent Business Service or Technical Service, complete with its own pricing, delivery commitments, and SLAs. In ServiceNow SPM, a single service can have multiple offerings (e.g., 'Gold', 'Silver', 'Bronze') each with distinct commitment levels. This is the level where SLAs and pricing are actually defined, not at the parent service level.

Exam trap

CIS-ITSM often tests the confusion between Service Offering and Service Level Commitment — candidates pick SLC thinking it is the priced level, but SLC is the commitment record attached to an offering, not the offering itself.

How to eliminate wrong answers

Option B is wrong because 'Business Service Definition' is not a standard ServiceNow SPM term for a priced/committed variant — Business Service is the parent CI/service record itself, not a sub-level with pricing and SLAs. Option C is wrong because a Service Level Commitment (SLC) is a specific commitment record (like an SLA definition) that is attached to a Service Offering, not the offering itself; it is a component, not the container. Option D is wrong because Service Portfolio is the highest-level grouping of all services across their lifecycle (pipeline, catalog, retired), not a distinct priced level of a single service.

Full explanation →

150

MCQhard

A high-volume enterprise experiences thousands of problem state updates daily. To optimize database performance, an administrator wants to archive closed Problem records older than 3 years. Which feature should be configured?

A.Dictionary entry attribute 'auto_purge'

B.A scheduled job running manual SQL DELETE statements

C.Client script cleanup routine

D.Archiving Rules (Data Archiving plugin)

AnswerD

Archiving Rules in the Data Archiving plugin move closed Problem records older than a defined age into the archive tables, removing them from active queries. This directly satisfies the stem's three-year retention threshold and reduces load on the primary database.

Why this answer

ServiceNow's Data Archiving plugin provides Archiving Rules that let administrators define conditions (such as 'Closed Problem records older than 3 years') and schedule automated archival of matching records to the archive tables. This is the supported, upgrade-safe mechanism for reducing active table size and improving query performance on high-volume tables like Problem.

Exam trap

The trap here is confusing 'auto_purge' (hard delete via Table Cleanup) with Archiving Rules (move to archive tables) — candidates who see 'archive' in the question often still pick auto_purge because it sounds like a cleanup mechanism.

How to eliminate wrong answers

Option A is wrong because 'auto_purge' is a dictionary attribute used by the Table Cleanup / purge utility for hard-deleting records based on age, not for archiving them to a separate archive table — it destroys data rather than preserving it. Option B is wrong because running manual SQL DELETE statements against the ServiceNow database is unsupported, bypasses business rules and audit trails, and can corrupt referential integrity. Option C is wrong because client scripts run in the browser and cannot perform server-side bulk archival of thousands of records.

Option D is correct because Archiving Rules are the native, supported feature for moving aged records out of the active table while keeping them queryable in archive tables.

Full explanation →

ServiceNow Certified Implementation Specialist - IT Service Management (CIS-ITSM) (CIS-ITSM) (CIS-ITSM) — Questions 76–150