The answer is that the GlideRecord query requires an explicit gr.updateMultiple() or gr.update() call to persist changes. This is because in ServiceNow, after business rules execute after the database commit for the triggering record, meaning any additional GlideRecord operations on other tables are not automatically saved—they exist only in the current transaction scope until you explicitly invoke a persistence method. On the ServiceNow Certified Application Developer CAD exam, this tests your understanding of transaction boundaries and the critical distinction between before and after business rules; a common trap is assuming that setting field values on a GlideRecord object is enough without calling update(). Remember the memory tip: "After the commit, you must submit it"—in after business rules, you always need an explicit update call to commit changes to other tables.
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. 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 creates a business rule on the Incident table that executes a GlideRecord query to update related records. The rule runs on 'after' update and queries the Problem table to set a field. However, the update is not being committed. What is the most likely reason?
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 GlideRecord query requires an explicit gr.updateMultiple() or gr.commit() to persist changes.
In ServiceNow, when a GlideRecord query is used in an 'after' business rule to update records on another table, the changes are not automatically committed. The developer must explicitly call gr.updateMultiple() to persist updates to multiple records, or gr.update() for a single record. Option B correctly identifies this requirement, as the update is not being committed without an explicit method call.
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 developer forgot to use gr.insert() instead of gr.update().
Why it's wrong here
gr.update() is correct for updating existing records.
✓
The GlideRecord query requires an explicit gr.updateMultiple() or gr.commit() to persist changes.
Why this is correct
When updating multiple records, gr.updateMultiple() is needed to commit all changes at once.
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.
✗
After business rules cannot update other tables.
Why it's wrong here
After rules can update any table using GlideRecord.
✗
The query returns more than 100 records, causing a governor limit.
Why it's wrong here
There is no hard limit of 100 records; governor limits are higher.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume GlideRecord updates are automatically committed in any context, but ServiceNow requires explicit update calls in 'after' business rules for cross-table modifications, unlike 'before' rules where changes to the current record are auto-saved.
Detailed technical explanation
How to think about this question
Under the hood, GlideRecord queries in 'after' business rules operate within a database transaction that is not automatically flushed for cross-table updates. The gr.updateMultiple() method is required to batch-commit changes, as the engine treats the query as read-only unless an explicit write operation is called. In real-world scenarios, developers often forget this when updating related records in bulk, leading to silent failures where the script runs without errors but changes are not persisted.
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 GlideRecord query requires an explicit gr.updateMultiple() or gr.commit() to persist changes. — In ServiceNow, when a GlideRecord query is used in an 'after' business rule to update records on another table, the changes are not automatically committed. The developer must explicitly call gr.updateMultiple() to persist updates to multiple records, or gr.update() for a single record. Option B correctly identifies this requirement, as the update is not being committed without an explicit method call.
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.