How should I use these Service Catalog and Workflows practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Service Catalog and Workflows questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Service Catalog and Workflows domain.

SNOW-CSA · topic practice

Service Catalog and Workflows practice questions

Practise ServiceNow Certified System Administrator CSA Service Catalog and Workflows practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Service Catalog and Workflows

Practice 10 questions Browse domain →

What the exam tests

What to know about Service Catalog and Workflows

Service Catalog and Workflows questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Service Catalog and Workflows exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Service Catalog and Workflows questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Service Catalog and Workflows explanation →

A catalog item has a variable of type 'Single Line Text' with a default value. Users report that when they submit the request, the default value is not being used. A catalog client script that runs on submit is setting the variable to empty string. What is the most likely cause?

Trap 1: Variable is mandatory

Mandatory does not affect default value application.

Trap 2: Client script runs after submit cancels default

The script runs during submit, after the default has been applied, so it still overrides it.

Trap 3: Default value is only for display, not submission

Default values are submitted with the request if not changed.

Study all Service Catalog and Workflows common traps →

A
Variable is mandatory
Why wrong: Mandatory does not affect default value application.
B
Client script runs before default value is applied
On submit, client scripts execute before the default value is set to the variable, so the script can override the default.
C
Client script runs after submit cancels default
Why wrong: The script runs during submit, after the default has been applied, so it still overrides it.
D
Default value is only for display, not submission
Why wrong: Default values are submitted with the request if not changed.

Full breakdown with real-world context →

Question 2mediummultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: Configure a notification to inform the user of the approval status.

Notifications do not control approval logic.

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

Business Rules are not designed for approval decisions.

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

This would require manual approval, not automatic.

Study all Service Catalog and Workflows common traps →

A
Configure a notification to inform the user of the approval status.
Why wrong: Notifications do not control approval logic.
B
Set up a Business Rule to approve all requests under $1,000.
Why wrong: Business Rules are not designed for approval decisions.
C
Use a Flow to send an approval request to the manager every time.
Why wrong: This would require manual approval, not automatic.
D
Create an Approval rule with conditions on cost and department budget.
Approval rules can auto-approve based on conditions.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: Set the variable as 'Read only' and rely on data from sys_user…

This does not validate the email.

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

The Email type already validates format; regex is redundant.

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

Unnecessary; the Email type does this automatically.

Study all Service Catalog and Workflows common traps →

A
Set the variable as 'Read only' and rely on data from sys_user table.
Why wrong: This does not validate the email.
B
Add a regular expression in the variable's 'Regex' field.
Why wrong: The Email type already validates format; regex is redundant.
C
Use a 'String' variable and add a client script to check format.
Why wrong: Unnecessary; the Email type does this automatically.
D
Use the 'Email' variable type; it includes validation.
The Email type validates the format upon submission.

Full breakdown with real-world context →

Question 4hardmultiple choice

Read the full Service Catalog and Workflows explanation →

A catalog item uses a 'Catalog Client Script' to hide a variable when another variable is set to 'No'. However, the script is not working. The script is of type 'onChange' and the variable to hide is a 'Single Line Text'. What is the most likely cause?

Trap 1: The variable type 'Single Line Text' does not support hiding.

Any variable type can be hidden via script.

Trap 2: The script is missing a 'g_form.setDisplay()' call.

This is a common cause, but the question asks most likely; Display property is often overlooked.

Trap 3: The script should be of type 'onSubmit' instead of 'onChange'.

onChange is appropriate for reacting to value changes.

Study all Service Catalog and Workflows common traps →

A
The variable type 'Single Line Text' does not support hiding.
Why wrong: Any variable type can be hidden via script.
B
The script is missing a 'g_form.setDisplay()' call.
Why wrong: This is a common cause, but the question asks most likely; Display property is often overlooked.
C
The script should be of type 'onSubmit' instead of 'onChange'.
Why wrong: onChange is appropriate for reacting to value changes.
D
The variable's 'Display' property is set to 'Static' or 'Read only'.
If Display is static, client scripts cannot hide it.

Full breakdown with real-world context →

Question 5mediummultiple choice

Read the full Service Catalog and Workflows explanation →

An administrator needs to create a workflow that sends an email to the approver when a request is approved, and sends a different email when the request is rejected. What is the appropriate workflow component to use for this branching logic?

Trap 1: Use a 'Timer' activity to delay and then check state.

Timer is for delays, not branching.

Trap 2: Use a 'Begin Approval' activity and then a 'Decision' activity.

Begin Approval is not a standard workflow activity.

Trap 3: Use a 'Condition' activity to check the approval state.

A condition could work but is less direct; Approval activity is designed for this.

Study all Service Catalog and Workflows common traps →

A
Use a 'Timer' activity to delay and then check state.
Why wrong: Timer is for delays, not branching.
B
Use a 'Begin Approval' activity and then a 'Decision' activity.
Why wrong: Begin Approval is not a standard workflow activity.
C
Use an 'Approval' activity with two 'Outcome' branches.
Approval activity provides outcomes for approved and rejected.
D
Use a 'Condition' activity to check the approval state.
Why wrong: A condition could work but is less direct; Approval activity is designed for this.

Full breakdown with real-world context →

Question 6easymultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: A Business Rule on the request table sets the variable mandatory.

Business Rules run server-side after submission, not before.

Trap 2: A UI Policy on the record producer makes the variable mandatory.

UI Policies are for forms, not catalog variables.

Trap 3: The variable is mandatory in the parent catalog category.

Mandatory is defined per item, not inherited.

Study all Service Catalog and Workflows common traps →

A
A Catalog Client Script of type 'onSubmit' sets the variable mandatory.
Client scripts can enforce mandatory before submission.
B
A Business Rule on the request table sets the variable mandatory.
Why wrong: Business Rules run server-side after submission, not before.
C
A UI Policy on the record producer makes the variable mandatory.
Why wrong: UI Policies are for forms, not catalog variables.
D
The variable is mandatory in the parent catalog category.
Why wrong: Mandatory is defined per item, not inherited.

Full breakdown with real-world context →

Question 7mediummulti select

Read the full Service Catalog and Workflows explanation →

Which THREE of the following are true about Service Catalog variables? (Choose three.)

Trap 1: All catalog variables are stored in the 'sys_variable' table.

They are stored in 'sc_item_option' and 'sc_item_option_mtom'.

Trap 2: Once created, the order of variables cannot be changed.

Order can be changed at any time.

Study all Service Catalog and Workflows common traps →

A
All catalog variables are stored in the 'sys_variable' table.
Why wrong: They are stored in 'sc_item_option' and 'sc_item_option_mtom'.
B
Once created, the order of variables cannot be changed.
Why wrong: Order can be changed at any time.
C
Variables can have default values that reference other variables.
Default values can be scripted to reference other variables.
D
The variable type determines how the variable is displayed on the form.
Each variable type has a specific UI representation.
E
Variables can be reordered using the 'Order' field in the variable list.
The Order field controls display order.

Full breakdown with real-world context →

Question 8hardmulti select

Read the full Service Catalog and Workflows explanation →

Which TWO of the following are valid ways to trigger a workflow from a catalog item? (Choose two.)

Trap 1: On the catalog item form, go to the 'Workflow' tab and select a…

There is no Workflow tab; the workflow is set in the 'Workflow' field on the item record.

Trap 2: Write a Business Rule on the 'sc_request' table that starts a…

Business rules can start flows or actions but not directly workflows; workflows are legacy.

Trap 3: In the workflow editor, add a 'Execute Workflow' activity pointing…

Workflows are triggered by events, not by an activity in another workflow.

Study all Service Catalog and Workflows common traps →

A
On the catalog item form, go to the 'Workflow' tab and select a workflow.
Why wrong: There is no Workflow tab; the workflow is set in the 'Workflow' field on the item record.
B
Write a Business Rule on the 'sc_request' table that starts a workflow.
Why wrong: Business rules can start flows or actions but not directly workflows; workflows are legacy.
C
Set the 'Workflow' field on the catalog item to the desired workflow.
The Workflow field directly associates a workflow.
D
In the workflow editor, add a 'Execute Workflow' activity pointing to the catalog item.
Why wrong: Workflows are triggered by events, not by an activity in another workflow.
E
Create a Flow in Flow Designer that triggers on 'Record Created' for the 'Request' table.
Flows can be triggered on record creation and can be scoped to catalog items.

Full breakdown with real-world context →

Question 9hardmultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Exhibit

Refer to the exhibit.

```javascript
// Catalog Client Script - onChange on variable 'department'
function onChange(control, oldValue, newValue, isLoading) {
    if (isLoading || newValue == '') { return; }
    if (newValue == 'IT') {
        g_form.addOption('cost_center', 'IT_CC', 'IT Cost Center');
    } else {
        g_form.clearOptions('cost_center');
    }
}
```

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

Client scripts use g_form.

Trap 2: The script needs to call 'g_form.clearOptions()' before adding…

clearOptions is already called in the else branch, but not needed before addOption.

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

Syntax is correct.

Study all Service Catalog and Workflows common traps →

A
The variable 'cost_center' is not a 'Choice' variable type.
addOption only works on choice-type variables.
B
The script is a server-side script and cannot use 'g_form'.
Why wrong: Client scripts use g_form.
C
The script needs to call 'g_form.clearOptions()' before adding options.
Why wrong: clearOptions is already called in the else branch, but not needed before addOption.
D
The method should be 'g_form.addOption()' with different syntax.
Why wrong: Syntax is correct.

Full breakdown with real-world context →

Question 10mediummultiple choice

Read the full Service Catalog and Workflows explanation →

Refer to the exhibit. A workflow for a catalog item has three stages. The 'Run Script' activity sets the assigned_to to the current user (the requester). The approval activity approves by the manager. The 'Create Task' activity creates a catalog task. When the workflow runs, the task is created but is assigned to the requester instead of the fulfillment group. What is the likely cause?

Exhibit

Refer to the exhibit.

```
Workflow: 'New User Onboarding'
- Stage: 'Request Hardware'
  - Activity: 'Run Script' - Script: "current.assigned_to = gs.getUserID();"
- Stage: 'Approval'
  - Activity: 'Approval' - Approver: 'manager'
- Stage: 'Fulfillment'
  - Activity: 'Create Task' - Task type: 'Catalog Task'
```

Trap 1: The task creation activity is configured to assign to the requester…

It might be, but the script is not the cause.

Trap 2: The workflow should have a 'Set Values' activity after the approval…

That would fix it, but the question asks for the cause of the current behavior.

Trap 3: The approval activity reassigned the request to the manager.

Approval does not change the assigned_to.

Study all Service Catalog and Workflows common traps →

A
The task creation activity is configured to assign to the requester by default.
Why wrong: It might be, but the script is not the cause.
B
The 'Run Script' activity sets the assigned_to on the request, but the task creation activity does not copy that value; the task should have its own assignment.
The script modifies the request record, not the task.
C
The workflow should have a 'Set Values' activity after the approval to assign the task.
Why wrong: That would fix it, but the question asks for the cause of the current behavior.
D
The approval activity reassigned the request to the manager.
Why wrong: Approval does not change the assigned_to.

Full breakdown with real-world context →

Question 11mediummultiple choice

Read the full Service Catalog and Workflows explanation →

A large enterprise uses ServiceNow for IT service management. They have a catalog item 'New Employee Setup' that is used by HR to request IT resources for new hires. The catalog item includes variables for employee name, start date, department, and manager. The workflow associated with this item creates a catalog task for the desktop team to prepare a laptop, and another catalog task for the network team to create accounts. Recently, the desktop team has been receiving tasks with incomplete information; the employee name variable is sometimes empty even though it is marked as mandatory. The administrator checked the variable definition and confirmed 'Mandatory' is set to 'true'. The variable is a 'Single Line Text' with no default value. The issue happens intermittently. What course of action should the administrator take to resolve this issue?

Trap 1: Reorder the workflow activities so that the validation occurs…

Order is not the issue; the variable should be validated at submission.

Trap 2: Change the variable type to 'Email' to enforce stronger validation.

The variable is for employee name, not email; also, mandatory is already set.

Trap 3: Set the variable to 'Read only' and populate it from a reference…

This would not fix the mandatory issue and would change the user experience.

Study all Service Catalog and Workflows common traps →

A
Add a workflow script activity that checks if the variable is empty and rejects the request if so.
Server-side validation ensures data integrity even if client-side checks fail.
B
Reorder the workflow activities so that the validation occurs earlier.
Why wrong: Order is not the issue; the variable should be validated at submission.
C
Change the variable type to 'Email' to enforce stronger validation.
Why wrong: The variable is for employee name, not email; also, mandatory is already set.
D
Set the variable to 'Read only' and populate it from a reference field.
Why wrong: This would not fix the mandatory issue and would change the user experience.

Full breakdown with real-world context →

Question 12easymulti select

Read the full Service Catalog and Workflows explanation →

A ServiceNow administrator needs to create a service catalog item that requires the user to select a configuration item (CI) that will be affected by the requested service. The catalog item should also send an email notification to the CI's assigned support group when the request is submitted. Which TWO actions must the administrator take?

Trap 1: Use a variable of type 'CI Selector' to allow selection of a CI.

Incorrect: 'CI Selector' is not a standard variable type; the correct type is 'Reference'.

Trap 2: Set up an email notification on the catalog item itself to send…

Incorrect: Email notifications are not configured directly on catalog items; they are based on events on the requested item record.

Trap 3: Configure the catalog item to automatically populate the 'Assigned…

Incorrect: The catalog item does not automatically populate fields on the CI record; this requires a business rule or flow.

Study all Service Catalog and Workflows common traps →

A
Use a variable of type 'CI Selector' to allow selection of a CI.
Why wrong: Incorrect: 'CI Selector' is not a standard variable type; the correct type is 'Reference'.
B
Create a business rule or flow that adds the CI’s assigned support group to the watch list of the CI record upon catalog item submission.
Correct: Adding the support group to the watch list enables email notifications to them.
C
Add a variable of type 'Reference' pointing to the Configuration Item [cmdb_ci] table.
Correct: A reference variable to cmdb_ci allows the user to select a CI.
D
Set up an email notification on the catalog item itself to send when the request is submitted.
Why wrong: Incorrect: Email notifications are not configured directly on catalog items; they are based on events on the requested item record.
E
Configure the catalog item to automatically populate the 'Assigned group' field on the CI record.
Why wrong: Incorrect: The catalog item does not automatically populate fields on the CI record; this requires a business rule or flow.

Full breakdown with real-world context →

Question 13hardmultiple choice

Read the full Service Catalog and Workflows explanation →

Refer to the exhibit. A ServiceNow administrator created a catalog item that allows users to select a CI via a reference variable named 'ci'. The business rule shown is supposed to update the CI's operational status to 'In Production' when the requested item is closed complete. However, the CI status is not being updated. What is the most likely cause?

Exhibit

Refer to the exhibit.

Business Rule: 'Update CI Status'
Table: Requested Item [sc_req_item]
When: After
Condition: current.state.changesTo(3) // 'Closed Complete'
Script:
gr = new GlideRecord('cmdb_ci');
gr.get(current.variables.ci);
gr.setValue('operational_status', 1); // In Production
gr.update();

Catalog Item Variable 'ci':
Type: Reference
Reference table: Configuration Item [cmdb_ci]

Trap 1: The condition 'current.state.changesTo(3)' is incorrect; it should…

Incorrect: changesTo() is a valid condition that triggers when the state changes to the specified value.

Trap 2: The reference variable 'ci' is not storing the sys_id of the CI; it…

Incorrect: Reference variables store the sys_id, not the display value.

Trap 3: The business rule runs 'Before' instead of 'After', so the state…

Incorrect: The rule is configured to run 'After', not 'Before'.

Study all Service Catalog and Workflows common traps →

A
The condition 'current.state.changesTo(3)' is incorrect; it should check if the state is already 3.
Why wrong: Incorrect: changesTo() is a valid condition that triggers when the state changes to the specified value.
B
The script does not properly retrieve the CI record because current.variables.ci returns the sys_id but may not be accessible directly in an after business rule without using the sc_item_option table.
Correct: Variable values are stored in the sc_item_option table and may not be directly accessible via current.variables in an after business rule. The script should use a GlideRecord query on sc_item_option.
C
The reference variable 'ci' is not storing the sys_id of the CI; it stores the display value.
Why wrong: Incorrect: Reference variables store the sys_id, not the display value.
D
The business rule runs 'Before' instead of 'After', so the state hasn't changed yet.
Why wrong: Incorrect: The rule is configured to run 'After', not 'Before'.

Full breakdown with real-world context →

Question 14mediummultiple choice

Read the full Service Catalog and Workflows explanation →

A large enterprise uses ServiceNow for IT service management. The Service Catalog includes a 'New Employee Setup' bundle that contains multiple catalog items such as 'Create AD Account', 'Assign Laptop', and 'Provision Email'. Each catalog item has its own workflow. Recently, the 'Assign Laptop' catalog item has been failing intermittently. The workflow that runs for this item includes an approval step and several tasks. When the workflow fails, the requested item shows a state of 'Work in Progress' and the workflow context shows an error: 'The workflow could not find the activity named: Approve Laptop'. The workflow has an approval activity named 'Approve Laptop' and it is active. The approval activity is set to 'Run as' the workflow user. The workflow is associated with the catalog item correctly. The failure occurs only when the request is submitted by users who are not in the 'IT' role. What is the most likely cause of the failure?

Trap 1: The 'Approve Laptop' approval activity is deactivated.

Incorrect: The activity is active as stated.

Trap 2: The catalog item is not correctly linked to the workflow.

Incorrect: The workflow is associated correctly.

Trap 3: The approval activity requires a specific approval group that is…

Incorrect: The error is about not finding the activity, not about the approval group.

Study all Service Catalog and Workflows common traps →

A
The 'Approve Laptop' approval activity is deactivated.
Why wrong: Incorrect: The activity is active as stated.
B
The catalog item is not correctly linked to the workflow.
Why wrong: Incorrect: The workflow is associated correctly.
C
The approval activity requires a specific approval group that is not defined.
Why wrong: Incorrect: The error is about not finding the activity, not about the approval group.
D
The workflow user does not have sufficient rights to execute the approval activity when the requester lacks the 'IT' role.
Correct: The workflow runs under the context of the workflow user, and if that user cannot access the activity due to ACLs, the workflow fails.

Full breakdown with real-world context →

Question 15mediumdrag order

Read the full Service Catalog and Workflows explanation →

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Click 'New', then Navigate to System Definition > Business Rules,…

This is incorrect because you cannot click 'New' without first navigating to the Business Rules module; there is no context for the new record.

Trap 2: Navigate to System Definition > Business Rules, then Configure…

This is incorrect because you must click 'New' to open the empty form before you can configure the rule; configuring without an open form is not possible.

Trap 3: Navigate to System Definition > Business Rules, then Click 'New',…

This is incorrect because you should configure the rule (name, table, etc.) before writing the script, as the script logic depends on the table and condition settings.

Study all Service Catalog and Workflows common traps →

A
Navigate to System Definition > Business Rules, then Click 'New', then Configure rule (name, table, condition, order), then Write script, set Active, and Submit
This is the correct order because you must first access the Business Rules module, create a new record, define the rule properties, and finally add the script and save it.
B
Click 'New', then Navigate to System Definition > Business Rules, then Configure rule, then Write script and Submit
Why wrong: This is incorrect because you cannot click 'New' without first navigating to the Business Rules module; there is no context for the new record.
C
Navigate to System Definition > Business Rules, then Configure rule, then Click 'New', then Write script and Submit
Why wrong: This is incorrect because you must click 'New' to open the empty form before you can configure the rule; configuring without an open form is not possible.
D
Navigate to System Definition > Business Rules, then Click 'New', then Write script, then Configure rule and Submit
Why wrong: This is incorrect because you should configure the rule (name, table, etc.) before writing the script, as the script logic depends on the table and condition settings.

Full breakdown with real-world context →

Question 16mediummatching

Read the full Service Catalog and Workflows explanation →

Match each ServiceNow user role to its typical permission.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Full access to all records and configurations

Access to ITIL processes like incident, problem, change management

ServiceNow internal use, not assigned to customers

Basic access to create and view own records

Manage service catalog items and categories

Trap 1: admin: Permission to approve or reject requests

Incorrect — this describes the approver role, not admin. Admin has full access, including approval, but the primary definition is broader.

Trap 2: user: Access to ITIL processes such as incident, problem, and…

Incorrect — this describes the itil role, not user. User role only provides basic self-service access.

Study all Service Catalog and Workflows common traps →

A
admin: Full administrative access to all modules
The admin role provides unrestricted access to all ServiceNow features and settings.
B
itil: Access to ITIL processes such as incident, problem, and change management
The itil role grants permissions to perform ITIL process tasks like managing incidents and changes.
C
user: Basic access to create and view their own records
The user role allows users to create and view only their own tickets and records.
D
approver: Permission to approve or reject requests
The approver role enables users to approve or reject catalog requests and change requests.
E
admin: Permission to approve or reject requests
Why wrong: Incorrect — this describes the approver role, not admin. Admin has full access, including approval, but the primary definition is broader.
F
user: Access to ITIL processes such as incident, problem, and change management
Why wrong: Incorrect — this describes the itil role, not user. User role only provides basic self-service access.

Full breakdown with real-world context →

Question 17easymultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: Workflow stage that sets visibility after submission

Workflows run after submission and cannot alter form visibility during entry.

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

Client scripts can hide fields but are less efficient and may not persist; UI Policy is preferred for visibility conditions.

Trap 3: Variable set with a condition on Department

Variable sets group variables but do not provide conditional visibility for individual variables.

Study all Service Catalog and Workflows common traps →

A
Workflow stage that sets visibility after submission
Why wrong: Workflows run after submission and cannot alter form visibility during entry.
B
Catalog client script on the Cost Center variable's onChange event
Why wrong: Client scripts can hide fields but are less efficient and may not persist; UI Policy is preferred for visibility conditions.
C
Catalog UI policy with a condition on Department
UI Policy directly controls visibility based on conditions and is the standard approach.
D
Variable set with a condition on Department
Why wrong: Variable sets group variables but do not provide conditional visibility for individual variables.

Full breakdown with real-world context →

Question 18mediummultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: The workflow context variable for requested for is missing

Missing context variable would cause a script error, not a silent incorrect assignment.

Trap 2: The workflow is not published

An unpublished workflow would not run at all, so the field would not be set by the activity.

Trap 3: The catalog item variable mapping is incorrectly configured

Variable mapping affects variable values, not the 'Requested for' field directly.

Study all Service Catalog and Workflows common traps →

A
The workflow context variable for requested for is missing
Why wrong: Missing context variable would cause a script error, not a silent incorrect assignment.
B
The workflow is not published
Why wrong: An unpublished workflow would not run at all, so the field would not be set by the activity.
C
The 'Set Requested For' activity is configured with a static user value
This activity can explicitly set the requested for user; if static, it replaces the submitted value.
D
The catalog item variable mapping is incorrectly configured
Why wrong: Variable mapping affects variable values, not the 'Requested for' field directly.

Full breakdown with real-world context →

Question 19hardmultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: The workflow script references a variable that is undefined in that…

An undefined variable would cause a script error in both manual and workflow execution.

Trap 2: The script uses incorrect GlideRecord API methods

If the script works manually, API usage is likely correct.

Trap 3: The workflow is in draft mode

A draft workflow would not execute, so no failure would occur.

Study all Service Catalog and Workflows common traps →

A
The workflow runs with a different security context, causing permission issues
Background scripts run as the user executing them, while workflow scripts may run as system or a designated user with different rights.
B
The workflow script references a variable that is undefined in that context
Why wrong: An undefined variable would cause a script error in both manual and workflow execution.
C
The script uses incorrect GlideRecord API methods
Why wrong: If the script works manually, API usage is likely correct.
D
The workflow is in draft mode
Why wrong: A draft workflow would not execute, so no failure would occur.

Full breakdown with real-world context →

Question 20easymultiple choice

Read the full Service Catalog and Workflows explanation →

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?

Trap 1: Workflow with a 'Set Mandatory' activity

Workflows run after submission and cannot affect form fields during entry.

Trap 2: Variable set with mandatory condition

Variable sets group variables but do not support conditional mandatory settings.

Trap 3: Catalog client script on Country's onChange event

Client scripts can set mandatory, but UI Policy is the recommended approach for such declarative rules.

Study all Service Catalog and Workflows common traps →

A
Catalog UI policy with condition on Country
UI Policy actions include setting mandatory based on conditions, which is clean and efficient.
B
Workflow with a 'Set Mandatory' activity
Why wrong: Workflows run after submission and cannot affect form fields during entry.
C
Variable set with mandatory condition
Why wrong: Variable sets group variables but do not support conditional mandatory settings.
D
Catalog client script on Country's onChange event
Why wrong: Client scripts can set mandatory, but UI Policy is the recommended approach for such declarative rules.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Service Catalog and Workflows sessions

Start a Service Catalog and Workflows only practice session

Every question in these sessions is drawn from the Service Catalog and Workflows domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Service Catalog and Workflows questions →Mixed SNOW-CSA session

Frequently asked questions

What does the SNOW-CSA exam test about Service Catalog and Workflows?: Service Catalog and Workflows questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Service Catalog and Workflows questions in a focused session?: Yes — the session launcher on this page draws every question from the Service Catalog and Workflows domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other SNOW-CSA topics?: Use the topic links above to move to related areas, or go back to the SNOW-CSA question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the SNOW-CSA exam covers. They are not copied from any real exam or dump site.

Service Catalog and Workflows only

10 questions 20 questions 30 questions 50 questions

Mixed SNOW-CSA session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All SNOW-CSA questions Service Catalog and Workflows domain overview SNOW-CSA exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Service Catalog and Workflows practice questions

What to know about Service Catalog and Workflows

Common Service Catalog and Workflows exam traps

Service Catalog and Workflows questions

A catalog item has a variable of type 'Single Line Text' with a default value. Users report that when they submit the request, the default value is not being used. A catalog client script that runs on submit is setting the variable to empty string. What is the most likely cause?

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?

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?

A catalog item uses a 'Catalog Client Script' to hide a variable when another variable is set to 'No'. However, the script is not working. The script is of type 'onChange' and the variable to hide is a 'Single Line Text'. What is the most likely cause?

An administrator needs to create a workflow that sends an email to the approver when a request is approved, and sends a different email when the request is rejected. What is the appropriate workflow component to use for this branching logic?

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?

Which THREE of the following are true about Service Catalog variables? (Choose three.)

Which TWO of the following are valid ways to trigger a workflow from a catalog item? (Choose two.)

Exhibit

Exhibit

Exhibit

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

Match each ServiceNow user role to its typical permission.

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?

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?

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?

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?

Track your progress over time

Start a Service Catalog and Workflows only practice session

Related SNOW-CSA topic practice pages

Reporting, SLA and Imports practice questions

Self-Service and Automation practice questions

UI, Navigation and Forms practice questions

Database Administration and CMDB practice questions