Courseiva

CCNA Service Catalog And Request Management Questions

75 of 101 questions · Page 1/2 · Service Catalog And Request Management topic · Answers revealed

Practice these questionsExam hubAll questions
1
MCQeasy

Which tab on a Catalog Item form is used to define which categories the item appears under?

A.Categories related list
B.Item Relationships related list
C.Catalogs related list
D.Portal Sections tab
AnswerA

The Categories related list on the Catalog Item form maps the item to one or more category records, controlling where it appears in the service catalogue. Adding entries there satisfies the requirement to define the categories the item is listed under.

Why this answer

The Categories related list on a Catalog Item form is used to associate the item with one or more categories, which determine where the item appears in the catalog browsing structure. This related list allows administrators to define the item's categorization.

Exam trap

CIS-ITSM often tests the distinction between Categories (browsing taxonomy) and Catalogs (container of items), so candidates must not confuse the two related lists.

How to eliminate wrong answers

Option B is wrong because the Item Relationships related list defines relationships between catalog items (e.g., 'requires' or 'bundled with'), not categories. Option C is wrong because the Catalogs related list determines which catalogs the item belongs to, not the categories within a catalog. Option D is wrong because Portal Sections tab is used to configure which portal sections the item appears in, which is a different level of organization than categories.

Practice this question →
2
MCQmedium

You are configuring a Catalog UI Policy to hide a specific variable on a catalog item form. Which setting ensures the policy also applies when the variable is viewed in the Request Item (RITM) form?

A.Reverse if false
B.Catalog conditions
C.Applies on Requested Items
D.Global scope enforcement
AnswerC

Enabling Applies on Requested Items extends the Catalog UI Policy beyond the catalog item form to the RITM form, hiding the variable there too. Applies on Catalog Tasks and Applies on Target Record affect other record types, so they would not satisfy the RITM visibility requirement.

Why this answer

The 'Applies on Requested Items' setting on a Catalog UI Policy ensures the policy's actions (like hiding a variable) also apply when the variable is displayed on the Request Item (RITM) form, not just the initial catalog item form. Without this, the UI policy only affects the catalog item view, and the variable may still appear on the RITM. This is the specific checkbox that extends the policy's scope to requested items.

Exam trap

CIS-ITSM often tests the distinction between catalog item form behavior and RITM form behavior, tricking candidates into choosing 'Reverse if false' or 'Catalog conditions' when the question is about extending a UI policy to requested items.

How to eliminate wrong answers

Option A is wrong because 'Reverse if false' controls whether the policy's actions are inverted when the condition is false — it does not extend the policy to the RITM form. Option B is wrong because 'Catalog conditions' define when the policy runs on the catalog item form, not whether it applies to requested items. Option D is wrong because 'Global scope enforcement' is not a real Catalog UI Policy setting — scope is a development concept (application scope), not a UI policy option.

Practice this question →
3
MCQmedium

A developer needs to ensure that a variable named 'request_justification' becomes mandatory only when another variable 'urgency' has a value of 'High'. Which configuration tool should be used to accomplish this without writing code?

A.Catalog UI Policy
B.Business Rule
C.Data Policy
D.Catalog Client Script
AnswerA

Catalog UI Policies enforce client-side field behaviour on catalog forms, making a variable mandatory based on another variable's value. A UI Policy with a condition of urgency equals High, and a mandatory action on request_justification, satisfies the no-code requirement directly, unlike client scripts or data policies.

Why this answer

Catalog UI Policies are the no-code tool in ServiceNow for dynamically changing the behavior of catalog item variables based on other variable values or user actions. They can make a variable mandatory, read-only, or hidden when a condition is met—exactly the requirement here: set 'request_justification' to mandatory when 'urgency' equals 'High'. Because UI Policies are configuration records, no scripting is needed, satisfying the 'without writing code' constraint.

Exam trap

CIS-ITSM often tests the distinction between client-side UI Policies and server-side Data Policies/Business Rules, and candidates frequently confuse Data Policies (for table fields) with Catalog UI Policies (for catalog variables).

How to eliminate wrong answers

Option B is wrong because Business Rules run on the server side against database records and cannot directly control the client-side mandatory state of catalog variables; they would require scripting and would not achieve the dynamic form behavior. Option C is wrong because Data Policies enforce data integrity at the database level (e.g., mandatory, read-only) but do not apply to catalog item variables on the form; they are used for table fields, not variable sets. Option D is wrong because Catalog Client Scripts require writing JavaScript (e.g., onChange or onLoad) to achieve the same result, violating the no-code requirement.

Practice this question →
4
MCQmedium

An administrator needs to create a variable that allows a user to select a single record from the 'User' (sys_user) table. Which variable type should be selected?

A.List Collector
B.Lookup Select Box
C.Single Line Text
D.Reference
AnswerD

A Reference variable stores a sys_refrence to a single record on a specified table, presenting a lookup that resolves to one sys_user record. This matches the requirement for selecting exactly one record rather than a list.

Why this answer

A Reference variable type allows a user to select a single record from a specified table, such as sys_user. It provides a lookup field with a reference to the target table, ensuring data integrity and enabling dot-walking. This is the standard variable type for selecting one record from another table.

Exam trap

CIS-ITSM often tests the difference between Reference (single record from a table) and List Collector (multiple records), tricking candidates who confuse 'select a single record' with 'select from a list.'

How to eliminate wrong answers

Option A is wrong because a List Collector allows selection of multiple records from a table, not a single record. Option B is wrong because a Lookup Select Box is used to select from a predefined set of choices (a choice list), not from a table of records. Option C is wrong because a Single Line Text variable accepts free-form text input and does not enforce a reference to a table record.

Practice this question →
5
Multi-Selectmedium

Which TWO of the following options correctly describe Record Producers? (Choose two.)

Select 2 answers
A.They always create a parent Request [sc_request] and Requested Item [sc_req_item] instead of a target table record.
B.They generate a record on a target table, such as Incident or Task.
C.They cannot contain variable sets.
D.They are restricted to administrators only and cannot be accessed by end users.
E.They use variables to capture user input that can be mapped to fields on the target record.
AnswersB, E

Record Producers create records on a specified target table, such as Incident or Task, satisfying the stem's requirement that they generate records. This is their defining function: a catalogue item or producer configuration maps submitted variables directly onto fields of the target table, producing a new record without the user accessing that table directly.

Why this answer

Option B is correct because a Record Producer's defining behavior is to insert a new record into a specified target table, such as Incident, Task, or a custom table, rather than being limited to request/requested-item creation. Option E is correct because Record Producers present catalog variables (including variable sets) that capture user input, and these variables can be mapped via the producer's script or field mapping to populate fields on the generated target record. Option A is incorrect because Record Producers do not always create sc_request and sc_req_item records; that is the behavior of standard catalog items, whereas producers create the target table record directly.

Option C is incorrect because Record Producers can contain variable sets just like other catalog items. Option D is incorrect because Record Producers are catalog items that can be published to the service catalog and accessed by end users, not restricted to administrators.

Exam trap

CIS-ITSM often tests the misconception that Record Producers always create Request and Requested Item records, when they can create records directly on any target table.

Practice this question →
6
Multi-Selectmedium

A service catalog administrator needs to make a catalog item available only during a specific two-week window each quarter and also prevent it from appearing to users who are not in the 'Finance' department. Which TWO configurations should the administrator use? (Choose two.)

Select 2 answers
A.Configure a Catalog UI Policy that hides the item from users outside Finance.
B.Set the catalog item's Start date and End date fields to define the availability window.
C.Use a scheduled job to activate and deactivate the item each quarter.
D.Add an access control list entry on the sc_cat_item table that denies read to non-Finance users.
E.Create a user criteria record that includes the 'Finance' department and attach it to the catalog item's Available for list.
AnswersB, E

Catalog items include Start date and End date fields on the item record that control when the item is orderable. Setting these dates restricts availability to the desired two-week quarterly window without scripting, directly satisfying the time-bound requirement.

Why this answer

Catalog items support Start date and End date fields for time-bound availability and user criteria for audience targeting. Setting the dates limits ordering to the quarterly window, and attaching Finance department criteria to the Available for list ensures only that department sees the item. Together these two native configurations meet both requirements without custom code.

Exam trap

The trap here is reaching for ACLs or Catalog UI Policies to control who sees a catalog item, when user criteria and the item's date fields are the intended visibility controls.

Practice this question →
7
Multi-Selectmedium

Which TWO of the following entities can be restricted using User Criteria in the Service Catalog? (Choose two.)

Select 2 answers
A.Workflow Activity Types
B.Catalog Categories
C.Catalog Items
D.Individual Catalog Variables
E.Service Portal Widgets
AnswersB, C

User Criteria can be applied to catalog categories, restricting which users see an entire grouping of items in the Service Catalog. This satisfies the stem's constraint because category-level restriction governs visibility of all contained items, complementing item-level criteria.

Why this answer

User Criteria in the Service Catalog is used to control visibility and access to catalog content based on conditions such as user role, department, or group. Option B, Catalog Categories, is correct because User Criteria can be applied to categories to restrict which users can see or access those categories in the catalog. Option C, Catalog Items, is also correct because User Criteria can be assigned to individual catalog items to determine which users are eligible to view or order them.

Option A, Workflow Activity Types, is not restricted via User Criteria; workflow activities are controlled through workflow configuration and conditions, not catalog user criteria. Option D, Individual Catalog Variables, is not restricted via User Criteria; variable visibility is managed through variable attributes and UI policies, not user criteria. Option E, Service Portal Widgets, is not restricted via User Criteria; widget visibility is controlled through portal configuration, roles, and widget instances, not catalog user criteria.

Exam trap

CIS-ITSM often tests the misconception that User Criteria can be applied to any catalog-related record (variables, widgets, workflows), when in fact only Categories and Catalog Items expose the User Criteria related lists.

Practice this question →
8
MCQeasy

What is the primary function of an Order Guide in the ServiceNow Service Catalog?

A.To guide users through a questionnaire and help them submit multiple related catalog items in a single request.
B.To automate the generation of Knowledge Base articles from resolved requests.
C.To enforce approval chains across multiple departments before submission.
D.To restrict catalog items based on user roles and company location.
AnswerA

An Order Guide presents a questionnaire that branches based on answers, then bundles the resulting related catalog items into one cart and request. This satisfies the need to submit multiple linked items together rather than as separate orders.

Why this answer

An Order Guide in the ServiceNow Service Catalog is a wizard-style interface that presents a series of questions (via a catalog UI policy or variable set) and, based on the answers, generates a single request containing multiple related catalog items (a 'bundle'). It is designed to simplify multi-item ordering by guiding the user through a decision tree and automatically adding the appropriate items to the cart. This reduces the need for users to search for and add each item individually.

Exam trap

CIS-ITSM often tests the distinction between Order Guides and other catalog features like Record Producers or Catalog UI Policies; candidates may confuse the multi-item bundling capability with approval or visibility controls.

How to eliminate wrong answers

Option B is wrong because Knowledge Base article generation is handled by Knowledge Management workflows or the 'Article' creation process, not by Order Guides. Option C is wrong because approval chains are enforced by workflow/approval engines or catalog item approval configurations, not by Order Guides themselves. Option D is wrong because restricting catalog items based on user roles or location is done through User Criteria, Access Control Lists (ACLs), or catalog item visibility settings, not Order Guides.

Practice this question →
9
MCQeasy

What is the primary function of the Catalog Task [sc_task] table in Request Fulfillment?

A.To store the catalog item definition and pricing details.
B.To act as the top-level shopping cart container.
C.To represent individual work assignments generated during request fulfillment.
D.To track approvals required from department managers.
AnswerC

The sc_task table stores the individual fulfilment tasks spawned from a requested item, each assigned to a group or user. It captures the discrete work assignments that drive a request through fulfilment, distinct from the request itself.

Why this answer

The Catalog Task [sc_task] table is the workhorse of Request Fulfillment in ServiceNow. When a catalog item is ordered and the request [sc_request] and requested item [sc_req_item] records are created, the fulfillment workflow or flow generates one or more sc_task records, each representing a discrete unit of work assigned to a fulfillment group or individual. This is why sc_task is described as representing individual work assignments generated during request fulfillment.

Exam trap

CIS-ITSM often tests the distinction between the request lifecycle tables — sc_request (container), sc_req_item (what was ordered), and sc_task (the work) — so candidates who confuse the cart, request, or approval tables with the task table pick the wrong answer.

How to eliminate wrong answers

Option A is wrong because catalog item definitions and pricing are stored in the Catalog Item [sc_cat_item] table (with pricing on the item or via price fields), not in sc_task. Option B is wrong because the top-level shopping cart container is the Cart [sc_cart] table (with cart items in sc_cart_item), which exists before checkout and is unrelated to task fulfillment. Option D is wrong because approvals are tracked in the Approval [sysapproval_approver] table, which references the requested item or request, not in sc_task.

Practice this question →
10
MCQhard

A custom catalog item requires variable validation that depends on complex calculations spanning multiple fields, which cannot be achieved using standard UI Policy conditions. What is the best method to implement this client-side validation before the user submits the form?

A.Dictionary Client Script
B.UI Action with client-side script
C.Catalog Client Script (onSubmit) returning false upon failure
D.Business Rule (Before Insert)
AnswerC

A Catalog Client Script with an onSubmit script runs complex JavaScript across multiple fields and can return false to block submission. This handles calculations beyond UI Policy conditions, enforcing validation client-side before the form is submitted.

Why this answer

A Catalog Client Script with an onSubmit script is the correct choice because it runs client-side when the user submits the catalog item form and can return false to block submission. This allows complex, multi-field calculations and validation logic in JavaScript before the record is created. UI Policies cannot handle complex calculations, so a client script is required.

Exam trap

CIS-ITSM often tests the confusion between client-side onSubmit validation (which blocks submission) and server-side Business Rules (which run after submission), causing candidates to pick the Business Rule for pre-submit validation.

How to eliminate wrong answers

Option A is wrong because a Dictionary Client Script runs on the server against a table dictionary and is not designed for catalog form validation or multi-field client-side calculations. Option B is wrong because a UI Action with client-side script is typically used for buttons/links on forms, not for intercepting catalog item submission validation. Option D is wrong because a Business Rule (Before Insert) runs server-side after submission, so it cannot prevent the user from submitting the form in the first place — it can only abort the insert after the fact.

Practice this question →
11
Multi-Selecthard

An implementation specialist is designing an Order Guide that triggers three different child items based on user selections. Which THREE of the following components are essential parts of configuring this Order Guide? (Choose three.)

Select 3 answers
A.Child Catalog Items that are active and accessible to the submitting user.
B.Order Guide Rule Base rules to determine when child items are included.
C.Catalog UI Policies mapped specifically to the order guide container.
D.A scheduled job on sc_cart to purge abandoned order guides.
E.Prompt variables to collect initial user information shared across items.
AnswersA, B, E

Child catalog items must be active and accessible to the submitting user, otherwise the Order Guide cannot add them to the request or the user cannot order them. This satisfies the requirement that three different child items are triggered, since inactive or restricted items would break the branching outcome.

Why this answer

Option A is correct because an Order Guide can only include child catalog items that are active and available to the user submitting the request; inactive or access-restricted items cannot be added to the guide. Option B is correct because Order Guide rules (defined in the Order Guide Rule Base) evaluate conditions and determine which child items are automatically included or excluded based on the user's selections. Option E is correct because prompt variables (also called Order Guide variables) collect initial user input that is shared across the child items, driving the rule logic and pre-populating item variables.

Option C is incorrect because Catalog UI Policies apply to individual catalog items or variable sets, not to an Order Guide container as a distinct configuration component. Option D is incorrect because a scheduled job to purge abandoned sc_cart records is unrelated to Order Guide configuration and is not required for triggering child items.

Exam trap

CIS-ITSM often tests the misconception that UI Policies or scheduled jobs are part of Order Guide configuration, when the essential trio is child items, Rule Base rules, and prompt variables.

Practice this question →
12
MCQmedium

An order guide is configured with three catalog items. The administrator wants to ensure that a specific item in the order guide is only displayed in the rule base when the user selects 'International' in a location variable. Where is this condition specified?

A.Workflow switch activity
B.Order Guide Rule Base condition builder
C.Variable Set mapping table
D.Catalog UI Policy on the parent order guide
AnswerB

The rule base's condition builder evaluates variables at runtime, so a condition testing the location variable against 'International' controls whether that catalog item appears. This keeps the item hidden until the user's selection satisfies the rule.

Why this answer

The Order Guide Rule Base condition builder is where you define the logic that determines which catalog items are included or excluded from the order guide based on user selections. When a user selects 'International' in a location variable, the rule base evaluates that condition and conditionally displays the specific item. This is the native mechanism for conditional item inclusion in order guides, not a UI policy or workflow activity.

Exam trap

CIS-ITSM often tests the confusion between UI Policies (which control field behavior) and Order Guide Rule Base (which controls item inclusion), so candidates mistakenly pick a UI Policy for conditional item display.

How to eliminate wrong answers

Option A is wrong because a Workflow switch activity controls process branching after submission, not the display of items in the order guide UI. Option C is wrong because a Variable Set mapping table is used to map variable sets to catalog items, not to define conditional display logic. Option D is wrong because a Catalog UI Policy on the parent order guide affects field behavior on the form (visible, mandatory, read-only) but does not control which catalog items appear in the order guide's rule base.

Practice this question →
13
MCQmedium

An organization wants to reuse a set of standard hardware specification questions across twenty different laptop and desktop catalog items. Which feature should the administrator implement?

A.Record Producer Template
B.Catalog UI Policy Collection
C.Variable Set
D.Order Guide Rule Base
AnswerC

Variable Sets bundle a group of variables that can be attached to multiple catalog items, so the twenty hardware specification questions are maintained once and reused everywhere. This directly satisfies the stem's requirement to reuse standard questions across many catalog items without duplicating them.

Why this answer

Variable Sets in ServiceNow are containers that hold a group of variables (questions) which can be attached to multiple catalog items. By creating a Variable Set containing the standard hardware specification questions, the administrator can reuse it across all twenty catalog items without redefining the questions each time. This ensures consistency and simplifies maintenance: updating the Variable Set updates all catalog items that use it.

Thus, Variable Set is the correct feature for reusing a set of questions across multiple catalog items.

Exam trap

CIS-ITSM often tests the distinction between features that sound similar but serve different purposes, such as confusing Variable Sets with Record Producer Templates or Order Guides, leading candidates to choose an option that does not support reuse of variables across multiple catalog items.

How to eliminate wrong answers

Option A is wrong because Record Producer Templates are used to pre-populate record producers with default values, not to group and reuse variables across catalog items. Option B is wrong because Catalog UI Policy Collection is not a standard ServiceNow feature; UI Policies are used to dynamically change form behavior, but there is no 'Collection' feature for reuse across catalog items. Option D is wrong because Order Guide Rule Base is not a feature; Order Guides are used to bundle catalog items into a single order, but they do not provide a mechanism to reuse a set of variables across multiple catalog items.

Practice this question →
14
MCQhard

An administrator has configured a Catalog UI Policy with a Catalog UI Policy Action. However, the action is not taking effect when the dependent variable changes value. What is a common troubleshooting step for Catalog UI Policies?

A.Clear the browser cache and restart the instance JVM
B.Convert the UI Policy into a Business Rule
C.Change the UI Policy execution order to zero
D.Verify that 'Applies on Target' (such as Service Portal or Catalog Item) is correctly checked on the UI Policy definition
AnswerD

Catalog UI Policies only run against the interface or target specified in 'Applies on Target'. If that checkbox omits the relevant Service Portal or Catalog Item, the policy and its actions never execute when the dependent variable changes, so verifying it is the first troubleshooting step.

Why this answer

Catalog UI Policies only execute when the form is rendered in a context where the policy is marked as applicable. The 'Applies on Target' setting (also called 'Applies to' in some versions) determines whether the policy runs on the Catalog Item, the Service Portal, or both. If this is unchecked or set to the wrong target, the policy and its actions silently do nothing even though the configuration looks correct.

Exam trap

CIS-ITSM often tests the 'Applies on Target' / 'Applies to' setting because candidates assume a UI Policy runs everywhere by default, when in fact it must be explicitly scoped to the Catalog Item and/or Service Portal target.

How to eliminate wrong answers

Option A is wrong because clearing browser cache or restarting the JVM is a generic troubleshooting step that does not address UI Policy execution context; UI Policies are evaluated server-side and delivered to the client, so cache is rarely the cause. Option B is wrong because converting a UI Policy to a Business Rule is a redesign, not a troubleshooting step, and Business Rules run server-side without the same client-side form behavior. Option C is wrong because execution order only matters when multiple UI Policies conflict; setting order to zero does not make an inapplicable policy run.

Practice this question →
15
MCQhard

When designing a complex fulfillment workflow, an administrator uses a 'Create Task' activity to generate a catalog task. How are variable values collected from the requested item passed or accessed within the task description?

A.By referencing variables using syntax like ${current.variables.variable_name} directly in the task description or workflow script.
B.By configuring a Catalog UI Policy to sync task descriptions on submission.
C.By mapping variable sets in the workflow properties related list.
D.Variables must be manually copied using a Business Rule because workflows cannot read variable data.
AnswerA

The ${current.variables.variable_name} syntax reads the requested item's variable values through the current record, so the catalog task description inherits the collected answers without extra scripting. This satisfies the requirement to pass variable values into the generated task.

Why this answer

In ServiceNow workflows, the Create Task activity and workflow scripts can access catalog variable values through the current.variables object, using the syntax ${current.variables.variable_name} in the task description or short description fields. This substitution is evaluated at runtime when the task is created, pulling the value from the parent sc_req_item. The same syntax works in workflow script activities via current.variables.variable_name.

Exam trap

The trap is assuming workflows need a Business Rule or UI Policy to read variables — candidates who haven't built workflows often pick the Business Rule option, not realizing current.variables is natively available in workflow context.

How to eliminate wrong answers

Option B is wrong because Catalog UI Policies operate on the catalog item form at submission time and cannot sync data into downstream task descriptions — they control field visibility and mandatory state, not workflow data propagation. Option C is wrong because variable sets are containers for variable definitions, not a mapping mechanism for passing values into workflow tasks; there is no 'workflow properties related list' that maps variable sets to task fields. Option D is wrong because workflows absolutely can read variable data via current.variables — no Business Rule is required, and this misconception leads to unnecessary custom scripting.

Practice this question →
16
MCQeasy

In ServiceNow Service Catalog terminology, what does the Request [sc_request] table represent?

A.The parent container representing the overall shopping cart order submission.
B.The fulfillment task assigned to a specific assignment group.
C.The individual catalog item being requested by the end user.
D.The workflow definition triggered upon catalog checkout.
AnswerA

The sc_request table acts as the parent record for a submitted catalog order, grouping one or more sc_req_item rows beneath it. It represents the overall cart submission, satisfying the stem's definition of the parent container.

Why this answer

The Request [sc_request] table is the parent container that represents the overall shopping cart submission — it groups one or more Requested Items (sc_req_item) that were checked out together. It holds header-level information like the requester, submission date, and approval state for the entire order.

Exam trap

CIS-ITSM often tests whether candidates confuse the three-tier catalog hierarchy — Request (parent order), Requested Item (individual item), and Catalog Task (fulfillment work) — since all three sound similar but represent distinct levels.

How to eliminate wrong answers

Option B is wrong because fulfillment tasks assigned to assignment groups are represented by Task [sc_task] records, which are children of Requested Items, not the Request itself. Option C is wrong because the individual catalog item being requested is the Requested Item [sc_req_item], which is a child of the Request. Option D is wrong because the workflow definition triggered at checkout is a Workflow [wf_workflow] record, not the Request table.

Practice this question →
17
MCQhard

A developer needs to retrieve the value of a catalog variable named 'urgency_level' within a Service Catalog Workflow using a Run Script activity. Which syntax is correct?

A.producer.urgency_level
B.current.variables.urgency_level
C.workflow.scratchpad.urgency_level
D.g_form.getValue('urgency_level')
AnswerB

Within a Service Catalog Workflow Run Script activity, the current object exposes the requested catalog item's variables, so current.variables.urgency_level retrieves the submitted value directly. This satisfies the developer's need to read the named variable during workflow execution.

Why this answer

In a Service Catalog Workflow Run Script activity, the `current` object represents the current record (the catalog task or requested item), and catalog variable values are accessed through the `variables` property. The correct syntax is `current.variables.urgency_level`, which retrieves the value of the 'urgency_level' variable. This is the standard method for reading catalog variables in server-side scripts within workflows.

Exam trap

CIS-ITSM often tests the distinction between client-side and server-side variable access, confusing candidates with methods like g_form.getValue() that only work in client scripts, or misusing workflow scratchpad for variable retrieval.

How to eliminate wrong answers

Option A is wrong because `producer` is not a valid object in this context; it might be confused with a workflow producer, but it does not hold catalog variable values. Option C is wrong because `workflow.scratchpad` is used to store and retrieve temporary data within a workflow, not to directly access catalog variables. Option D is wrong because `g_form.getValue('urgency_level')` is a client-side method used in catalog client scripts or UI policies, not available in server-side Run Script activities.

Practice this question →
18
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.

Practice this question →
19
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.

Practice this question →
20
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.

Practice this question →
21
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.

Practice this question →
22
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.

Practice this question →
23
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.

Practice this question →
24
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.

Practice this question →
25
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.

Practice this question →
26
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.

Practice this question →
27
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.

Practice this question →
28
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.

Practice this question →
29
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.

Practice this question →
30
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.

Practice this question →
31
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.

Practice this question →
32
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.

Practice this question →
33
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.

Practice this question →
34
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.

Practice this question →
35
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.

Practice this question →
36
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.

Practice this question →
37
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.

Practice this question →
38
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.

Practice this question →
39
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.

Practice this question →
40
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.

Practice this question →
41
MCQmedium

An administrator created a Catalog UI Policy that makes a variable mandatory when another variable equals 'Other'. However, the policy does not apply when the item is loaded via an Order Guide. How should the administrator resolve this?

A.Add the order guide to the 'Catalog UI Policy Related Lists' tab.
B.Change the execution order of the UI policy to 1.
C.Ensure 'Applies to Order Guides' is checked on the Catalog UI Policy record.
D.Convert the Catalog UI Policy into a Catalog Client Script using g_form.setMandatory().
AnswerC

Catalog UI Policies only run on standalone catalog items unless the 'Applies to Order Guides' flag is enabled. Ticking it makes the policy evaluate variables rendered through an Order Guide, restoring the mandatory condition when the dependent variable equals 'Other'.

Why this answer

Catalog UI Policies have an 'Applies to Order Guides' option that must be checked for the policy to execute when the catalog item is part of an Order Guide. By default, this option is unchecked, so the policy does not apply in the Order Guide context.

Exam trap

CIS-ITSM often tests the subtlety that Catalog UI Policies do not automatically apply to Order Guides unless explicitly configured, and candidates may overlook the 'Applies to Order Guides' checkbox.

How to eliminate wrong answers

Option A is wrong because there is no 'Catalog UI Policy Related Lists' tab on an Order Guide; UI policies are not associated that way. Option B is wrong because changing the execution order does not affect whether the policy applies to Order Guides; it only affects the order of execution relative to other policies. Option D is wrong because converting to a Catalog Client Script is unnecessary and more complex; the simple fix is to check the 'Applies to Order Guides' option.

Practice this question →
42
MCQmedium

A catalog item 'New Employee Laptop' uses a Record Producer to create a task on the 'sc_task' table. The administrator needs to ensure that the 'short_description' of the created task includes the value of the 'laptop_model' variable from the catalog item. Where should the administrator configure this mapping?

A.Create a Business Rule on the 'sc_task' table that sets 'short_description' from the 'laptop_model' variable after insert.
B.In the Catalog Item's 'Variable' record for 'laptop_model', set the 'Map to field' attribute to 'short_description'.
C.In the Record Producer's 'Variable Mapping' related list, create a mapping for the 'short_description' field to the 'laptop_model' variable.
D.In the Record Producer's 'Script' field, use 'current.short_description = producer.laptop_model;' before the insert.
AnswerC

The Variable Mapping related list on a Record Producer allows you to map catalog variables to fields on the target table. This is the intended, no-code method to populate fields like short_description with variable values. The mapping is evaluated when the record is created. This approach is maintainable and does not require custom scripting, making it the best practice for this requirement.

Why this answer

The Variable Mapping related list on a Record Producer is the designed feature to map catalog variables to target table fields. It provides a declarative way to set values like short_description without scripting. Other options involve custom scripts or misusing variable attributes, which are unnecessary and less maintainable.

The mapping is evaluated during record creation, ensuring the field is populated correctly.

Exam trap

The trap here is assuming that variable mapping must be done via scripting or that the 'Map to field' attribute on a variable applies to Record Producers, when in fact Record Producers have a dedicated Variable Mapping related list.

Practice this question →
43
Multi-Selectmedium

Which TWO of the following are valid ways to structure layouts in a Service Catalog item form? (Choose two.)

Select 2 answers
A.UI Macro Table Mappings
B.Variable Sets
C.Dictionary Layout Overrides
D.Container Begin / Container Split / Container End
E.CSS Flexbox Injection via Catalog UI Policy Actions
AnswersB, D

Variable Sets group related variables into a reusable container that can be attached to multiple catalog items, satisfying the requirement for a valid layout structure. They render as a distinct section within the form, letting administrators organise fields logically without rebuilding them per item.

Why this answer

In ServiceNow Service Catalog, form layouts for catalog items are built using variables, and Container Begin, Container Split, and Container End are the standard variable types used to create multi-column and sectioned layouts on a catalog item form, so option D is correct. Variable Sets are also a valid structural mechanism: they group a reusable collection of variables (including their own containers and ordering) that can be attached to one or more catalog items, so option B is correct. Option A is incorrect because UI Macros are used for custom rendering/widgets, not for defining catalog item layout structure, and there is no 'UI Macro Table Mappings' layout construct.

Option C is incorrect because dictionary layout overrides apply to table forms (sys_dictionary/sys_ui), not to catalog item variable layouts. Option E is incorrect because injecting CSS Flexbox through a Catalog UI Policy action is a styling hack, not a supported way to structure catalog item layouts.

Exam trap

CIS-ITSM often tests whether candidates can distinguish supported catalog layout mechanisms (Variable Sets, Containers) from plausible-sounding but invalid options like CSS injection or dictionary overrides.

Practice this question →
44
MCQmedium

An administrator is configuring a Catalog Item for a new laptop. The item has a 'Model' variable (Select Box) and a 'RAM' variable (Select Box). The requirement is that the available RAM options must change based on the selected Model, and the list of RAM choices is maintained in a separate table (u_laptop_ram_options). What should the administrator configure to meet this requirement?

A.Create a Variable Lookup Select Box for the RAM variable, referencing the u_laptop_ram_options table and filtering by the Model variable.
B.Create a new Variable Set containing all possible RAM options and use a Catalog Client Script to hide irrelevant ones.
C.Create a Catalog UI Policy with a Run Script that filters the RAM variable's choices based on the Model variable.
D.Use a Record Producer on the u_laptop_ram_options table to generate the RAM choices dynamically when the Model is selected.
AnswerA

A Variable Lookup Select Box is designed to dynamically populate choices from a table. It supports a reference qualifier that can filter records based on another variable's value, such as the selected Model. This provides a maintainable, out-of-box solution without custom scripting. The administrator can set the reference qualifier to something like 'model=javascript:current.variables.model', ensuring RAM options are relevant to the chosen model.

Why this answer

The requirement is to dynamically filter the RAM variable's choices based on the selected Model, with choices stored in a separate table. A Variable Lookup Select Box is the correct tool because it pulls choices from a table and supports a reference qualifier that can reference other variables. This provides a no-code solution that is maintainable and scalable.

Other options either misuse UI Policies, Variable Sets, or Record Producers, none of which natively support dynamic choice filtering from an external table.

Exam trap

The trap here is assuming that Catalog UI Policies can dynamically repopulate a Select Box's choices from an external table, when in fact they are limited to client-side form behavior.

Practice this question →
45
MCQmedium

A developer needs to populate a user's department automatically into a catalog variable when the Catalog Item form loads. Which type of script should be used?

A.Business Rule
B.Catalog Client Script (onLoad)
C.Catalog UI Policy Script
D.Script Include
AnswerB

A Catalog Client Script with an onLoad type runs in the browser when the form loads, allowing g_scratchpad or a GlideAjax call to populate the department variable before the user interacts. This satisfies the stem's requirement for automatic population at form load.

Why this answer

A Catalog Client Script with an onLoad script type runs in the browser when the Catalog Item form loads, making it the correct choice to populate a variable such as department based on the logged-in user. Client scripts can call g_form.setValue() to set the variable value before the user interacts with the form. This is the standard mechanism for dynamic, client-side variable population on catalog item forms.

Exam trap

CIS-ITSM often tests the confusion between client-side and server-side scripts, so candidates pick Business Rule or Script Include when the requirement explicitly says the value must populate when the form loads in the browser.

How to eliminate wrong answers

Option A is wrong because a Business Rule runs server-side on database operations and cannot directly populate a catalog variable at form load time in the user's browser. Option C is wrong because a Catalog UI Policy Script runs in response to UI policy conditions (such as making fields mandatory or visible) and is not the primary mechanism for initializing variable values on load. Option D is wrong because a Script Include is a server-side reusable script library and does not execute in the browser to set form variables.

Practice this question →
46
MCQeasy

When configuring a Service Catalog item, what is the purpose of setting the 'No cart' field to true?

A.It prevents users from ordering more than one quantity of the item.
B.It deletes all existing items currently stored in the user's active shopping cart.
C.It disables the Service Portal shopping experience completely for that user.
D.It hides the 'Add to Cart' button and forces immediate checkout upon submission.
AnswerD

Setting 'No cart' to true bypasses the shopping cart stage entirely, hiding the 'Add to Cart' button so the item is submitted and checked out immediately. This satisfies the requirement for a one-step request flow rather than a multi-item cart interaction.

Why this answer

Setting the 'No cart' field to true on a catalog item bypasses the shopping cart entirely: the 'Add to Cart' button is hidden and the item is submitted for immediate checkout when the user clicks 'Order Now' or equivalent. This is used for items that should not be combined with other purchases or that require immediate fulfillment.

Exam trap

CIS-ITSM often tests the 'No cart' field by offering distractor options about quantity limits or cart deletion, so candidates must remember that 'No cart' specifically hides the Add to Cart button and forces immediate checkout.

How to eliminate wrong answers

Option A is wrong because quantity limits are controlled by the 'Max quantity' or 'Mandatory quantity' fields, not 'No cart'. Option B is wrong because 'No cart' does not delete existing cart contents; it only affects the current item's checkout flow. Option C is wrong because 'No cart' does not disable the Service Portal shopping experience globally — it only changes the behavior for that specific catalog item.

Practice this question →
47
MCQhard

A developer needs to populate a List Collector variable with records from a custom table based on criteria evaluated at runtime. How can this dynamic filtering be achieved?

A.By modifying the sc_req_item dictionary directly
B.Using a client-side alert message
C.Using a reference qualifier on the List Collector variable definition
D.Using a Catalog UI Policy action to set filter attributes
AnswerC

A reference qualifier on the List Collector applies an encoded query or scripted condition that filters the referenced table's records dynamically at runtime, so only matching records appear in the collector. This satisfies the requirement for criteria evaluated when the form loads.

Why this answer

A List Collector variable can be dynamically filtered by applying a reference qualifier on the variable definition in item_option_new. The reference qualifier is a query string (or advanced script) that restricts which records from the referenced table appear in the collector's available list, evaluated at runtime based on user or form context. This is the standard, supported mechanism for dynamic filtering of reference and list collector variables.

Exam trap

The trap is confusing UI Policies (which control form field behavior) with reference qualifiers (which control record filtering) — candidates often pick the UI Policy option because both are 'dynamic' catalog configurations.

How to eliminate wrong answers

Option A is wrong because modifying the sc_req_item dictionary directly changes table schema, not variable filtering behavior, and would be a dangerous, unsupported customization. Option B is wrong because a client-side alert message only displays a notification to the user — it has no effect on which records populate a List Collector. Option D is wrong because Catalog UI Policy actions control field visibility, mandatory state, and read-only state on the form; they cannot set the reference qualifier or filter attributes of a List Collector's underlying query.

Practice this question →
48
Multi-Selectmedium

An administrator is configuring a Catalog UI Policy. Which TWO of the following statements are true regarding Catalog UI Policies? (Choose two.)

Select 2 answers
A.They execute on the server side prior to database insertion.
B.They can be applied to both Catalog Items and Record Producers.
C.They can execute client-side logic without requiring JavaScript when using declarative UI policy actions.
D.They only function on legacy UI16 forms and are unsupported in Service Portal.
E.They replace the need for Catalog Client Scripts in all scenarios, including asynchronous database lookups.
AnswersB, C

Catalog UI Policies attach to the catalog item definition itself, so they govern both catalog items and record producers, which share that same underlying structure. This satisfies the stem's requirement by covering record producers, not just items.

Why this answer

Catalog UI Policies are applicable to both Catalog Items and Record Producers, so option B is correct because these policies can control field visibility, mandatory status, and read-only behavior on any catalog-facing form, including record producer forms that create records like incidents or requests. Option C is also correct because Catalog UI Policies support declarative actions such as setting a field to visible, mandatory, or read-only without writing JavaScript, unlike Catalog Client Scripts which require scripting. Option A is incorrect because Catalog UI Policies run on the client side to dynamically alter the form, not on the server side before database insertion; server-side logic would be handled by business rules or other server scripts.

Option D is incorrect because Catalog UI Policies work in Service Portal and other catalog interfaces, not only legacy UI16 forms. Option E is incorrect because Catalog UI Policies cannot replace Catalog Client Scripts in all scenarios; client scripts are still needed for asynchronous database lookups, complex validation, or custom logic that declarative UI policy actions cannot perform.

Exam trap

CIS-ITSM often tests the confusion between Catalog UI Policies and Catalog Client Scripts, leading candidates to incorrectly think UI Policies can handle all client-side logic including asynchronous lookups.

Practice this question →
49
MCQhard

A developer is writing a Catalog Client Script that needs to interact with variables inside a Multi-Row Variable Set (MRVS). Which g_form method is used to retrieve the entire contents of an MRVS as an object/string?

A.g_form.getValue('mrvs_internal_name')
B.g_scratchpad.getVariableSet()
C.g_form.getMRVSValue()
D.g_form.getMatrixValue()
AnswerA

For a Multi-Row Variable Set, g_form.getValue returns the entire set serialised as a JSON string using the MRVS internal name, which the script can then parse. This satisfies the requirement to retrieve all rows at once.

Why this answer

In ServiceNow, g_form.getValue() is the standard method used to retrieve the value of a variable, including Multi-Row Variable Sets, where it returns the MRVS contents as a JSON string that can be parsed into an object. This is the documented approach for accessing the entire MRVS payload from a Catalog Client Script.

Exam trap

The trap is inventing plausible-sounding API method names — candidates who have not memorized the actual g_form API may select getMRVSValue() or getMatrixValue(), which do not exist in ServiceNow.

How to eliminate wrong answers

Option B is wrong because g_scratchpad is a server-to-client data passing mechanism, not a method for reading MRVS values, and getVariableSet() is not a valid g_scratchpad method. Option C is wrong because g_form.getMRVSValue() does not exist in the ServiceNow API — it is a fabricated method name. Option D is wrong because g_form.getMatrixValue() is not a real API method; matrix variables use g_form.getValue() with the variable name, not a dedicated getMatrixValue() call.

Practice this question →
50
Multi-Selecthard

Which THREE of the following features are characteristic of Order Guides in ServiceNow? (Choose three.)

Select 3 answers
A.They replace the requirement for approval workflows entirely.
B.They allow users to submit multiple related catalog items as a single order.
C.They provide a 'Describe Needs' initial stage to gather high-level user requirements.
D.They use a Rule Base to conditionally include or exclude specific catalog items.
E.They can only be used by ITIL fulfillment agents, not end users.
AnswersB, C, D

Order Guides let users select and submit multiple related catalog items together as a single order, rather than raising separate requests. This bundling is the core purpose of an Order Guide and distinguishes it from individual catalogue items.

Why this answer

Order guides present an initial describe needs phase, evaluate rule bases to determine conditional items, and bundle multiple items into a single cart checkout.

Practice this question →
51
MCQhard

When configuring an Order Guide, how does the system determine which Catalog Items to present to the user in the subsequent steps?

A.Using Catalog Client Scripts attached to the Order Guide container
B.Using variable sets mapped to the target items
C.Using Order Guide Rules
D.Using Flow Designer flow triggers
AnswerC

Order Guide Rules drive conditional logic that filters and presents eligible Catalog Items based on the user's prior selections, satisfying the requirement that subsequent steps adapt dynamically. Unlike static inclusion lists, rules evaluate variables at runtime, ensuring only relevant items appear as the user progresses through the guide.

Why this answer

Order Guide Rules determine which Catalog Items are presented in subsequent steps of an Order Guide. These rules are evaluated based on user selections in previous steps, and they conditionally include or exclude catalog items. This allows for dynamic, guided ordering experiences where the available items depend on earlier choices.

Exam trap

CIS-ITSM often tests the confusion between Order Guide Rules and other mechanisms like Client Scripts or Flow Designer, leading candidates to overlook the specific rule-based determination of catalog items.

How to eliminate wrong answers

Option A is wrong because Catalog Client Scripts attached to the Order Guide container can manipulate the form but do not determine which catalog items are presented in steps; that is the role of Order Guide Rules. Option B is wrong because variable sets mapped to target items are used to share variables across items, not to determine which items appear in steps. Option D is wrong because Flow Designer flow triggers are used for automation and orchestration, not for defining the presentation of catalog items in an Order Guide.

Practice this question →
52
Multi-Selecthard

An administrator is troubleshooting a Catalog Client Script that is not executing properly on a Service Portal catalog item. Which THREE factors should be verified? (Choose three.)

Select 3 answers
A.The user has admin rights to the database
B.The 'UI Type' field is set to 'Mobile/Service Portal' or 'All'
C.The correct variable name is referenced in the script and applies to the catalog item
D.The script is written in Java rather than JavaScript
E.The script is marked as 'Active'
AnswersB, C, E

Scripts configured exclusively for Desktop (UI Type = Desktop) will not execute in Service Portal.

Why this answer

Option B is correct because a Catalog Client Script only runs on the Service Portal when its UI Type field is set to 'Mobile/Service Portal' or 'All'; if it is set to 'Desktop' or 'Both' (legacy), it will not fire in the portal. Option C is correct because the script must reference the exact variable name (sys_id/name) defined on that catalog item, and the script must be associated with the correct catalog item or variable set, otherwise the logic never applies. Option E is correct because an inactive Catalog Client Script is not executed at all, so the Active flag must be checked.

Option A is incorrect because admin rights to the database are irrelevant to client-side script execution in the portal. Option D is incorrect because Catalog Client Scripts are written in JavaScript (with the GlideForm/g_form API), not Java.

Exam trap

CIS-ITSM often tests the misconception that Catalog Client Scripts work identically across all interfaces, but the UI Type field is a common cause of scripts not executing in Service Portal.

Practice this question →
53
MCQmedium

An administrator needs to ensure that a catalog item displays a warning message at the top of the form whenever a specific variable is changed. Which script type is best suited for this?

A.Catalog Client Script (OnChange)
B.Catalog UI Policy (Run scripts)
C.Business Rule (Display)
D.Catalog Server Script
AnswerA

A Catalog Client Script with an OnChange event fires immediately in the browser when the specified variable's value changes, letting the script call `g_form.showFieldMsg` or similar to render the warning at the top of the form without a server round-trip. This satisfies the stem's requirement for instant, client-side feedback on variable change.

Why this answer

A Catalog Client Script with the OnChange script type is designed to execute when a specific variable's value changes on the catalog item form. This is the correct place to evaluate the new value and display a warning message (e.g., via g_form.showFieldMsg or alert) at the top of the form. It runs client-side in the browser, giving immediate feedback without a server round-trip.

Exam trap

The trap is confusing UI Policy 'Run scripts' with Catalog Client Script OnChange — both can run JavaScript on variable change, but the exam expects you to know that OnChange is the purpose-built script type for reacting to a specific variable's change.

How to eliminate wrong answers

Option B is wrong because Catalog UI Policies with 'Run scripts' execute on field value changes but are intended for field visibility, mandatory, and read-only logic — they can run scripts, but the canonical mechanism for custom warning messages tied to a variable change is a Catalog Client Script OnChange. Option C is wrong because Business Rules run server-side on database operations and cannot directly display a form warning to the user in real time. Option D is wrong because 'Catalog Server Script' is not a standard ServiceNow script type — server-side catalog logic uses Business Rules, Script Includes, or workflow scripts, none of which render client-side warnings.

Practice this question →
54
MCQeasy

What is the function of the 'No 'Add to Cart'' checkbox on a catalog item form?

A.It completely disables ordering of the item.
B.It removes the 'Add to Cart' button, leaving only the 'Order Now' button.
C.It prevents the item from appearing in search results.
D.It restricts checkout to users with the admin role.
AnswerB

Ticking this checkbox suppresses the cart workflow entirely, so the catalog item form renders only the 'Order Now' button. The item is submitted directly as a request rather than staged in a cart, which suits single-quantity or service-style items.

Why this answer

The 'No Add to Cart' checkbox on a catalog item form, when checked, removes the 'Add to Cart' button from the item's catalog page, leaving only the 'Order Now' button. This forces users to go through the checkout process immediately for that item, rather than adding it to a cart with other items. It does not disable ordering entirely.

Exam trap

CIS-ITSM often tests the difference between 'No Add to Cart' and 'Hide on search' or 'Disable ordering'; candidates may think it disables ordering, but it only removes the cart option.

How to eliminate wrong answers

Option A is wrong because the item can still be ordered via 'Order Now'; it only removes the cart option. Option C is wrong because the checkbox does not affect search visibility; that is controlled by 'Hide on search' or catalog visibility settings. Option D is wrong because it does not restrict checkout to admins; that would require user criteria or role restrictions.

Practice this question →
55
MCQeasy

An administrator is creating a Record Producer. Which table should the resulting records be generated in?

A.sc_req_item
B.sc_request
C.A target table specified in the Record Producer definition (e.g., incident or custom table)
D.sys_user
AnswerC

A Record Producer writes into whatever target table its definition names, so records land in that specified table rather than a fixed one. This satisfies the requirement that the resulting records be generated in a chosen destination.

Why this answer

A Record Producer can generate records in any specified target table, such as incident, problem, change, or a custom table. The target table is defined in the Record Producer's configuration. This allows the producer to create records of that type when the catalog item is ordered.

Exam trap

CIS-ITSM often tests the distinction between Record Producers and standard catalog items; candidates may think Record Producers always create sc_req_item records, but they actually create records in the specified target table.

How to eliminate wrong answers

Option A is wrong because sc_req_item is the default table for catalog items that go through the request process, but a Record Producer can target other tables. Option B is wrong because sc_request is the request table, not the target for Record Producer output. Option D is wrong because sys_user is the user table, which is not a typical target for a Record Producer unless specifically configured, but the question asks for the general answer.

Practice this question →
56
MCQmedium

An organization requires that when a user selects 'Hardware' in a dropdown variable, three specific hardware-related variables become mandatory. Which approach represents best practice in ServiceNow?

A.Catalog UI Policy
B.Catalog Client Script (OnChange)
C.Data Policy on the sc_req_item table
D.Order Guide Rule Base
AnswerA

A Catalog UI Policy dynamically makes variables mandatory or visible based on another variable's value, satisfying the requirement that selecting 'Hardware' forces three related fields to become mandatory. Client scripts could also do this, but UI Policies are declarative best practise, requiring no code and remaining maintainable.

Why this answer

A Catalog UI Policy is the best practice in ServiceNow for dynamically making variables mandatory based on the value of another variable. UI Policies run on the client side and can set variables to mandatory, visible, or read-only without writing custom scripts. This declarative approach is easier to maintain and less error-prone than client scripts.

Exam trap

CIS-ITSM often tests the preference for declarative UI Policies over custom client scripts for dynamic form behavior, causing candidates to choose the scripted solution.

How to eliminate wrong answers

Option B is wrong because a Catalog Client Script (OnChange) would require custom JavaScript to set the mandatory flag, which is less maintainable and not best practice when a UI Policy can achieve the same result. Option C is wrong because a Data Policy on the sc_req_item table enforces rules at the database level and is not designed for dynamic form behavior based on variable values. Option D is wrong because an Order Guide Rule Base is used to define multi-step order guides, not to enforce variable mandatory conditions within a single catalog item.

Practice this question →
57
Multi-Selectmedium

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

Select 2 answers
A.Automatically generating a separate incident record for each row submitted
B.Supporting Catalog UI Policies and Catalog Client Scripts
C.Storing data directly in permanent custom table columns during initial cart checkout
D.Allowing users to enter tabular, multi-row data collections within a single catalog item
E.Replacing standard workflows with spreadsheet imports
AnswersB, D

Multi-Row Variable Sets render as a grid, and ServiceNow supports Catalog UI Policies and Catalog Client Scripts against their child variables, letting you enforce mandatory fields or dynamic behaviour per row. This satisfies the requirement for interactive control within the tabular collection.

Why this answer

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

Exam trap

CIS-ITSM often tests the misconception that MRVS create separate records or replace workflows — the correct understanding is that MRVS are a tabular data collection tool stored as JSON, with client script and UI policy support.

Practice this question →
58
Multi-Selectmedium

Which TWO statements are true regarding Record Producers in ServiceNow? (Choose two.)

Select 2 answers
A.They prevent users from accessing the Service Portal
B.Variables can be mapped directly to fields on the target table record
C.They are restricted to creating records only in the sc_req_item table
D.They require an Order Guide to function
E.They generate records in a target table specified in their definition, such as Incident or a custom table
AnswersB, E

Record Producer variables can be mapped to target table fields, so values entered on the producer form populate the created record directly. This satisfies the stem's truth condition by describing the actual data-flow mechanism between the producer's variable set and the target record.

Why this answer

Option B is correct because Record Producers use variable-to-field mapping so that values entered in the producer's variables are written directly into fields on the newly created target record. Option E is correct because a Record Producer is defined with a target table (for example Incident, sc_req_item, or a custom table), and submitting the producer creates a record in that specified table. Options A, C, and D are incorrect: Record Producers do not block Service Portal access, they are not limited to sc_req_item, and they do not require an Order Guide to function.

Exam trap

CIS-ITSM often tests the misconception that Record Producers are tied to sc_req_item or require an Order Guide — candidates confuse them with catalog items and Order Guides, which are separate constructs.

Practice this question →
59
MCQhard

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

A.Write a standalone Business Rule on the sys_user table.
B.Modify the Order Guide rule base to evaluate manager hierarchy.
C.Use the Assignment group field in the Catalog Task activity configuration directly.
D.Configure the Catalog Task activity assignment to use script/dot-walking to reach current.variables.target_employee.manager.
AnswerD

Dot-walking from `current.variables.target_employee` to `.manager` resolves the referenced user's manager record at runtime, satisfying the dynamic assignment constraint without hard-coding a name. Because the variable stores a sys_user reference, the manager field is directly traversable, letting the Catalog Task activity assign to that manager automatically.

Why this answer

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

Exam trap

CIS-ITSM often tests the misconception that assignment must be done via groups or business rules, overlooking the scripting capabilities within workflow activities.

How to eliminate wrong answers

Option A is wrong because a standalone Business Rule on sys_user would not have context of the catalog variable and would trigger on all user updates, not just this workflow. Option B is wrong because Order Guide rules are used for guiding catalog item selection, not for dynamic task assignment. Option C is wrong because the Assignment group field expects a group, not a user, and cannot dynamically resolve to a manager without scripting.

Practice this question →
60
MCQeasy

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

A.Maintain Items
B.Maintain Categories
C.Order Guides
D.Catalog Definitions
AnswerB

Maintain Categories provides the hierarchical taxonomy that classifies Service Catalog items, letting administrators define parent categories and nested subcategories so end users browse offerings logically. This directly satisfies the stem's requirement to configure categories and subcategories for organising catalog items, unlike modules handling request fulfilment or approval routing.

Why this answer

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

Exam trap

CIS-ITSM often tests the distinction between Maintain Categories (taxonomy/navigation) and Maintain Items (the actual catalog records), so candidates who conflate 'organizing items' with 'creating items' pick Maintain Items incorrectly.

How to eliminate wrong answers

Option A is wrong because Maintain Items is used to create and edit the catalog items themselves (their variables, pricing, fulfillment process), not the category taxonomy that organizes them. Option C is wrong because Order Guides are multi-item request wizards that bundle several catalog items into a sequenced form — they consume categories but do not define them. Option D is wrong because 'Catalog Definitions' is not a ServiceNow module; the actual related admin modules are Maintain Catalogs, Maintain Categories, and Maintain Items, so this option is a fabricated distractor.

Practice this question →
61
Multi-Selectmedium

Which TWO of the following are true regarding 'Catalog Client Scripts'?

Select 2 answers
A.They are used to update the sc_task state directly
B.They only run on the Service Portal
C.They can be used to make fields mandatory
D.They execute on the server side
E.They can be applied to Variable Sets
AnswersC, E

Catalog Client Scripts run in the browser against the catalog form, so they can set a variable's mandatory flag dynamically based on user input or other variables. This satisfies the requirement that the control enforces field completion before submission.

Why this answer

Option C is correct because Catalog Client Scripts run in the browser on catalog item forms and can enforce field-level validation, such as using g_form.setMandatory() to make a variable mandatory before submission. Option E is correct because Catalog Client Scripts can be associated with Variable Sets, allowing the same client-side logic to be reused across multiple catalog items that include that variable set. Option A is not correct because updating an sc_task state is a server-side record operation typically handled by Business Rules, Workflow, or Flow Designer, not by a catalog client script.

Option B is not correct because Catalog Client Scripts run on the catalog item form in both the standard platform UI and the Service Portal, not exclusively on the Service Portal. Option D is not correct because Catalog Client Scripts execute on the client side (browser), unlike Catalog Script Includes or Business Rules which run server-side.

Exam trap

CIS-ITSM often tests the misconception that Catalog Client Scripts run server-side or only on Service Portal, when they are actually client-side and run on both UIs.

Practice this question →
62
MCQmedium

A developer has created a Catalog Client Script that runs onchange of a variable named 'hardware_type'. The script needs to clear and repopulate a 'model' variable based on the selected hardware type using AJAX. Which client-side API method is best suited for making this asynchronous server call?

A.GlideRecordSecure
B.g_scratchpad
C.GlideAjax
D.g_form.getReference()
AnswerC

GlideAjax performs asynchronous client-to-server calls from a Catalog Client Script, invoking a Script Include to query the model records and return them without a page reload. This satisfies the requirement to clear and repopulate the 'model' variable onchange of 'hardware_type'.

Why this answer

GlideAjax is the client-side API method designed for making asynchronous server calls from a client script. It allows the client to call a server-side script include without a full page reload, which is ideal for dynamically repopulating a variable based on user input. This is the standard way to perform AJAX calls in ServiceNow.

Exam trap

CIS-ITSM often tests the difference between client-side and server-side APIs; candidates may choose g_form.getReference() thinking it's asynchronous, but it's synchronous and not suitable for AJAX.

How to eliminate wrong answers

Option A is wrong because GlideRecordSecure is a server-side API for database queries, not for client-side AJAX calls. Option B is wrong because g_scratchpad is used to pass data from the server to the client during form load, not for making asynchronous calls. Option D is wrong because g_form.getReference() is a client-side method that retrieves a reference field's record synchronously, which can cause performance issues and is not asynchronous.

Practice this question →
63
MCQmedium

An administrator is configuring a variable where users can select multiple options from a predefined list. Which variable type should be selected?

A.List Collector
B.Single Line Text
C.Select Box
D.Multiple Choice
AnswerA

A List Collector presents a predefined set of options and stores multiple selected values in a single variable, using slushbucket controls to move items between available and selected lists. A simple Choice variable permits only one selection, so it cannot satisfy the multiple-selection requirement.

Why this answer

A List Collector variable type in ServiceNow allows users to select multiple options from a predefined list, moving items between an available list and a selected list. It is specifically designed for multi-select scenarios and stores the selected values as a comma-separated list or in a related list depending on configuration. This makes it the correct choice for selecting multiple options.

Exam trap

CIS-ITSM often tests the difference between single-select and multi-select variable types, and candidates commonly confuse Multiple Choice with List Collector when multiple selections are required.

How to eliminate wrong answers

Option B is wrong because Single Line Text allows free-form text entry, not selection from a predefined list. Option C is wrong because a Select Box allows only a single selection from a dropdown list, not multiple selections. Option D is wrong because Multiple Choice presents radio buttons or a dropdown for a single selection, not multiple selections.

Practice this question →
64
MCQeasy

Which application menu contains the module for creating and managing Catalog Categories?

A.Service Catalog > Administration > Categories
B.System Definition > Catalog Categories
C.Request Management > Categories
D.Self-Service > Category Setup
AnswerA

Catalog Categories are maintained within the Service Catalog application, not the ITSM or platform menus. Navigating to Service Catalog > Administration > Categories exposes the category hierarchy used to organise catalogue items, which is where creation and management of those categories occurs.

Why this answer

In ServiceNow, Catalog Categories are managed from the Service Catalog application's Administration section. The correct path is Service Catalog > Administration > Categories, which opens the Category table where you can create, edit, and organize categories and subcategories for catalog items. This location is consistent with other catalog administration tasks like catalog management and item design.

Exam trap

CIS-ITSM often tests the exact navigation path for administrative tasks, and candidates may confuse the Service Catalog Administration menu with System Definition or Self-Service options.

How to eliminate wrong answers

Option B is wrong because System Definition contains platform-level configuration tables (like tables, dictionary, and UI properties), not catalog-specific categories. Option C is wrong because Request Management deals with request processes and workflows, not catalog category definitions. Option D is wrong because Self-Service is a user-facing portal for end users, not an administrative area for category setup.

Practice this question →
65
MCQmedium

An administrator wants to ensure that a catalog item is only visible to users located in the 'United Kingdom' company. Which feature should be configured?

A.Catalog Client Script evaluating g_user.getClientData('company')
B.User Criteria with the Company condition set to United Kingdom
C.Order Guide Rule Base location filter
D.Location Access List on the sc_cat_item table
AnswerB

User Criteria restrict catalog item visibility by conditions such as company, department or location, so setting the Company condition to United Kingdom limits the item to those users. This is the mechanism that enforces the visibility requirement.

Why this answer

User Criteria is the correct feature to control catalog item visibility based on user attributes such as company, location, department, etc. By creating a User Criteria record with the Company condition set to 'United Kingdom' and associating it with the catalog item, only users in that company will see the item.

Exam trap

The trap is confusing client-side hiding (Catalog Client Scripts) with server-side visibility control (User Criteria); the exam expects knowledge that User Criteria is the correct, secure method for restricting item visibility.

How to eliminate wrong answers

Option A is wrong because Catalog Client Scripts run on the client side and can hide fields or sections, but they are not the proper mechanism for controlling item visibility based on user attributes; they can be bypassed and are not secure. Option C is wrong because Order Guide Rule Base location filter is used within order guides to conditionally include items, not to control visibility of a standalone catalog item. Option D is wrong because there is no 'Location Access List' on the sc_cat_item table; access control is managed via User Criteria and ACLs.

Practice this question →
66
MCQeasy

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

A.Service Catalog > Catalog Items
B.Incident > Open
C.Service Catalog > Requests
D.Request Management > Active Cart
AnswerC

Service Catalog > Requests is the module listing every submitted catalog request organisation-wide, letting administrators track, approve or cancel them. It satisfies the requirement to view and manage all requests across the organisation, unlike category or item configuration views.

Why this answer

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

Exam trap

CIS-ITSM often tests the confusion between catalog item definitions (Catalog Items) and submitted request records (Requests), causing candidates to pick the item management module instead of the request management module.

How to eliminate wrong answers

Option A is wrong because Service Catalog > Catalog Items is where item definitions are created and maintained, not where submitted requests are viewed. Option B is wrong because Incident > Open lists incidents, which are unrelated to catalog requests. Option D is wrong because 'Request Management > Active Cart' is not a standard ServiceNow module for viewing all submitted requests; carts are pre-submission and not a management view.

Practice this question →
67
MCQeasy

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

A.Assignment Group
B.Catalog Definition
C.Catalog Category
D.Knowledge Base
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
68
MCQmedium

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

A.Order Guide UI Policy Mapping
B.Catalog Data Policy Global Template
C.Catalog UI Policy associated with a Variable Set
D.Global Catalog Client Script Collection
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
69
Multi-Selecthard

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

Select 3 answers
A.Database View Item
B.Workflow Template
C.Catalog Item
D.Record Producer
E.Order Guide
AnswersC, D, E

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

Why this answer

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

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

Exam trap

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

Practice this question →
70
MCQhard

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

A.Rebuild the Catalog Item cache
B.Verify the Catalog Item workflow
C.Inspect Catalog UI Policies and Catalog Client Scripts for visibility logic
D.Check the Variable Set order
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
71
Multi-Selectmedium

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

Select 2 answers
A.Single Line Text
B.Label
C.Select Box
D.Container Begin
E.Reference
AnswersC, E

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

Why this answer

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

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

Exam trap

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

Practice this question →
72
MCQhard

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

A.Create three separate catalog items and rely on the user to order all three.
B.Build a Flow Designer flow triggered on the requested item that uses three Create Catalog Task actions with distinct assignments and due dates.
C.Configure a Record Producer that inserts three records into the sc_task table directly.
D.Use a single Create Task workflow activity that creates one task and rely on the assignment group to split it manually.
AnswerB

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

Why this answer

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

Exam trap

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

Practice this question →
73
Multi-Selecthard

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

Select 3 answers
A.Catalog Client Script 'approve()' function
B.Approval - Group workflow activity
C.Approval - User workflow activity
D.Flow Designer 'Ask for Approvals' action
E.Dictionary Policy approval rules
AnswersB, C, D

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

Why this answer

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

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

Exam trap

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

Practice this question →
74
MCQeasy

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

A.To log errors in the system log when the variable is empty
B.To define default database values for the variable
C.To restrict the user role required to view the variable
D.To provide additional instructions or guidance to users filling out the form
AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
75
MCQeasy

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

A.It sets the default inventory stock count to zero.
B.It disables checkout for bulk orders exceeding 10 items.
C.It prevents the item from being added to the shopping cart.
D.It hides the quantity selector on the item form, forcing the quantity to be 1.
AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
Page 1 of 2 · 101 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Service Catalog And Request Management questions.

Start 20-question session