SNOW-CAD Automating application logic with business rules and scripts Practice Test 2 — 15 Questions

Question 1

The business rule above is intended to set the category of an incident based on the correlation_id. However, it is not working as expected. What is the most likely cause?

Accepted Answer

The business rule runs before insert, so the correlation_id field may not have a value yet.. Business rules that run 'before insert' execute before the record is saved to the database. At that point, the `correlation_id` field may not yet have a value if it is not provided by the user or set by another process. The script attempts to read `current.correlation_id` to determine the category, but if the field is empty, the condition fails and the category is never set.

Answer

The script is trying to set a field that is read-only before insert.

Answer

The sys_choice table does not contain the choices for the incident category field.

Answer

The GlideRecord query is incorrectly using 'name' instead of 'table'.

Question 2

Drag and drop the steps to create a Client Script in ServiceNow into the correct order.

Accepted Answer

Navigate to Client Scripts, then click New, then set the Table and Name, then choose the UI Type and Trigger, then write the script, then submit.. The correct order: navigate, create new, set table and name, choose UI type and trigger, then write script and submit.

Answer

Navigate to Client Scripts, then click New, then choose the UI Type and Trigger, then set the Table and Name, then write the script, then submit.

Answer

Navigate to Client Scripts, then click New, then set the Table and Name, then write the script, then choose the UI Type and Trigger, then submit.

Answer

Navigate to Client Scripts, then set the Table and Name, then click New, then choose the UI Type and Trigger, then write the script, then submit.

Question 3

Match each ServiceNow table naming convention to its purpose.

Accepted Answer

sys_: Core system tables for storing configuration and metadata. In ServiceNow, table naming conventions use prefixes to indicate their origin or module. sys_ denotes core system tables, u_ denotes user-created custom tables, and m2m_ denotes many-to-many relationship tables. Common confusions involve swapping these prefixes.

Answer

sys_: User-created custom tables for business-specific data

Answer

u_: Core system tables for storing configuration and metadata

Answer

m2m_: Tables for external data integration (e.g., LDAP)

Question 4

A company needs to prevent updates to a field after a record has been in state 'Closed' for more than 30 days. What is the best approach?

Accepted Answer

Use a Business Rule on update with condition state=Closed and days since closed > 30, and abort action when field is being updated.. It uses a Business Rule on update with condition state=Closed and days since closed > 30, and abort action when the field is being updated. This server-side rule directly prevents any updates to the field after the condition is met. Option A (Business Rule on query) runs on query, not on update, so it does not prevent updates. Option B (UI Policy) is client-side only and can be bypassed by direct web service or scripted updates. Option C (Business Rule when state changes to Closed, set field read-only) only makes the field read-only at the time of closure, but after 30 days it may not be enforced; also read-only is client-side and not a true prevention.

Answer

Use a Business Rule on query to check state and field value.

Answer

Use a UI Policy to set field read-only.

Answer

Use a Business Rule with condition when state changes to Closed, set the field to read-only.

Question 5

A developer writes a Business Rule to calculate a total on an Aggregate field. The rule runs on 'insert' and 'update' on the parent table. However, the total is not updating correctly when child records are deleted. Why?

Accepted Answer

The Business Rule should be on the child table's delete event.. A Business Rule that runs on 'insert' and 'update' on the parent table will not fire when a child record is deleted, because the delete event occurs on the child table, not the parent. To correctly update an aggregate field on the parent when child records are deleted, the Business Rule must be defined on the child table's 'delete' event. This ensures the rule executes when the child record is removed, allowing the aggregate to be recalculated.

Answer

The Business Rule should use 'current' and 'previous' to detect deletion.

Answer

The Business Rule should also run on 'delete'.

Answer

The Business Rule should be a Global Business Rule.

Question 6

A script include is defined as a public static function and is called from multiple business rules. After an upgrade, some business rules start failing with 'undefined' errors. What is the most likely cause?

Accepted Answer

The script include's function signature changed.. If the function signature changed (e.g., parameters or return type), existing calls to the script include would fail with 'undefined' errors. Option A would cause 'not found' errors, not undefined. Option B: ACLs do not affect server-side execution. Option D: scope change could cause access errors or 'not found', not typically 'undefined'.

Answer

The script include was made private.

Answer

The script include's ACLs changed.

Answer

The script include's scope changed.

Question 7

To debug a Business Rule that runs on update, which technique is most efficient?

Accepted Answer

Use the Business Rule debug tool.. The Business Rule debug tool provides a dedicated interface for stepping through business rule execution, inspecting variable values, and identifying issues without modifying code. Options A, C, and D are less efficient: A (breakpoint) and C (Studio debugger) require more setup and are not as streamlined for business rules, while D (gs.log()) requires scrolling through logs and does not offer interactive debugging.

Answer

Add a breakpoint in the script.

Answer

Use the debugger in Studio.

Answer

Insert a gs.log() message.

Question 8

A developer wants to trigger a Business Rule on a child table when a parent record is updated. How can this be achieved?

Accepted Answer

Add a condition on the child table's Business Rule referencing the parent.. A Business Rule on the child table can include a condition that checks whether a related parent record has been updated. This is done by referencing the parent table's fields via dot-walking (e.g., `current.parent_field.changes()`) or by querying the parent record's sys_updated_on field. The Business Rule runs on the child table when a child record is inserted or updated, and the condition evaluates the parent's state, allowing the rule to trigger logic based on parent changes without requiring a direct trigger on the parent table.

Answer

Use a workaround with a scheduled job.

Answer

This is not possible in ServiceNow.

Answer

Use a before query Business Rule on the child table.

Question 9

A Business Rule uses 'current.setAbortAction(true)' to stop a record from being saved. However, the record is still saved under certain conditions. Which scenario could cause this?

Accepted Answer

The Business Rule runs after the database operation.. `current.setAbortAction(true)` must be called in a Business Rule that runs before the database operation (e.g., 'before' or 'before query' order). If the Business Rule runs 'after' the database operation, the record has already been committed to the database, so aborting the action has no effect on the save. The abort flag only prevents the pending database write; once the write is complete, the flag is irrelevant.

Answer

The Business Rule is on a table that is extended from a table with a higher order Business Rule.

Answer

Another Business Rule runs in the same order but sets abort to false.

Answer

The Business Rule has a condition that is not met.

Question 10

Which scripting environment should be used to write a Business Rule that runs on schedule?

Accepted Answer

Scheduled Job. A Scheduled Job is the correct scripting environment for running a Business Rule on a schedule because Business Rules in ServiceNow are event-driven and execute only when a record is inserted, updated, deleted, or queried. To run logic at a specific time or interval, you must use a Scheduled Job, which leverages the system's job scheduler (based on Quartz) to execute a script at defined intervals or cron expressions.

Answer

Business Rule

Answer

Events

Answer

Script Include

Question 11

A Business Rule is designed to send an email notification when a record is assigned to a specific group. The email is sent despite the condition not being met. What is the most likely cause?

Accepted Answer

The condition is written incorrectly.. A Business Rule condition that is syntactically or logically incorrect can cause the condition to always evaluate to true, triggering the email notification even when the intended condition is not met. For example, using an incorrect operator or referencing a field that always evaluates to true (e.g., `current.state == 1` when the field is a string) may cause the condition to be true unexpectedly. In ServiceNow, Business Rules evaluate conditions in JavaScript; if the condition is written incorrectly, it may always return true, causing the action to execute despite the intended condition not being satisfied.

Answer

The Business Rule runs on insert only.

Answer

The email notification is also triggered by a different Business Rule.

Answer

The condition is using a field that is not on the table.

Question 12

A script include has a function that uses the 'GlideRecordSecure' class. When called from a Business Rule in a different scope, it throws a security exception. What is the most likely cause?

Accepted Answer

The script include does not have the 'Accessible from' property set to all scopes.. The 'Accessible from' property on a Script Include controls which scopes can invoke its functions. When this property is not set to 'All scopes', a Business Rule in a different scope cannot call the Script Include, resulting in a security exception. The GlideRecordSecure class itself is accessible across scopes, but the Script Include's access restriction prevents the call.

Answer

The function is not defined as a static function.

Answer

The GlideRecordSecure class is not accessible from other scopes.

Answer

The script include is not marked as public.

Question 13

Which TWO statements are true about ServiceNow Business Rules? (Select TWO)

Accepted Answer

Business Rules can be set to run on 'before' or 'after' the database operation.. Business Rules are server-side scripts that execute when a record is inserted, updated, deleted, or queried. They can be configured to run 'before' the database operation (to modify data before it is saved) or 'after' the operation (to perform additional actions like logging or notifications). This flexibility is a core feature of the ServiceNow platform.

Answer

Business Rules run on the client side.

Answer

Business Rules can only be triggered by updates to a record.

Answer

Business Rules are executed asynchronously by default.

Question 14

Which THREE factors should be considered when designing a Business Rule for optimal performance? (Select THREE)

Accepted Answer

Limit the use of gs.log() statements in production.. Excessive gs.log() statements in production can degrade performance by writing to the system log, which consumes I/O resources and can fill up the database. In ServiceNow, logging should be minimized or removed in production scripts to avoid unnecessary overhead, especially in high-volume Business Rules.

Answer

Avoid using synchronous GlideAjax calls.

Answer

Set the Business Rule to run on 'before' if possible.

Question 15

Which THREE statements are correct about script includes and their usage across scopes? (Select THREE)

Accepted Answer

A script include can be accessed from a Business Rule in a different scope if the script include is defined as a global script include.. Script includes in ServiceNow are isolated by scope by default. To make a script include accessible from a business rule in a different scope, it must be defined as a global script include (i.e., its scope is set to 'Global'). This allows the script include to be referenced and executed from any scope without requiring the global scope prefix.

Answer

Script includes defined as 'public' can be accessed from any scope without restriction.

Answer

To call a script include from another scope, you must use the global scope prefix.