The answer is that the business rule runs before insert, so the correlation_id field may not have a value yet. This is because a "before insert" business rule executes before the record is saved to the database, meaning any field values that are not explicitly provided by the user or set by a prior process—such as correlation_id—may still be empty when the script runs. On the ServiceNow Certified Application Developer CAD exam, this concept tests your understanding of business rule execution order and field availability, a common trap where candidates assume all fields are populated at the time of a before operation. A key memory tip is "before insert, fields can be absent"—if a field isn’t supplied, it’s null, so always check for values before using them in conditions.
SNOW-CAD Practice Question: Automating application logic with business rules and scripts
This SNOW-CAD practice question tests your understanding of automating application logic with business rules and scripts. 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.
Exhibit
Refer to the exhibit.
Business Rule: 'Set Category on Insert'
Table: [incident]
When to run: Before insert
Condition: true
Script:
(function executeRule(current, previous /*null when async*/) {
var cat = new GlideRecord('sys_choice');
cat.addQuery('name', 'incident');
cat.addQuery('element', 'category');
cat.addQuery('value', current.correlation_id.toString());
cat.query();
if (cat.next()) {
current.category = cat.value;
}
})(current, previous);
The business rule above is intended to set the category of an incident based on the correlation_id. However, it is not working as expected. What is the most likely cause?
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.
Refer to the exhibit.
Business Rule: 'Set Category on Insert'
Table: [incident]
When to run: Before insert
Condition: true
Script:
(function executeRule(current, previous /*null when async*/) {
var cat = new GlideRecord('sys_choice');
cat.addQuery('name', 'incident');
cat.addQuery('element', 'category');
cat.addQuery('value', current.correlation_id.toString());
cat.query();
if (cat.next()) {
current.category = cat.value;
}
})(current, previous);
A
The script is trying to set a field that is read-only before insert.
Why wrong: Category is writable before insert.
B
The business rule runs before insert, so the correlation_id field may not have a value yet.
Before insert, the record is new; correlation_id might be empty if not provided.
C
The sys_choice table does not contain the choices for the incident category field.
Why wrong: It does, choices are stored there.
D
The GlideRecord query is incorrectly using 'name' instead of 'table'.
Why wrong: 'name' is the correct field for table name in sys_choice.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The business rule runs before insert, so the correlation_id field may not have a value yet.
Option B is correct because business rules that run 'before insert' execute before the record is saved to the database. At that point, the `correlation_id` field may not yet have a value if it is not provided by the user or set by another process. The script attempts to read `current.correlation_id` to determine the category, but if the field is empty, the condition fails and the category is never set.
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 script is trying to set a field that is read-only before insert.
Why it's wrong here
Category is writable before insert.
✓
The business rule runs before insert, so the correlation_id field may not have a value yet.
Why this is correct
Before insert, the record is new; correlation_id might be empty if not provided.
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.
✗
The sys_choice table does not contain the choices for the incident category field.
Why it's wrong here
It does, choices are stored there.
✗
The GlideRecord query is incorrectly using 'name' instead of 'table'.
Why it's wrong here
'name' is the correct field for table name in sys_choice.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ServiceNow often tests the misconception that all fields are populated at the time a 'before insert' business rule runs, when in fact only fields explicitly provided in the current operation are available.
Detailed technical explanation
How to think about this question
In ServiceNow, business rules have an order of execution: 'before' rules run during the database operation but before the record is saved, while 'after' rules run after the record is committed. When a 'before insert' rule runs, fields that are not explicitly set in the incoming payload (e.g., from a web service or UI) will be null. The `correlation_id` is often populated by inbound email or REST integrations after the initial insert, so relying on it in a 'before insert' rule will fail. A common fix is to change the business rule to run 'after insert' or to use a condition that checks if `correlation_id` is not empty.
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.
Automating application logic with business rules and scripts — This question tests Automating application logic with business rules and scripts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The business rule runs before insert, so the correlation_id field may not have a value yet. — Option B is correct because business rules that run 'before insert' execute before the record is saved to the database. At that point, the `correlation_id` field may not yet have a value if it is not provided by the user or set by another process. The script attempts to read `current.correlation_id` to determine the category, but if the field is empty, the condition fails and the category is never set.
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.
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 →
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.