Self-Service and Automation →mediumMultiple ChoiceObjective-mapped

SNOW-CSA Self-Service and Automation Practice Question

Exhibit

Refer to the exhibit. The following is an excerpt from a Flow Designer flow that triggers when a catalog item is submitted:

{
  "trigger": "Catalog Item Submitted",
  "conditions": {
    "catalog_item": "sys_id_of_laptop_request"
  },
  "actions": [
    {
      "type": "Create Record",
      "table": "task",
      "values": {
        "short_description": "{{variables.short_description}}",
        "assignment_group": "{{variables.assignment_group}}"
      }
    },
    {
      "type": "Send Email",
      "to": "{{variables.email}}",
      "subject": "Request Submitted",
      "body": "Your request {{variables.short_description}} has been submitted."
    }
  ]
}

The flow above is not creating the task record. The variables are not being populated. What is the most likely cause?

⚠ Common exam trap

It's easy for candidates to assume the flow is not published or that the trigger conditions are wrong, when in fact the flow is running but failing due to a missing variable definition on the catalog item.

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 catalog item does not have the specified short_description variable.

The flow references a variable named 'short_description' that does not exist on the catalog item. When a flow tries to read a variable that is not defined on the record, the variable resolves to null, causing the 'Create Record' action to fail silently or produce an empty field. This is a common misconfiguration where the variable name in the flow does not match the variable name defined on the catalog item.

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 flow is not yet published.
Why it's wrong here
If not published, the flow wouldn't trigger at all.
✓
The catalog item does not have the specified short_description variable.
Why this is correct
The flow references a variable that doesn't exist, causing the action to fail.
✗
The 'Create Record' action requires a 'number' field.
Why it's wrong here
The 'number' field is auto-populated by the system.
✗
The trigger conditions are incorrectly referencing the catalog item.
Why it's wrong here
The condition looks correct; the issue is within the actions.

Visual reference

Go deeper

SNOW-CSA Self-Service and Automation Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question