SNOW-CSA Service Catalog and Workflows Practice Question
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' ```
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?
⚠ Common exam trap
ServiceNow often tests the misconception that setting a field on the request record (via a 'Run Script' activity) will automatically propagate to child records like tasks, when in reality each record type has its own independent assignment logic.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
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 'Run Script' activity sets the `assigned_to` field on the request record itself, but the 'Create Task' activity creates a separate catalog task record. The task creation activity does not automatically inherit the `assigned_to` value from the request; it uses its own assignment configuration, which defaults to the requester if no fulfillment group or specific assignment is defined. This causes the task to be assigned to the requester instead of the intended fulfillment group.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The task creation activity is configured to assign to the requester by default.
Why it's wrong here
It might be, but the script is not the cause.
- ✓
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.
Why this is correct
The script modifies the request record, not the task.
- ✗
The workflow should have a 'Set Values' activity after the approval to assign the task.
Why it's wrong here
That would fix it, but the question asks for the cause of the current behavior.
- ✗
The approval activity reassigned the request to the manager.
Why it's wrong here
Approval does not change the assigned_to.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CSA question from scratch — 504 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CSA practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CSA exam.