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

Question 1

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 2

During a workflow, a catalog item's quantity variable 'qty' must be validated to be between 1 and 10. If the value is outside this range, the request should be rejected with a message. Which approach should the administrator take?

Accepted Answer

Add a 'Before Order' script in the catalog item that validates and aborts if invalid.. The 'Before Order' script runs server-side when the user clicks the 'Order Now' button, allowing the administrator to validate the 'qty' variable and use `gs.addErrorMessage()` followed by `current.abortAction()` to reject the request with a message. This approach ensures the validation occurs at the point of submission, before the request is processed, and provides immediate feedback to the user.

Answer

Create a Catalog Client Script with 'onChange' event to validate and show error.

Answer

Create a UI Policy to set the variable as mandatory and add a condition.

Answer

Set the variable's 'Type' to 'Integer' and add a 'Min' and 'Max' attribute.

Question 3

A catalog item uses a workflow that includes a 'Wait for Condition' activity. The condition checks if a custom table record 'approval_status' equals 'approved'. Requests are not progressing past this activity even though the record is updated. What could be the issue?

Accepted Answer

The 'Check Condition' property of the activity is set to 'After Update', but the record was already updated before the workflow reached this activity.. The 'Wait for Condition' activity's 'Check Condition' property determines when the condition is evaluated. If set to 'After Update', the condition is only checked when the record is updated after the workflow reaches this activity. If the record was already updated before the workflow reached the 'Wait for Condition' activity, the condition will never be re-evaluated, causing the workflow to stall indefinitely.

Answer

The 'Wait for Condition' activity is not in the same application scope as the custom table.

Answer

The user updating the record does not have the 'workflow_admin' role.

Answer

The custom table record is not related to the catalog item.

Question 4

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

Accepted Answer

Variables can be configured as 'Read only' after submission.. Catalog item variables can be configured as 'Read only' after submission. This setting is found in the variable's dictionary record under the 'Read only after submission' checkbox. When enabled, the variable's value becomes non-editable once the requested item (RITM) is submitted, which is useful for preserving audit trails or preventing changes to critical data like asset tags or approval decisions.

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 5

Which THREE of the following are valid workflow activities in a Service Catalog workflow? (Choose three.)

Accepted Answer

Run Script. Run Script is a valid workflow activity in ServiceNow Service Catalog workflows. It allows you to execute a script (JavaScript) during the workflow, enabling custom logic such as updating records, calling APIs, or performing calculations. This activity is part of the standard workflow activities available in the Workflow Editor.

Answer

Approval - Dynamic

Answer

Scrum Task

Question 6

A large enterprise with over 15,000 users reporting to ServiceNow has a catalog item 'Request New Laptop' that is popular. Recently, users have complained that the form takes a long time to load in the Service Portal. The administrator notices that the catalog item has 20 variables, 3 variable sets, and 5 catalog client scripts. Performance metrics show that the 'sc_cat_item' view is slow. Additionally, the 'Before Order' script contains a loop that queries the user's previous requests. Which corrective action should the administrator take to improve performance?

Accepted Answer

Move the heavy script from the 'Before Order' script to a workflow 'Run Script' activity and simplify client scripts.. Simplifying catalog client scripts reduces the JavaScript executed during form rendering in the Service Portal, directly addressing the slow load time. The Before Order script runs at order submission, not during form load, so moving it to a workflow does not improve form load performance. The corrective action that targets the root cause of slow form loading is simplifying client scripts.

Answer

Enable 'Caching' for the catalog item in the 'sys_properties' table.

Answer

Increase the number of Service Portal widgets to distribute the load.

Answer

Remove all variable sets and create individual variables to reduce complexity.

Question 7

A company has a catalog item 'Travel Authorization' with a workflow that requires approval from the user's manager and the finance department if the travel cost is above $1000. The workflow is set up with two 'Approval - User' activities: one for the manager and one for a finance user. However, when a request with cost $1500 is submitted, only the manager approval is triggered; the finance approval is skipped. The workflow has a condition on the finance approval activity that checks 'variable_cost > 1000'. The variable 'cost' is defined as a monetary value and is being passed correctly. What is the most likely cause?

Accepted Answer

The condition on the finance approval activity uses the variable while the workflow is still in the 'default' stage before variable values are committed.. The most likely cause is that the condition on the finance approval activity is evaluated while the workflow is still in the 'default' stage, before the variable values from the catalog item request are committed. In ServiceNow, workflow variables are not populated until the workflow enters the appropriate stage or the variable is explicitly set. Since the condition checks 'variable_cost > 1000' but the variable hasn't been assigned yet, the condition evaluates to false, causing the finance approval to be skipped.

Answer

The 'cost' variable has a default value of 0, so the condition never passes.

Answer

The 'Approval - User' for finance is placed before the manager approval in the workflow.

Answer

The workflow is configured with a 'Starting Condition' that blocks the finance activity.

Question 8

A small business uses ServiceNow for internal services. The catalog item 'New Employee Onboarding' includes a variable set with a variable 'Start Date'. The workflow sends an email notification to HR when the start date is within 7 days of submission. Currently, the notification is sent immediately upon request submission even if the start date is months away. The workflow has a 'Send Event' activity that triggers a notification. How should the administrator fix this?

Accepted Answer

Add a condition on the 'Send Event' activity to only proceed if the 'Start Date' variable is within 7 days of now.. The 'Send Event' activity in a workflow can have a condition that evaluates the 'Start Date' variable against the current date and time. By adding a condition that checks if the start date is within 7 days of now, the workflow will only proceed to send the event (and trigger the notification) when the condition is met, preventing premature notifications.

Answer

Modify the notification record to include a condition on the 'Start Date' field.

Answer

Add a 'Mandatory Condition' on the 'Start Date' variable to require it to be within 7 days.

Answer

Create a business rule on the 'sc_req_item' table that checks the start date and sends the notification.

Question 9

An organization has multiple catalog items that use the same variable set 'Contact Info'. Recently, a change was made to the variable set to add a new variable 'Phone'. However, the existing catalog items that use this variable set do not show the new 'Phone' variable on their forms. The variable set is marked as 'Strictly enforced'? Actually, the variable set is not strictly enforced. The administrator expects the new variable to appear automatically on the items. What should the administrator do?

Accepted Answer

For each catalog item, use the 'Update Variable Set' option to synchronize the changes.. When a variable set is not strictly enforced, changes made to the variable set (such as adding a new variable) are not automatically propagated to catalog items that already use it. The administrator must use the 'Update Variable Set' action on each catalog item to synchronize the item's form with the updated variable set. This action refreshes the item's copy of the variable set variables, making the new 'Phone' variable appear.

Answer

Publish the variable set again from the application publisher.

Answer

Delete the variable set and recreate it as a new one and re-associate all items.

Answer

Set the variable set to 'Strictly enforced' to force the new variable to appear.

Question 10

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 11

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 12

Refer to the exhibit. A user submits a Laptop Request but receives the error shown. The user's session does not have a location set. What is the most likely cause?

Accepted Answer

The catalog item is configured to use a mandatory variable without a default value.. The error indicates that a mandatory variable is missing a value at submission. Since the catalog item is configured with a mandatory variable that has no default value, and the user's session lacks a location, the system cannot auto-populate the variable, causing the submission to fail. This is the most common cause of such errors in Service Catalog flows.

Answer

The user's role does not have access to u_location variable.

Answer

The flow is incorrectly configured to require u_location before submission.

Answer

The variable u_location is missing from the catalog item form.

Question 13

Refer to the exhibit. When a user submits a request for a laptop, the approval is granted by admin even though admin is not the manager. Which configuration allows this?

Accepted Answer

The catalog item's approval rule is set to 'Use approval group' and admin is a member of that group.. The catalog item's approval rule is set to 'Use approval group', which allows any member of the specified approval group to approve the request. Since admin is a member of that group, admin can approve the laptop request even though admin is not the user's manager. This configuration overrides the default manager-based approval logic.

Answer

Admin has the 'approval_admin' role that overrides normal approval constraints.

Answer

The workflow has an approval activity with 'Delegate to group' and admin is the group manager.

Answer

The approval group 'IT Hardware' has admin as a member and approval delegation is enabled.

Question 14

Refer to the exhibit. A ServiceNow administrator configures a catalog item for software installations. The flow logic is as shown. When a user requests 'Adobe Photoshop', the approval goes to Software Approvers instead of IT Management. What is the most likely cause?

Accepted Answer

The condition uses '==' which is case-sensitive; the user typed 'adobe photoshop' in lowercase.. The condition in the flow uses '==' which is case-sensitive in ServiceNow. If the user typed 'adobe photoshop' in lowercase, it will not match the condition expecting 'Adobe Photoshop' (with capital letters), so the approval defaults to the 'Software Approvers' group instead of 'IT Management'. ServiceNow string comparisons with '==' are case-sensitive, unlike the '=' operator which is case-insensitive.

Answer

The variable u_software_name is not being passed to the flow correctly.

Answer

The approval group 'IT Management' is not a valid group.

Answer

The flow is running in an older version that does not support conditions.

Question 15

Refer to the exhibit. A user selects 'Full Tunnel' and sees the info message, but the request is auto-approved. What is the most likely cause?

Accepted Answer

The workflow condition uses the variable value from the request, which may be set to 'Split Tunnel' due to a default.. The most likely cause is option D: The workflow condition uses the variable value from the request, which may be set to 'Split Tunnel' due to a default. When a catalog item variable has a default value, that default is used in the workflow condition if the user's selection is not properly captured or if the condition is evaluated before the variable is updated. In this case, even though the user selects 'Full Tunnel', the workflow condition might be checking the initial default value of 'Split Tunnel', causing the condition to fail and leading to auto-approval. Option A is unlikely because client scripts typically run on load and can set values, but they would not normally override the workflow condition after submission. Option B is incorrect because workflow conditions are evaluated at submission time, after the user selects the variable. Option C is irrelevant because workflow conditions in ServiceNow do not use JavaScript equality operators like '==='.

Answer

The client script runs on load and overrides the workflow condition.

Answer

The workflow condition is evaluated before the user selects the variable value.

Answer

The workflow condition is based on the variable 'u_vpn_type' but the condition is incorrectly configured to use '==' instead of '==='.