SNOW-CSA Self-Service and Automation Practice Question
Exhibit
Refer to the exhibit.
Business Rule (async) on Incident 'update':
```javascript
(function executeRule(current, previous /*null when async*/) {
if (current.state == 6) { // state 6 = resolved
var gr = new GlideRecord('task');
gr.addQuery('parent', current.sys_id);
gr.addQuery('state', '!=', 3); // 3 = closed complete
gr.query();
while (gr.next()) {
gr.state = 3;
gr.update();
}
}
})(current, previous);
```An administrator wrote a business rule to automatically close all child tasks when an incident is resolved. However, some child tasks are not getting closed. Which of the following is the most likely reason for this issue?
⚠ Common exam trap
Candidates often assume asynchronous business rules are always better for performance, but they forget that asynchronous rules cannot see uncommitted data, leading to missed child record updates when the rule depends on the parent's new state.
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
✓
The business rule is async and may not run correctly if the state change is not committed
When a business rule is asynchronous, it runs after the database transaction that triggered it has been committed. This means there can be a delay between when the incident is resolved and when the rule executes. During that interval, it's possible for the incident state to be changed again or for new child tasks to be created. If the incident state is no longer "Resolved" when the async rule runs, the condition in the script may prevent child tasks from being closed. Additionally, any child tasks created after the rule runs will remain open. A synchronous business rule would execute within the same transaction, ensuring that all existing child tasks are closed immediately and eliminating such timing issues.
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 'parent' field does not exist on the task table
Why it's wrong here
'parent' exists on task table as a reference to the parent record.
- ✓
The business rule is async and may not run correctly if the state change is not committed
Why this is correct
Async business rules run after the record update, but the condition might be evaluated before the commit in some cases, causing issues.
- ✗
The business rule should be synchronous to affect child records
Why it's wrong here
Synchronous could work but async is also fine; the issue is the condition evaluation.
- ✗
The GlideRecord query syntax is incorrect
Why it's wrong here
The query syntax is correct.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CSA question from scratch — 504 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CSA 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-CSA exam.