SNOW-CAD Practice Test 36 — 15 Questions

Question 1

A company uses an import set to bring in hardware asset data from an external inventory system. The staging table 'u_hardware_staging' maps fields to the 'alm_hardware' table via a transform map. Recently, the import set started failing with the error 'Invalid reference field value: 'PO123' for field 'purchase_order''. The 'purchase_order' field on 'alm_hardware' is a reference to the 'purchase_order' table, and the staging field contains the purchase order number (e.g., 'PO123'). The transform map has a field map that uses the 'Find' and 'Map' functionality to match the purchase order number. The 'purchase_order' table uses the 'number' field as the display value. Which change should the administrator make to fix the error?

Accepted Answer

In the transform map, enable 'Find map for each record' and set the match field to 'number' on the purchase_order table. Option B is correct because the error indicates that the transform map is not finding the matching purchase order record. Using 'Find map for each record' with the correct match field ('number') will resolve it. Option A is wrong because the lookup field is already correct. Option C is wrong because it overcomplicates. Option D is wrong because the source table is fine.

Answer

Modify the staging table to include the sys_id of the purchase order instead of the number

Answer

Change the field map to use 'Direct' instead of 'Find' and 'Map'

Answer

Create a database view between the staging table and the purchase_order table to auto-populate the reference

Question 2

A multinational corporation uses a single ServiceNow instance for IT service management. The ServiceNow portal serves thousands of users across multiple departments (HR, Finance, IT, Legal). Each department requires a customized portal experience: specific branding, tailored service catalog, and unique knowledge bases. The current implementation uses a single portal with multiple widgets that conditionally display content based on user group membership. Users have reported slow page loads and inconsistent styling across departments. The ServiceNow administrator must redesign the portal architecture to improve performance and maintainability while accommodating each department's requirements. Which approach should the administrator take?

Accepted Answer

Maintain a single portal but leverage ServiceNow's branding records and theme variants to apply department-specific styling; optimize widgets with client-side caching and lazy loading.. Option B is correct because using a single portal with ServiceNow's branding infrastructure (branding records, theme variants) allows centralized management while providing department-specific customization. Optimizing widgets with client-side caching and lazy loading addresses performance concerns. Option A is incorrect because creating separate portals per department leads to significant maintenance overhead and fragmentation of configurations. Option C relies on client scripts for styling, which is inefficient and difficult to maintain; performance remains poor. Option D ignores departmental requirements, resulting in a poor user experience.

Answer

Create a separate portal for each department, each with its own theme and set of widgets to fully isolate customizations.

Answer

Standardize all departments onto a single, simple portal with no customizations to reduce complexity and improve load times.

Answer

Keep one portal with a single theme and use extensive client scripts to alter styling and content based on the user's department.

Question 3

A company is redesigning its service catalog to improve user experience. One of the catalog items, 'Request New Software', contains 10 variables including software category, license type, and required approvals. The variable fields should dynamically show/hide and become mandatory based on previous selections. Currently, the catalog item uses a single, complex catalog client script that handles all visibility and mandatory conditions. This script has become difficult to maintain, and users experience delays when interacting with the form. The IT team wants a more efficient and maintainable solution. What should the administrator do?

Accepted Answer

Implement UI policies for visibility and mandatory conditions, and keep a streamlined catalog client script only for dynamic field values or complex calculations.. Option C is correct because UI policies are designed to handle visibility, read-only, and mandatory conditions declaratively, improving maintainability. The catalog client script should be reserved for complex dynamic values or calculations that UI policies cannot perform. Option A is incorrect because while UI policies are good, some complex logic may still require client scripts; a full conversion may not always be possible. Option B is incorrect because a single script with complex conditions will still be hard to maintain and may cause performance issues. Option D is incorrect because business rules run server-side and cannot directly control client-side form behavior such as field visibility.

Answer

Move the entire logic to a business rule that runs on the server side to reduce client-side processing.

Answer

Convert all conditions to UI policies to replace the catalog client script entirely.

Answer

Refactor the existing catalog client script into a single, more efficient script with optimized conditions.

Question 4

A developer created a custom form section for the 'change_request' table that contains a reference field to 'cmdb_ci'. The section is visible in the form layout for all change request types. However, when the 'type' field is set to 'Emergency', the section should not be visible. The developer added a UI Policy to hide the entire section when type is 'Emergency'. But the section remains visible. After checking, the UI Policy is active and the condition is set correctly. What is the most likely reason the UI Policy is not working, and what is the best fix?

Accepted Answer

UI Policies cannot hide form sections; they only control field-level visibility. The developer should hide each field in the section individually via UI Policy or use a client script to hide the section div. Option C is correct because UI Policies can only control individual field visibility, not entire form sections. The best fix is to hide all fields in the section, or use a client script to hide the section via CSS. Option A is incorrect because UI Policies cannot directly target form sections. Option B is incorrect because there is no default order issue; UI Policies work on fields. Option D is incorrect because the section has no 'visible' attribute.

Answer

The section's 'Visible' checkbox in the form layout must be unchecked and then controlled by the UI Policy

Answer

The UI Policy must be set to 'Run for all users' and the section must be assigned a 'visible' attribute

Answer

The UI Policy order is too low; it should be set to a higher priority number

Question 5

A Service Portal widget displays a list of open incidents. The data is updated via a GlideAjax call in the client controller. Users report that the list does not refresh automatically when a new incident is created. The developer wants to implement auto-refresh without manual page reload. The widget is used on a dashboard that does not require real-time updates every second. Which approach is most efficient?

Accepted Answer

Use Angular $interval to call the GlideAjax every 30 seconds in the client controller. Option D is correct because a polling interval with a reasonable delay (e.g., 30 seconds) balances freshness and server load. Option A is incorrect because using 'spNavigation' to reload the entire page causes a full page reload, which is inefficient. Option B is incorrect because WebSocket-like channels are not native to Service Portal and require custom setup; plus, real-time is not needed. Option C is incorrect because calling the GlideAjax each time the user interacts with the widget misses updates when the user is not interacting.

Answer

Set up a real-time data channel using WebSocket and push updates from server

Answer

Use the 'spNavigation' API to reload the entire page every 30 seconds

Answer

Trigger the GlideAjax call on mouseover and focus events

Question 6

A large enterprise uses ServiceNow for IT Service Management. They have a custom Service Portal for end-users to submit catalog requests. Recently, mobile users reported that the portal is extremely slow on their devices, while desktop users experience no issues. The portal theme uses many custom CSS animations and high-resolution images. Additionally, the widget client scripts are complex and make multiple GlideAjax calls on page load. The development team wants to optimize mobile performance without redesigning the entire portal. Evaluate the options and select the best course of action.

Accepted Answer

Consolidate multiple GlideAjax calls into a single server-side script and use mobile-optimized images. Option D is correct because reducing unnecessary client-side processing and network calls directly addresses mobile performance bottlenecks. Option A is incorrect because lazy loading helps initial load but does not reduce total number of calls; it may still be heavy. Option B is incorrect because caching only helps repeated visits, not the first load. Option C is incorrect because disabling animations reduces rendering, but the main issue is likely the GlideAjax calls and assets; option D combines reducing server calls and optimizing assets.

Answer

Increase server-side caching for widgets and use a CDN for static assets

Answer

Remove all custom CSS animations and replace high-res images with scalable vector graphics

Answer

Implement lazy loading for images and defer all GlideAjax calls until after page load

Question 7

An organization uses a scheduled data import to load incident data from an external system into ServiceNow. The import set runs successfully, but the transform map sometimes fails to update certain records because the unique key field (sys_id) from the source does not match the sys_id in ServiceNow due to a different format. The team wants to update existing records based on a custom 'external_id' field in the incident table, which is guaranteed to be unique and correctly populated from the source. The target table already has a unique index on 'external_id'. Which configuration should the developer implement to achieve reliable updates?

Accepted Answer

Create a new transform map with coalesce on the 'external_id' field and map the source field to incident.external_id.. Option A is correct because the developer should create a new transform map (or modify the existing one) with coalesce on the 'external_id' field, mapping the source field to the target 'external_id'. This allows the system to match and update records based on that field. Option B is wrong because coalesce on sys_id would not match due to format differences. Option C is not a solution for data import updates. Option D does not address the matching issue.

Answer

Use a database view to join the import set and incident table on the external_id field.

Answer

Modify the existing transform map to use 'update' action and set coalesce on the sys_id field.

Answer

Increase the scheduled import frequency to overwrite the records.

Question 8

A large enterprise is importing 500,000 asset records from an external inventory system using a scheduled data import into the alm_asset table. The transform map uses a coalesce on the 'asset_tag' field to match existing records. The 'asset_tag' field in the target table is a string field with a unique index. The import set table has no unique index on any field. The transform map has 'Enable Duplicate Detection' checked. After the first import, the team notices that many duplicate records were created instead of updating existing ones. There are no errors in the import log. The source data contains only unique asset_tag values. What is the most likely cause of the duplicates?

Accepted Answer

The import set table lacks a unique index on the 'asset_tag' field.. Option B is correct because for duplicate detection to work properly, the import set table must have a unique index on the coalesce field. Without it, the system cannot detect duplicates within the same import set, leading to multiple rows being inserted into the target. Option A is incorrect because the mapping is likely correct if coalesce is set. Option C is incorrect because the checkbox is checked. Option D is incorrect because the source data has unique asset_tag values, so case mismatch is not the issue.

Answer

The source data contains multiple records with the same 'asset_tag' but different case.

Answer

The 'Enable Duplicate Detection' checkbox is not properly configured.

Answer

The coalesce field mapping is incorrectly mapped to the 'asset_tag' field.

Question 9

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.. Option D is correct because 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 10

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 11

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.. Option A is correct because 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 12

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.. Option D is correct because 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 13

An organization has a ServiceNow instance that integrates with an external HR system using a scheduled job that runs every hour. The job uses a REST message to fetch new hire records and creates user accounts in ServiceNow via a transform map. Recently, the number of new hires has increased significantly, and the job now takes over an hour to complete, causing the next job to start before the previous one finishes. The administrator notices that the transform map is using 'Coalesce' set to 'false' because the external system does not provide a unique identifier. The job also creates a large number of intermediate records that are later updated. The administrator wants to optimize the process to prevent overlapping job runs. Which course of action should the administrator take?

Accepted Answer

Set the 'Maximum rows to load' property on the transform map to a value that ensures the job finishes within 60 minutes. Option B is correct because setting the 'Maximum rows to load' property on the transform map limits the number of rows processed per run, ensuring the job completes within the 60-minute window. This prevents overlapping runs by capping the workload, allowing the scheduled job to finish before the next trigger, without requiring changes to the integration logic or external system.

Answer

Increase the scheduled job's interval to run every 2 hours to avoid overlap

Answer

Change the transform map to run asynchronously using a flow triggered by the import set row

Answer

Configure the import set table loader to run in multiple parallel threads to process records faster

Question 14

A small IT department uses ServiceNow for incident management. They have a business rule that runs after insert on the Incident table. The rule is intended to send an email notification to the assignment group whenever a new incident is created. The rule uses a standard "send event" method, and the email notification is set up in the system mail properties. Recently, the group leader noticed that some incidents are not triggering emails. The developer investigates the business rule and confirms that the script executes without errors, but the email is not sent for those specific incidents. The developer checks the email notification configuration and finds that it is set to send to the "assigned user" rather than the "assigned group". After correcting this, the emails start working. However, the developer wants to understand why only some incidents were affected. Which of the following best explains the issue?

Accepted Answer

The email notification was incorrectly configured to send to the user, so only incidents assigned to a specific user triggered emails; incidents assigned to a group had no recipient. Option A is correct because the email notification was configured to send to the 'assigned user' field, which is populated only when an incident is assigned to a specific individual. Incidents assigned directly to a group (with no user assigned) would have an empty 'assigned user' field, causing the notification to have no recipient and thus not be sent. After correcting the configuration to send to the 'assigned group', emails were triggered for all incidents, confirming that the issue was the recipient field mismatch.

Answer

The assignment group did not have any members for those incidents

Answer

The business rule script had a condition that randomly skipped some incidents

Answer

The SMTP server was intermittently down

Question 15

A large enterprise runs ServiceNow on a single instance. They have a custom table 'u_project_task' that stores task details for projects. Each project task has a reference field to the 'u_project' table. The 'u_project' table has approximately 50,000 records, and the 'u_project_task' table has about 2 million records. Users report that opening a project record and viewing its related tasks takes over 30 seconds. The system uses an out-of-box related list to display tasks. The instance has standard hardware resources. The administrator has already confirmed that there are no performance issues with the database server or network. Which course of action should the administrator take to improve the performance of the related list?

Accepted Answer

Create a database index on the 'u_project' field in the 'u_project_task' table to speed up the join.. The performance bottleneck is the database query that joins the large 'u_project_task' table (2M records) with the 'u_project' table on the reference field. Without an index on the 'u_project' field in 'u_project_task', the database must perform a full table scan for each related list query. Creating a database index on that foreign key column allows the database to use an index seek, dramatically reducing query time.

Answer

Archive project tasks older than 1 year to a separate table to reduce the data volume.

Answer

Increase the glide.ui.related_list.max_timeout property to allow the query more time.

Answer

Add additional application nodes to the instance to distribute the load.