The answer is that the business rule is running twice because the script updates the same record, causing a self-update loop. This occurs when an after business rule executes a `current.update()` or similar operation on the Change Request record that triggered it, which fires the same business rule again synchronously, creating recursion. On the ServiceNow Certified Application Developer CAD exam, this scenario tests your understanding of business rule execution order and the dangers of self-referential updates—a common trap where developers mistakenly think an after rule is safe to modify the triggering record. The key distinction is that the rule is neither scheduled nor async, so each update happens immediately in the same transaction, doubling execution. A useful memory tip: if a business rule updates its own table, expect it to run again—think “self-update equals second fire.”
SNOW-CAD Core Application Development Practice Question
This SNOW-CAD practice question tests your understanding of core application development. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 developer reports that an after business rule on the Change Request table is running twice for each update. The business rule is not scheduled or async. Which 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.
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 script updates the same record, causing a loop
Option C is correct because an after business rule that updates the same record it triggered on will cause the business rule to fire again on the subsequent update, creating a recursive loop. Since the rule is not scheduled or async, each update triggers the rule synchronously, and if the script performs a `current.update()` or similar operation on the same table, it re-fires the same business rule, leading to duplicate execution.
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 business rule is set to run 'On Update' and also 'On Insert'
Why it's wrong here
Incorrect; if it's set to both, it would run once on update, not twice.
✗
The business rule order is too high
Why it's wrong here
Incorrect; order only influences sequence among multiple rules, not double execution.
✓
The business rule script updates the same record, causing a loop
Why this is correct
Correct; the after business rule triggers an update that re-executes the rule, resulting in double execution.
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 business rule exists in two different scoped applications
Why it's wrong here
Incorrect; scoped applications isolate rules; they wouldn't both run on the same record unless the rule is global.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse a business rule running twice due to a loop with other causes like incorrect event conditions or scope duplication, but the core issue is the recursive update within the same rule's script.
Detailed technical explanation
How to think about this question
Under the hood, ServiceNow's business rule engine uses a stack-based execution model where synchronous after business rules are queued and executed sequentially. If a script calls `current.update()` on the same record, it triggers a new database write, which re-evaluates all business rules for that table, including the original rule, causing an infinite loop unless guarded by a condition like `!current.changes()` or a flag. In real-world scenarios, this often manifests as performance degradation or stack overflow errors in the instance logs.
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.
Core Application Development — This question tests Core Application Development — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The business rule script updates the same record, causing a loop — Option C is correct because an after business rule that updates the same record it triggered on will cause the business rule to fire again on the subsequent update, creating a recursive loop. Since the rule is not scheduled or async, each update triggers the rule synchronously, and if the script performs a `current.update()` or similar operation on the same table, it re-fires the same business rule, leading to duplicate execution.
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.