The answer is that the ACL condition lacks parentheses to properly group the state checks, causing JavaScript operator precedence to evaluate the logic incorrectly. This happens because the `&&` operator binds more tightly than `||`, so the condition `gs.hasRole('incident_manager') && current.state == 1 || current.state == 2` is parsed as `(gs.hasRole('incident_manager') && current.state == 1) || current.state == 2`, meaning any user—regardless of role—can delete incidents in state 2, and role-checked users can delete in any state. On the ServiceNow CSA exam, this scenario tests your understanding of how ACL conditions are evaluated as JavaScript expressions, where operator precedence is a common trap that leads to overly permissive access. The fix is to add parentheses: `gs.hasRole('incident_manager') && (current.state == 1 || current.state == 2)`. Remember the mnemonic: "And binds first, or comes last—parentheses make the logic fast."
SNOW-CSA Application Rules, ACL and Notifications Practice Question
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 system administrator needs to allow users with the 'incident_manager' role to delete incidents only if the incident state is 'New' or 'Work in Progress'. They create an ACL with the following conditions: type='record', operation='delete', name='incident', condition: gs.hasRole('incident_manager') && current.state == 1 || current.state == 2. After testing, users with the role can delete incidents in any state. 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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The condition lacks parentheses to group the state checks.
The condition `gs.hasRole('incident_manager') && current.state == 1 || current.state == 2` is evaluated by JavaScript operator precedence, where `&&` binds tighter than `||`. This means it is parsed as `(gs.hasRole('incident_manager') && current.state == 1) || current.state == 2`. Consequently, any user (even without the role) can delete incidents in state 2 (Work in Progress), and users with the role can delete incidents in any state because the role check only applies to state 1. Adding parentheses—`gs.hasRole('incident_manager') && (current.state == 1 || current.state == 2)`—fixes the logic.
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 ACL is set on the 'incident' table but should be on the 'task' table.
Why it's wrong here
The ACL is correctly on the incident table; incident extends task, but delete ACL on incident is appropriate.
✓
The condition lacks parentheses to group the state checks.
Why this is correct
Without parentheses, the OR binds weaker than AND, allowing state 2 to bypass role check.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The ACL should be created using the condition builder instead of script.
Why it's wrong here
The condition builder also allows scripting; the issue is the logic, not the method.
✗
The condition does not check for the 'incident_manager' role.
Why it's wrong here
It does check for the role, but operator precedence causes the logic flaw.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ServiceNow often tests operator precedence in ACL conditions, tricking candidates into overlooking that `&&` binds tighter than `||`, which causes the role check to apply only to the first state condition.
Detailed technical explanation
How to think about this question
In ServiceNow, ACL conditions are evaluated as JavaScript expressions. Operator precedence follows ECMAScript standards: logical AND (`&&`) has higher precedence than logical OR (`||`). This is a common pitfall when combining multiple conditions without explicit parentheses. In real-world scenarios, this bug can lead to unauthorized data access or deletion, as the ACL fails to enforce the intended role-based restriction for certain states.
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 security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
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.
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: The condition lacks parentheses to group the state checks. — The condition `gs.hasRole('incident_manager') && current.state == 1 || current.state == 2` is evaluated by JavaScript operator precedence, where `&&` binds tighter than `||`. This means it is parsed as `(gs.hasRole('incident_manager') && current.state == 1) || current.state == 2`. Consequently, any user (even without the role) can delete incidents in state 2 (Work in Progress), and users with the role can delete incidents in any state because the role check only applies to state 1. Adding parentheses—`gs.hasRole('incident_manager') && (current.state == 1 || current.state == 2)`—fixes the logic.
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: "most likely". 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 →
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. A junior administrator configures the above business rule and ACL. When a user without any role opens an incident with category 'database' and state 1, the priority is set to 1 correctly. However, the user cannot view the incident record. What is the most likely reason?
hard
A.The ACL condition uses sys_id of assignment group, but the field stores display value.
B.The business rule runs before insert, but the ACL check occurs after insert.
✓ C.The ACL requires a role (empty role list means no role requirement? Actually requires role checked, but no roles listed means any authenticated user, but unauthenticated? The user has no role, and condition fails because assignment group mismatch.
D.The business rule order (100) is too low and another rule overrides the priority.
Why C: Option C is correct because the ACL condition checks if the assignment group's sys_id matches a value, but the user has no role and the assignment group field likely stores the display value (group name) rather than the sys_id. This mismatch causes the ACL to deny read access, even though the business rule sets the priority correctly. The empty role list in the ACL means no roles are required, but the condition still fails due to the sys_id vs. display value mismatch.
Last reviewed: Jun 30, 2026
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.
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.
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.