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

Question 1

A ServiceNow developer is working on a custom application that tracks employee training completions. The application has a table 'u_training' with fields: u_name (string), u_completion_date (date), u_employee (reference to sys_user). The requirement is to automatically send an email to the employee one week before the training completion date. The developer created a scheduled job that runs daily and queries for trainings where the completion date is exactly 7 days from today. However, the email is not being sent. The developer has verified the email notification is configured correctly and the scheduled job runs without errors. The script uses GlideRecord to query the table. What is the most likely reason the email is not sent?

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

Accepted Answer

The scheduled job runs with a system user that does not have read access to the 'u_training' table.. The most likely reason the email is not sent is that the scheduled job runs with a system user that lacks read access to the 'u_training' table. In ServiceNow, scheduled jobs execute under a specific user context (often the 'system' user or the user who created the job). If that user does not have the required read ACL on the table, the GlideRecord query will return zero records, even though the job runs without errors and the email notification is correctly configured. The developer verified the email configuration and job execution, but did not check the security context of the running job.

Answer

The scheduled job is running in a different time zone than the completion date field.

Answer

The email notification requires an ACL that the system user does not have.

Answer

The 'u_completion_date' field is a date/time field but the script compares using date only.

Question 2

Drag and drop the steps to create a new application in ServiceNow Studio into the correct order.

Accepted Answer

Access Application Creator, then Initiate wizard, then Provide application details, then Choose template, then Create application. The correct sequence starts with accessing the Application Creator, then initiating the wizard, providing application details, choosing a template, and finally creating the application.

Answer

Access Application Creator, then Initiate wizard, then Choose template, then Provide application details, then Create application

Answer

Initiate wizard, then Access Application Creator, then Provide application details, then Choose template, then Create application

Answer

Access Application Creator, then Provide application details, then Initiate wizard, then Choose template, then Create application

Question 3

Drag and drop the steps to create a new Notification in ServiceNow into the correct order.

Accepted Answer

Navigate to Notifications, then click New, then set the table and name, then define the condition, then configure email details, then submit.. The sequence: navigate to Notifications, create new, set table and name, define conditions, configure email details, and submit.

Answer

Navigate to Notifications, then click New, then configure email details, then define the condition, then set the table and name, then submit.

Answer

Navigate to Notifications, then click New, then define the condition, then set the table and name, then configure email details, then submit.

Answer

Click New, then navigate to Notifications, then set the table and name, then define the condition, then configure email details, then submit.

Question 4

Match each ServiceNow acronym to its definition.

Accepted Answer

ITSM: IT Service Management. Correct matches are ITSM: IT Service Management, ITOM: IT Operations Management, ITBM: IT Business Management, and CSM: Customer Service Management. Common confusions occur between ITSM and ITOM definitions.

Answer

ITSM: IT Operations Management

Answer

ITOM: IT Service Management

Question 5

Match each ServiceNow portal widget property to its purpose.

Accepted Answer

Name: A unique identifier used to reference the widget in code. The correct matches are: Name as a unique identifier used in code, ID as the system-assigned sys_id, Roles as access control, and Filter Condition as display condition. Common confusions include swapping Name and ID or mixing Roles with Filter Condition.

Answer

Name: The unique system identifier assigned automatically

Answer

Roles: A condition that determines when the widget is displayed

Question 6

A company needs to retrieve all active users whose department is 'Sales' and who have a manager assigned. They are using GlideRecord. Which script will correctly accomplish this?

Accepted Answer

var gr = new GlideRecord('sys_user'); gr.addQuery('active', true); gr.addQuery('department', 'Sales'); gr.addQuery('manager', 'ISNOTEMPTY'); gr.query();. It correctly adds queries for active = true, department = 'Sales', and manager ISNOTEMPTY, then executes query() to retrieve all matching records. Option A is incorrect because getRow() is not a valid GlideRecord method. Option C lacks the manager condition. Option D incorrectly uses get() which retrieves a single record by sys_id, not a query.

Answer

var gr = new GlideRecord('sys_user'); gr.addQuery('active', true); gr.addQuery('department', 'Sales'); gr.addQuery('manager', 'ISNOTEMPTY'); var rows = gr.getRow();

Answer

var gr = new GlideRecord('sys_user'); gr.addQuery('active', true); gr.addQuery('department', 'Sales'); gr.query();

Answer

var gr = new GlideRecord('sys_user'); gr.get('active', true); gr.get('department', 'Sales'); gr.get('manager', 'ISNOTEMPTY');

Question 7

A developer is working on a catalog client script that references the 'caller_id' field on the 'sc_req_item' table. The caller_id field references the 'sys_user' table. To get the caller's email, which dot-walking syntax is correct?

Accepted Answer

current.caller_id.email. Dot-walking uses the reference field name followed by a dot and the target field. 'caller_id' references the sys_user table, so current.caller_id.email retrieves the caller's email. Option B is wrong because 'caller' is not a field on sc_req_item. Option C is wrong because parentheses are not used in dot-walking. Option D is wrong because you do not need to specify the table name; the reference is automatically followed.

Answer

current.caller.email

Answer

current.caller_id(email)

Answer

current.caller_id.sys_user.email

Question 8

A developer needs to find the number of open incidents assigned to each assignment group. Which GlideAggregate script correctly groups by assignment group and counts?

Accepted Answer

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.addAggregate('COUNT'); ga.groupBy('assignment_group'); ga.query();. The GlideAggregate API requires addQuery() to filter open incidents, then addAggregate('COUNT') to define the aggregation, then groupBy('assignment_group') to specify the grouping field, and finally query() to execute. Option A is wrong because it uses addAggregate('COUNT', 'assignment_group'), which incorrectly passes the grouping field as a second parameter; the correct method is separate groupBy() call. Option B is wrong because getRowCount() returns the number of rows after query(), not the count per group; also missing addAggregate(). Option C is wrong because it uses get() instead of query() and the order of methods is incorrect; get() is for fetching a single record, not aggregate queries.

Answer

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.addAggregate('COUNT', 'assignment_group'); ga.query();

Answer

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.groupBy('assignment_group'); var count = ga.getRowCount();

Answer

var ga = new GlideAggregate('incident'); ga.get('active', true); ga.groupBy('assignment_group'); ga.addAggregate('COUNT');

Question 9

A company is importing data from a CSV into the 'cmdb_ci' table using an Import Set Row transform map. After running the import, some records were not created. The transform map has a 'Coalese' field set to true on the 'name' field. What is the most likely reason for records not being created?

Accepted Answer

The 'Coalese' field is set to true on the 'name' field, so existing records are updated instead of new ones created.. Coalese=true on name means if a record with the same name exists, it will update instead of insert. If the name matches an existing record, no new record is created. Option A is wrong because missing fields trigger errors, not silent failure. Option C is wrong because field mapping issues cause different problems. Option D is wrong because coalesce is for matching, not data type.

Answer

The transform map has incorrect field mappings for the CSV columns.

Answer

The target table has a data policy that prevents insert from import sets.

Answer

The CSV file has missing fields that are mandatory on the target table.

Question 10

A developer is writing a scripted REST API endpoint that returns a list of users. The requirement is to return only users who are in the 'IT' department and have a role of 'itil' or 'admin'. The endpoint uses GlideRecord. Which query condition is most efficient?

Accepted Answer

gr.addQuery('department', 'IT'); gr.addQuery('role', 'itil'); gr.addOrCondition('role', 'admin');. It uses addQuery('department', 'IT') to filter by department, then addQuery('role', 'itil') and addOrCondition('role', 'admin') to create an OR condition for roles. This ensures only users in the IT department with either the itil or admin role are returned efficiently using GlideRecord's built-in OR logic. Option B is wrong because it only returns users with both department IT and role itil, missing those with role admin. Option C is wrong because it's inefficient to query all IT department users then iterate to check role in script; better to use an encoded query or OR condition directly. Option D is wrong because passing 'itil,admin' as a single string would be interpreted as a literal value, not an OR condition; GlideRecord would look for users whose role field equals exactly 'itil,admin', which is incorrect.

Answer

gr.addQuery('department', 'IT'); gr.addQuery('role', 'itil');

Answer

gr.addQuery('department', 'IT'); gr.query(); then iterate and check role.

Answer

gr.addQuery('department', 'IT'); gr.addQuery('role', 'itil,admin');

Question 11

A developer needs to filter a list of records based on a reference field condition using a reference qualifier. Which method is used to define a reference qualifier on a dictionary entry?

Accepted Answer

Reference qual. Reference qualifiers are defined in the 'Reference qual' field on the dictionary entry to filter records based on a reference field condition. Option A is incorrect because 'Reference specification' is used for setting the reference table, not for filtering with a qualifier. Option B is incorrect because 'Default value' sets a default value for the field, not a filter. Option D is incorrect because 'Dependent fields' are used to define field dependencies, not reference qualifiers.

Answer

Reference specification

Answer

Default value

Answer

Dependent fields

Question 12

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 13

Which TWO methods are valid for adding a condition to a GlideRecord query? (Choose two.)

Accepted Answer

addQuery. Options B and C are correct. addQuery is the standard method for adding an AND condition to a GlideRecord query. addOrCondition is a valid method for adding an OR condition. Option A is wrong because addAndCondition is not a valid GlideRecord method. Option D (setCondition) is not a valid method. Option E (addWhere) is not a valid method.

Answer

addAndCondition

Answer

setCondition

Answer

addWhere

Question 14

Which THREE are best practices when working with data imports via Import Sets? (Choose three.)

Accepted Answer

Ensure all target fields are mapped to avoid missing data.. Options A, B, and D are correct. Ensuring all target fields are mapped avoids missing data. Using the coalesce field prevents duplicate records. Using a staging table allows data validation before transforming. Option C is wrong because mapping import set rows directly to the target table without a transform is not a best practice; transforms allow data manipulation and cleansing. Option E is wrong because skipping the transform map would bypass necessary transformations and validations.

Answer

Map import set rows directly to the target table columns without using a transform.

Answer

Skip creating a transform map to speed up the import.

Question 15

A developer is designing a data architecture for a multi-tenant environment where each company's data must be isolated. Which TWO strategies can achieve this? (Choose two.)

Accepted Answer

Implement domain separation.. Options A and E are correct. Domain separation (A) provides built-in data isolation by partitioning data based on domains, ensuring each company sees only its own data. Separate tables for each company (E) physically isolate data at the database level. Option B (ACLs) adds security but does not inherently isolate data in a multi-tenant architecture. Option C (database views) filters data but does not enforce isolation at the application layer. Option D (GlideRecord conditions) relies on developer discipline and is not a robust architectural solution.

Answer

Use access control lists (ACLs) on each record.

Answer

Create database views that filter data by company.

Answer

Add a condition to every GlideRecord query to filter by company.