SNOW-CAD Practice Test 29 — 15 Questions

Question 1

A developer created a UI Script and a Client Script as shown. Both scripts set urgency and impact to '1' when priority is '1'. However, when the priority is changed to '1' on an existing record, the urgency and impact fields do not update. What is the most likely cause?

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

Accepted Answer

The UI Script is not being called because it is not associated with any form or event. A UI Script is a reusable client-side script that must be explicitly called from a Client Script, UI Policy, or form event to execute. In this scenario, the UI Script is not associated with any form or event, so it never runs when the priority field changes. The Client Script alone cannot invoke the UI Script without a direct call, leaving the urgency and impact fields unupdated.

Answer

The priority field is not a choice field, so onChange does not fire

Answer

The Client Script function name is incorrect; it should be 'onChangePriority'

Answer

The g_form API is deprecated and no longer works

Question 2

An organization has a custom table 'u_incident_task' that extends 'task'. They need to allow users to create records in this table from the 'Incidents' module. The 'u_incident_task' table should appear as a related list on the incident form. However, the related list is not showing the 'New' button. What is the most likely cause?

Accepted Answer

There is no reference field on 'u_incident_task' pointing to the incident table. The 'New' button appears on a related list only when there is a reference field on the target table (u_incident_task) that points back to the source table (incident). Without this reference field, the platform cannot automatically populate the parent record's sys_id when creating a new child record, so it suppresses the 'New' button. This is a core requirement for related list creation in ServiceNow.

Answer

The table is in a different application scope

Answer

The table does not extend 'incident'

Answer

The user does not have the required role

Question 3

A company has a custom table 'u_training_course' with a reference field to 'sys_user' named 'u_instructor'. The requirement is that only users with the 'instructor' role can be selected in this field. Which approach should be used to enforce this?

Accepted Answer

Add a reference qualifier on the field to filter users with the 'instructor' role. A reference qualifier is the declarative way to filter the records available in a reference field on ServiceNow. By adding a condition like 'roles=instructor' to the reference qualifier of the 'u_instructor' field, only users with the 'instructor' role will appear in the lookup, enforcing the requirement at the database query level without custom scripting.

Answer

Create a business rule on the table to check the role and reject invalid selections

Answer

Use a client script to validate the selection before form submission

Answer

Configure an ACL on the reference field to restrict write access

Question 4

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 5

A company has a requirement that the 'state' field of an incident cannot be changed from 'In Progress' to 'Resolved' if the 'category' field is empty. This validation must be enforced server-side to prevent data integrity issues. Which implementation should be used?

Accepted Answer

Create a 'before' Business Rule that checks if the state is changing to 'Resolved' and if category is empty, aborts the update with an error message.. A 'before' Business Rule runs server-side and can check if the state is changing to 'Resolved' and if the category field is empty. Using gs.addErrorMessage() and returning false aborts the update, enforcing the validation server-side. Option A (Data Policy) would make category mandatory globally, not only during the specified state transition. Option B (ACL) controls field-level access but cannot validate value transitions. Option C (Client Script) runs client-side and can be bypassed.

Answer

Make the 'category' field mandatory using a Data Policy.

Answer

Configure an ACL on the 'state' field to deny write access when category is empty.

Answer

Create a Client Script on 'state' change that checks if category is empty and shows an error message.

Question 6

A company needs to allow employees to request a new laptop through a catalog item. The form should only show a 'Configuration' section if the user selects 'Yes' for 'Custom Configuration?'. Which design approach best accomplishes this?

Accepted Answer

Use a UI Policy to show/hide the section based on the field value.. UI Policies are declarative and maintainable for showing/hiding variables based on conditions, unlike client scripts which can be brittle.

Answer

Use a client script to hide the section when the field changes.

Answer

Use an ACL to restrict access to the section.

Answer

Use a catalog client script to set the visibility.

Question 7

A developer needs to import CSV data into a custom table using Import Sets. The data contains a reference field to a user record. Which configuration ensures that the user record is correctly matched?

Accepted Answer

Set the target field 'email' as coalesce on the transform map.. Setting the 'email' field as a coalesce field on the transform map tells the Import Set engine to use that field to match incoming records against existing target table records. When the reference field points to a user record, the coalesce field (e.g., email) is used to look up the sys_user table and automatically populate the correct sys_id, ensuring the reference is properly resolved without manual scripting.

Answer

Set the source field as coalesce on the transform map.

Answer

Configure the import set row to be ignored if the user is not found.

Answer

Use a script in the 'on before' transform script to find the user.

Question 8

A developer writes a business rule that queries the 'incident' table using GlideRecord. The script loops through all incidents and updates a field. After running, the developer notices that only a subset of records were updated. What is the most likely cause?

Accepted Answer

The GlideRecord query did not include a condition, so it used a default filter that limited results. GlideRecord queries in ServiceNow automatically apply a default filter when no explicit condition is set, typically limiting results to records where the `active` field is `true`. This default behavior, known as the 'active filter,' causes the script to only process a subset of incidents (those that are active) rather than all records in the table, explaining why only some were updated.

Answer

The user running the script lacks write ACL on the table

Answer

The field name used in the update was misspelled

Answer

The script did not call getRowCount() before the loop

Question 9

During development, a developer creates a new application module and adds a table 'x_abc_incident' with a reference field to the 'sys_user' table. The developer wants to ensure that when a user is deleted, all related incident records are also deleted. What database constraint should be configured on the reference field?

Accepted Answer

Cascade delete. A cascade delete constraint ensures that when a record in the parent table (sys_user) is deleted, all child records in the referencing table (x_abc_incident) that have a foreign key pointing to that parent are automatically deleted. In ServiceNow, this is configured on the reference field's 'Delete constraint' property by selecting 'Cascade delete', which enforces referential integrity at the database level.

Answer

No action

Answer

Restrict delete

Answer

Set null on delete

Question 10

A developer notices that the business rule does not set the assignment group as expected when a new record is created with state 0. What is the most likely issue?

Accepted Answer

The assignment_group value is not a valid sys_id of a group.. The most likely issue is that the assignment_group value provided in the script is not a valid sys_id of an existing group. In ServiceNow, the assignment_group field is a reference field to the sys_user_group table, and it must contain a valid sys_id. If the sys_id is invalid or does not exist, the field will not be set, and the business rule will appear to have no effect.

Answer

The script has a syntax error.

Answer

The business rule runs after the record is saved, so updates are ignored.

Answer

The business rule condition is incorrect.

Question 11

A developer is building a custom application that requires a scheduled job to run every hour and check for overdue tasks. In ServiceNow Studio, what is the best way to implement this?

Accepted Answer

Create a Scheduled Job in Studio that runs every hour and executes a script to check overdue tasks.. ServiceNow Studio provides a native 'Scheduled Jobs' module that allows developers to create and manage recurring server-side scripts directly within the IDE. This approach leverages the platform's job scheduler, which runs on the node's clock and integrates with the glide system, ensuring reliable hourly execution without external dependencies or performance overhead from transactional triggers.

Answer

Set up a REST API endpoint that external cron jobs call every hour.

Answer

Create a Business Rule that runs on 'after' insert and update to check for overdue tasks.

Answer

Use Flow Designer to create a scheduled flow that runs every hour.

Question 12

A company uses a custom application with a table 'incident_task' to track work on incidents. The requirement is to automatically reassign any incident_task that has not been updated in the last 7 days to a specific 'Escalation' group. A developer writes a Business Rule on the 'incident_task' table with the condition 'Current' table and runs on 'before query'. The script checks if (gs.daysAgo(current.sys_updated_on) >= 7) and then performs a current.assignment_group.setValue('escalation_group_sys_id'), followed by current.update(). After testing, the tasks are not being reassigned. What is the most likely cause of this issue?

Accepted Answer

Before query business rules cannot perform updates; they are read-only.. Before query business rules in ServiceNow are executed during the retrieval of records from the database, and they are strictly read-only. They cannot perform updates, inserts, or deletes because the database operation is not yet complete. Attempting to call current.update() within a before query business rule will be ignored or cause an error, which is why the reassignment never occurs.

Answer

The business rule should be changed to 'after' update.

Answer

The condition should use 'sys_updated_on' instead of 'sys_updated_on' (the same field).

Answer

The script uses current.update() which causes recursion.

Question 13

A developer writes a widget client controller that uses spUtil.get to fetch data from the server. The data is correctly returned, but the widget does not update the UI. What is the most likely cause?

Accepted Answer

The callback does not assign the result to a $scope variable. spUtil.get returns a promise, and the success callback should assign to $scope to trigger digest cycle. If the callback does not update a $scope property, the view will not update.

Answer

The widget's HTML template does not reference the correct variable name

Answer

The server script did not set data correctly

Answer

The spUtil.get method is deprecated

Question 14

Refer to the exhibit. A developer created this Script Include to be used as a REST API endpoint. However, when calling the API, the response is empty. What is the most likely reason?

Accepted Answer

The Script Include is not marked as 'REST API endpoint' or does not extend the appropriate class.. A Script Include used as a REST API endpoint must either extend the appropriate class (such as 'RESTAPI' or 'RESTAPIV2') or be explicitly marked as a REST API endpoint in its definition. Without this, the platform does not recognize it as a valid endpoint, resulting in an empty response when the API is called.

Answer

The Script Include is not marked as 'Client callable'.

Answer

The function name 'getOpenIncidents' is not exposed.

Answer

The GlideRecord query returns no results.

Question 15

A developer is troubleshooting a business rule in a scoped application that is not triggering. The rule is set to run 'before' query, with condition 'current.state == 1'. The table has read ACLs that restrict access. What is the most likely reason the business rule is not executing?

Accepted Answer

The user does not have read access to the records, so the query does not execute the rule.. Business rules that run 'before query' execute when a query is made against the table. If the user lacks read access due to ACL restrictions, the query itself is not permitted, so the business rule never triggers. This is because the platform's security layer evaluates ACLs before executing business rules, preventing the rule from running when the user cannot read the records.

Answer

The condition 'current.state == 1' is incorrect syntax.

Answer

Another business rule with higher order is preventing execution.

Answer

The business rule is scoped and cannot access the table.