- 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.
Quick Answer
The answer is a Catalog Client Script of type 'onSubmit' that sets the variable mandatory using the `g_form.setMandatory()` method. This is correct because an onSubmit script executes after the user clicks Submit but before the record is saved, allowing it to dynamically override the variable's definition in the catalog item. Even if the variable is not marked mandatory in the item's variable definitions, the script can enforce it at runtime, triggering the 'mandatory but has no value' error when the field is left empty. On the ServiceNow CSA exam, this tests your understanding of client-side scripting versus declarative configuration—a common trap is assuming mandatory settings only come from the variable definition itself. Remember that onSubmit scripts run last in the client-side lifecycle, so they can override earlier settings. Memory tip: "Submit scripts set secrets" — meaning onSubmit can silently enforce mandatory rules that aren't visible in the variable definitions.
SNOW-CSA Service Catalog and Workflows Practice Question
This SNOW-CSA practice question tests your understanding of service catalog and workflows. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
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?
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
A Catalog Client Script of type 'onSubmit' sets the variable mandatory.
Option A is correct because 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.
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.
- ✓
A Catalog Client Script of type 'onSubmit' sets the variable mandatory.
Why this is correct
Client scripts can enforce mandatory before submission.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
A Business Rule on the request table sets the variable mandatory.
Why it's wrong here
Business Rules run server-side after submission, not before.
- ✗
A UI Policy on the record producer makes the variable mandatory.
Why it's wrong here
UI Policies are for forms, not catalog variables.
- ✗
The variable is mandatory in the parent catalog category.
Why it's wrong here
Mandatory is defined per item, not inherited.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume mandatory status is only set in the variable definition or via UI Policies, overlooking that Catalog Client Scripts of type 'onSubmit' can dynamically enforce mandatory validation at submission time.
Detailed technical explanation
How to think about this question
Catalog Client Scripts of type 'onSubmit' execute client-side before the form is submitted to the server. The `g_form.setMandatory()` method dynamically adds the 'mandatory' attribute to a variable, which is then enforced by the client-side validation logic. If the variable is left empty, the system throws the 'mandatory but has no value' error, bypassing the static variable definition. This is a common pattern for conditional mandatory fields, such as requiring a 'reason' field only when a 'change type' is selected.
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.
- →
Service Catalog and Workflows — study guide chapter
Learn the concepts, then practise the questions
- →
Service Catalog and Workflows practice questions
Targeted practice on this topic area only
- →
All SNOW-CSA questions
510 questions across all exam domains
- →
ServiceNow Certified System Administrator CSA study guide
Full concept coverage aligned to exam objectives
- →
SNOW-CSA practice test guide
How to use practice tests most effectively before exam day
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.
Reporting, SLA and Imports practice questions
Practise SNOW-CSA questions linked to Reporting, SLA and Imports.
Self-Service and Automation practice questions
Practise SNOW-CSA questions linked to Self-Service and Automation.
UI, Navigation and Forms practice questions
Practise SNOW-CSA questions linked to UI, Navigation and Forms.
Database Administration and CMDB practice questions
Practise SNOW-CSA questions linked to Database Administration and CMDB.
Service Catalog and Workflows practice questions
Practise SNOW-CSA questions linked to Service Catalog and Workflows.
Application Rules, ACL and Notifications practice questions
Practise SNOW-CSA questions linked to Application Rules, ACL and Notifications.
SNOW-CSA fundamentals practice questions
Practise SNOW-CSA questions linked to SNOW-CSA fundamentals.
SNOW-CSA scenario practice questions
Practise SNOW-CSA questions linked to SNOW-CSA scenario.
SNOW-CSA troubleshooting practice questions
Practise SNOW-CSA questions linked to SNOW-CSA troubleshooting.
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: A Catalog Client Script of type 'onSubmit' sets the variable mandatory. — Option A is correct because 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.
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 →
Last reviewed: Jun 11, 2026
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.
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.
Sign in to join the discussion.