SNOW-CAD Working with Data Practice Test 3 — 15 Questions

Question 1

Which TWO methods are commonly used to prevent performance issues when using GlideRecord in a client script?

Accepted Answer

Use GlideAjax to call a script include for server-side processing.. Option D is correct because GlideAjax lets a client script call a Script Include asynchronously on the server, so the heavy GlideRecord query runs server-side without blocking the browser or exposing the record data to the client. Option E is correct because calling setLimit() on the GlideRecord constrains the result set to only the needed number of rows, reducing query cost and payload size, which directly prevents performance degradation. Options A and B are not correct: running GlideRecord directly in a client script and using synchronous queries both force blocking, client-side database access that ServiceNow discourages for performance and security reasons. Option C is not correct because although moving the query to a business rule can be a valid server-side pattern, it is not one of the two methods specifically recommended for preventing performance issues when GlideRecord is used from a client script.

Answer

Use GlideRecord directly in client scripts.

Answer

Use synchronous GlideRecord queries for immediate results.

Answer

Use a business rule instead to perform the query.

Question 2

Which TWO conditions must be met for a transform map to automatically ignore duplicate records during an import?

Accepted Answer

The target table has a unique index on the coalesce field.. Option B is correct because ServiceNow's duplicate detection during transform relies on a unique index existing on the target table's coalesce field; without that index, the transform engine cannot reliably identify and skip records that already exist. Option E is correct because the transform map must have 'Enable Duplicate Detection' set to true, which activates the coalesce-based logic that compares incoming import set rows against existing target records and ignores matches. Option A is incorrect because a unique index on the source table is irrelevant; duplicate detection compares against the target table, not the source. Option C is incorrect because 'Ignore if Empty' only skips mapping when the coalesce value is blank and does not perform duplicate detection. Option D is incorrect because the import set (staging) table does not require a unique index; the uniqueness constraint must be on the target table's coalesce field.

Answer

The source table has a unique index on the coalesce field.

Answer

The coalesce field mapping uses the 'Ignore if Empty' checkbox.

Answer

The import set table has a unique index on the coalesce field.

Question 3

A company is importing user records from a CSV file using an import set. The transform map is configured to update existing records and insert new ones based on the email field. After running the import, they notice that some existing records were not updated even though the email matched. The email field in the target user table is correctly populated and has a unique index. The source CSV file has no obvious formatting issues. The import set runs without errors. What is the most likely cause?

Accepted Answer

The transform map's 'Coalesce' checkbox is not selected on the email field mapping.. The most likely cause is that the 'Coalesce' checkbox is not selected on the email field mapping in the transform map. Coalesce must be enabled for the system to use that field to match existing records in the target table. Without coalesce, the system treats all incoming records as new, so updates will not occur even if the email matches. Option B is incorrect because trailing spaces would affect all matching, not just some records, and the scenario states no formatting issues. Option C is incorrect because indexing affects performance, not matching. Option D is incorrect because the import set table does not need a unique index for target matching; the matching is based on the target table's email field, which has a unique index.

Answer

The source CSV has trailing spaces in the email field.

Answer

The email field in the target table is not indexed.

Answer

The import set table does not have a unique index on the email field.

Question 4

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.. The import set table lacks a unique index on the 'asset_tag' field. For duplicate detection to work properly during an import, the import set table must have a unique index on the coalesce field (here 'asset_tag'). Without that index, the system cannot detect duplicates within the same import set, causing multiple records to be inserted instead of updated. Option A is incorrect because the source data contains unique asset_tag values, so case differences are not the issue. Option B is incorrect because the 'Enable Duplicate Detection' checkbox is checked, so it is configured. Option D is incorrect because the coalesce field mapping is correctly set to 'asset_tag'.

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 5

Which TWO GlideRecord methods can be used to create OR conditions in a query? (Choose two.)

Accepted Answer

GlideRecord.addEncodedQuery(). B is correct because `GlideRecord.addEncodedQuery()` allows you to pass an encoded query string that can include OR conditions using the `^OR` operator. This method is a direct way to construct complex queries with OR logic without chaining multiple method calls. D is correct because `GlideRecord.addOrCondition()` explicitly adds an OR condition to the current query, typically used after an initial `addQuery()` call.

Answer

GlideRecord.ORQuery()

Answer

Using addQuery().addOrCondition() pattern

Answer

GlideRecord.addQuery()

Question 6

Refer to the exhibit. A developer created this data policy on the incident table. What will be the result when a user creates or updates an incident where the caller's name is 'VIP'?

Accepted Answer

The condition is invalid because dot-walking is not supported in data policy conditions.. Data policy conditions in ServiceNow do not support dot-walking to reference fields like 'caller.name'. The condition must use a direct field on the table (e.g., 'caller') or a scripted condition. Since the condition is invalid, the data policy will not execute, and no field behavior changes will occur.

Answer

The condition will always evaluate to true regardless of the caller's name.

Answer

The short_description field will become mandatory for all incidents.

Answer

The data policy will cause a client-side error.

Question 7

A ServiceNow instance is configured with a custom table 'u_asset_history' that stores historical records for asset changes. This table has a reference field 'u_asset' pointing to the 'alm_asset' table, and a date field 'u_change_date'. The application uses a business rule that runs on 'alm_asset' after update, querying the 'u_asset_history' table to find the most recent change for that asset. The business rule is declared as 'async' to improve performance. However, recently the async business rule has been failing frequently with an 'async queue limit reached' error. The instance has default configuration for transaction quotas. The team suspects that the async queue is getting overloaded because many asset updates are happening simultaneously. Which action should the administrator take to resolve this issue while minimizing impact on other processes?

Accepted Answer

Increase the system property 'glide.scope.async.quota' to allow more async transactions.. The error 'async queue limit reached' indicates that the instance's asynchronous transaction queue is full, which is a quota issue. Increasing the system property 'glide.scope.async.quota' raises the maximum number of concurrent asynchronous transactions allowed, directly addressing the overload without changing the business logic or impacting other processes. This is the correct approach because the business rule is already optimized to run asynchronously for performance, and the root cause is a capacity limit, not a query or design flaw.

Answer

Add an index on the 'u_asset' and 'u_change_date' fields in the 'u_asset_history' table to optimize the query.

Answer

Rewrite the business rule to run synchronously with a background script to avoid async queue limits.

Answer

Disable the business rule and implement a scheduled job to perform the same logic during off-peak hours.

Question 8

A developer needs to create a database view that combines the Incident table with the Problem table, showing only incidents where a problem record is linked. The view must allow filtering and sorting in list views. Which configuration step is required when creating the database view?

Accepted Answer

Add a WHERE clause to the database view definition that enforces the join condition between incident.problem_id and problem.sys_id.. A database view is the correct tool for combining data from multiple tables into a single read-only view. It requires a base table and joined tables with a WHERE clause to define the join condition. This allows users to filter and sort on columns from any included table, meeting the requirement for a unified list.

Answer

Create a many-to-many relationship between Incident and Problem using a custom table, then build the view on that table.

Answer

Define a reference field on Incident pointing to Problem, then create a related list on the Problem form.

Answer

Use a scheduled job to populate a custom table with joined data from Incident and Problem.

Question 9

A developer is building a scheduled job that runs nightly on a custom table 'u_vehicle_log'. The job must process every record and update a field 'u_status' based on the record's 'u_mileage'. To minimize server-side memory and avoid loading all records into an array at once, which GlideRecord approach should be used?

Accepted Answer

Use GlideRecord.query() with a while (gr.next()) loop.. Streaming iteration with while (gr.next()) processes records one by one and avoids holding the entire result set in memory, which is critical for a nightly job over a large custom table. Methods that preload the result set, such as setLimit, getRowCount, or chooseWindow, do not provide true streaming and can cause memory issues.

Answer

Use GlideRecord.query() followed by a for loop over gr.getRowCount().

Answer

Use GlideRecord.setLimit() with the total record count, then iterate with while (gr.next()).

Answer

Use GlideRecord.chooseWindow() to page through the records in memory.

Question 10

A developer is asked to create a database view that joins the Incident table and the User table (sys_user) to show incident number, short description, caller name, and caller email. The view must be queryable as a single table and must not duplicate incidents when a caller has multiple roles. Which configuration should the developer use?

Accepted Answer

Create a Database View with Incident as the primary table, add sys_user as a related table, and set the joining condition to incident.caller_id = sys_user.sys_id.. A database view joins a primary table to one or more related tables using explicit joining conditions. To ensure one row per incident, the primary table must be Incident and the related table must be joined on a unique key, such as sys_user.sys_id. This allows the view to be queried like a normal table while exposing caller fields such as name and email.

Answer

Create a table extension where Incident extends sys_user so that caller fields are inherited.

Answer

Create a Database View with sys_user as the primary table and Incident as a related table, joining on sys_user.sys_id = incident.caller_id.

Answer

Create a many-to-many relationship between Incident and sys_user and add a related list to the Incident form.

Question 11

A developer is writing a scheduled job that processes all active incidents and updates a custom field on each. The job must run efficiently and avoid long transaction times. Which approach is recommended?

Accepted Answer

Use a GlideRecord query with a batch update via GlideRecord.updateMultiple() or a background script with chunking.. For bulk updates in a scheduled job, using updateMultiple() or processing in chunks is recommended to avoid long transactions and performance issues. updateMultiple() performs a single database update for all matching records, while chunking breaks the work into smaller transactions. Both methods are efficient and scalable.

Answer

Use a client script to update records when the form is loaded.

Answer

Use GlideRecord with setWorkflow(false) and autoSysFields(false) to reduce overhead, then update in a loop.

Answer

Use a single GlideRecord query with a while loop, calling update() on each record.

Question 12

A developer needs to create a record in the 'incident' table from a client script when a user clicks a button on a form. The client script must set the short description and caller, and then redirect the user to the new incident record. Which method should the developer use to create the incident?

Accepted Answer

Use GlideAjax to call a script include that uses GlideRecord to insert the incident, then use the returned sys_id to redirect.. Client scripts run in the browser and cannot access the database directly. To create a record, the client must use GlideAjax to invoke a server-side script include. The script include uses GlideRecord to insert the incident and returns the sys_id. The client script then redirects using the returned sys_id. This is the standard pattern for creating records from client-side code.

Answer

Use a UI action with a server-side script to insert the incident and then redirect the user.

Answer

Use g_form.submit() to save the current form and then create the incident via a business rule.

Answer

Use GlideRecord from the client script to insert the incident directly.

Question 13

A developer needs to create a new table in ServiceNow to track project milestones. The table should have a reference field to the Project table and a date field for the milestone date. Which data type should be used for the reference field?

Accepted Answer

Reference. In ServiceNow, a reference field is specifically designed to create a relationship between two tables by storing the sys_id of the referenced record. This allows the developer to link a project milestone record to a specific project record in the Project table, enabling dot-walking and data integrity through referential integrity constraints.

Answer

GlideRecord

Answer

Integer

Answer

String

Question 14

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 15

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