Question 218 of 520
UI, Navigation and FormshardMultiple ChoiceObjective-mapped

Why a UI Policy Fails: Field-Level Security Hides Condition Field

This SNOW-CSA practice question tests your understanding of ui, navigation and forms. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.

An administrator notices that a UI policy on the Incident form is not firing for a specific user role. The UI policy is set to 'Run script' and has conditions on the 'State' field. The script uses g_form.setValue to set a field. What is the most likely reason the UI policy fails to execute for that role?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 condition uses a field that the role cannot see due to field-level security

Option D is correct because UI policies execute client-side, and if a field used in the condition (e.g., 'State') is hidden from the user's role due to field-level security (FLS), the client-side script cannot read the field's value. This causes the condition to evaluate as false or undefined, preventing the UI policy from firing. The g_form.setValue call in the script would also fail silently if the target field is not visible or accessible to the role.

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.

  • The UI policy is configured to run on the server side

    Why it's wrong here

    UI policies are client-side; they don't run on server.

  • The role does not have read access to the field being set

    Why it's wrong here

    Read access is not required to set a field via script on client.

  • The UI policy is set to 'Run script' but the script has a syntax error

    Why it's wrong here

    Syntax error would affect all users, not just a role.

  • The UI policy condition uses a field that the role cannot see due to field-level security

    Why this is correct

    If the condition depends on a hidden field, the policy may not evaluate correctly.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse field-level security with ACLs or assume that g_form.setValue requires read access, when in fact the issue is that the condition field is invisible to the role, causing the UI policy to never trigger.

Detailed technical explanation

How to think about this question

Field-level security (FLS) in ServiceNow controls visibility and editability of fields per role. When a UI policy condition references a field that is hidden by FLS, the client-side script cannot retrieve its value (g_form.getValue returns undefined), causing the condition to fail. Additionally, g_form.setValue may still execute but will have no visible effect if the target field is also hidden, leading to the appearance that the UI policy did not fire. This behavior is distinct from ACLs, which control server-side access.

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.

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.

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?

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: The UI policy condition uses a field that the role cannot see due to field-level security — Option D is correct because UI policies execute client-side, and if a field used in the condition (e.g., 'State') is hidden from the user's role due to field-level security (FLS), the client-side script cannot read the field's value. This causes the condition to evaluate as false or undefined, preventing the UI policy from firing. The g_form.setValue call in the script would also fail silently if the target field is not visible or accessible to the role.

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.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SNOW-CSA practice questions

Last reviewed: Jul 4, 2026

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.

Loading comments…

Sign in to join the discussion.

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.