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

Question 1

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?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The condition 'current.category.changes()' returns false on insert.. The condition 'current.category.changes()' checks if the category field has changed from its previous value. On insert, there is no previous value, so this condition returns false, causing the business rule to not execute the assignment group update. Option B is incorrect because the business rule does run on insert (it is configured to run on insert as well, despite the stem mentioning only 'before update'), but the condition fails. Option C is incorrect because the rule runs before the database operation. 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 2

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 3

Refer to the exhibit. A Business Rule in the same scope calls this script include using 'var total = new MyUtils().getTotal("invoice", "state=paid");' but gets '0' even though there are records. What is the most likely cause?

Accepted Answer

The 'amount' field is not numeric in the invoice table.. The Business Rule calls `getTotal` which uses `GlideAggregate` to sum the `amount` field. If the `amount` field is not numeric (e.g., it is a string or another non-numeric type), `GlideAggregate.addAggregate('SUM', 'amount')` will return `0` because it cannot perform a numeric aggregation on non-numeric data. This matches option B.

Answer

The getTotal method is not properly defined.

Answer

The GlideAggregate query syntax is incorrect.

Answer

The script include is not accessible from the Business Rule's scope.

Question 4

A company has a business rule that runs on update of the Incident table. The rule sets the caller_id field to the sys_id of the user who last modified the record. However, the rule does not fire when an update is made via web services. What is the most likely cause?

Accepted Answer

The business rule's 'When' field is set to 'UI action only' which excludes web service updates.. When the 'When' field of a business rule is set to 'UI action only', the rule only triggers on UI actions and not on web service updates. Option B is incorrect because if the business rule were inactive, it would never fire at all, but the question states it doesn't fire only when updated via web services, so it must be active. Option C is incorrect because business rules do run on web service updates unless specifically excluded. Option D is incorrect because the condition 'current.operation() == 'update'' would still be true for web service updates since web services use the update operation.

Answer

The business rule is inactive.

Answer

Business rules never run when updates are made via web services.

Answer

The business rule's condition is 'current.operation() == 'update'' but the web service uses a different operation.

Question 5

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.. If the script include is not global (i.e., it is scoped to a specific application), it may not be accessible from all execution contexts. Even though the scheduled job is defined in the same scope, scheduled jobs can run under a different context (such as the global scope) or have additional restrictions that prevent access to non-global script includes. This explains why the business rule works (as it runs in the application scope) but the scheduled job does not. Option A is incorrect because log level settings do not affect script include accessibility—they control whether log messages are displayed. Option B is incorrect because the scenario states the scheduled job is in the same scope. Option D is incorrect because user context does not affect script include visibility; it affects record access.

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 6

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');. The proper order is to call `current.setAbortAction(true)` first to abort the save, then use `gs.addErrorMessage()` to display an error message. Option A is incorrect because it uses `gs.addInfoMessage()` for an informational message instead of an error, which does not properly indicate a validation failure. Option B is incorrect both because it reverses the order (the error message may not display after abort) and uses `addInfoMessage`. Option C is incorrect because it reverses the order: the error message is added before the abort action, which may cause the message to be lost. Only D uses the correct order and the correct method for error messages.

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 7

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.. 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 8

Which script function is used to query the database in a business rule?

Accepted Answer

new GlideRecord('table').query();. In ServiceNow, a business rule must instantiate a new GlideRecord object using the 'new' keyword and then call the query() method on that instance to retrieve records from the database. The syntax 'new GlideRecord('table').query()' properly creates a GlideRecord object for the specified table and executes the query to fetch matching records.

Answer

GlideRecord.query();

Answer

gs.query();

Answer

GlideRecord.newQuery();

Question 9

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. (Before) is correct because 'Before' business rules run before the record is saved to the database, allowing default values to be set. Option B (Async) is incorrect because Asynchronous rules run later in a separate transaction. Option C (After) is incorrect because 'After' rules run after the record is already saved, so they cannot set default values before insert. Option D (Display) is incorrect because 'Display' rules run when the form is loaded, not before insert.

Answer

Async

Answer

After

Answer

Display

Question 10

A business rule on the Incident table runs 'after' update and calls a script include that modifies the current record. However, changes made by the script include are not saved. What is the reason?

Accepted Answer

The business rule is set to 'after' and cannot modify the current record.. Business rules set to run 'after' the database operation cannot modify the current record directly; any changes made to the current record in an 'after' business rule are not saved to the database. The script include may alter the record in memory, but since the database write has already occurred, those changes are discarded unless a separate database operation (like current.update()) is explicitly called.

Answer

The script include uses current.update() which triggers the same business rule recursively.

Answer

The business rule condition uses current.operation() incorrectly.

Answer

The script include uses gs.sleep(1000) and times out.

Question 11

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 execute in a separate background thread after the database operation, which avoids performance impact on the main transaction. Therefore, option D is correct. Option A is incorrect because running immediately is the default synchronous behavior, not async. Option B is incorrect because 'Async' is not related to record viewing; that is controlled by the 'Display' condition. Option C is incorrect because async rules still run on updates; they just run asynchronously.

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 12

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'). 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 13

Which three actions require a business rule to be set to 'before' to work correctly? (Choose three.)

Accepted Answer

Setting a default value on a new record. Options C, D, and E are correct. C: Setting a default value on a new record must occur before the record is saved to the database. D: Updating a field on the current record must be done before the record is saved, because after save the record is already stored. E: Aborting the current transaction must happen before the database write; in an after business rule, the transaction has already been committed. Options A (sending an email notification) and B (deleting a related record) can be performed in after business rules because they do not require modifying the record before it is saved.

Answer

Sending an email notification

Answer

Deleting a record related to the current record

Question 14

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 should not have side effects on current record to maintain reusability. D: Script includes can be scoped and still accessible from business rules in the same scope. A is incorrect because script includes can call other script includes. C is incorrect because script includes do not need to be global; they can be scoped. 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 15

The business rule has an empty script. What will happen when an incident state changes to 'Resolved'?

Accepted Answer

Nothing, because there is no script.. The business rule will fire because the condition (incident state changes to 'Resolved') is valid. However, since the script is empty, nothing happens. No default actions are executed. Option A is wrong because the condition is not invalid; it is valid. Option C is wrong because a script is not required for a business rule to fire. Option D is wrong because there are no default actions; the business rule only runs the script, which is empty.

Answer

The business rule will not fire because condition is invalid.

Answer

The business rule will cause an error because script is required.

Answer

The business rule will still fire and execute default actions.