SNOW-CAD Practice Test 24 — 15 Questions

Question 1

The script above fails with HTTP 400 Bad Request. What is the most likely missing configuration?

Accepted Answer

The Content-Type header is not set to application/json. The 400 Bad Request error typically indicates malformed request syntax. A common cause is missing or incorrect Content-Type header. For REST API endpoints expecting JSON payload, the Content-Type header must be set to application/json. Option C is correct because without this header, the server cannot parse the request body and returns 400. Option A is wrong because the HTTP method (POST) is often correct for creating data; PUT would be for updates. Option B is wrong because missing authentication would result in 401 Unauthorized, not 400. Option D is wrong because the Accept header controls response format; setting it to text/plain is not required for JSON requests.

Answer

The HTTP method should be PUT instead of POST

Answer

Missing authentication credentials

Answer

The Accept header should be text/plain

Question 2

Which THREE of the following are valid components of the ServiceNow IntegrationHub?

Accepted Answer

Action steps. Action steps are a core component of IntegrationHub, representing individual, reusable actions that can be composed into a flow to perform specific tasks, such as making API calls or transforming data. They are the building blocks that define the logic and operations within an IntegrationHub flow, enabling complex integrations without custom scripting.

Answer

REST Message

Answer

Data Source

Question 3

A company wants to allow their customers to submit requests via email. The email should create a new record in the 'Request' table. Which component should be used to define the mapping of email fields to the ServiceNow table fields?

Accepted Answer

Inbound Email Action. An Inbound Email Action is the correct component because it defines the mapping of email fields (e.g., subject, body, sender) to ServiceNow table fields (e.g., 'Short description', 'Description', 'Caller'). It uses a script or condition to parse the incoming email and create or update records in a specified table, such as the 'Request' table. This is the standard mechanism for turning an email into a ServiceNow record.

Answer

Email Account

Answer

Inbound Email Script

Answer

Email Notification

Question 4

A company needs to create a new application in ServiceNow Studio. What is the correct first step?

Accepted Answer

Open Studio from the left navigation menu, then click 'Create Application'.. The correct first step because ServiceNow Studio is accessed from the left navigation menu, and then clicking 'Create Application' starts the application creation wizard. Option A is incorrect because navigating to System Applications > Studio is not the standard path; Studio is available directly. Option C is incorrect because the Application Navigator is used for navigating existing applications, not creating new ones. Option D is incorrect because Application Files > New is for creating individual files within an application, not the application itself.

Answer

Navigate to System Applications > Studio and click 'Create Application'.

Answer

Use the Application Navigator to create a new application.

Answer

Go to Application Files > New and select 'Application'.

Question 5

A developer needs to import user records from a CSV file. The CSV contains a field 'department' that should map to a reference field 'department' on the sys_user table. However, the CSV contains department names, not sys_ids. What is the best approach to map the department names to the correct sys_ids?

Accepted Answer

Use a transform script to query the department table and set the reference field.. A transform script allows you to write custom logic to query the department table and retrieve the sys_id based on the department name from the CSV. Option A (default value) would set a static value for all records, not map dynamically. Option B (coalesce) is used for deduplication during import, not for field mapping. Option C (reference qualifier) filters the reference picker in forms but does not affect import mapping.

Answer

Set a default value for the department field in the transform map.

Answer

Use a coalesce field mapping on the department field.

Answer

Add a reference qualifier to the department field in the target table.

Question 6

A developer needs to import data from a CSV file into a custom table. Which ServiceNow module should be used for this task?

Accepted Answer

Import Sets. Import Sets are the correct ServiceNow module for importing data from a CSV file into a custom table. They provide a structured pipeline that maps CSV columns to table fields, with staging tables for validation before final insertion. This is the standard approach for one-time or recurring data imports in ServiceNow.

Answer

Scheduled Jobs

Answer

Update Sets

Answer

Data Source

Question 7

A developer is tasked with creating a reference field on a custom table that shows only 'Windows' servers from the 'cmdb_ci_server' table. What is the proper way to implement this?

Accepted Answer

Define a reference qualifier on the field with the condition 'os_type=Windows'.. In ServiceNow, a reference qualifier is used to filter the records that appear in a reference field's lookup. By defining a reference qualifier with the condition 'os_type=Windows', only Windows servers from the cmdb_ci_server table will be available for selection. Option A is incorrect because a choice list is not a reference field and cannot dynamically filter a reference based on a table. Option B is incorrect because a business rule can modify data but is not the standard mechanism to filter a reference field's picker. Option C is incorrect because a dynamic filter on a form typically applies to related lists or reports, not to the lookup of a reference field.

Answer

Use a choice list instead of a reference field.

Answer

Create a business rule that filters the reference field.

Answer

Create a dynamic filter on the form.

Question 8

A global company is using ServiceNow for IT Service Management. They have an external asset management system that needs to update asset records in ServiceNow in real-time. The integration is implemented using REST API calls from the external system to ServiceNow. Recently, the integration started failing intermittently with HTTP 429 (Too Many Requests) errors. The external system is sending a high volume of update requests (up to 1000 per minute) to the /api/now/table/alm_asset endpoint. The administrator noticed that the instance performance is degraded during peak times. The company wants to resolve the 429 errors while ensuring data is updated as quickly as possible, but without overloading the instance. Which course of action should the administrator take?

Accepted Answer

Implement a queue-based integration using Flow Designer to process updates asynchronously with a controlled rate.. It addresses the root cause of the 429 errors—overwhelming the REST API endpoint with synchronous requests—by decoupling the external system from direct writes. Using Flow Designer with a queue (e.g., via the ServiceNow Queue or a custom table) allows the external system to submit requests asynchronously, and then a scheduled flow or script processes them at a controlled rate (e.g., using a rate limiter or batch size). This ensures data is updated as quickly as possible without exceeding the instance's API rate limits or degrading performance, as the processing is throttled server-side.

Answer

Increase the API rate limit in the instance's system properties.

Answer

Reduce the number of requests from the external system to 500 per minute.

Answer

Switch the authentication method from basic to OAuth to reduce overhead.

Question 9

The business rule above does not set the urgency on new incidents created via web service when the caller's department is IT. What is the most likely reason?

Accepted Answer

The condition uses current.urgency == '' but the field may have a default value of 3. The business rule condition checks if `current.urgency` is an empty string, but the Incident table has a default value of 3 for the urgency field. When a new record is created via web service, the system populates the urgency field with the default value before the business rule runs, so the condition `current.urgency == ''` evaluates to false, and the script never executes to set the urgency.

Answer

The table is not 'Incident' but 'Incident Task'

Answer

The business rule is set to 'before' but web service calls trigger after rules

Answer

The gs.log statement is preventing the script from completing

Question 10

What is the purpose of using the 'Async' option in a business rule?

Accepted Answer

To run the rule in a separate background thread to avoid performance impact.. The 'Async' option in a business rule causes the rule to execute in a separate background thread after the database operation, which avoids performance impact on the main transaction. Therefore, option D is correct. Option A is incorrect because running immediately is the default synchronous behavior, not async. Option B is incorrect because 'Async' is not related to record viewing; that is controlled by the 'Display' condition. Option C is incorrect because async rules still run on updates; they just run asynchronously.

Answer

To run the rule immediately after the database operation.

Answer

To run the rule only when the record is viewed.

Answer

To prevent the rule from running on updates.

Question 11

In a large enterprise environment, the ServiceNow instance is heavily customized. A business rule on the Change Request [change_request] table runs on after update to initiate a complex workflow involving multiple approvals and updates to Configuration Items (CIs). Recently, the IT operations team noticed that the workflow fails to start for many change requests. The system logs show the error: "Business rule script error: Cannot read property 'sys_id' of null". The developer inspects the business rule script and sees the following code snippet:
var task = new GlideRecord('task');
task.get(current.sys_id);
var relatedCI = task.cmdb_ci;
// The rest of the script uses relatedCI to update the CI's status.
The developer knows that change requests are not stored in the task table; they are in change_request. However, the script was written by a previous developer and has been working for months. The developer must fix the script to ensure the workflow starts correctly. Which action should the developer take?

Accepted Answer

Use current.cmdb_ci directly. Best because current is already the change request record, so current.cmdb_ci is directly available. Option A would work but adds unnecessary database query. Option B would prevent the error but not fix the root cause; the script would still fail to get the CI if the record is not in task. Option D would hide the error but not fix the logic.

Answer

Wrap the script in a try-catch block and log the error then return

Answer

Change GlideRecord('task') to GlideRecord('change_request')

Answer

Add a check if (task.isValidRecord()) before accessing cmdb_ci

Question 12

Which script function is used to query the database in a business rule?

Accepted Answer

new GlideRecord('table').query();. In ServiceNow, a business rule must instantiate a new GlideRecord object using the 'new' keyword and then call the query() method on that instance to retrieve records from the database. The syntax 'new GlideRecord('table').query()' properly creates a GlideRecord object for the specified table and executes the query to fetch matching records.

Answer

GlideRecord.query();

Answer

gs.query();

Answer

GlideRecord.newQuery();

Question 13

A developer has a GlideRecord query that retrieves 10,000 records. They need to perform an update on each record. Which approach is most efficient to avoid performance issues?

Accepted Answer

Use setWorkflow(false) and setAutoSysFields(false) before updating each record.. Using `setWorkflow(false)` disables business rules and `setAutoSysFields(false)` prevents automatic updates of system fields (like `sys_updated_by` and `sys_updated_on`), significantly reducing database write overhead and improving performance when updating many records. Option A is wrong because GlideRecord's batch mode alone does not disable workflows or system fields; business rules still execute. Option C is wrong because using multiple queries increases the number of database operations and overall load. Option D is wrong because `setLimit(100)` restricts the query to only 100 records, so updates would miss the remaining 9,900 records.

Answer

Use GlideRecord's batch mode without any modifications.

Answer

Use multiple GlideRecord queries to process records in batches.

Answer

Use setLimit(100) and run the script multiple times.

Question 14

The ACL is meant to allow users to read an incident only if they are the manager of the assigned user. However, users who are not managers can also read the incident. What is the flaw?

Accepted Answer

The script should include an else statement that sets answer = false. When an ACL condition script runs, it must explicitly set the answer variable to true or false. If the script lacks an else statement that sets answer = false, the script returns undefined (or the last evaluated expression) for non-matching conditions, which ServiceNow treats as true, inadvertently granting read access to unauthorized users. Adding an else statement that sets answer = false ensures that only users who satisfy the manager condition are granted read access.

Answer

The operation should be 'write' not 'read'

Answer

The table should be 'sys_user'

Answer

The condition in the ACL condition field should be removed and replaced with the script

Question 15

An organization has a ServiceNow instance that integrates with a third-party monitoring tool using a webhook. The monitoring tool sends HTTP POST requests to a Scripted REST API in ServiceNow to create incidents automatically. Recently, the monitoring tool started sending duplicate requests due to a retry mechanism. The developer wants to ensure that duplicate incidents are not created. The Scripted REST API currently creates a new incident record for every request without checking for duplicates. The request payload includes a unique 'alert_id' field. The developer decides to implement idempotency logic. Which approach should the developer use to prevent duplicate incident creation?

Accepted Answer

In the Scripted REST API, use a GlideRecord to query the incident table with a condition on the 'alert_id' field before inserting a new record; if a record exists, skip creation and return the existing record's sys_id. It implements idempotency directly within the Scripted REST API by querying the incident table using GlideRecord with a condition on the unique 'alert_id' field before inserting. If a record with that 'alert_id' already exists, the API skips creation and returns the existing sys_id, ensuring no duplicate incidents are created despite duplicate webhook requests.

Answer

Create a GlideAggregate script that counts incidents with the same 'alert_id'; proceed only if count is zero

Answer

Add a before-insert business rule on the incident table that checks for duplicates using the 'alert_id' field

Answer

Use a flow in Flow Designer triggered by the REST API that creates an incident only if the 'alert_id' is not already present in a custom table