SNOW-CSA Application Rules, ACL and Notifications Practice Test 2 — 15 Questions

Question 1

Drag and drop the steps to configure an inbound email action in ServiceNow into the correct order.

Question 2

Match each ServiceNow module to its function.

Question 3

A system administrator needs to prevent users from deleting any records in the 'incident' table. Which method will achieve this most effectively?

Accepted Answer

Create an application ACL on the incident table with the 'delete' operation set to 'no access'. Option C is correct because an 'application' record ACL with the 'delete' operation set to 'no access' explicitly denies delete permissions for all users. Options A and B only affect display or creation. Option D affects updating, not deleting.

Answer

Create a write ACL on the incident table with condition 'false'

Answer

Create a read ACL on the incident table with condition 'false'

Answer

Set the incident table 'Update' access to 'none' in the table configuration

Question 4

A business rule is configured to run 'before' a record is updated. If the business rule sets a field value and then a subsequent 'after' business rule also updates the same field, what will be the final value stored in the database?

Accepted Answer

The value set by the 'after' business rule. In ServiceNow, business rules execute in a defined order: 'before' business rules run first, followed by 'after' business rules. When both a 'before' and an 'after' business rule update the same field, the 'after' business rule executes later in the transaction and its value overwrites the 'before' business rule's value. The final value stored in the database is therefore the one set by the 'after' business rule, because the database write occurs after all business rules have completed.

Answer

Both values are stored in a history field

Answer

The database rejects the second change

Answer

The value set by the 'before' business rule

Question 5

A notification is not sending emails to the intended recipients. The notification's 'Who will receive' tab is set to 'Event creator' and the event is triggered by a business rule. However, the email recipient list is empty. What is the most likely cause?

Accepted Answer

The event was created by a system account, not a real user. When a notification's 'Who will receive' tab is set to 'Event creator' and the event is triggered by a business rule, the system resolves the recipient by looking up the user who triggered the event. If the event was created by a system account (e.g., 'system' or 'guest'), that account has no valid email address, resulting in an empty recipient list. This is the most likely cause because the notification is otherwise correctly configured and active.

Answer

The notification is inactive

Answer

The email template is missing the recipient field

Answer

The system property 'glide.email.smtp.port' is set incorrectly

Question 6

An administrator wants to enforce that when the 'state' field of an incident is set to 'Resolved', the 'resolution_notes' field must be filled. Which approach should be used?

Accepted Answer

Create a UI Policy that sets the 'resolution_notes' field to mandatory when state is 'Resolved'. Option C is correct because a UI Policy can set mandatory on the field based on a condition without requiring server-side coding. Option A requires coding, option B is server-side but less user-friendly, option D doesn't enforce mandatory.

Answer

Create a data policy with a condition on the state field

Answer

Create a data lookup condition on the incident table

Answer

Create a business rule that checks the condition and shows an error message

Question 7

A company has an advanced business rule running on the 'incident' table with condition 'current.state == 2' (In Progress). The business rule creates a new child incident and also updates a field on the parent. However, when a state changes from 1 to 2 via a sys_created_by script, the child incident is created but the parent field is not updated. What is the most likely reason?

Accepted Answer

The business rule runs 'before' and there is an uncaught script error that aborts the update. Option D is correct because if the business rule runs 'before', the update to the parent happens before the database operation, and if there is an error in the script (perhaps due to a glideRecord operation that fails silently), the update may not persist. Option A is less likely because the condition matches. Option B would affect child creation too. Option C would affect all updates, not just the field update.

Answer

The business rule condition is not met

Answer

The child incident creation also fails

Answer

The business rule runs 'after' instead of 'before'

Question 8

A system administrator notices that users in the 'itil' role can see the 'cost' field on the 'cmdb_ci_server' table, but the requirement is to hide it from all except users with the 'cmdb_admin' role. The administrator has already created an ACL with 'read' operation, type 'record', condition 'current.cost' (no script) and granted 'no access' to all roles. However, the field is still visible. What is missing?

Accepted Answer

The ACL type must be 'field' instead of 'record'. Option D is correct because a 'record' ACL controls access to the entire record, but the requirement is to hide a specific field ('cost') from certain roles. To control visibility at the field level, the ACL type must be 'field', not 'record'. A 'record' ACL determines whether a user can see or interact with the whole record, while a 'field' ACL governs access to individual fields. Since the 'cost' field is still visible, the existing 'record' ACL is not applied to the field itself, allowing the 'itil' role to see it via default field-level access.

Answer

The ACL condition should use a script instead of a condition

Answer

The ACL must be set to 'mandatory'

Answer

The user must be removed from the 'itil' role

Question 9

Which of the following best describes the purpose of a 'Script Include' in ServiceNow?

Accepted Answer

To encapsulate reusable server-side logic. A Script Include in ServiceNow is designed to encapsulate reusable server-side logic that can be called from other server-side scripts, such as Business Rules, Scheduled Jobs, or other Script Includes. It promotes code modularity and reusability by defining functions or classes that execute on the server instance, not on the client. Option D correctly identifies this core purpose.

Answer

To run automated actions on a schedule

Answer

To set field values dynamically based on conditions

Answer

To define client-side behavior when a form loads

Question 10

A notification is configured to send an email when a new incident is created. The email template uses the field 'Short Description', but the email shows empty for that field. The template is correct. What is the most likely cause?

Accepted Answer

The 'Short Description' field is not populated at the time the notification is sent. Option D is correct because the notification fires when the incident is created, but the 'Short Description' field may not yet be populated at that exact moment if the record is saved before the field is filled. Notifications are triggered by the database write operation, and if the field is empty at that time, the email template will render it as blank, even though the template itself is correct.

Answer

The notification is not set to fire on create

Answer

The email template has a syntax error

Answer

The 'Short Description' field is read-only on the form

Question 11

A business rule set to run 'async' is supposed to update a large number of child records. The administrator notices that the updates are not being applied consistently. What is the most likely reason?

Accepted Answer

The async queue processes multiple instances simultaneously, causing race conditions. When a business rule is set to run 'async', it executes asynchronously via the system's queue. If the business rule updates a large number of child records, multiple instances of the same async business rule can be processed simultaneously by different queue workers. This concurrency can lead to race conditions, where one instance reads stale data or overwrites changes made by another instance, resulting in inconsistent updates.

Answer

The business rule condition is incorrect

Answer

The system property 'glide.sys.schedulers.max_threads' is set too low

Answer

The business rule is running 'before' instead of 'after'

Question 12

Which TWO of the following are valid ways to control the visibility of a field on a form for specific users?

Accepted Answer

Create a UI Policy that sets the field's 'visible' attribute to false based on user role. Option A is correct because a UI Policy runs on the client side and can set the 'visible' attribute of a field to false based on conditions such as user role. This directly controls the field's visibility on the form for specific users without affecting server-side access.

Answer

Create a Data Policy with a read condition

Answer

Create a Client Script that sets g_form.setVisible() on load

Answer

Create a Business Rule that hides the field

Question 13

Which TWO of the following are best practices when working with ACLs?

Accepted Answer

Ensure ACLs are scoped to the application that needs them. Option B is correct because ACLs should be scoped to the specific application that requires them. This ensures that only the necessary records and fields are accessible, following the principle of least privilege. Overly broad ACLs can expose sensitive data and violate data security requirements.

Answer

Always create a single, broad ACL that covers all needs

Answer

Grant 'read' access to all users on all tables to simplify administration

Answer

Write complex scripts in ACLs to handle all edge cases

Question 14

Which THREE of the following are true regarding Business Rules?

Accepted Answer

They can be used to perform data validation before a record is saved. Option C is correct because Business Rules in ServiceNow are server-side scripts that execute before or after a database operation, and they are commonly used to validate data before the record is saved. By using the 'Before' order, a business rule can check field values and abort the save if validation fails, ensuring data integrity.

Answer

They are executed on the client side to improve performance

Answer

They automatically fire on every record in the database when created

Question 15

A company has a business rule that runs on the Incident table during update. The rule checks if the state is 'In Progress' and sets a field. However, after saving, the field is not being set. Which of the following is the most likely cause?

Accepted Answer

The business rule is set to run after the record updates but another business rule with a higher order reverts the field.. Option B is correct because if a business rule runs after the record updates (i.e., 'When to run' is set to 'After'), and another business rule with a higher order number runs later and reverts the field, the first rule's change will be overwritten. The order of execution is determined by the 'Order' field; lower numbers run first. Since the field is not being set after save, a higher-order 'After' rule is the most likely culprit, as it can undo the change made by the original rule.

Answer

The business rule is using 'setValue' instead of 'setDisplayValue'.

Answer

The business rule has the condition 'Current state changes' unchecked.

Answer

The business rule is set to run on 'display' instead of 'update'.