Question 505 of 510
Service Catalog and WorkflowsmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the task is assigned to the requester because the Create Task activity does not inherit the assignment from the request record. When the Run Script activity sets the assigned_to field on the request, it only updates that specific record; the Create Task activity generates a separate catalog task record with its own assignment configuration. Since no fulfillment group or explicit assignment is defined on the task activity, it defaults to the requester, overriding any expectation of inheritance. On the ServiceNow CSA exam, this tests your understanding of how workflow activities operate on distinct records—a common trap is assuming that field values propagate automatically between parent and child records. Remember the key principle: each record manages its own assignments, and the Create Task activity requires its own assignment rules. A useful memory tip is “Tasks are not clones; they need their own assignment bones.”

SNOW-CSA Service Catalog and Workflows Practice Question

This SNOW-CSA practice question tests your understanding of service catalog and workflows. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

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?

Question 1mediummultiple choice
Full 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'
```

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.

Option B is correct because 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.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

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.

    Related concept

    Read the scenario before looking for a memorised answer.

  • 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.

Common exam traps

Common exam trap: answer the scenario, not the keyword

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.

Detailed technical explanation

How to think about this question

In ServiceNow, catalog tasks are independent records with their own assignment fields. The 'Create Task' activity uses a task template or default values from the catalog item definition; if the template does not specify a fulfillment group or assignee, the task defaults to the requester (the user who submitted the request). This behavior is controlled by the 'Assignment group' and 'Assigned to' fields on the task record, which are not automatically populated from the request record's `assigned_to` field. A common real-world scenario is when a catalog item requires a fulfillment group to handle tasks, but the workflow creator forgets to set the task's assignment group in the activity configuration, leading to tasks being assigned to the requester instead.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the SNOW-CSA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SNOW-CSA practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SNOW-CSA practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SNOW-CSA question test?

Service Catalog and Workflows — This question tests Service Catalog and Workflows — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: 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. — Option B is correct because 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.

What should I do if I get this SNOW-CSA question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.