The correct approach is to use an onChange client script with g_form.addErrorMessage() or g_form.showFieldMsg(). This works because client scripts execute on the browser side after a field value changes, and these methods display a warning message without interfering with the form’s submission logic—unlike a UI Policy that can set a field mandatory or an onSubmit script that can block save entirely. On the ServiceNow Certified Application Developer exam, this scenario tests your understanding of client-side scripting and the distinction between warning versus blocking behaviors; a common trap is confusing g_form.addErrorMessage() with g_form.submit() or g_form.setMandatory(), which would prevent saving. Remember the key difference: addErrorMessage shows a red banner but still allows the record to be saved, while setMandatory forces a required field check on submit. A useful memory tip is “warn, don’t block”—if the requirement says “warning without blocking,” reach for addErrorMessage in an onChange script.
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 needs to display a warning message to the user when a specific field value changes on a form, but the record should still be savable. Which approach should be used?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create an 'onChange' Client Script using g_form.addErrorMessage() or g_form.showFieldMsg().
Option C is correct because an 'onChange' Client Script runs on the client side when a specific field value changes, allowing the developer to display a warning message using g_form.addErrorMessage() or g_form.showFieldMsg() without preventing the record from being saved. This approach ensures the user sees the warning interactively while still being able to submit the form, which matches the requirement exactly.
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.
✗
Create a UI Policy with a condition and a UI message.
Why it's wrong here
UI Policies can show messages but also affect field states, which is overkill for just a warning.
✗
Create a Business Rule that uses gs.addErrorMessage().
Why it's wrong here
gs.addErrorMessage() runs server-side and returns the message on the next server interaction, not instantly client-side.
✓
Create an 'onChange' Client Script using g_form.addErrorMessage() or g_form.showFieldMsg().
Why this is correct
Client Script 'onChange' can display a message client-side without preventing save.
Related concept
Read the scenario before looking for a memorised answer.
✗
Create a Data Policy for the field and set a warning message.
Why it's wrong here
Data Policies are for enforcing mandatory/read-only, not for displaying warnings.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse client-side warnings with server-side blocking mechanisms, often choosing a Business Rule (Option B) because they think gs.addErrorMessage() can display a warning before save, but it actually runs after the record is committed, making it unsuitable for real-time field change notifications.
Trap categories for this question
Command / output trap
UI Policies can show messages but also affect field states, which is overkill for just a warning.
Detailed technical explanation
How to think about this question
Under the hood, an 'onChange' Client Script uses the GlideForm (g_form) API to interact with the form in the browser, and g_form.showFieldMsg() can display a message next to the field with a specific type (e.g., 'info' or 'warning') without blocking form submission. A subtle behavior is that g_form.addErrorMessage() adds a global error banner that can be dismissed, but it does not prevent saving unless combined with a return false or a submit check; for a pure warning, showFieldMsg() is often preferred because it targets the specific field and does not interfere with the save flow.
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: Create an 'onChange' Client Script using g_form.addErrorMessage() or g_form.showFieldMsg(). — Option C is correct because an 'onChange' Client Script runs on the client side when a specific field value changes, allowing the developer to display a warning message using g_form.addErrorMessage() or g_form.showFieldMsg() without preventing the record from being saved. This approach ensures the user sees the warning interactively while still being able to submit the form, which matches the requirement exactly.
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.