The answer is that the data policy condition is invalid and will not execute because dot-walking is not supported in data policy conditions. ServiceNow data policies can only evaluate conditions using direct fields on the target table, such as the 'caller' field itself, not dot-walked references like 'caller.name'. When a condition attempts to traverse a reference field with a dot-walk, the platform treats the entire condition as invalid, meaning no field behavior changes—such as making a field mandatory or read-only—will apply when a user creates or updates an incident with a caller named 'VIP'. On the ServiceNow Certified Application Developer CAD exam, this concept frequently appears as a trap: candidates see a dot-walked condition and assume it will work, but the exam tests your understanding that data policies are restricted to table-level fields, while dot-walking is reserved for ACLs, business rules, and client scripts. A helpful memory tip is "data policies are flat, not deep"—they can only see the surface fields of the table, not the nested values of related records.
SNOW-CAD Working with Data Practice Question
This SNOW-CAD practice question tests your understanding of working with data. 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.
Refer to the exhibit. A developer created this data policy on the incident table. What will be the result when a user creates or updates an incident where the caller's name is 'VIP'?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The condition is invalid because dot-walking is not supported in data policy conditions.
Data policy conditions in ServiceNow do not support dot-walking to reference fields like 'caller.name'. The condition must use a direct field on the table (e.g., 'caller') or a scripted condition. Since the condition is invalid, the data policy will not execute, and no field behavior changes will occur.
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 condition will always evaluate to true regardless of the caller's name.
Why it's wrong here
The condition is invalid and will not evaluate as true; it is effectively ignored.
✗
The short_description field will become mandatory for all incidents.
Why it's wrong here
The condition is invalid, so the mandatory rule does not apply to any records.
✗
The data policy will cause a client-side error.
Why it's wrong here
Data policies with invalid conditions are ignored, they do not throw errors.
✓
The condition is invalid because dot-walking is not supported in data policy conditions.
Why this is correct
Data policies do not support dot-walking in conditions; the condition is ignored.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ServiceNow often tests the misconception that dot-walking is universally supported across all ServiceNow condition builders, when in fact data policy conditions explicitly require direct field references or scripted logic.
Detailed technical explanation
How to think about this question
Data policy conditions are evaluated server-side using the GlideRecord query model, which only supports direct field names or scripted conditions via the 'Advanced' checkbox. Dot-walking (e.g., caller.name) is reserved for client-side scripts or ACL conditions, not data policy conditions. In a real-world scenario, a developer might mistakenly use dot-walking to filter on a related record's attribute, only to find the policy never triggers, leading to unexpected data integrity gaps.
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-CAD 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.
Working with Data — This question tests Working with Data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The condition is invalid because dot-walking is not supported in data policy conditions. — Data policy conditions in ServiceNow do not support dot-walking to reference fields like 'caller.name'. The condition must use a direct field on the table (e.g., 'caller') or a scripted condition. Since the condition is invalid, the data policy will not execute, and no field behavior changes will occur.
What should I do if I get this SNOW-CAD 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-CAD 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-CAD 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.