SNOW-CAD Practice Test 35 — 15 Questions

Question 1

A company has developed a custom Scripted REST API endpoint that processes incoming orders and then makes synchronous outbound REST calls to an external shipping system for validation. During testing with low concurrency, the endpoint works correctly. However, in production with high concurrency, the endpoint frequently times out and returns 504 errors to the caller. The performance team has confirmed that the external shipping system is responsive and the network latency is acceptable. Which course of action should the development team take to resolve the timeout issue?

Accepted Answer

Refactor the script to make asynchronous HTTP requests and process the shipping validation response using a separate queue or business rule.. The synchronous HTTP request blocks the script until the response is received. With high concurrency, this leads to thread starvation and timeouts. The best solution is to use asynchronous HTTP requests and handle the response via a queue or event mechanism, freeing the script to process other requests.

Answer

Deploy additional MID Servers to distribute the outbound call load.

Answer

Implement a caching layer to store shipping validation results and avoid repeated calls to the external system.

Answer

Increase the timeout value in the outbound REST Message record to accommodate peak loads.

Question 2

A large enterprise manages its IT assets using a custom table 'u_asset_tracking', which includes a reference field 'u_location' pointing to the 'cmn_location' table. After a recent application upgrade, users report that the location is not being displayed for assets older than six months, although it works for newer assets. A client script uses GlideAjax to fetch the location via a Script Include called 'AssetUtils'. The Script Include performs a GlideRecord query on 'u_asset_tracking' and then dot-walks to 'u_location.sys_id' to retrieve the location name. The upgrade included changes to the application's access controls. The logs show no errors, but the Ajax call returns null for the location. What should the developer do to resolve this issue?

Accepted Answer

Ensure the 'read' role on the 'cmn_location' table is granted to the application's scope or the user's role.. The issue is that after the upgrade, access controls (ACLs) were changed, and the Script Include's GlideRecord query dot-walks to 'cmn_location' to retrieve the location name. Even though the query on 'u_asset_tracking' succeeds, the dot-walk to 'cmn_location' fails silently because the script's execution context (or the user's session) lacks the 'read' role on the 'cmn_location' table. Granting the 'read' role ensures the GlideRecord can access the referenced record, resolving the null return.

Answer

Modify the Script Include to use addNullQuery('u_location') to skip empty location fields.

Answer

Change the client script to use a UI Policy instead of GlideAjax to handle the location display.

Answer

Write a fix script to update the 'u_location' field for all assets older than six months.

Question 3

A company uses Service Portal for employee self-service. One widget displays a list of open requests from the sc_request table. The widget uses a server script that queries all records without a filter. As the request table grows, users experience slow loading times. The widget configuration allows client-side filtering but not server-side pagination. The developer must improve performance without changing the user experience. What should the developer do?

Accepted Answer

Implement pagination in the server script and modify the widget to load data in chunks.. Option B is correct because implementing server-side pagination reduces the amount of data retrieved from the database in a single query, which directly addresses the performance bottleneck caused by loading all records from the sc_request table. By modifying the server script to return only a subset of records (e.g., 25 per page) and updating the widget to request subsequent pages as the user scrolls or clicks, the developer improves load times without altering the user experience. This approach leverages ServiceNow's GlideRecord query efficiency and avoids the overhead of transferring and rendering large datasets on the client.

Answer

Increase the server timeout value to allow more time for the query to complete.

Answer

Add a client-side filter to the widget to display only a subset of records.

Answer

Use a UI Policy to hide the widget for users with many requests.

Question 4

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?

Accepted Answer

A subsequent business rule that runs after this one in the same order is clearing the assignment field.. Option B is correct because 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 5

A ServiceNow administrator is configuring Single Sign-On (SSO) using SAML 2.0 with a corporate identity provider. Users report that after authenticating, they are redirected back to ServiceNow but see an error: 'Unable to process SAML response. Invalid user.' The administrator checks the SSO log and sees the message: 'No user found with username: [user@company.com]'. The username format in the SAML assertion is userPrincipalName (e.g., user@company.com). ServiceNow user records use the 'User ID' field (e.g., 'user'). What configuration change should the administrator make to resolve this issue?

Accepted Answer

Set the 'User Field' property to 'User ID' in the SAML2 configuration to match users based on their User ID. Option D is correct because the SAML assertion contains the userPrincipalName (user@company.com), but ServiceNow's default user matching field is the 'User ID' field, which stores only the username (e.g., 'user'). By setting the 'User Field' property to 'User ID' in the SAML2 configuration, ServiceNow will extract the username portion from the NameID (or a custom attribute) and match it against the 'User ID' field, resolving the mismatch. This avoids the need to change user records or the NameID format.

Answer

Change the 'NameID format' from 'Unspecified' to 'EmailAddress' in the SAML2 configuration

Answer

Create an LDAP integration to automatically create ServiceNow users from the identity provider

Answer

Update all ServiceNow user records to have the 'User ID' field populated as full email addresses

Question 6

A senior developer has created a complex business rule called 'Asset Assignment' on the 'alm_asset' table that runs after insert. The rule queries the 'User' table to find a manager and assigns the asset to that manager's department via a GlideRecord update. The rule has an order of 100. Another business rule called 'Asset Log' on the same table also runs after insert with an order of 200, which logs the assignment in a separate table. After deploying to production, the 'Asset Log' rule executes but the assignment update from 'Asset Assignment' fails silently. The developer discovers that the 'Asset Assignment' rule has a condition script that references a new field that was not added to the 'alm_asset' table in production. The field exists in the developer's instance but not in production. The developer wants to minimize disruption and fix the issue quickly. Which action should the developer take?

A. Change the condition script to check if the field exists before using it, and if not, exit the script gracefully.
B. Reorder the business rules so that 'Asset Log' runs first and 'Asset Assignment' runs second, and add a condition to 'Asset Log' to only run if the assignment succeeded.
C. Remove the condition from 'Asset Assignment' and move the field existence check into the script, setting the field value only if it exists.
D. Deactivate the 'Asset Assignment' business rule until the field is added to the table in production, then reactivate it after the next maintenance window.

Accepted Answer

Change the condition script to check if the field exists before using it, and if not, exit the script gracefully.. Option A is correct because it is the quickest fix with minimal disruption: adding a condition check prevents the business rule from failing when the field is missing, and the rule will run correctly once the field is added. Option B is incorrect because reordering does not fix the root cause; the first rule can run, but the second would still fail if the field is missing. Option C is incorrect because removing the condition entirely would cause the script to run on every insert, which might have unintended side effects, and the field existence check in the script would still be needed. Option D is incorrect because deactivating the rule prevents the intended functionality entirely until the field is added, which is more disruptive.

Answer

Reorder the business rules so that 'Asset Log' runs first and 'Asset Assignment' runs second, and add a condition to 'Asset Log' to only run if the assignment succeeded.

Answer

Remove the condition from 'Asset Assignment' and move the field existence check into the script, setting the field value only if it exists.

Answer

Deactivate the 'Asset Assignment' business rule until the field is added to the table in production, then reactivate it after the next maintenance window.

Question 7

A ServiceNow instance has a business rule named 'Update CI Status' that runs on the 'Change Request' table after insert. The rule is intended to update the 'Configuration Item' record's 'Operational Status' to 'Under Maintenance' when a change request is created. The business rule uses the following script:

(function executeRule(current, previous != null)) {
    var gr = new GlideRecord('cmdb_ci');
    gr.get(current.cmdb_ci);
    gr.operational_status = 'Under Maintenance';
    gr.update();
})(current, previous);

After a recent upgrade to the Vancouver release, the business rule stopped working. The change request is created successfully, but the CI's operational status remains unchanged. The system logs show no errors. What is the most likely cause and the correct fix?

A. The business rule is running asynchronously; change it to synchronous.
B. The condition field is empty; add 'gs.action() === 'insert'' as the condition.
C. The 'current.cmdb_ci' field is not populated; check that the field is required on the form.
D. The script uses 'previous' incorrectly; remove 'previous != null' from the function signature.

Accepted Answer

The 'current.cmdb_ci' field is not populated; check that the field is required on the form.. Option C is correct because the script assumes 'current.cmdb_ci' is populated. If the CI field is not required, a change request can be submitted without a CI, causing the GlideRecord get() to fail silently. Option A is incorrect because asynchronous execution does not affect the script logic; the issue is data. Option B is incorrect because the condition is not missing; the script runs on insert by default. Option D is incorrect because the syntax 'previous != null' in the function signature is invalid; the correct syntax is 'current, previous' but the extra '!= null' would cause a script error, not a silent failure. The error would be logged, which contradicts the statement that no errors are shown.

Answer

The condition field is empty; add 'gs.action() === 'insert'' as the condition.

Answer

The business rule is running asynchronously; change it to synchronous.

Answer

The script uses 'previous' incorrectly; remove 'previous != null' from the function signature.

Question 8

A company is integrating with an external HR system using a REST API to create and update user records in the sys_user table. The API endpoint requires a token that expires every 24 hours. The integration is scheduled to run hourly. The token is stored in a credential record. After a few days, the integration fails with a 401 Unauthorized error. The error log shows "Invalid token". What is the most likely cause?

Accepted Answer

The token was refreshed but the credential record was not updated.. Option B is correct because the token expires every 24 hours, so after the first day, the token used by the integration is stale. The credential record must be updated with a fresh token, but if the integration does not handle token refresh, it will fail.

Answer

The REST API endpoint URL changed.

Answer

The credential record was deleted.

Answer

The IP address of the external system changed.

Question 9

An organization uses an LDAP integration to import user accounts into ServiceNow. The integration creates a large number of users, but some users are missing their manager field. The manager field in LDAP is a distinguished name (DN). The transform map uses a reference field mapping with "Display value" unchecked. The target field "manager" on sys_user is a reference to sys_user. The import set log shows no errors for those records. What is the most likely cause?

Accepted Answer

The LDAP DN values do not match the sys_id of the manager users.. Option A is correct because the manager field is a reference, and with "Display value" unchecked, the mapping expects a sys_id. Since the LDAP provides a DN, the mapping fails silently, leaving the field empty.

Answer

The transform map's "Coalesce" field is set on manager.

Answer

The import set's "On Conflict" setting is set to "Ignore".

Answer

The manager field in LDAP is empty for some users.

Question 10

A company uses a scheduled import from an external database to update the user table nightly. Recently, the import has been failing with a timeout error after 30 minutes. The import set contains 50,000 records. What should the administrator do to resolve this issue?

Accepted Answer

Split the import into multiple smaller batches.. Option B is the best course of action because splitting the import into smaller batches reduces the processing time per batch and avoids timeout, addressing the root cause.

Answer

Use a transform map to skip unnecessary fields.

Answer

Increase the timeout value in the scheduled import configuration.

Answer

Upgrade the instance to a larger size.

Question 11

A developer is working on a new application and wants to ensure all changes are tracked for deployment. The developer creates a new application in Studio and makes modifications. When the developer tries to create an update set, the application changes are not captured. The developer checks the application properties and sees the 'Update Set' field is set to 'Default'. The developer is in a scoped application. What is a possible reason?

Accepted Answer

The application is marked as 'Not in an update set'.. Option A is correct because if the application's 'Update Set' field is set to 'None' or 'Not in an update set', changes won't be captured. Option B is wrong because the application is scoped. Option C is wrong because there is no 'Update Set' field on the application record directly; it's a property. Option D is wrong because phases are irrelevant.

Answer

The application's scope is set to 'Global'.

Answer

The application is in a different phase.

Answer

The developer has not set the 'Update Set' field on the application.

Question 12

A developer is asked to add a new field to a scoped application's table. The developer opens Studio, navigates to the table, and tries to add a new field but the 'Add Field' button is greyed out. The table is part of the scoped application. The developer has the admin role. Other tables in the same application allow field addition. What is the most likely cause?

Accepted Answer

The table is from a different scope.. Option C is correct because if the table is from a different scope (e.g., global scope), you cannot modify it directly from the scoped application. Option A is wrong because locking is not a common feature. Option B is wrong because the developer has admin. Option D is wrong because application phase does not affect field addition.

Answer

The application is not set to 'In Process'.

Answer

The developer does not have the admin role.

Answer

The table is locked by another developer.

Question 13

A large enterprise runs a ServiceNow instance with a heavily customized Task table. The 'Task' table has been extended to create 'u_WorkOrder', which is used by over 50,000 active records. Recently, users complain that when they open a WorkOrder record, the form takes more than 10 seconds to load. On investigation, you discover that the 'u_WorkOrder' table has 150 fields, many of which are UI policies and client scripts that trigger on load. Additionally, there is a business rule that runs 'after query' and dot-walks through multiple related tables (e.g., calling 'current.assigned_to.department.manager.email' in a loop for each record). The instance uses SQL Server as its database. Which action would most effectively reduce the form load time without losing required functionality?

Accepted Answer

Rewrite the after query business rule to use GlideAggregate or avoid dot-walking in loops, and consider caching the dot-walked data. Option C is the most effective because it addresses the primary performance killer: the after query business rule that performs expensive dot-walking for every record. Option A is wrong because removing fields may lose functionality. Option B is wrong because it doesn't fix the slow business rule. Option D is wrong because ordering does not affect the heavy operation.

Answer

Change the order of the business rule to 100 so that it runs after other rules

Answer

Remove 50 of the 150 fields from the table to reduce data retrieval

Answer

Convert the after query business rule to an after update business rule

Question 14

A ServiceNow administrator is responsible for setting up a custom table called 'u_incident_change' to track incidents that require a change request. Each 'u_incident_change' record must be linked to exactly one incident and one change request. The administrator creates two reference fields: 'incident_ref' pointing to the 'Incident' table, and 'change_ref' pointing to the 'Change Request' table. However, after deployment, users report that when they create a new 'u_incident_change' record from an incident form (using a related list), the 'incident_ref' field is automatically populated, but the 'change_ref' field is empty. The users want to be able to create a change request directly from that same form and have the reference automatically filled. What configuration should the administrator use to achieve this?

Accepted Answer

Create a UI Action labeled 'Create Change Request' on the incident form that runs a script to create a new 'u_incident_change' record with both references populated and then opens the change request form. Option A is correct because a UI Action with a script creates the change request and sets the reference fields accordingly. Option B is wrong because referenced records don't auto-populate. Option C is wrong because business rules run on records, not UI. Option D is wrong because related lists don't create records with cross-reference.

Answer

Configure the related list to automatically create the 'u_incident_change' record with both references when a change request is added

Answer

Use a business rule on the 'u_incident_change' table that auto-populates the 'change_ref' when the record is created from a related list

Answer

Add a reference field on the Incident table that points to the 'u_incident_change' table

Question 15

A small business uses ServiceNow to manage IT assets. They have a custom table 'u_company_asset' with fields for asset name, serial number, purchase date, and a reference field 'assigned_to' pointing to the User table. The administrator is asked to add a new field called 'Category' that will contain a short list of categories: Desktop, Laptop, Server, Network. The categories will not change frequently. The administrator also needs to ensure that when a user selects a category, a corresponding icon appears next to the field in the form. What is the most efficient way to accomplish this?

Accepted Answer

Create a Choice field with the four categories, and then configure a UI policy to show different icons based on the selected value. Option A is correct because a Choice field provides a simple drop-down list and supports image mappings. Option B is wrong because a List Collector is for multiple selections. Option C is wrong because a custom table is overkill. Option D is wrong because a string field does not support predefined values.

Answer

Use a List Collector field to allow multiple categories

Answer

Create a custom table 'u_category' and a reference field on 'u_company_asset' pointing to it

Answer

Use a single-line text field and manually enter the categories