SNOW-CSA UI, Navigation and Forms Practice Question
A system administrator has created a UI Policy to make several fields mandatory on the incident form when the 'Category' field equals 'Software'. The policy works correctly when creating a new incident: if the user selects 'Software', the fields become mandatory. However, when viewing an existing incident and changing the category to 'Software', the fields do not become mandatory. The administrator verifies that the condition is correctly set to 'Category equals Software' and the action sets mandatory true on the target fields. The UI Policy is active and the order is not relevant. What is the most likely reason for this behavior?
⚠ Common exam trap
It's easy for candidates to assume a UI Policy with a condition will automatically re-evaluate when the condition field changes, but they overlook the separate 'Run on Change' checkbox required for that behavior.
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 UI Policy is set to 'Run on Load' only, not 'Run on Change'.
UI Policies have two execution triggers: 'Run on Load' (fires when the form loads) and 'Run on Change' (fires when a specified field changes). When creating a new incident, the form loads with the condition already evaluated, so 'Run on Load' makes the fields mandatory. However, when editing an existing incident and changing the Category to 'Software', the change event does not re-trigger the policy unless 'Run on Change' is enabled. Without this setting, the policy only applies on initial form load, not on subsequent field modifications.
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 UI Policy condition is checking the wrong field.
Why it's wrong here
The condition is correct as it works on new records; the issue is with the trigger, not the condition.
- ✓
The UI Policy is set to 'Run on Load' only, not 'Run on Change'.
Why this is correct
UI Policies must have 'Run on Change' checked to execute when a field value changes on an existing record.
- ✗
The UI Policy order is too low compared to other policies.
Why it's wrong here
Order affects priority, but policies still execute regardless of order.
- ✗
The UI Policy is inactive.
Why it's wrong here
The policy is active and works on new records, so inactivity is not the issue.
Go deeper
Related to this question
About these practice questions
One of 504 original SNOW-CSA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.