Question 483 of 520

Application Rules, ACL and Notifications →hardMultiple ChoiceObjective-mapped

Fix Recursive Loops: Use current.setValue() Instead of update()

This SNOW-CSA practice question tests your understanding of application rules, acl and notifications. 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 before business rule on the Change Request table is supposed to set the 'risk' field based on the 'impact' and 'urgency' fields. The rule uses the current.update() method. However, when the rule runs, it causes a recursive loop. What is the best solution?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

A
Use current.setValue() instead of current.update().
setValue() modifies the field without triggering another business rule.
B
Use current.update() with a query to avoid recursion.
Why wrong: current.update() always triggers the business rule on the same record.
C
Add a condition to check if the risk field is already set.
Why wrong: This prevents unnecessary updates but does not stop recursion if the field is not set.
D
Set the business rule to run after instead of before.
Why wrong: After update still triggers recursion if update() is called.

Full breakdown with real-world context →

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

✓

Use current.setValue() instead of current.update().

Option A is correct because current.update() triggers the business rule again on the same record, causing a recursive loop. Using current.setValue() only modifies the field in memory without writing to the database, so it does not re-trigger the business rule. This is the standard pattern for avoiding recursion in before business rules when setting field values.

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.

✓
Use current.setValue() instead of current.update().
Why this is correct
setValue() modifies the field without triggering another business rule.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use current.update() with a query to avoid recursion.
Why it's wrong here
current.update() always triggers the business rule on the same record.
✗
Add a condition to check if the risk field is already set.
Why it's wrong here
This prevents unnecessary updates but does not stop recursion if the field is not set.
✗
Set the business rule to run after instead of before.
Why it's wrong here
After update still triggers recursion if update() is called.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think checking a condition or changing the timing (before vs. after) will stop recursion, but the root cause is the use of current.update() which always triggers a new database write and re-evaluation of business rules.

Detailed technical explanation

How to think about this question

In ServiceNow, before business rules execute during the database write operation, and calling current.update() within them forces a separate database write that re-evaluates all business rules on the same table. current.setValue() modifies the GlideRecord object in memory, and the changes are only committed when the original update completes, avoiding recursion. This is a common pattern for setting calculated fields like risk based on impact and urgency without triggering additional rule evaluations.

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-CSA 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.

Related SNOW-CSA practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Reporting, SLA and Imports practice questions

Practise SNOW-CSA questions linked to Reporting, SLA and Imports.

Self-Service and Automation practice questions

Practise SNOW-CSA questions linked to Self-Service and Automation.

UI, Navigation and Forms practice questions

Practise SNOW-CSA questions linked to UI, Navigation and Forms.

Database Administration and CMDB practice questions

Practise SNOW-CSA questions linked to Database Administration and CMDB.

Service Catalog and Workflows practice questions

Practise SNOW-CSA questions linked to Service Catalog and Workflows.

Application Rules, ACL and Notifications practice questions

Practise SNOW-CSA questions linked to Application Rules, ACL and Notifications.

SNOW-CSA fundamentals practice questions

Practise SNOW-CSA questions linked to SNOW-CSA fundamentals.

SNOW-CSA scenario practice questions

Practise SNOW-CSA questions linked to SNOW-CSA scenario.

SNOW-CSA troubleshooting practice questions

Practise SNOW-CSA questions linked to SNOW-CSA troubleshooting.

Practice this exam

Start a free SNOW-CSA practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

SNOW-CSA practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this SNOW-CSA question test?

Application Rules, ACL and Notifications — This question tests Application Rules, ACL and Notifications — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use current.setValue() instead of current.update(). — Option A is correct because current.update() triggers the business rule again on the same record, causing a recursive loop. Using current.setValue() only modifies the field in memory without writing to the database, so it does not re-trigger the business rule. This is the standard pattern for avoiding recursion in before business rules when setting field values.

What should I do if I get this SNOW-CSA 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: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

2 more ways this is tested on SNOW-CSA

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Refer to the exhibit. The business rule is set to run 'before' update. When a user changes the state to 'Resolved' (value 3), the comments field is updated. However, the change does not appear on the form after save. What is the most likely reason?

hard

A.The state condition is incorrect because state 3 is not 'Resolved'.
✓ B.The script uses current.update() causing recursion and rollback.
C.The script should use current.setValue() instead of assignment.
D.The business rule should be 'after' instead of 'before'.

Why B: Option B is correct because calling current.update() inside a 'before' business rule triggers the same business rule again, causing recursion. ServiceNow detects this recursion and rolls back the update to prevent an infinite loop, so the comment field change is not saved. A 'before' business rule should modify fields directly without calling update(), as the system handles the save automatically.

Variation 2. A business rule is set to run on 'before update' on the 'incident' table. The script updates 'current.description' and then calls 'current.update()'. What is the likely outcome?

medium

A.The description is updated and no error occurs.
✓ B.The script causes a recursion error or multiple updates.
C.The script fails silently because current.update() is not allowed in before business rules.
D.The script runs but the description is not updated.

Why B: In ServiceNow, calling `current.update()` inside a 'before update' business rule triggers a recursive loop because the update operation re-invokes the same business rule. The platform detects this recursion and typically throws an error or causes multiple updates, leading to the described outcome. Option B is correct because the script explicitly calls `current.update()`, which is prohibited in before business rules to prevent infinite loops.

Keep practising

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.

Loading comments…

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.