SNOW-CSA Service Catalog and Workflows Practice Test 5 — 15 Questions

Question 1

Which TWO scenarios would require a Catalog UI Policy instead of a Catalog Client Script?

Accepted Answer

Hiding a variable based on another variable's value. A Catalog UI Policy is the correct choice for hiding a variable based on another variable's value (B) because UI Policies are declarative, server-side-evaluated rules that can automatically set a variable's visibility (visible=false) when a condition on another variable is met, without writing client-side JavaScript. It is also correct for making a variable mandatory only when a condition is met (E), since UI Policies natively support the 'Mandatory' action driven by a condition, which is exactly the conditional-requirement use case they are designed for. In contrast, A (displaying a warning message when a variable is invalid) typically requires a Catalog Client Script with an onChange or onSubmit script using g_form.showFieldMsg or alert, because UI Policies cannot display custom warning messages. C (setting a variable's value from a record producer mapping) is handled by the record producer's variable mapping/script configuration, not a UI Policy. D (making a variable read-only after the catalog item is submitted) is a post-submission behavior on the task/record, not a catalog form UI behavior, so it falls outside Catalog UI Policy scope.

Answer

Displaying a warning message when a variable is invalid

Answer

Setting a variable's value from a record producer mapping

Answer

Making a variable read-only after the catalog item is submitted

Question 2

A company wants to allow users to request software licenses through the service catalog. The request requires approval from the manager and then automatically creates a task for the procurement team. Which configuration option should be used?

Accepted Answer

Catalog Item with Approval and Task. A Catalog Item can be configured with an approval flow (manager approval) and a task creation step for the procurement team, directly fulfilling the requirement. Record Producers create records from catalog requests but lack built-in approval and task generation. Order Guides bundle items but don't handle approvals or tasks. Variable Sets collect data but don't define workflow actions.

Answer

Record Producer

Answer

Order Guide

Answer

Variable Set

Question 3

An order guide contains multiple catalog items. When the order guide is submitted, what is created?

Accepted Answer

One request with multiple requested items. When an order guide is submitted in ServiceNow, it creates a single request (sc_request) containing multiple requested items (sc_req_item), one for each catalog item in the guide. This is because the order guide acts as a container that groups multiple catalog items into one submission, and the system automatically generates a parent request with child requested items to track fulfillment individually.

Answer

One request with one requested item that contains all items

Answer

Multiple requests, one for each item

Answer

A single cart item

Question 4

A workflow on a catalog item has a 'Set Values' activity that sets the variable 'state' to 'approved'. The workflow then proceeds to a 'Task' activity. However, the task is never created. The log shows the workflow completed successfully. What is a possible reason?

Accepted Answer

The condition on the 'Task' activity evaluated to false. The 'Task' activity in a ServiceNow workflow has a condition property that must evaluate to true for the task to be created. If the condition evaluates to false, the workflow engine skips the activity entirely and continues to the next step, logging the workflow as completed successfully without creating the task. This matches the symptom where the 'Set Values' activity runs (setting state to 'approved') but no task appears.

Answer

The 'Set Values' activity failed silently

Answer

The catalog item's 'Run workflow' flag is unchecked

Answer

The workflow is set to run asynchronously and the task is delayed

Question 5

A catalog item uses Flow Designer to send an email notification when the state changes to 'fulfilled'. The flow uses a trigger 'State changed' on the requested item table. However, the email is not sent. The flow logs show the trigger fired. What is the most likely issue?

Accepted Answer

The flow action 'Send Email' is not configured with a valid recipient. The most common reason a flow trigger fires but the email is not sent is that the 'Send Email' action lacks a valid recipient. In Flow Designer, the 'Send Email' action requires a recipient (e.g., user, group, or email address) to be explicitly defined; if the recipient field is empty or references a non-existent variable, the action will execute without sending the email, and no error will be logged in the flow logs.

Answer

The trigger is set to 'State changed' but the state field is not properly referenced

Answer

The flow is set to 'Deactivated'

Answer

The email notification is blocked by an email property

Question 6

Refer to the exhibit. A catalog client script with the above code runs on load of a catalog item. Which statement is true?

Accepted Answer

The script will run on every page load and set the category to 'software'.. The `onLoad` catalog client script runs every time the catalog item form is loaded, and the code `g_form.setValue('category', 'software')` unconditionally sets the category field to 'software' on each load. This overrides any previous value or user input from a prior session, ensuring the field is always set to 'software' when the form renders.

Answer

The category variable will be set to 'software' only if the user does not change it.

Answer

The script will cause an error because onLoad should use g_form.setDisplay.

Answer

The script will only run if the variable 'category' is visible.

Question 7

Refer to the exhibit. A UI policy is defined with the above script condition. Which of the following is correct?

Accepted Answer

The UI policy runs on client-side and makes serial_number mandatory when type is hardware.. UI policies run on the client side (in the browser) and can use script conditions to evaluate field values. In this case, the script condition checks if the 'type' field equals 'hardware', and if true, the UI policy makes the 'serial_number' field mandatory. This is a standard client-side behavior for UI policies.

Answer

The UI policy will only apply if the 'type' field is changed.

Answer

The UI policy must run on server-side to use g_form.

Answer

The script is invalid because UI policies cannot use script conditions.

Question 8

Refer to the exhibit. A workflow includes a 'Run Script' activity with the above configuration. What will happen when the workflow reaches this activity?

Accepted Answer

The script runs and updates the current record's state to pending.. The 'Run Script' activity in a ServiceNow workflow executes the provided script when the workflow reaches that activity. The script uses the 'current' GlideRecord object, which is automatically available in workflow scripts and represents the record that triggered the workflow. The 'current.state = 3' line sets the state field to the value for 'pending' (typically 3 in the standard incident or task table), and 'current.update()' commits this change to the database, so the record's state is updated to pending.

Answer

The script will cause an error because current is not defined in workflow.

Answer

The script runs but current.update() is unnecessary because state is set automatically.

Answer

The script only runs when the workflow is started, not when the activity is reached.

Question 9

Which TWO of the following are valid ways to add variables to a catalog item?

Accepted Answer

Variable Set. Option A, Variable Set, is correct because a variable set is a reusable container of variables that can be attached to a catalog item (via the 'Variable Sets' related list or the 'Add Variable Set' option in the Variable Editor), letting you add multiple variables to the item at once. Option C, Variable Editor, is correct because it is the interface used to create and add individual variables directly to a catalog item's question set. Option B, Catalog Client Script, is not a way to add variables; it only runs client-side JavaScript to control behavior of existing variables (e.g., onChange, onLoad, onSubmit). Option D, Order Guide, is a catalog item type that bundles multiple catalog items into a single ordering flow, not a mechanism for adding variables to an item. Option E, UI Policy, does not create variables; it dynamically makes existing variables mandatory, read-only, or visible based on conditions.

Answer

Catalog Client Script

Answer

Order Guide

Answer

UI Policy

Question 10

A ServiceNow administrator is designing a catalog workflow that requires approval from the user's manager only if the total cost of the request exceeds $500. Which workflow configuration should be used?

Accepted Answer

Add an Approval - User activity with a Condition that checks if the variable 'total_cost' is greater than 500.. The Approval - User activity allows you to specify a single user (the manager) and attach a condition that evaluates the 'total_cost' variable. When the condition is true (total_cost > 500), the approval activity runs; otherwise, it is skipped. This directly implements the requirement for manager approval only when the cost exceeds $500.

Answer

Add an Approval - Group activity and set the 'Approval Group' to 'Manager's Group'.

Answer

Set the variable 'total_cost' as 'Required If' a condition.

Answer

Use an Approval Group activity and add the manager as a member.

Question 11

A company wants to collect the same set of user details (name, email, department) in multiple catalog items. What is the best practice to achieve this?

Accepted Answer

Create a variable set with the required variables and add it to each catalog item.. Variable sets in ServiceNow allow you to define a reusable group of variables (e.g., name, email, department) that can be added to multiple catalog items. This ensures consistency, reduces duplication, and simplifies maintenance because any update to the variable set automatically propagates to all items that use it. Cloning items (Option A) would create separate copies of the variables, leading to maintenance overhead and potential drift.

Answer

Create a single catalog item with all variables and clone it for each item.

Answer

Use UI policies to display the same fields on multiple items.

Answer

Configure the variables on the 'sc_cat_item' table and reference them.

Question 12

Which TWO of the following are true regarding catalog item variables? (Choose two.)

Accepted Answer

Variables can be configured as 'Read only' after submission.. Option C is correct because catalog item variables support a 'Read only' attribute that can be enforced after the item is submitted, preventing users from editing the value once the request is placed. Option E is correct because a variable's Default Value can be set dynamically using a script (e.g., a client script or dynamic default value), allowing values to be computed at form load rather than hard-coded. Option A is incorrect because variables can be referenced in workflows and other server-side logic via the variable name or the question/answer records. Option B is incorrect because display order is controlled by the Order field, not creation sequence. Option D is incorrect because variable sets can share values and variables across sets through the same record context, so they are not strictly independent.

Answer

Variables defined on a catalog item cannot be referenced in workflows.

Answer

Variables are always displayed in the order they were created.

Answer

Variables in a variable set are independent and cannot share values across sets.

Question 13

A ServiceNow administrator is configuring a catalog item that requires end users to provide their department and cost center. The administrator wants the 'Cost Center' variable to appear only when the 'Department' variable is set to 'Finance'. Which ONE configuration would enable this behavior?

Accepted Answer

Create a Variable visibility condition on the 'Cost Center' variable that checks when 'Department' equals 'Finance'.. To make the 'Cost Center' variable appear only when 'Department' is 'Finance', the correct configuration is to create a Variable visibility condition on the 'Cost Center' variable that checks when 'Department' equals 'Finance'. This directly controls the visibility based on the condition. Option A, setting the Order field, only determines the sequence of fields on the form and does not affect visibility.

Answer

Set the 'Cost Center' variable Order field to a value higher than the 'Department' variable.

Answer

Set the 'Cost Center' variable Default value to 'Finance'.

Answer

Set the 'Cost Center' variable Read only field to true.

Answer

Set the 'Cost Center' variable Mandatory field to true.

Question 14

A multinational company has implemented a Service Catalog to streamline IT requests. The catalog item 'New Laptop Request' includes a workflow that routes approvals based on the cost center of the requester. Recently, several requests submitted by employees in the Finance department are stuck in 'Submitted' state without any approval activity. The workflow has a condition that checks the variable 'cost_center' and if it equals 'Finance', the approval is sent to the Finance manager. Other requests from departments like HR and Marketing proceed normally. The administrator has verified that the 'Finance' cost center value is correctly entered on the requests, the users have appropriate roles, and the approval assignments are active. What is the most likely cause of the issue?

Accepted Answer

The workflow condition that triggers the Finance approval stage is not evaluating correctly.. The issue is that the workflow condition checking the 'cost_center' variable for 'Finance' is not evaluating correctly, causing the approval stage to be skipped or not triggered. Since other departments work fine, the workflow logic itself is likely flawed—perhaps due to a data type mismatch (e.g., comparing a string to a different type) or a typo in the condition script. The administrator has verified data entry, roles, and approval assignments, so the root cause is the condition logic in the workflow.

Answer

The approval rule should be changed to auto-approve for Finance.

Answer

The workflow approval timeout is set too short and needs to be increased.

Answer

The catalog item should be reconfigured to not use a workflow.

Question 15

Refer to the exhibit. A catalog task for a software request with cost $6000 is in progress. The flow is waiting at the 'Manager Approval' step. What is the current approval state?

Accepted Answer

Approval is waiting for any member of IT Managers group to approve or reject. The flow is waiting at the 'Manager Approval' step, which is configured to use the 'IT Managers' approval group. In ServiceNow, when an approval is assigned to a group, the approval state shows as 'Waiting for approval' until any member of that group approves or rejects it. Since the task is still in progress and the flow is paused at this step, the current approval state is that it is waiting for any member of the IT Managers group to act.

Answer

Approval has been approved by Jane Smith

Answer

Approval is waiting for John Doe

Answer

Approval has been rejected by Bob Lee