The answer is to check the Visibility field on the dictionary entry for assignment_group and set it to All if it is currently set to Admin. This is correct because the Quebec release introduced a new Visibility attribute on dictionary records that overrides form layouts and UI Policies; when set to Admin, it hides the field from all non-admin users regardless of roles or other configurations. On the CSA exam, this scenario tests your understanding of dictionary-level visibility controls versus form-level layout or UI Policy logic, and it often appears as a trap where candidates mistakenly check roles or reactivate a UI Policy. The key insight is that a field missing after upgrade due to visibility dictionary field settings is a common Quebec-specific issue, and the fix is not in roles or layouts but in that new Visibility attribute. Memory tip: think of the Visibility field as a master override switch—if it says Admin, no other setting can make the field appear for non-admins.
SNOW-CSA UI, Navigation and Forms Practice Question
This SNOW-CSA practice question tests your understanding of ui, navigation and forms. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 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?
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.
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.
✓
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.
Related concept
Read the scenario before looking for a memorised answer.
✗
Create a UI Policy that sets the 'assignment_group' field visible when the form loads.
Why it's wrong here
This might work but is not the root cause; the 'Visibility' field is the simpler fix.
✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
The 'Visibility' field on a dictionary entry is a Quebec-introduced feature that overrides form layout and UI Policies by controlling whether a field appears on forms for non-admin users. It has three values: 'All' (visible to everyone), 'Admin' (visible only to admins), and 'Same as roles' (follows the Roles field). This setting is checked at form rendering time, making it a powerful tool for hiding sensitive fields without complex UI Policies.
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 security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
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.
UI, Navigation and Forms — This question tests UI, Navigation and Forms — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 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.
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 →
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.
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.