SNOW-CSA UI, Navigation and Forms Practice Question
A company recently upgraded their ServiceNow instance from Paris to Quebec. After the upgrade, several users report that the 'Assignment Group' field on the Incident form is missing for users with the 'itil' role. The field is still visible for administrators. The administrator checks the dictionary entry for the 'assignment_group' field and finds that it has no roles set. The form layout for the 'Default view' includes the field. The UI Policy that previously controlled visibility of this field has been deactivated. An audit of the upgrade logs shows no errors related to this field. The administrator suspects that a new feature introduced in Quebec might have affected the field visibility. Which action should the administrator take to restore the field visibility for 'itil' users?
⚠ Common exam trap
The trap here is that candidates may focus on UI Policies or ACLs, overlooking the new Quebec-specific 'Visibility' dictionary field that directly controls field visibility at the metadata level.
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
✓
Check the 'Visibility' field on the dictionary entry for 'assignment_group' and set it to 'All' if it is set to 'Admin'.
In Quebec, a new 'Visibility' field was added to dictionary entries. When set to 'Admin', the field is hidden from non-admin users regardless of form layout or UI Policies. Since the dictionary entry for 'assignment_group' has no roles set but the field is missing for 'itil' users, the administrator should check and set the 'Visibility' field to 'All' to restore visibility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Check the 'Visibility' field on the dictionary entry for 'assignment_group' and set it to 'All' if it is set to 'Admin'.
Why this is correct
The 'Visibility' field on the dictionary can hide fields from non-admin users.
- ✗
Create a UI Policy that sets the 'assignment_group' field visible when the form loads.
Why it's wrong here
Creating a UI Policy to set the field visible is incorrect because the issue stems from a platform-level change in Quebec, likely a new security feature or ACL, preventing the field from rendering for 'itil' users *before* client-side UI Policies execute. UI Policies operate on elements already present on the form's Document Object Model, so they cannot force a field to appear if the server-side rendering has omitted it. This option is tempting as UI Policies are commonly used for dynamic field visibility control, and would be correct if the field was present but conditionally hidden by another active UI Policy or if the requirement was to make a field conditionally visible based on other form data.
- ✗
Add the 'itil' role to the 'Roles' field on the dictionary entry for 'assignment_group'.
Why it's wrong here
Adding roles would restrict the field to those roles, not make it visible to all.
- ✗
Create a new Access Control Rule (ACL) to grant read access to the 'itil' role for the 'assignment_group' field.
Why it's wrong here
ACLs do not affect form visibility.
Go deeper
Related to this question
About these practice questions
This SNOW-CSA question is part of Courseiva's 504-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.