SNOW-CAD Practice Test 12 — 15 Questions

Question 1

A Service Portal widget uses AngularJS. The developer needs to share data between the client script and the HTML template. What is the correct approach?

Accepted Answer

Use the 'c' object (c.data) provided by the widget framework.. In ServiceNow portal widgets, the 'c' object serves as the client-side controller context, and data stored in c.data is accessible in both the client script and the HTML template. This is the recommended approach for sharing data within a widget. Option A is wrong because $rootScope makes data global and can lead to unintended side effects. Option B is wrong because $scope is not directly used in the widget framework; instead, the 'c' object provides the scoped context. Option D is wrong because AngularJS factories are meant for reusable services, not for widget-specific data binding.

Answer

Use $rootScope to make data globally available.

Answer

Use $scope to store data in the client controller.

Answer

Create a custom AngularJS factory to manage data.

Question 2

After importing an update set from another instance, a scoped application shows multiple conflicts in Studio. What is the best first step to resolve?

Accepted Answer

Review each conflict and choose the correct version.. Reviewing each conflict and choosing the correct version allows the developer to selectively merge changes, preserving important modifications while discarding unwanted ones. Option A is wrong because deleting and re-importing disregards the resolution of conflicts and may lose customizations. Option C is wrong because discarding all local changes removes any work done locally without consideration. Option D is wrong because accepting all remote changes may overwrite intentional local customizations.

Answer

Delete the application and re-import.

Answer

Discard all local changes.

Answer

Accept all remote changes.

Question 3

A developer needs to display a warning message to the user when the 'priority' field is changed to '1 - Critical'. Which TWO client-side implementations can achieve this?

Accepted Answer

UI Policy with condition: 'Priority changes' and action script to call g_form.showFieldMsg(). A UI Policy with the condition 'Priority changes' triggers an action script when the priority field is modified, allowing the use of `g_form.showFieldMsg()` to display an inline warning message on the field. Option E is correct because an onChange client script fires when the 'priority' field changes, and within it you can check `newValue` against '1 - Critical' and call `g_form.showFieldMsg()` to show the warning. Both are client-side implementations that respond to field changes without a server round-trip.

Answer

Business Rule with 'when to run' set to 'before' and script to call g_scratchpad.message

Answer

onLoad client script that checks the current value of priority and shows a message

Answer

Data Policy with condition on priority field and message set

Question 4

A developer is writing a business rule that should trigger on update of the 'short_description' field of an incident. The rule needs to check if the new value contains 'urgent' and, if so, set the priority to 1. Which TWO statements are true about implementing this rule?

Accepted Answer

The condition 'current.short_description.changes()' can be used to ensure the rule runs only when short_description changes.. The changes() method on a GlideElement returns true only when the field's value has been modified during the current transaction. Placing `current.short_description.changes()` in the business rule's condition ensures the rule triggers only when the short_description field is updated, not on other field changes. Option B is correct because `current` always holds the updated record after the database write; thus `current.short_description` contains the new value. Options C and D are incorrect: `previous.short_description` holds the old value before the update, and `setValue()` is not a method on GlideRecord fields—priority should be set by direct assignment (e.g., `current.priority = 1`). Option E is incorrect because `current.short_description` is a GlideElement object, not a plain string; the indexOf() method does not exist on GlideElement. To check for a substring, you must convert to string first, e.g., `current.short_description.toString().indexOf('urgent') !== -1`. Therefore, the two true statements are A and B.

Answer

The new value of short_description can be accessed using previous.short_description.

Answer

To set the priority, use current.priority.setValue(1).

Answer

The comparison should use current.short_description.indexOf('urgent') !== -1.

Question 5

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 6

A developer wants to prevent users from closing an incident after it has been resolved for more than 30 days. Which approach should be used?

Accepted Answer

Create a business rule on 'before' that aborts the operation if the condition is met.. A 'before' business rule with an abort action is the correct server-side approach to prevent an operation from completing. When the condition (resolved_at is more than 30 days ago) is true, the business rule can call current.setAbortAction(true) to stop the incident from being updated or closed, ensuring the restriction is enforced regardless of the client interface.

Answer

Create an ACL to deny closing after 30 days.

Answer

Create a UI policy that disables the close button.

Answer

Create a client script that alerts the user.

Question 7

A business rule runs on 'before' and 'update' for the incident table. The rule sets the short_description to 'Test' only when the state changes to 'In Progress'. However, the short_description is being updated even when the state does not change. What is the most likely cause?

Accepted Answer

The business rule does not have an 'if (current.state.changes())' condition.. The business rule lacks an 'if (current.state.changes())' condition. Without this check, the script runs on every update, setting the short_description to 'Test' regardless of whether the state field actually changed. The 'before' and 'update' triggers ensure the rule executes on every update, but the conditional logic must explicitly verify the state transition.

Answer

The business rule is set to run globally.

Answer

The business rule script modifies the field directly without checking.

Answer

The business rule is using the 'cancel' action.

Question 8

A developer creates a business rule on the Incident table that executes a GlideRecord query to update related records. The rule runs on 'after' update and queries the Problem table to set a field. However, the update is not being committed. What is the most likely reason?

Accepted Answer

The GlideRecord query requires an explicit gr.updateMultiple() or gr.commit() to persist changes.. In ServiceNow, when a GlideRecord query is used in an 'after' business rule to update records on another table, the changes are not automatically committed. The developer must explicitly call gr.updateMultiple() to persist updates to multiple records, or gr.update() for a single record. Option B correctly identifies this requirement, as the update is not being committed without an explicit method call.

Answer

The developer forgot to use gr.insert() instead of gr.update().

Answer

After business rules cannot update other tables.

Answer

The query returns more than 100 records, causing a governor limit.

Question 9

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 10

A developer needs to capture the time when a field (assigned_to) was last changed. Which approach should be used?

Accepted Answer

Create a business rule on 'after' update that sets a 'last_assigned' field when assigned_to changes.. A business rule running 'after' update can check if the 'assigned_to' field value changed (using previous()) and set a 'last_assigned' field to the current date/time (gs.nowDateTime()). This server-side, platform-native approach reliably captures the timestamp when the field changes. Option A (calculated field) is incorrect because calculated fields are read-only and derive values from other fields; they cannot set a timestamp when a field changes. Option C (database trigger) is not recommended as it bypasses the ServiceNow platform and could cause synchronization issues. Option D (dictionary override to enable auditing) is incorrect because auditing tracks all changes to the field in the audit table but does not store the last change timestamp in a separate field on the record; it would require querying the audit log to find the last change.

Answer

Create a calculated field using a formula.

Answer

Create a database trigger to log the change.

Answer

Use a dictionary override to enable auditing.

Question 11

A company is using an Import Set to load data from a CSV file into the Incident table. The CSV contains a column "Assigned to" with user names (e.g., "John Doe"). The transform map maps the "Assigned to" column to the "assigned_to" field on the Incident table. The import set runs successfully but the "assigned_to" field remains empty. What is the most likely cause?

Accepted Answer

The transform map's field mapping uses "Reference" type but the "Display value" checkbox is not selected.. When mapping to a reference field using display value, the "Display value" checkbox must be selected in the field mapping. Without it, ServiceNow attempts to map the value as a sys_id, which fails silently, leaving the field empty.

Answer

The transform map's field mapping uses "Direct" type instead of "Reference" type.

Answer

The transform map is set to "Create and Update" but the "Coalesce" field is not set.

Answer

The "Assigned to" column header contains a space.

Question 12

A developer needs to ensure that a catalog variable of type 'Reference' displays only active users from the sys_user table. Which property configuration should be applied to the variable?

Accepted Answer

Set 'Ref qual' to 'active=true'. The 'Ref qual' (Reference qualifier) property on a reference variable allows you to specify a condition to filter the records displayed in the lookup. Setting it to 'active=true' restricts the reference field to show only active users from the sys_user table, ensuring the developer meets the requirement.

Answer

Set 'Reference qual' to 'active=true'

Answer

Set 'Condition' to 'active=true'

Answer

Set 'Default value' to 'active=true'

Question 13

A developer needs to create a business rule that runs only when the 'State' field of an Incident changes from 'New' to 'In Progress'. Which condition script should be used?

Accepted Answer

current.state.changes() && current.state.changesFrom('New'). It uses both `current.state.changes()` to verify the field has changed and `current.state.changesFrom('New')` to ensure the previous value was 'New'. This combination precisely captures the transition from 'New' to any other state, which when combined with the business rule's 'when to run' condition (set to 'In Progress' in the rule's filter or script), ensures the rule fires only when the state changes from 'New' to 'In Progress'.

Answer

current.state == 'New' && current.state.changesTo('In Progress')

Answer

current.state.changes() && previous.state == 'New'

Answer

current.state.changesTo('In Progress')

Question 14

A company is expanding its use of ServiceNow and needs to create a custom application for managing employee onboarding tasks. The application includes several tables: Onboarding Request, Task, and Checklist Items. The business requires that when an onboarding request is submitted, a set of tasks should be automatically created in a specific order. Additionally, when all tasks are completed, the onboarding request status should automatically update to 'Completed'. The developer decides to use Flow Designer to automate this process. The developer creates a flow with a trigger on the Onboarding Request table for 'Record created or updated' and adds actions to create tasks. However, during testing, the flow creates tasks but does not update the request status when tasks are completed. What is the most likely issue?

Accepted Answer

The flow is not configured to listen for updates on the Task table.. The flow is triggered only by events on the Onboarding Request table. To update the request status when tasks are completed, the flow must also listen for updates on the Task table (e.g., via a separate flow or a 'Wait for condition' that polls the Task table). Without a trigger or condition monitoring the Task table, the flow has no way to know when tasks finish.

Answer

The flow is set to run only on create, not on update.

Answer

The flow uses a 'Wait for condition' action that is not configured correctly.

Answer

The user does not have rights to update the Onboarding Request table.

Question 15

A developer creates a business rule that runs before a record is inserted or updated on the Incident table. The rule sets the assignment group based on the category. However, after the rule runs, the assignment group is not being saved. What is the most likely cause?

Accepted Answer

The rule runs after the record is saved. The most likely cause is that the business rule is configured to run 'after' the record is saved (option B), even though the developer intended it to run 'before'. In a 'before' business rule, changes to fields on the current record are automatically saved when the record is committed. However, in an 'after' business rule, the record is already saved, so modifications to current are not persisted unless the script explicitly calls current.update(). Option A describes a display business rule, which runs client-side and does not affect server-side saving. Option C is unlikely because if it ran on before update only, it would still run before save. Option D is incorrect because setAbortAction(false) is used in 'before' rules to allow the save to proceed, not to persist changes.

Answer

The rule is a display business rule

Answer

The business rule is set to run on before update only

Answer

The script does not use current.setAbortAction(false)