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

Question 1

Which THREE of the following are best practices when writing business rules? (Choose three.)

Accepted Answer

Set the Order field to control execution sequence. Setting the Order field on a business rule controls the sequence in which multiple business rules execute on the same table and event. This is critical when rules have dependencies, ensuring that prerequisite logic (e.g., data validation) runs before subsequent logic (e.g., field updates). Without explicit ordering, execution order is undefined and may vary between instances.

Answer

Use gs.sleep() to wait for other processes

Answer

Use GlideAggregate for updating records

Question 2

Which TWO statements are true about using GlideAggregate in business rules?

Accepted Answer

GlideAggregate can be used to perform SQL-like GROUP BY operations.. GlideAggregate extends GlideRecord and allows performing SQL-like GROUP BY operations on database queries, enabling aggregation of data such as sums, counts, averages, etc. Option C is correct because GlideAggregate can be instantiated and used within a business rule to compute aggregated values from the database, which is a common pattern for server-side calculations.

Answer

GlideAggregate allows adding non-aggregated fields to the result set using addField().

Answer

GlideAggregate automatically orders the results by the aggregated field.

Answer

GlideAggregate can only be used in client scripts.

Question 3

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 4

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 5

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 6

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.. A Business Rule on update with a condition that checks if the record is in 'Closed' state and the days since closed is greater than 30, and then aborts the update if the field is being modified, is the best approach. This enforces the restriction at the database level, regardless of how the update is attempted (UI, API, import). It ensures that the field cannot be updated after the 30-day period.

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 7

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 8

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 a Script Include's function signature changes — for example, a parameter is added, removed, or renamed, or the function is renamed — existing callers in business rules that pass the old arguments will receive undefined values or fail to resolve the method, producing 'undefined' errors. The callers were not updated in lockstep with the signature change, which is the classic post-upgrade breakage pattern.

Answer

The script include was made private.

Answer

The script include's ACLs changed.

Answer

The script include's scope changed.

Question 9

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 10

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.. Option B is correct because ServiceNow Business Rules support 'before', 'after', 'async', and 'display' timing, and the 'before' and 'after' timings specifically execute relative to the database operation (before the record is saved to the database, or after it has been committed). Option E is correct because Business Rules can invoke email notifications, for example by calling gs.eventQueue() or GlideEmailOutbound within the script to send notifications as part of server-side logic. Option A is incorrect because Business Rules run on the server side, not the client side; client-side logic is handled by Client Scripts, UI Policies, and UI Actions. Option C is incorrect because Business Rules can be triggered on insert, update, delete, and query operations, not only updates. Option D is incorrect because Business Rules run synchronously by default; asynchronous execution requires explicitly setting the timing to 'async'.

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 11

Refer to the exhibit. Which scenario most likely caused this error?

Accepted Answer

The Business Rule uses 'previous.sys_id' but the record is new.. When a Business Rule runs on 'insert' or 'update' and references 'previous.sys_id', the 'previous' object is null for new records (since there is no prior version). This causes a 'Cannot read property 'sys_id' of null' error. The error occurs specifically because the script attempts to access a property on an undefined object.

Answer

The Business Rule runs on delete and 'current' is null.

Answer

The Business Rule tries to access a field that doesn't exist.

Answer

The Business Rule is not active.

Question 12

A business rule on the Change Request table needs to update a field on the same record after the record is updated. Which 'When' option should be used?

Accepted Answer

After. 'After' runs after the database operation and is appropriate for updating the same record after the fact. Option A is incorrect because 'Display' runs when the form is displayed, not after the record is updated. Option C is incorrect because 'Async' runs asynchronously, but 'After' is the appropriate synchronous choice for updating after the record is saved. Option D is incorrect because 'Before' runs before the database operation, not after.

Answer

Display

Answer

Async

Answer

Before

Question 13

A developer needs to create a script that runs before a record is inserted, to set a default value. Which business rule 'When' option is appropriate?

Accepted Answer

Before. The 'Before' business rule runs synchronously before the database operation completes, which is exactly when you need to set a default value on the record being inserted. Because it executes pre-save, the value is written as part of the same transaction and is available to any subsequent logic.

Answer

Async

Answer

After

Answer

Display

Question 14

What is the purpose of using the 'Async' option in a business rule?

Accepted Answer

To run the rule in a separate background thread to avoid performance impact.. The 'Async' option in a business rule causes the rule to run asynchronously in a separate background thread, after the database operation completes. This prevents the rule from delaying the user's transaction and avoids performance impact on the user interface. It is used for long-running or resource-intensive logic that does not need to block the user.

Answer

To run the rule immediately after the database operation.

Answer

To run the rule only when the record is viewed.

Answer

To prevent the rule from running on updates.

Question 15

A developer wants to use a script include to reuse logic across multiple business rules. Which two considerations should be made? (Choose two.)

Accepted Answer

Script includes should not have side effects on current record.. Option B is correct because a script include is a reusable library of logic, so it should be designed as a stateless, side-effect-free function that operates on data passed to it rather than mutating the current record (e.g., calling current.update() or setting current.field values) as a hidden consequence of being invoked. Option D is correct because script includes are scope-aware: a script include created in a given application scope is accessible to business rules in that same scope without needing to be marked global, and it only needs the 'Accessible from all scopes' flag when it must be called from a different scope. Option A is wrong because script includes can absolutely call other script includes (via new ClassName() or ClassName.method()) as long as the called include is accessible in the caller's scope. Option C is wrong because making a script include global is not required for same-scope access; it is only needed for cross-scope access, so 'must be global' is an overstatement. Option E is wrong because script includes are not automatically evaluated at server start; they are loaded/instantiated on demand when referenced by a business rule or other server-side script.

Answer

Script includes cannot call other script includes.

Answer

Script includes must be global to be accessible from all scopes.

Answer

Script includes are automatically evaluated at server start.