The answer is that the developer used gs.setValue() instead of current.setValue(). This is incorrect because gs.setValue() is not a valid GlideSystem method for modifying record fields; it simply does not exist in the ServiceNow API. The correct method, current.setValue(), directly updates the field on the current GlideRecord object within the business rule scope, so using gs.setValue() results in no change to the short description, even when the condition is met. On the ServiceNow Certified Application Developer CAD exam, this question tests your understanding of GlideRecord vs. GlideSystem methods and the proper context for field manipulation in business rules. A common trap is confusing global GlideSystem methods with record-specific methods, especially when developers are accustomed to using gs methods for other purposes like logging or session data. Remember the memory tip: "current" is the record you're working on, so always use current.setValue() to set a field; gs is for system-level actions, not record edits.
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 writes a business rule to run on 'before' update of the Incident table. The rule sets a short description only if it is empty. However, the short description is never set even when it's empty. 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.
Clue: "never"
Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The developer used gs.setValue() instead of current.setValue().
The correct answer is A because in ServiceNow business rules, `gs.setValue()` is a GlideSystem method that does not exist for setting field values on the current record. The proper method is `current.setValue()`, which directly modifies the field on the current GlideRecord object. Using `gs.setValue()` would result in no change to the short description, even if the condition is met.
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 used gs.setValue() instead of current.setValue().
Why this is correct
gs.setValue() is not a valid method; current.setValue() must be used to set field values in business rules.
Clue confirmation
The clue words "most likely", "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The business rule runs after the database update.
Why it's wrong here
Business rules can run before or after; the issue is not timing but the method used to set the field.
✗
The condition 'short_description IS EMPTY' is evaluated on the old value.
Why it's wrong here
The condition checks the current record's value, which is empty before the update.
✗
The business rule is set to run on insert only.
Why it's wrong here
The rule is set to run on update, as described.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse `gs.setValue()` with a valid method, not realizing that `gs` is a system-level object without record manipulation capabilities, and that `current.setValue()` is the required approach for modifying fields on the current record.
Detailed technical explanation
How to think about this question
In ServiceNow, `current.setValue()` is the correct method to modify fields on the current GlideRecord within a business rule, as it triggers the proper field-level operations and ensures the change is persisted. The `gs` object (GlideSystem) provides utility methods like `gs.addInfoMessage()` or `gs.log()`, but lacks a `setValue()` method for record manipulation. This is a common pitfall for developers transitioning from other platforms where global setter methods might exist.
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 developer used gs.setValue() instead of current.setValue(). — The correct answer is A because in ServiceNow business rules, `gs.setValue()` is a GlideSystem method that does not exist for setting field values on the current record. The proper method is `current.setValue()`, which directly modifies the field on the current GlideRecord object. Using `gs.setValue()` would result in no change to the short description, even if the condition is met.
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", "never". 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.