- A
current.state == 'Resolved'
Why wrong: Incorrect; this is true on load even if already resolved, not just on change.
- B
current.state.changesTo('Resolved')
Correct; this specifically checks if state changes to Resolved.
- C
current.state.changesTo('Resolved') && current.operation() == 'update'
Correct; this combines the change check with an operation check to avoid triggers on insert.
- D
current.state.changes()
Why wrong: Incorrect; this triggers on any state change, not just to Resolved.
- E
current.state.changesFrom() != 'Resolved'
Why wrong: Incorrect; this checks if the previous state was not Resolved, but does not check the new state.
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 business rule on the Incident table should send an email notification when the state changes to 'Resolved'. Which two conditions should be checked in the business rule script? (Choose two.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
current.state.changesTo('Resolved')
Option B is correct because the `changesTo()` method in GlideRecord checks if the specified field has changed to a specific value during the current transaction. This is the precise way to detect a state transition to 'Resolved'. Option C is also correct because it adds the `current.operation() == 'update'` condition, which ensures the business rule only fires on update operations, preventing false triggers on insert or delete. Together, these two conditions guarantee the email is sent only when an existing record's state is updated to 'Resolved'.
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.
- ✗
current.state == 'Resolved'
Why it's wrong here
Incorrect; this is true on load even if already resolved, not just on change.
- ✓
current.state.changesTo('Resolved')
Why this is correct
Correct; this specifically checks if state changes to Resolved.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
current.state.changesTo('Resolved') && current.operation() == 'update'
Why this is correct
Correct; this combines the change check with an operation check to avoid triggers on insert.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
current.state.changes()
Why it's wrong here
Incorrect; this triggers on any state change, not just to Resolved.
- ✗
current.state.changesFrom() != 'Resolved'
Why it's wrong here
Incorrect; this checks if the previous state was not Resolved, but does not check the new state.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often pick only option B, forgetting that `changesTo()` can return true on insert if the field is set to that value, so the additional `current.operation() == 'update'` condition is necessary to restrict the rule to updates only, which is the intended behavior for a state transition notification.
Detailed technical explanation
How to think about this question
Under the hood, `changesTo()` compares the previous value stored in the `sys_audit` or the in-memory `_previous` copy of the record against the current value, and returns true only if the field changed to the specified value. The `current.operation()` method returns a string like 'insert', 'update', or 'delete', and is essential for business rules that should only run on updates; without it, a business rule with `changesTo()` could still fire on insert if the field is set during creation, causing unintended emails. In real-world scenarios, failing to include the operation check can lead to duplicate notifications when a record is first created with a state of 'Resolved' via a flow or import set.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Automating application logic with business rules and scripts practice questions
Targeted practice on this topic area only
- →
All SNOW-CAD questions
500 questions across all exam domains
- →
ServiceNow Certified Application Developer CAD study guide
Full concept coverage aligned to exam objectives
- →
SNOW-CAD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SNOW-CAD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Working with Data practice questions
Practise SNOW-CAD questions linked to Working with Data.
Platform Features and Integration practice questions
Practise SNOW-CAD questions linked to Platform Features and Integration.
Integrating and managing application data practice questions
Practise SNOW-CAD questions linked to Integrating and managing application data.
Automating application logic with business rules and scripts practice questions
Practise SNOW-CAD questions linked to Automating application logic with business rules and scripts.
Application development using ServiceNow Studio practice questions
Practise SNOW-CAD questions linked to Application development using ServiceNow Studio.
Creating and customizing tables and data practice questions
Practise SNOW-CAD questions linked to Creating and customizing tables and data.
Designing interfaces and user experiences practice questions
Practise SNOW-CAD questions linked to Designing interfaces and user experiences.
Core Application Development practice questions
Practise SNOW-CAD questions linked to Core Application Development.
User Interface Development practice questions
Practise SNOW-CAD questions linked to User Interface Development.
SNOW-CAD fundamentals practice questions
Practise SNOW-CAD questions linked to SNOW-CAD fundamentals.
SNOW-CAD scenario practice questions
Practise SNOW-CAD questions linked to SNOW-CAD scenario.
SNOW-CAD troubleshooting practice questions
Practise SNOW-CAD questions linked to SNOW-CAD troubleshooting.
Practice this exam
Start a free SNOW-CAD practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SNOW-CAD question test?
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: current.state.changesTo('Resolved') — Option B is correct because the `changesTo()` method in GlideRecord checks if the specified field has changed to a specific value during the current transaction. This is the precise way to detect a state transition to 'Resolved'. Option C is also correct because it adds the `current.operation() == 'update'` condition, which ensures the business rule only fires on update operations, preventing false triggers on insert or delete. Together, these two conditions guarantee the email is sent only when an existing record's state is updated to 'Resolved'.
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 →
Last reviewed: Jun 25, 2026
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.