SNOW-CAD Working with Data — 10 Questions

Question 1

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?

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

Accepted Answer

Highly Confidential. 'Highly Confidential' is the ServiceNow data classification level designed for sensitive personal data such as social security numbers and medical information. This classification enforces mandatory encryption at rest and in transit, strict role-based access controls, and audit logging, aligning with regulatory requirements like GDPR and HIPAA.

Answer

Confidential

Answer

Internal

Answer

Public

Question 2

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?

Accepted Answer

Rewrite the job to use GlideAggregate with query and update in bulk. The script timeout error indicates that the scheduled job is taking too long to process individual record updates. Rewriting the job to use GlideAggregate with bulk update operations reduces the number of database round-trips and processes records in batches, which is the standard approach for handling large data sets in ServiceNow without hitting script timeout limits.

Answer

Add a business rule to run asynchronously for each update

Answer

Increase the timeout value in the scheduled job configuration

Answer

Split the job into multiple smaller jobs running sequentially

Question 3

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?

Accepted Answer

Bar chart. A bar chart is the correct choice because it is ideal for comparing discrete categories (such as days) over a period (the past month), showing the count of incidents per day. In ServiceNow, the 'Report Builder' allows you to create a bar chart with the 'Created on' field grouped by day and the 'Count' aggregation, which directly visualizes the number of incidents created each day.

Answer

List report

Answer

Pie chart

Answer

Line chart

Question 4

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?

Accepted Answer

The GlideRecord query did not include a condition, so it used a default filter that limited results. GlideRecord queries in ServiceNow automatically apply a default filter when no explicit condition is set, typically limiting results to records where the `active` field is `true`. This default behavior, known as the 'active filter,' causes the script to only process a subset of incidents (those that are active) rather than all records in the table, explaining why only some were updated.

Answer

The user running the script lacks write ACL on the table

Answer

The field name used in the update was misspelled

Answer

The script did not call getRowCount() before the loop

Question 5

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?

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 6

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 7

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 8

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?

Accepted Answer

The developer forgot to call the query() method after grouping.. In GlideAggregate, after adding aggregates and grouping, the query() method must be called to execute the query. If it is omitted, no results are returned, which can explain why some categories show zero counts. Option A is incorrect because addAggregate('COUNT', 'category') is not a valid method signature; the correct approach is to use addAggregate('COUNT') and then groupBy('category'). Option B is incorrect because the issue is not related to filtering by active incidents; the query should return all incidents regardless of active status unless specified. Option D is incorrect because GlideAggregate can handle null values in grouped fields; they would typically appear as a separate group or be ignored.

Answer

The developer used addAggregate('COUNT', 'category') instead of addAggregate('COUNT').

Answer

The developer must use addQuery('active', true) to include only active incidents.

Answer

The GlideAggregate cannot handle null values in the grouped field.

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');. The correct query uses addQuery for the department condition and then addQuery plus addOrCondition to express the role filter as 'role = itil OR role = admin'. This builds a single encoded query that the database evaluates server-side, returning only matching records. It is the most efficient because filtering happens in the query, not in script, and the OR is scoped correctly to the role field.

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');