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

Question 1

Match each ServiceNow user role to its typical permission.

Accepted Answer

admin: Full administrative access to all modules. Roles in ServiceNow define user permissions. Admin has full access, ITIL handles ITIL processes, User has basic self-service, Approver can approve requests. Common confusion is mixing admin with approver or user with ITIL.

Answer

admin: Permission to approve or reject requests

Answer

user: Access to ITIL processes such as incident, problem, and change management

Question 2

A catalog item has a variable 'Department' and another 'Cost Center'. The Cost Center should only be visible when Department is 'IT'. Which configuration is most efficient?

Accepted Answer

Catalog UI policy with a condition on Department. A Catalog UI Policy can conditionally show or hide variables on a catalog item based on the value of another variable (e.g., Department = 'IT') without requiring a record to exist or a submission to occur. It runs client-side in real-time as the user fills out the form, making it the most efficient and immediate approach for controlling visibility based on a field value.

Answer

Workflow stage that sets visibility after submission

Answer

Catalog client script on the Cost Center variable's onChange event

Answer

Variable set with a condition on Department

Question 3

A user reports that a catalog item's 'Requested for' field is not being set correctly after submission. The catalog item uses a workflow that includes a 'Set Requested For' activity. What is the most likely cause?

Accepted Answer

The 'Set Requested For' activity is configured with a static user value. The 'Set Requested For' activity in a ServiceNow workflow explicitly overrides the 'Requested for' field on the catalog item. If it is configured with a static user value, it will always set that user regardless of who submitted the request, causing the reported issue. This is the most direct cause because the activity's configuration takes precedence over the default behavior of populating the field with the requester.

Answer

The workflow context variable for requested for is missing

Answer

The workflow is not published

Answer

The catalog item variable mapping is incorrectly configured

Question 4

A catalog item uses a workflow with a 'Run Script' activity that contains a script to update a custom table. The script works correctly when executed manually in the Scripts Background, but fails when invoked by the workflow. What is the most likely reason?

Accepted Answer

The workflow runs with a different security context, causing permission issues. The most likely reason is that the workflow runs under the security context of the workflow engine (typically the 'workflow' user or the system user), not the current user's context. When the script is executed manually in Scripts Background, it runs with the full privileges of the admin user, which may include write access to the custom table. In contrast, the workflow's Run Script activity may lack the necessary ACL permissions (e.g., write or create) on the custom table, causing the GlideRecord update to fail silently or throw an error.

Answer

The workflow script references a variable that is undefined in that context

Answer

The script uses incorrect GlideRecord API methods

Answer

The workflow is in draft mode

Question 5

A catalog item has a variable 'Country' and another 'State'. The State variable should be mandatory only when Country is 'USA'. What is the most efficient way to achieve this?

Accepted Answer

Catalog UI policy with condition on Country. The most efficient way is to use a Catalog UI Policy (Option A). A Catalog UI Policy can set the mandatory attribute of a variable based on a condition on another variable, such as making 'State' mandatory when 'Country' equals 'USA'. This is declarative and requires no scripting. Option B (Workflow with a 'Set Mandatory' activity) acts after submission and cannot make a field mandatory before submission. Option C (Variable set with mandatory condition) is for grouping variables and does not enforce mandatory conditions. Option D (Catalog client script on Country's onChange event) is possible but requires more coding and is less supportable than a UI Policy.

Answer

Workflow with a 'Set Mandatory' activity

Answer

Variable set with mandatory condition

Answer

Catalog client script on Country's onChange event

Question 6

A catalog item is configured to use an order guide. When a user submits the order guide, only the first catalog item in the guide appears. What is the most likely cause?

Accepted Answer

The order guide's 'Delivery method' is set to 'One at a time'. When an order guide's 'Delivery method' is set to 'One at a time', the system processes only the first catalog item and stops, rather than adding all items to the cart. This setting is designed for scenarios where each item must be ordered individually, so submitting the guide results in only the first item appearing.

Answer

The workflow attached to the order guide is incomplete

Answer

The catalog items have mandatory variables that are not filled

Answer

The order guide is in a restricted category

Question 7

A catalog client script is used to populate a variable's value from an external table. The script works in the development instance but fails in production. Which troubleshooting step should be taken first?

Accepted Answer

Verify that the script's 'Run as' and 'Global' flags are set correctly in production. Catalog client scripts run in the browser context, and their behavior depends on the 'Run as' (user impersonation) and 'Global' flags. In production, these flags may differ from development, causing the script to fail silently if it lacks permissions to query the external table or if it is scoped incorrectly. This is the first step to check because it directly affects script execution context and data access.

Answer

Ensure the external table exists in the production instance

Answer

Review the system logs for script errors

Answer

Check if the workflow attached to the catalog item is active

Question 8

A record producer is configured to create a task when a user submits a form from the service portal. The task is created but the variables from the form are not mapped. What is the most likely cause?

Accepted Answer

The 'Variable mapping' section of the record producer is not configured. The record producer's 'Variable mapping' section is responsible for explicitly mapping form variables to fields on the target table. When this section is left unconfigured, the system creates the task record but does not transfer variable values from the service portal form, even if the form is submitted successfully. This is a common oversight because the record producer itself is triggered correctly, but the variable data is not passed without explicit mapping.

Answer

The record producer's mandatory fields are not all filled

Answer

The target table does not have the same fields as the source

Answer

The service portal is not configured to pass variables to the record producer

Question 9

A workflow includes an 'Approval' activity that requires approval from the user's manager. However, the approval is not being assigned to the manager. What should be checked first?

Accepted Answer

The 'Approver' field in the approval activity properties. The 'Approver' field in the approval activity properties defines who receives the approval request. If it is not set to the user's manager (e.g., using the 'Manager' field from the sys_user table or a reference to the user's manager), the approval will not route correctly. This is the most direct and likely cause, so it should be checked first before investigating other potential issues.

Answer

The user's delegation settings in the user profile

Answer

The workflow stage before the approval activity

Answer

The conditions on the approval activity

Question 10

A catalog item uses a 'Variable set' that includes several variables. After updating the variable set, the changes do not appear on the catalog item form. What is the most likely cause?

Accepted Answer

The variable set cache has not been cleared. ServiceNow caches variable set definitions to improve performance. When a variable set is updated, the cache must be cleared (via 'Cache Flush' or by deactivating/reactivating the variable set) before the changes are reflected on the catalog item form. Without clearing the cache, the system continues to serve the stale, cached version of the variable set.

Answer

The variable set is not published

Answer

The catalog item's category has been changed

Answer

The catalog item is shared with a restricted role

Question 11

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. Catalog UI Policies are server-side scripts that run before the form is rendered, making them ideal for conditionally hiding variables based on other variable values. Unlike Catalog Client Scripts, which run client-side and can be bypassed, UI Policies enforce visibility and mandatory rules on the server, ensuring compliance even if JavaScript is disabled.

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 12

Which THREE are valid ways to bring data into a catalog item variable?

Accepted Answer

Lookup select box that references a table. A Lookup Select Box variable type can be configured to reference a table, allowing the user to select a record from that table, which brings data into the variable. This is a standard way to populate a catalog item variable with data from a ServiceNow table, such as selecting a user from the sys_user table.

Answer

Workflow context variable

Answer

Catalog client script on submit

Question 13

Which TWO conditions are necessary for a catalog item to trigger a workflow automatically upon submission?

Accepted Answer

The workflow must be in 'Published' state. A workflow must be in the 'Published' state to be available for execution. Only published workflows can be triggered automatically by a catalog item submission. Option E is correct because the catalog item's 'Workflow' field must be explicitly populated with a reference to a workflow; otherwise, no workflow will be associated with the item, and no automatic trigger will occur.

Answer

The catalog item must be in a category that allows workflow execution

Answer

The workflow must be subscribed to the catalog item

Answer

The workflow must contain a 'Begin' activity

Question 14

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 15

An administrator notices that a catalog client script is not firing when a variable changes. The script is set to 'onChange' and the variable reference is correct. The script uses g_form.setValue to update another variable. However, the other variable does not get updated. What could be the issue?

Accepted Answer

The variable being updated has a catalog client script that clears it. When a catalog client script uses g_form.setValue to update another variable, that action triggers the onChange event for the target variable. If the target variable has its own onChange catalog client script that clears its value, that script will execute after the setValue, effectively overriding the update. This creates a conflict where the first script sets a value, but the second script immediately clears it, resulting in the variable appearing unchanged.

Answer

The other variable's value is protected by a UI policy

Answer

The script is running on the server side

Answer

The script is using g_form.setValue incorrectly for that variable type