SNOW-CAD Practice Test 13 — 15 Questions

Question 1

A business rule on the Task table uses 'current.assignment_group' in a condition. After cloning the application, the business rule fails with 'undefined' error for the assignment_group field. What is the most likely cause?

Accepted Answer

The field was renamed in the cloned instance.. Option D is correct because cloning an application copies the business rule as-is, but if the assignment_group field was renamed in the cloned instance (e.g., from 'assignment_group' to 'assignment_group_new'), the condition referencing 'current.assignment_group' will fail with an 'undefined' error. The business rule still runs, but the field name no longer matches the database column, causing the script to reference a non-existent property on the GlideRecord object.

Answer

The assignment_group field does not exist on the Task table.

Answer

The script include that defines the field is missing.

Answer

The clone process incorrectly copies business rules.

Question 2

In a large enterprise environment, the ServiceNow instance is heavily customized. A business rule on the Change Request [change_request] table runs on after update to initiate a complex workflow involving multiple approvals and updates to Configuration Items (CIs). Recently, the IT operations team noticed that the workflow fails to start for many change requests. The system logs show the error: "Business rule script error: Cannot read property 'sys_id' of null". The developer inspects the business rule script and sees the following code snippet:
var task = new GlideRecord('task');
task.get(current.sys_id);
var relatedCI = task.cmdb_ci;
// The rest of the script uses relatedCI to update the CI's status.
The developer knows that change requests are not stored in the task table; they are in change_request. However, the script was written by a previous developer and has been working for months. The developer must fix the script to ensure the workflow starts correctly. Which action should the developer take?

Accepted Answer

Use current.cmdb_ci directly. Option C is best because current is already the change request record, so current.cmdb_ci is directly available. Option A would work but adds unnecessary database query. Option B would prevent the error but not fix the root cause; the script would still fail to get the CI if the record is not in task. Option D would hide the error but not fix the logic.

Answer

Wrap the script in a try-catch block and log the error then return

Answer

Change GlideRecord('task') to GlideRecord('change_request')

Answer

Add a check if (task.isValidRecord()) before accessing cmdb_ci

Question 3

Refer to the exhibit. The Business Rule is set to run on before update. When a record's category is changed to 'hardware', the assignment group is updated correctly. However, when a record is inserted with category 'hardware', the assignment group is not set. Why?

Accepted Answer

The condition 'current.category.changes()' returns false on insert.. Option B is correct. On insert, 'current.category.changes()' returns false because there is no previous value. Option A is incorrect because the rule may run on insert but condition fails. Option C is incorrect because 'before' rule runs before save. Option D is incorrect because setValue works on insert.

Answer

The Business Rule does not run on insert.

Answer

The Business Rule runs after the database operation.

Answer

The setValue method does not work on insert.

Question 4

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. Option B is correct because 'Before' runs before the database insert, allowing default values to be set. Option A is incorrect because 'After' runs after the record is already saved. Option C is incorrect because 'Async' runs later. Option D is incorrect because 'Display' runs on form display.

Answer

Async

Answer

After

Answer

Display

Question 5

A global business rule that runs on after query on the Task table is causing performance degradation. The rule modifies the query condition for all task records. The developer needs to optimize the rule without changing its functionality. Which approach is best?

Accepted Answer

Use glideRecord.addEncodedQuery() instead of addQuery(). Option D is correct because using `glideRecord.addEncodedQuery()` allows the business rule to directly apply a pre-encoded query string to the GlideRecord object, which is more efficient than using multiple `addQuery()` calls. This reduces the overhead of parsing individual conditions and improves performance when modifying query conditions on the Task table, without altering the rule's functionality.

Answer

Move the script to a condition builder script include

Answer

Convert the business rule to a script action in a flow designer

Answer

Make the business rule asynchronous

Question 6

A mid-sized company heavily relies on ServiceNow for incident management. They have a business rule that runs before insert on the Incident table. The rule dynamically sets the assignment group based on the category of the incident and the location of the caller. To determine the correct group, the script performs a GlideRecord query against a custom table called "u_group_mapping", which contains approximately 5000 records mapping category-location pairs to groups. During peak business hours, when many incidents are created simultaneously, the business rule causes significant delays and occasional timeouts, impacting user experience. The development team has been tasked with optimizing this business rule without changing its functionality. The current script structure is roughly:
(function executeRule(current, previous) {
    var gr = new GlideRecord('u_group_mapping');
    gr.addQuery('category', current.category);
    gr.addQuery('location', current.caller_id.location);
    gr.query();
    if (gr.next()) {
        current.assignment_group = gr.assignment_group;
    }
})(current, previous);
The team wants to reduce the database access overhead. Which optimization technique should the developer implement?

Accepted Answer

Create a script include with a static variable to cache the mapping for the duration of the current transaction. Option C is correct because caching the mapping data in a static variable within a script include ensures that the GlideRecord query against the 5000-record custom table is executed only once per transaction, rather than on every incident creation. This drastically reduces database access overhead during peak hours, as subsequent invocations of the business rule within the same transaction reuse the cached results, eliminating redundant queries and preventing timeouts.

Answer

Use GlideAggregate to retrieve the count of matching groups

Answer

Store the mapping in a global script include variable that persists across sessions

Answer

Move the business rule to run after insert so it does not block the insert

Question 7

A business rule on the Incident table should send an email notification when the state changes to 'Resolved'. Which two conditions should be checked in the business rule script? (Choose two.)

Accepted Answer

current.state.changesTo('Resolved'). Option B is correct because the `changesTo()` method in GlideRecord checks if the specified field has changed to a specific value during the current transaction. This is the precise way to detect a state transition to 'Resolved'. Option C is also correct because it adds the `current.operation() == 'update'` condition, which ensures the business rule only fires on update operations, preventing false triggers on insert or delete. Together, these two conditions guarantee the email is sent only when an existing record's state is updated to 'Resolved'.

Answer

current.state == 'Resolved'

Answer

current.state.changes()

Answer

current.state.changesFrom() != 'Resolved'

Question 8

A developer is writing a business rule that should run on after update of the Incident table to send an email notification when the state changes. The developer uses the method current.state.changes() to detect the change. However, the email is sent multiple times for the same incident update. What are two possible reasons? (Choose two.)

Accepted Answer

The business rule runs on both insert and update. Option C: another business rule might also send an email for state changes, causing duplicates. Option E: if the rule runs on insert as well, it will send an email when the state is first set. Option A would not cause duplicates. Option B is incorrect because before and after are separate. Option D would not cause duplicates because changes() is correct.

Answer

The business rule is set to run on every update, but the script does not check the previous state

Answer

The business rule's condition field is set to 'state changes'

Answer

The business rule is set to run on before update as well

Question 9

A developer creates a script include named 'Utils' with a function that uses gs.log('message'). When called from a business rule on the incident table, the log is written. However, when called from a scheduled job in the same scope, no log appears. What could be the reason?

Accepted Answer

The script include is not global.. Option B is correct because if the script include is not global, it may not be accessible from all contexts like scheduled jobs. Option A is incorrect because user context does not affect script include visibility. Option C is incorrect because log level settings are separate. Option D is incorrect because the scheduled job is in the same scope.

Answer

The scheduled job's log level is set to 'errors only'.

Answer

The business rule runs in the same scope but the scheduled job runs in a different scope.

Answer

The scheduled job runs with a different user context.

Question 10

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.. Options B and D are correct. B: Script includes can be scoped and still accessible from business rules in the same scope. D: Script includes should not have side effects on current record to maintain reusability. A is incorrect because scoped script includes are accessible within their scope. C is incorrect because script includes can call other script includes. E is incorrect because they are not auto-evaluated.

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.

Question 11

A ServiceNow instance has a business rule that runs on after query on the Incident table. The rule adds a condition to the query to filter out incidents with state = 'Closed'. Recently, an update set containing a new business rule was installed, and now the filter is not applied. What might have caused this?

Accepted Answer

The new business rule uses query.setCondition() to set the query condition, replacing the existing condition. The new business rule likely uses query.setCondition() which replaces any existing conditions, including the filter from the existing rule. Option A is less likely because order determines execution sequence, but setCondition replaces. Option B is incorrect. Option D is irrelevant.

Answer

The new business rule has a higher order than the existing rule

Answer

The existing business rule is set to run only on insert

Answer

The new business rule uses glide.addNullQuery

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. Option B is correct because 'After' runs after the database operation and is appropriate for updating the same record after the fact. Option A is incorrect because 'Before' would modify the record before save, not after. Option C is incorrect because 'Async' runs asynchronously and may not be needed. Option D is incorrect because 'Display' runs when the form is displayed.

Answer

Display

Answer

Async

Answer

Before

Question 13

The above script runs in a business rule on the Incident table. What is a potential issue with this script?

Accepted Answer

It may cause an infinite loop if the same business rule triggers on update.. Option B is correct because updating incidents using gr.update() could trigger the same business rule again (if the rule runs on update), causing an infinite loop. Option A is incorrect because the API is not deprecated. Option C is incorrect because update() does commit changes. Option D is incorrect because the while loop iterates all matching records.

Answer

It will only update the first matching record.

Answer

It uses a deprecated API.

Answer

It will not commit changes because update() is not used correctly.

Question 14

A developer wants to use a business rule to prevent a user from saving an incident if the short description is empty. Which script should be used?

Accepted Answer

current.setAbortAction(true); gs.addErrorMessage('Short description required');. Option A is correct because the proper order is to setAbortAction(true) first, then add an error message. Option B is incorrect because the order is reversed; the error message may not display. Option C and D use addInfoMessage which is for informational messages, not errors.

Answer

current.setAbortAction(true); gs.addInfoMessage('Short description required');

Answer

gs.addInfoMessage('Short description required'); current.setAbortAction(true);

Answer

gs.addErrorMessage('Short description required'); current.setAbortAction(true);

Question 15

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.. Option B is correct because 'Async' runs the rule in a background thread, improving performance. Option A is incorrect because immediate execution is not async. Option C is incorrect because 'Display' is for form views. Option D is incorrect because async rules can run on updates.

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.