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

Question 1

A catalog item 'New Hire Laptop' uses a workflow that creates a catalog task. The task must be assigned to the 'Hardware Fulfillment' group and must be linked to the requested item. Which two configurations are required in the Catalog Task activity to achieve this? (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Set the Requested item field to the current requested item.. To assign the catalog task to a specific group, the Assignment group field must be set. To ensure the task is linked to the requested item, the Requested item field should be set, although the activity often does this automatically. The other options are either not applicable or not required for the stated requirements.

Answer

Set the Short description field to a static value.

Answer

Set the Table field to 'sc_task'.

Answer

Set the Wait for completion check box to true.

Question 2

A catalog item has a workflow that includes a 'Set Values' activity. The activity is configured to set the 'state' field on the requested item to 'Closed Complete' after a catalog task is completed. However, when the catalog task is closed, the requested item's state does not change. What is the most likely cause?

Accepted Answer

The 'Set Values' activity is placed after the catalog task activity, but the workflow is not set to wait for the catalog task to complete before proceeding.. The most likely cause is that the workflow does not wait for the catalog task to complete before executing the Set Values activity. Without the wait, the state change may occur before the task is closed, or the workflow may proceed without the task completion triggering the update. Configuring the Catalog Task activity to wait for completion aligns the timing.

Answer

The workflow is not published; it is still in draft mode.

Answer

The 'Set Values' activity is configured to set the state on the catalog task, not the requested item.

Answer

The 'Set Values' activity cannot modify the state field on a requested item.

Question 3

A catalog item uses a workflow that includes a 'Set Values' activity to update the 'Assigned to' field on the requested item record. The workflow then proceeds to a 'Create Task' activity. After submission, the requested item's 'Assigned to' field remains empty, but the task is created correctly. What is the most likely cause?

Accepted Answer

The 'Set Values' activity is configured to update a different record than the requested item.. The Set Values activity updates fields on a record specified in the activity. If the requested item's 'Assigned to' is empty after the workflow runs, the activity is likely targeting the wrong record or field. Since the task is created, the workflow is executing, so the problem is isolated to the Set Values configuration. Other options involve client-side policies, workflow context, or non-existent mappings.

Answer

The 'Assigned to' field is not included in the workflow's field mapping.

Answer

The 'Assigned to' field on the requested item is read-only due to a UI policy.

Answer

The workflow is not set to run on the requested item but on the catalog task.

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 that creates a catalog task. The administrator notices that the task is created but the 'state' variable on the task is not set to 'approved'. What is the most likely reason for this issue?

Accepted Answer

The 'state' variable is not a field on the catalog task table, so it cannot be set on the task.. The 'state' variable defined on a catalog item is not a field on the catalog task table. Variables are stored separately and are associated with the request, not the task. When a task is created, it does not automatically inherit variable values unless the workflow explicitly copies them. Therefore, setting the variable 'state' does not set the 'state' field on the task. To set a field on the task, the workflow must target the task record and set its actual fields.

Answer

The 'Set Values' activity only sets values on the request, not on the task.

Answer

The 'Set Values' activity must be placed after the 'Task' activity to affect the task.

Answer

The 'Set Values' activity requires a script to set variables, not a simple field selection.

Question 5

A company wants to ensure that when a user submits a catalog item for a new laptop, the request is automatically approved if the cost is under $1,000 and the user's department has sufficient budget. What is the best way to implement this requirement?

Accepted Answer

Create an Approval rule with conditions on cost and department budget.. Approval rules in ServiceNow are specifically designed to automate approval decisions based on conditions like cost and department budget. By creating an Approval rule on the catalog item, you can evaluate the requested cost against a threshold and check the department's budget balance via a condition script or reference to the budget table, enabling automatic approval without manual intervention.

Answer

Configure a notification to inform the user of the approval status.

Answer

Set up a Business Rule to approve all requests under $1,000.

Answer

Use a Flow to send an approval request to the manager every time.

Question 6

A Service Catalog item has a variable that asks for the user's manager's email. The variable type is 'Email'. When the user submits the item, the manager should receive a notification. How should the variable be configured to ensure the email is valid?

Accepted Answer

Use the 'Email' variable type; it includes validation.. The 'Email' variable type in Service Catalog automatically validates that the entered value conforms to a standard email format (e.g., user@domain.com). This built-in validation ensures the manager's email is syntactically correct before the notification is triggered, without requiring additional scripting or regex. Option D is correct because it leverages this native validation, which is the simplest and most reliable method.

Answer

Set the variable as 'Read only' and rely on data from sys_user table.

Answer

Add a regular expression in the variable's 'Regex' field.

Answer

Use a 'String' variable and add a client script to check format.

Question 7

A user complains that when they submit a catalog item, they receive an error: 'The variable is mandatory but has no value.' However, the variable is not marked as mandatory in the item's variable definition. What could be the cause?

Accepted Answer

A Catalog Client Script of type 'onSubmit' sets the variable mandatory.. A Catalog Client Script of type 'onSubmit' can dynamically set a variable as mandatory using the `g_form.setMandatory('variable_name', true)` method. This overrides the variable's definition in the catalog item, causing the 'mandatory but has no value' error even when the variable is not marked mandatory in the item's variable definition.

Answer

A Business Rule on the request table sets the variable mandatory.

Answer

A UI Policy on the record producer makes the variable mandatory.

Answer

The variable is mandatory in the parent catalog category.

Question 8

Refer to the exhibit. A catalog item has a variable 'department' (choice list with values 'IT', 'HR', 'Finance') and a variable 'cost_center' (choice list initially empty). The client script is supposed to add an option to 'cost_center' when 'department' is set to 'IT'. However, when a user selects 'IT', no new option appears. What is the most likely reason?

Accepted Answer

The variable 'cost_center' is not a 'Choice' variable type.. The `g_form.addOption()` method only works on variables of type 'Choice' (or similar select-type variables like 'Select Box'). If 'cost_center' is not a Choice variable, the client script cannot dynamically add options to it, and the method call silently fails or has no effect. In ServiceNow, only choice-based variable types support runtime option manipulation via client-side APIs.

Answer

The script is a server-side script and cannot use 'g_form'.

Answer

The script needs to call 'g_form.clearOptions()' before adding options.

Answer

The method should be 'g_form.addOption()' with different syntax.

Question 9

Drag and drop the steps to create a new Business Rule in ServiceNow into the correct order.

Accepted Answer

Navigate to System Definition > Business Rules, then Click 'New', then Configure rule (name, table, condition, order), then Write script, set Active, and Submit. The correct order starts by navigating to System Definition > Business Rules to access the Business Rules module. Then click 'New' to create a new rule. Next, configure the rule by setting the name, table, condition, and order to define when it runs. After configuration, write the script that contains the logic to execute. Finally, set the rule as active and click Submit to save and enable it. This sequence ensures that the rule is properly defined before writing the script and that all settings are complete before activating.

Answer

Click 'New', then Navigate to System Definition > Business Rules, then Configure rule, then Write script and Submit

Answer

Navigate to System Definition > Business Rules, then Configure rule, then Click 'New', then Write script and Submit

Answer

Navigate to System Definition > Business Rules, then Click 'New', then Write script, then Configure rule and Submit

Question 10

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 11

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 12

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 13

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 14

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 15

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