SNOW-CAD Core Application Development Practice Test 3 — 15 Questions

Question 1

A company is using ServiceNow for incident management. They have a business rule on the 'before update' of the incident table that automatically assigns the incident to the first available member of the 'Support' group when the state changes to 'New'. The business rule works correctly when an incident is first created with state 'New', but when an existing incident's state is changed to 'New' from another state, the assignment does not happen. The business rule script checks if current.state.changesTo('New') and then queries the group members. The group has multiple members. Other business rules that run on state changes work fine. What is the most likely cause?

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

Accepted Answer

A subsequent business rule that runs after this one in the same order is clearing the assignment field.. The business rule runs on 'before update', and if a subsequent business rule in the same execution order clears the assignment field after this rule sets it, the assignment will be lost. This is a common issue when multiple business rules interact on the same table and order of execution matters. The fact that other state-change business rules work fine indicates the logic itself is sound, but a later rule is overriding the assignment.

Answer

The condition current.state.changesTo('New') only works on insert, not on update.

Answer

The business rule should be set to run on 'after' update instead of 'before' to ensure the state is committed.

Answer

The script uses current.assignment_group which is not available on update because the group might be different.

Question 2

A developer has created a Business Rule that runs on the 'After' order of the incident table. The Business Rule modifies several fields on the incident record. After testing, the developer notices that the changes are not being saved to the database. What is the most likely cause?

Accepted Answer

The Business Rule does not include a call to current.update() after making field changes.. In ServiceNow, a Business Rule set to run 'After' the database operation does not automatically save field changes to the database. The developer must explicitly call `current.update()` to persist the modifications. Without this call, the changes exist only in memory during the script execution and are discarded after the rule completes. Option D is incorrect because the rule is specifically set to run 'After' as stated in the stem; if it were 'Before', changes would be saved automatically without needing `current.update()`. Options A and C are possible but less likely; the most common cause is the missing `current.update()` call.

Answer

The Business Rule is disabled for the current user's role.

Answer

The fields being modified are read-only due to a data policy.

Answer

The Business Rule is set to run on 'Before' instead of 'After'.

Question 3

Which TWO of the following are valid ways to retrieve a single record from a GlideRecord query on the task table?

Accepted Answer

gr.next(). `gr.next()` is the standard method to advance the cursor to the next record in a GlideRecord query result set. When called after a `query()`, it retrieves the first record (or subsequent records) and returns true if a record exists, making it a valid way to access a single record. Option D is correct because `gr.get(sys_id)` retrieves a single record by its sys_id directly, without needing a prior query, and returns true if the record is found.

Answer

gr.getRow()

Answer

gr.getUniqueValue()

Answer

gr.getByID()

Question 4

A ServiceNow developer is working on a new application that requires a custom table to store project information. The table needs to have fields for project name, start date, end date, and project manager (reference to sys_user). The developer creates the table using the Application Creator and adds the fields. After creating the table, the developer wants to automatically generate a unique project ID in the format 'PROJ-00001' for each new record. The developer considers using a Business Rule with a script or a Default Value with a scripted function. Which approach would be the most efficient and maintainable for generating the project ID?

Accepted Answer

Create a Default Value for the project ID field using a script that calls a helper function.. A Default Value script runs before the record is saved, allowing the unique ID to be generated without an extra update. Using a helper function promotes reusability and maintainability, and the script can query the current count of records to generate the next sequential ID in the desired format.

Answer

Create an After Insert Business Rule that updates the project ID after the record is saved.

Answer

Create a Before Insert Business Rule that uses a script to query the current count of records and generate the next ID.

Answer

Create a calculated field that uses a scripted formula to generate the ID.

Question 5

A senior developer is troubleshooting a performance issue in a Production instance. The instance has a large number of Business Rules that run on the incident table. One particular Business Rule, 'Update CI Impact', runs on the 'After Update' order and performs a GlideRecord query on the cmdb_ci table based on the incident's configuration item (ci) field. The query uses a filter to find all CIs related to the same location as the incident. Recently, users have reported that saving an incident takes over 30 seconds. The developer suspects this Business Rule is the cause. The developer examines the script and finds it uses a synchronous GlideRecord query with no scoping on the query. The developer wants to minimize impact on performance without removing the functionality. Which approach should the developer take?

Accepted Answer

Change the Business Rule to run asynchronously using the 'Async' checkbox in the Business Rule form.. Enabling the 'Async' checkbox on the Business Rule moves the execution to the background job scheduler, allowing the incident save transaction to complete immediately without waiting for the GlideRecord query to finish. This eliminates the synchronous delay that causes the 30-second save time, while preserving the functionality of updating CI impact.

Answer

Add an index on the cmdb_ci table for the location field and use an efficient query.

Answer

Move the logic to a scheduled job that runs every hour instead of on every update.

Answer

Convert the GlideRecord query to use GlideRecordSecure to limit access.

Question 6

A junior developer is creating a new catalog item for requesting software licenses. The catalog item includes several variables such as software name, quantity, and cost center. The business requires that when a user submits the request, the cost center variable should automatically populate with the cost center of the user's manager. The developer has written a script in the 'On Load' catalog client script to populate the cost center field. However, during testing, the cost center field remains empty after the form loads. The developer checks the script and finds it uses GlideAjax to call a Scripted REST API to fetch the manager's cost center. What is the most likely cause of the issue?

Accepted Answer

The 'On Load' client script runs before the GlideAjax response is received.. The 'On Load' catalog client script triggers when the form loads, but GlideAjax makes an asynchronous call to the server. The script continues executing without waiting for the response, so the cost center variable remains empty until the callback fires. Since the callback updates the field asynchronously, the field appears empty on load because the response hasn't arrived yet.

Answer

The cost center variable is read-only and cannot be set by client scripts.

Answer

The Scripted REST API is not accessible from client scripts due to cross-origin restrictions.

Answer

The GlideAjax call is missing the callback function.

Question 7

A developer needs to create a catalog item that requires approval from the user's manager. What is the best practice to configure this?

Accepted Answer

Add an 'Approval' activity in the workflow. Adding an 'Approval' activity in the workflow is the classic best practice for catalog items requiring manager approval because it leverages the built-in approval engine, which automatically routes to the manager via the 'Approves' related list and respects approval rules. This approach integrates with the standard approval state, audit trail, and notification mechanisms without custom code. It is the documented ServiceNow approach for catalog item approvals in workflow-driven fulfillment.

Answer

Use a Flow with a 'Get Approvals' action

Answer

Use a Client Script to trigger an approval request

Answer

Use a Business Rule to set the approval state

Question 8

Which TWO of the following are valid ways to personalize a Service Portal widget without modifying the original widget code?

Accepted Answer

Extend the widget via Widget Library. Option A is correct because the Widget Library in Service Portal allows you to create a clone/extension of an existing widget (via 'Create a copy' or by extending it) so you can customize its HTML, client script, server script, and CSS without touching the original widget's code, preserving upgradability. Option D is correct because a Widget Instance (placed on a page via the Page Designer) exposes configurable options defined in the widget's option schema, letting you override properties such as title, colors, or data source parameters per instance without editing the underlying widget code. Option B is not valid because Business Rules operate on table records and cannot override a widget's server-side script, which runs in the Service Portal widget execution context, not through Business Rule triggers. Option C is not valid because directly editing the widget's HTML template modifies the original widget code, which is exactly what the scenario prohibits and would be overwritten on upgrade. Option E is not valid because creating a brand-new widget from scratch does not personalize the existing widget; it replaces it with a separate artifact rather than customizing the original without modifying it.

Answer

Override the widget's server script via a Business Rule

Answer

Modify the widget's HTML template directly in the instance

Answer

Create a new widget from scratch

Question 9

A developer implements the above Business Rule on the 'incident' table. What is the effect of this script?

Accepted Answer

Aborts the update if the record is already in closed state. The Business Rule uses 'current.operation() == 'update'' and checks if the state is 'closed' before the update. If the record is already closed, it calls 'gs.addErrorMessage()' and returns false, which aborts the update. This prevents any changes to a closed record, not just preventing the state from being set to closed.

Answer

Deletes the record if the state is closed

Answer

Prevents the state from ever being set to closed

Answer

Sets the state to closed for all records

Question 10

A developer is building a custom scoped application for tracking equipment loans. The application includes a table named 'Equipment Loan' that extends the Task table. The developer wants to ensure that when an equipment loan record is inserted, a unique loan number is automatically generated and stored in the 'number' field. The loan number should follow the format 'LOAN' followed by a zero-padded sequence, for example, 'LOAN0001001'. Which approach should the developer use to generate this loan number?

Accepted Answer

Configure a system number range and assign it to the table's number field via the Number Maintenance module.. The Number Maintenance module is the standard, supported way to generate sequential numbers with a specific prefix and padding for any table. It handles concurrency and ensures uniqueness without custom scripting. Assigning a number range to the table's number field automates the generation on insert, meeting the requirement precisely and reliably.

Answer

Create a before insert business rule that queries the maximum loan number and increments it, then sets the number field.

Answer

Use a scripted default value on the number field that concatenates 'LOAN' with the sys_id of the record.

Answer

Create an after insert business rule that calls the getNextObjNumber() method to generate the number and updates the record.

Question 11

A developer is creating a UI policy on the 'incident' table that should make the 'close_notes' field mandatory and read-only when the 'state' is 'Closed'. The UI policy is configured with a condition 'state=7' and the actions 'Mandatory=true' and 'Read only=true'. After testing, the developer finds that the field is mandatory but not read-only; users can still edit it. What is the most likely reason?

Accepted Answer

Another UI policy on the same table has a lower order and sets the field to read-only false.. UI policies are evaluated in order, and actions from multiple policies can conflict. If a second UI policy on the same table has a lower order (higher priority) and sets the close_notes field to read-only false, it will override the read-only true action from the first policy. The mandatory action remains because it is not overridden. Checking UI policy order and other active policies is essential.

Answer

The UI policy is not executing because the condition is incorrect.

Answer

The UI policy actions are conflicting because a field cannot be both mandatory and read-only.

Answer

The 'close_notes' field is also being modified by a client script that runs after the UI policy.

Question 12

A developer is building a scheduled job that runs nightly to archive incident records older than 90 days. The job must process records in batches and continue even if one batch fails. Which approach should the developer use within the scheduled job script to meet these requirements?

Accepted Answer

Use GlideRecord with a while loop and a try/catch block around each batch of records, committing after each batch.. A scripted scheduled job using GlideRecord with explicit batching and try/catch around each batch provides the control needed to process records in chunks and continue after a failure. This pattern is standard for large-scale data operations in ServiceNow, ensuring reliability and performance. Other options either lack error handling, are not designed for bulk deletion, or do not provide batch-level resilience.

Answer

Use a GlideRecord query with addEncodedQuery and setLimit, then iterate with next() and deleteRecord().

Answer

Use GlideAggregate to count records, then delete them all with a single GlideRecord.deleteMultiple() call.

Answer

Use a Flow Designer flow with a scheduled trigger and a For Each action to iterate over records and delete them.

Question 13

A developer creates a Script Include named IncidentUtils that contains a method calculatePriority(category, impact). A Business Rule on the incident table is configured with the script `var utils = new IncidentUtils(); var p = utils.calculatePriority(current.category, current.impact); current.priority = p;`. The Business Rule is set to run before update and is active, but when an incident is updated, the priority is not changed and no errors appear in the system log. The Script Include has the Client callable checkbox selected and is otherwise correctly written. What is the most likely reason the method is not being invoked?

Accepted Answer

The Business Rule 'when' condition is not set to 'before' or the rule is not actually firing on the target table.. A silent failure where a Business Rule script produces no effect and no log entry almost always means the rule itself is not firing. Before inspecting the Script Include or the method body, verify the rule's table, when (before/after/async/display), and filter conditions. If the rule never executes, the Script Include is irrelevant to the observed behavior.

Answer

The calculatePriority method must be declared with the var keyword to be callable.

Answer

Server-side Business Rules cannot instantiate Script Includes; only client scripts can.

Answer

The Script Include must be marked as active in the Script Includes list.

Question 14

A developer needs to add a new field to the Incident table that will store the name of the assignment group manager. The field should be automatically populated when the assignment group changes. Which ServiceNow feature should be used to implement this requirement with minimal code?

Accepted Answer

Create a field of type Reference to sys_user and configure a Calculated Value that references the assignment group's manager.. Using a Reference field to sys_user combined with a Calculated Value that dot-walks to the assignment group's manager provides automatic, real-time population with minimal code. Calculated Values are evaluated on display and on update, ensuring the field stays current without custom scripts. This approach is efficient and maintainable, leveraging ServiceNow's built-in capabilities.

Answer

Add a field of type String and set its value using a UI Policy that runs on assignment group change.

Answer

Create a new field of type Reference to the sys_user table and set its value via a Business Rule on before update.

Answer

Add a field of type String and use a Scheduled Job to update it periodically.

Question 15

A developer is creating a client script that runs on the Incident form. The requirement is to display an alert message when a user changes the 'Priority' field to '1 - Critical', but only if the user is not a member of the 'Major Incident Manager' group. The script must run without a server round-trip. Which client script type and configuration should the developer use?

Accepted Answer

onChange client script on the 'priority' field, with a condition that checks group membership using a GlideAjax call to a script include that queries sys_user_grmember.. The requirement is to alert when priority changes to critical for users not in a specific group, without a server round-trip. An onChange client script on the priority field is the correct trigger. To check group membership without a full server round-trip, GlideAjax is used to asynchronously query the sys_user_grmember table via a script include. This keeps the form responsive and meets the condition. Other script types do not trigger on field change or use incorrect APIs for group checks.

Answer

onSubmit client script that checks the priority value and group membership, then displays an alert before submission.

Answer

onLoad client script that checks the initial priority value and group membership, then displays an alert if priority is critical.

Answer

onChange client script on the 'priority' field, with a condition that checks the user's group membership using g_user.hasRole() and displays the alert.