Working with Data practice questions

A developer runs a GlideAggregate to count the number of incidents per category. The query returns unexpected results: some categories show zero counts but should have incidents. What is the most likely cause?

Trap 1: The developer used addAggregate('COUNT', 'category') instead of…

False. The correct way to count incidents per category is to use addAggregate('COUNT', 'category'), which groups by the 'category' field and counts records in each group. Using addAggregate('COUNT') without a field would count all records without grouping, not per category. Therefore, using the two-argument form is not a mistake; it is the correct approach.

Trap 2: The developer must use addQuery('active', true) to include only…

False. There is no requirement to filter only active incidents. The unexpected zero counts are not related to an added query for active incidents. The issue is likely that the query() method was not called, causing no results to be returned.

Trap 3: The GlideAggregate cannot handle null values in the grouped field.

False. GlideAggregate can handle null values in the grouped field; they are grouped together and counted as a separate group. The unexpected zero counts are not due to null handling but rather due to forgetting to call the query() method.

A
The developer used addAggregate('COUNT', 'category') instead of addAggregate('COUNT').
Why wrong: False. The correct way to count incidents per category is to use addAggregate('COUNT', 'category'), which groups by the 'category' field and counts records in each group. Using addAggregate('COUNT') without a field would count all records without grouping, not per category. Therefore, using the two-argument form is not a mistake; it is the correct approach.
B
The developer must use addQuery('active', true) to include only active incidents.
Why wrong: False. There is no requirement to filter only active incidents. The unexpected zero counts are not related to an added query for active incidents. The issue is likely that the query() method was not called, causing no results to be returned.
C
The developer forgot to call the query() method after grouping.
Without query(), no records are processed.
D
The GlideAggregate cannot handle null values in the grouped field.
Why wrong: False. GlideAggregate can handle null values in the grouped field; they are grouped together and counted as a separate group. The unexpected zero counts are not due to null handling but rather due to forgetting to call the query() method.

Question 2mediummultiple choice

An administrator wants to create a database view that joins the 'incident' and 'task' tables to show incident details with task assignments. Which table is the most appropriate base table?

Trap 1: incident

Incident is a child table; a view based on incident cannot include records from the parent task table.

Trap 2: sys_attachment

Unrelated table.

Trap 3: task_assignment

No standard table with that name.

A
incident
Why wrong: Incident is a child table; a view based on incident cannot include records from the parent task table.
B
sys_attachment
Why wrong: Unrelated table.
C
task_assignment
Why wrong: No standard table with that name.
D
task
Task is the parent table; a view on task can include incidents and other task records.

Question 3mediummultiple choice

A service desk manager wants to create a report that shows the number of incidents assigned to each support group over the past month. The manager wants the report to update automatically every week and be emailed to the team leads. The developer needs to implement this efficiently without creating custom tables or scheduled jobs. Which approach should the developer take?

Trap 1: Create a database view that aggregates the data and schedule a data…

Incorrect: Database views are for real-time querying, not scheduled reporting; data export would not achieve the desired automatic email delivery.

Trap 2: Create a scheduled job that runs a report and emails the results.

This option fails because the question explicitly states the developer needs to implement the solution "without creating custom tables or scheduled jobs". Therefore, proposing a scheduled job directly violates a core requirement. However, creating a scheduled job to run a report and email results is a standard and effective method for automating recurring reporting tasks in ServiceNow when the use of scheduled jobs is permissible. It offers precise control over execution timing and distribution.

Trap 3: Create a transform map to import the incident data into a custom…

Incorrect: This introduces unnecessary complexity and data duplication; the standard report on the incident table is sufficient.

A
Create a database view that aggregates the data and schedule a data export.
Why wrong: Incorrect: Database views are for real-time querying, not scheduled reporting; data export would not achieve the desired automatic email delivery.
B
Create a scheduled job that runs a report and emails the results.
Why wrong: This option fails because the question explicitly states the developer needs to implement the solution "without creating custom tables or scheduled jobs". Therefore, proposing a scheduled job directly violates a core requirement. However, creating a scheduled job to run a report and email results is a standard and effective method for automating recurring reporting tasks in ServiceNow when the use of scheduled jobs is permissible. It offers precise control over execution timing and distribution.
C
Create a report using the 'Report' module and schedule it to run weekly with email delivery.
Correct: The Report module allows scheduling and emailing of reports directly, meeting all requirements efficiently.
D
Create a transform map to import the incident data into a custom table and then report.
Why wrong: Incorrect: This introduces unnecessary complexity and data duplication; the standard report on the incident table is sufficient.

Question 4mediummultiple choice

A company is building a ServiceNow application to manage employee onboarding. They need to store personal data like social security numbers (SSNs) and medical information. Which data classification scheme should they apply to these fields to ensure proper encryption and access controls?

Trap 1: Confidential

Confidential is for business-sensitive data, not the highest level.

Trap 2: Internal

Internal is for general internal use without special protection.

Trap 3: Public

Public is for non-sensitive data accessible to all.

A
Confidential
Why wrong: Confidential is for business-sensitive data, not the highest level.
B
Internal
Why wrong: Internal is for general internal use without special protection.
C
Highly Confidential
Correct, this is the highest classification for sensitive personal data.
D
Public
Why wrong: Public is for non-sensitive data accessible to all.

Question 5hardmultiple choice

An administrator notices that a scheduled job, 'Update Asset Status', fails every night with a 'Script timeout' error. The job updates a large number of records in the Asset table. Which approach should the administrator take to resolve the timeout issue?

Trap 1: Add a business rule to run asynchronously for each update

Business rules run on each record, not solving the timeout of the job itself.

Trap 2: Increase the timeout value in the scheduled job configuration

This only delays the failure, not solving the root cause.

Trap 3: Split the job into multiple smaller jobs running sequentially

Splitting the job into multiple sequential smaller jobs does not address the root cause of the script timeout, which is the total execution duration exceeding the platform’s governor limit for a single script. Running jobs sequentially still accumulates the same total processing time across the sequence, so the timeout will merely shift to whichever individual job takes longest. This approach is tempting because it is a standard pattern for breaking large data operations into manageable batches to avoid transaction size limits or record-locking contention, and it would be correct if the error were a 'Script too large' or a database deadlock rather than a timeout.

A
Add a business rule to run asynchronously for each update
Why wrong: Business rules run on each record, not solving the timeout of the job itself.
B
Increase the timeout value in the scheduled job configuration
Why wrong: This only delays the failure, not solving the root cause.
C
Split the job into multiple smaller jobs running sequentially
Why wrong: Splitting the job into multiple sequential smaller jobs does not address the root cause of the script timeout, which is the total execution duration exceeding the platform’s governor limit for a single script. Running jobs sequentially still accumulates the same total processing time across the sequence, so the timeout will merely shift to whichever individual job takes longest. This approach is tempting because it is a standard pattern for breaking large data operations into manageable batches to avoid transaction size limits or record-locking contention, and it would be correct if the error were a 'Script too large' or a database deadlock rather than a timeout.
D
Rewrite the job to use GlideAggregate with query and update in bulk
Bulk database operations reduce script execution time.

Question 6easymultiple choice

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?

Trap 1: GlideRecord

GlideRecord is a server-side class, not a field type.

Trap 2: Integer

Integer stores numbers, not references.

Trap 3: String

String stores text, not a relationship.

A
GlideRecord
Why wrong: GlideRecord is a server-side class, not a field type.
B
Integer
Why wrong: Integer stores numbers, not references.
C
String
Why wrong: String stores text, not a relationship.
D
Reference
Reference field links to a record in another table.

Question 7mediummultiple choice

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?

Trap 1: No action

No action does nothing, leaving orphan records.

Trap 2: Restrict delete

Restrict prevents deletion of parent if children exist.

Trap 3: Set null on delete

This sets the reference to null, not deleting the child records.

A
Cascade delete
Cascade delete removes child records when parent is deleted.
B
No action
Why wrong: No action does nothing, leaving orphan records.
C
Restrict delete
Why wrong: Restrict prevents deletion of parent if children exist.
D
Set null on delete
Why wrong: This sets the reference to null, not deleting the child records.

Question 8hardmultiple choice

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?

Trap 1: Create a business rule on the table to check the role and reject…

Business rules run after submission, so invalid data can be saved momentarily.

Trap 2: Use a client script to validate the selection before form submission

Client scripts can be bypassed by direct API calls.

Trap 3: Configure an ACL on the reference field to restrict write access

ACLs control permissions, not the list of selectable values.

A
Create a business rule on the table to check the role and reject invalid selections
Why wrong: Business rules run after submission, so invalid data can be saved momentarily.
B
Add a reference qualifier on the field to filter users with the 'instructor' role
Reference qualifiers restrict the list dynamically.
C
Use a client script to validate the selection before form submission
Why wrong: Client scripts can be bypassed by direct API calls.
D
Configure an ACL on the reference field to restrict write access
Why wrong: ACLs control permissions, not the list of selectable values.

Question 9easymultiple choice

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

Trap 1: Scheduled Jobs

Scheduled jobs run scripts automatically, not for importing files.

Trap 2: Update Sets

Update Sets capture application changes, not data import.

Trap 3: Data Source

Data Sources are configurations within Import Sets.

A
Scheduled Jobs
Why wrong: Scheduled jobs run scripts automatically, not for importing files.
B
Update Sets
Why wrong: Update Sets capture application changes, not data import.
C
Import Sets
Import Sets allow loading data from files and mapping fields.
D
Data Source
Why wrong: Data Sources are configurations within Import Sets.

Question 10mediummultiple choice

An admin wants to create a report showing the number of incidents created each day for the past month. Which type of report should be used?

Trap 1: List report

List reports show raw data, not aggregated counts.

Trap 2: Pie chart

Pie charts show proportions, not counts over time.

Trap 3: Line chart

A line chart plots continuous data points over a time interval, but the requirement is to count discrete daily totals for a fixed 30-day period. The correct option uses a bar chart, which groups each day as a distinct category, whereas a line chart implies a trend between intervals and can misrepresent non-continuous daily counts. It is tempting because line charts are commonly used for time-series data, such as tracking incident volume over months or years where interpolation between points is meaningful.

A
List report
Why wrong: List reports show raw data, not aggregated counts.
B
Pie chart
Why wrong: Pie charts show proportions, not counts over time.
C
Line chart
Why wrong: A line chart plots continuous data points over a time interval, but the requirement is to count discrete daily totals for a fixed 30-day period. The correct option uses a bar chart, which groups each day as a distinct category, whereas a line chart implies a trend between intervals and can misrepresent non-continuous daily counts. It is tempting because line charts are commonly used for time-series data, such as tracking incident volume over months or years where interpolation between points is meaningful.
D
Bar chart
Bar chart effectively shows counts per day.

Question 11hardmultiple choice

A developer writes a business rule that queries the 'incident' table using GlideRecord. The script loops through all incidents and updates a field. After running, the developer notices that only a subset of records were updated. What is the most likely cause?

Trap 1: The user running the script lacks write ACL on the table

Lack of ACL would cause an error, not a silent skip.

Trap 2: The field name used in the update was misspelled

A typo would cause a script error, not a partial update.

Trap 3: The script did not call getRowCount() before the loop

getRowCount() is not required for correct iteration.

A
The user running the script lacks write ACL on the table
Why wrong: Lack of ACL would cause an error, not a silent skip.
B
The GlideRecord query did not include a condition, so it used a default filter that limited results
Without an explicit query, GlideRecord may apply a default filter (e.g., active=true) or system limit.
C
The field name used in the update was misspelled
Why wrong: A typo would cause a script error, not a partial update.
D
The script did not call getRowCount() before the loop
Why wrong: getRowCount() is not required for correct iteration.

Question 12mediummulti select

Which TWO statements about Database Views in ServiceNow are correct?

Trap 1: Database Views improve write performance by reducing the number of…

Views are for reads, not writes.

Trap 2: Database Views are stored as separate physical tables.

Views are virtual, not physical.

Trap 3: Database Views allow direct updates to the underlying tables…

Views are read-only in ServiceNow.

A
Database Views improve write performance by reducing the number of tables.
Why wrong: Views are for reads, not writes.
B
Database Views are stored as separate physical tables.
Why wrong: Views are virtual, not physical.
C
Database Views allow direct updates to the underlying tables through the view.
Why wrong: Views are read-only in ServiceNow.
D
Database Views can be used to join multiple tables for reporting purposes.
Correct, they are used for reporting across tables.
E
Database Views can include fields from parent and child tables.
Views can include fields from related tables.

Question 13hardmulti select

Which THREE conditions must be met for a user to successfully see a record in a ServiceNow list view?

Trap 1: The user has write permission on the table.

Write permission is not needed for viewing.

Trap 2: The user has configured a personalized list view for the table.

Personalized views are optional.

A
The user has write permission on the table.
Why wrong: Write permission is not needed for viewing.
B
The user has read permission on the table via an ACL.
Read ACL is necessary to view records.
C
The user has configured a personalized list view for the table.
Why wrong: Personalized views are optional.
D
The user has a role that grants access to the table, if role-based access is configured.
Roles are often required for access.
E
The record is not excluded by a condition in the application's default filter.
Default filters can hide records from list views.

Question 14easymulti select

Which TWO data types are available in ServiceNow for storing date and time values?

Trap 1: Time

Time is not a standalone field type.

Trap 2: Duration

Duration stores a length of time.

Trap 3: Timestamp

Timestamp is not a field type in ServiceNow.

A
Time
Why wrong: Time is not a standalone field type.
B
Date/Time
Stores date and time.
C
Duration
Why wrong: Duration stores a length of time.
D
Date
Stores date only.
E
Timestamp
Why wrong: Timestamp is not a field type in ServiceNow.

Question 15hardmultiple choice

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?

Trap 1: Archive project tasks older than 1 year to a separate table to…

Archiving is a long-term solution and may not address the immediate performance issue.

Trap 2: Increase the glide.ui.related_list.max_timeout property to allow…

Timeout increase only masks slowness, does not improve query speed.

Trap 3: Add additional application nodes to the instance to distribute the…

Horizontal scaling may not help if the bottleneck is database query performance.

A
Archive project tasks older than 1 year to a separate table to reduce the data volume.
Why wrong: Archiving is a long-term solution and may not address the immediate performance issue.
B
Create a database index on the 'u_project' field in the 'u_project_task' table to speed up the join.
An index on the foreign key can significantly improve query performance for related lists.
C
Increase the glide.ui.related_list.max_timeout property to allow the query more time.
Why wrong: Timeout increase only masks slowness, does not improve query speed.
D
Add additional application nodes to the instance to distribute the load.
Why wrong: Horizontal scaling may not help if the bottleneck is database query performance.

Question 16mediummultiple choice

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?

Trap 1: The scheduled job is running in a different time zone than the…

Time zone differences could affect date comparison, but the job uses system date.

Trap 2: The email notification requires an ACL that the system user does…

Email notifications typically use the sender's context, but the job's user may lack send permission.

Trap 3: The 'u_completion_date' field is a date/time field but the script…

If the field is date-only, comparison works. If date/time, the script may need to handle time portion, but the job still should find records if dates match.

A
The scheduled job is running in a different time zone than the completion date field.
Why wrong: Time zone differences could affect date comparison, but the job uses system date.
B
The scheduled job runs with a system user that does not have read access to the 'u_training' table.
If the job's user lacks read ACL, the query returns no records.
C
The email notification requires an ACL that the system user does not have.
Why wrong: Email notifications typically use the sender's context, but the job's user may lack send permission.
D
The 'u_completion_date' field is a date/time field but the script compares using date only.
Why wrong: If the field is date-only, comparison works. If date/time, the script may need to handle time portion, but the job still should find records if dates match.

Question 17mediumdrag order

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Access Application Creator, then Initiate wizard, then Choose…

This is incorrect because you must provide application details before choosing a template; the template selection usually comes after you've entered basic info.

Trap 2: Initiate wizard, then Access Application Creator, then Provide…

This is incorrect because you cannot initiate the wizard before accessing the Application Creator; the creator is the entry point.

Trap 3: Access Application Creator, then Provide application details, then…

This is incorrect because the wizard initiation must occur before providing details; the wizard prompts you for details.

A
Access Application Creator, then Initiate wizard, then Provide application details, then Choose template, then Create application
This is the correct sequence: first you access the Application Creator, then start the wizard, fill in details, pick a template, and finally create the app.
B
Access Application Creator, then Initiate wizard, then Choose template, then Provide application details, then Create application
Why wrong: This is incorrect because you must provide application details before choosing a template; the template selection usually comes after you've entered basic info.
C
Initiate wizard, then Access Application Creator, then Provide application details, then Choose template, then Create application
Why wrong: This is incorrect because you cannot initiate the wizard before accessing the Application Creator; the creator is the entry point.
D
Access Application Creator, then Provide application details, then Initiate wizard, then Choose template, then Create application
Why wrong: This is incorrect because the wizard initiation must occur before providing details; the wizard prompts you for details.

Question 18mediumdrag order

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Navigate to Notifications, then click New, then configure email…

This is incorrect because you cannot configure email details before setting the table and name; the table determines which fields are available for conditions and email templates.

Trap 2: Navigate to Notifications, then click New, then define the…

This is incorrect because the condition depends on the table being selected first; you cannot define conditions without knowing which table the notification applies to.

Trap 3: Click New, then navigate to Notifications, then set the table and…

This is incorrect because you must navigate to the Notifications module first before creating a new notification; clicking New without navigating is not possible in the platform.

A
Navigate to Notifications, then click New, then set the table and name, then define the condition, then configure email details, then submit.
This is the correct order because you must first navigate to the Notifications module, create a new notification, then define its basic properties (table and name), set conditions for when it triggers, configure the email content, and finally save it.
B
Navigate to Notifications, then click New, then configure email details, then define the condition, then set the table and name, then submit.
Why wrong: This is incorrect because you cannot configure email details before setting the table and name; the table determines which fields are available for conditions and email templates.
C
Navigate to Notifications, then click New, then define the condition, then set the table and name, then configure email details, then submit.
Why wrong: This is incorrect because the condition depends on the table being selected first; you cannot define conditions without knowing which table the notification applies to.
D
Click New, then navigate to Notifications, then set the table and name, then define the condition, then configure email details, then submit.
Why wrong: This is incorrect because you must navigate to the Notifications module first before creating a new notification; clicking New without navigating is not possible in the platform.

Question 19mediummatching

Match each ServiceNow acronym to its definition.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Configuration Management Database

Customer Service Management

IT Service Management

Human Resources Service Delivery

Governance, Risk, and Compliance

Trap 1: ITSM: IT Operations Management

Incorrect — this definition belongs to ITOM, which focuses on managing IT infrastructure and operations.

Trap 2: ITOM: IT Service Management

Incorrect — this definition belongs to ITSM, not ITOM.

A
ITSM: IT Service Management
ITSM is the core framework for managing and delivering IT services, including incident, problem, and change management.
B
ITSM: IT Operations Management
Why wrong: Incorrect — this definition belongs to ITOM, which focuses on managing IT infrastructure and operations.
C
ITOM: IT Operations Management
ITOM handles the day-to-day management of IT infrastructure, including monitoring, discovery, and orchestration.
D
ITOM: IT Service Management
Why wrong: Incorrect — this definition belongs to ITSM, not ITOM.
E
ITBM: IT Business Management
ITBM focuses on aligning IT with business goals through project portfolio management, demand management, and resource planning.
F
CSM: Customer Service Management
CSM extends ServiceNow to external customer service, managing cases, knowledge, and service portals for customers.

Question 20mediummatching

Match each ServiceNow portal widget property to its purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Runs on the client browser

Runs on the server during rendering

Defines the widget's HTML structure

Styles the widget

Defines widget dependencies on other widgets

Trap 1: Name: The unique system identifier assigned automatically

Incorrect — this definition describes the ID property, not Name. Name is a human-readable identifier.

Trap 2: Roles: A condition that determines when the widget is displayed

Incorrect — this definition describes the Filter Condition property, not Roles.

A
Name: A unique identifier used to reference the widget in code
The Name property is a human-readable identifier used to reference the widget in scripts and conditions.
B
ID: The unique system identifier assigned automatically
The ID is a sys_id generated automatically by the system and uniquely identifies the widget record.
C
Roles: Defines which roles can view the widget
The Roles property restricts visibility of the widget to users with specified roles.
D
Filter Condition: A condition that determines when the widget is displayed
The Filter Condition property specifies a condition using conditions language, determining whether the widget appears on the portal page.
E
Name: The unique system identifier assigned automatically
Why wrong: Incorrect — this definition describes the ID property, not Name. Name is a human-readable identifier.
F
Roles: A condition that determines when the widget is displayed
Why wrong: Incorrect — this definition describes the Filter Condition property, not Roles.