To ensure data consistency across the entire ServiceNow platform, developers use Data Policies .

1. The Scope of Data Policies:

Data Policies enforce requirements on data payload at the database engine level (server-side). Because they operate at this deep layer, they act as a universal gatekeeper. It does not matter if a user types the data into a browser UI Form, if the data is bulk-loaded via an Import Set, or if it is pushed in via a REST/SOAP Web Service API—the Data Policy will evaluate the data. If the data fails the policy (for example, a mandatory field is missing), the database will reject the insert or update.

2. Comparison to UI Policies:

This is the critical distinction developers must know. UI Policies only run on the client-side (in the browser). If you make a field mandatory with a UI policy, a user on the form cannot submit it. However, an external API could easily bypass that UI Policy and insert a blank record. A Data Policy prevents that bypass.

3. Why the other options are incorrect:

B, C, and D: " Write Policies, " " Data Integrity Policies, " and " Data Submission Policies " are not standard ServiceNow platform features or terminology.

ServiceNow usesImport Setsto bring data from various sources (such as CSV files, Excel spreadsheets, or external databases) into ServiceNow tables. Import Sets provide a flexible way to map incoming data into ServiceNow’s database structure.

A. Import Set

Import Setsare atemporary staging tablewhere external data is first loaded.

ATransform Mapis then used to map and transfer data from the Import Set table into thetarget table(e.g., Incident, Change Request, CMDB, etc.).

Common use cases:

Importinguser recordsfrom an external HR system.

MigratingCI datainto the CMDB.

Loadinghistorical incident recordsinto ServiceNow.

B. Update Set

Update Setsare used formoving customizations(such as UI changes, workflows, or scripts) between instances,not for importing data.

C. Data Pack

No such standard featurein ServiceNow called " Data Pack. "

Possibly confused withData Sources, which define external data locations but do not perform imports themselves.

D. Transform Set

Incorrect terminology—ServiceNow usesTransform Maps, not " Transform Sets. "

Transform Mapsdefine how data in anImport Setis mapped to target tables, but the import process itself is handled byImport Sets.

Tofilter a long list of recordsand find those whereShort Description contains " email " , the best practice is to use thecolumn searchfeature:

Click the List Magnifier (???? )to open thecolumn searchoptions.

In the " Short Description " column search box, type:

Steps to Filter a List by " email " in Short Description:email

Press Enterto apply the filter.

This methodautomatically applies a " contains " filter, meaning it will showany records where " email " appears anywhere in the Short Description field.

A. Click List Magnifier to expand column search, on Short Description, type %email, click enter →Incorrect

% (percent sign) is not a valid wildcardin ServiceNow ' s list filters.

C. On Search box, select text, type email, click enter →Incorrect

Theglobal search box searches across multiple tables, not just the Short Description field.

D. Click List Magnifier to expand column search, on Short Description type ' email, click enter →Incorrect

Single quotes ( ' email ' ) are not requiredin column searches.

Why Other Options Are Incorrect?

Using List Filters in ServiceNow

ServiceNow Search Operators

Official ServiceNow Documentation Reference:

Business Rules are server-side scripts that run when a record is displayed, inserted, updated, or deleted. The " When " field on the Business Rule form determines exactly when the logic runs relative to the database operation. The four valid options are:

Display: Runs before the form is presented to the user (used to pass data from server to client via the Scratchpad).

Before: Runs after the user submits the form but before the data is written to the database. (Ideal for validation or updating the current record).

After: Runs immediately after the data is written to the database. (Ideal for updating related records).

Async: Runs after the data is written, but is processed by a background scheduler rather than immediately. (Ideal for external integrations or heavy calculations that shouldn ' t block the user ' s screen).

" Load, " " Change, " " Click, " and " Submit " are typically associated with Client Scripts (onLoad, onChange, onSubmit) or UI Actions, not Business Rules.

In ServiceNow, when viewing alist view, you can easily filter out specific values byright-clicking on the field value and selecting " Filter Out " . This action dynamically updates the filter to exclude records with that value.

Navigate to theIncident List.

Locate a record withState = Resolved.

Right-clickon the " Resolved " value in theStatecolumn.

Select " Filter Out " from the context menu.

The list automatically refreshes, showing only incidentsexcluding " Resolved " .

A. On the list of records, locate the right-click on the Resolved value, select Exclude.

" Exclude " isnot an optionin the ServiceNow list filter menu. The correct option is " Filter Out " .

B. Click Funnel icon, click AND, Select Resolved, is Not State click Run.

Thefunnel iconopens the filter panel, but this answer is unnecessarily complex.Right-clicking and filtering out is faster.

C. On state column title, right-click, select Filter Out > Resolved.

Youcannot right-click the column titleto filter out a specific value; you must right-click on aspecific field value.

D. On Search, select State, type not Resolved, press enter.

The correct syntax in the filter bar is " State != Resolved " , butright-clicking is a more user-friendly method.

ServiceNow Filtering and List Views

ServiceNow CSA Training Module: " Working with Lists and Filters "

Steps to Exclude Incidents with the State " Resolved " :Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow Catalog Item Workflows, anapproval processoften includes aManager Approval step, which typically requires the requester ' smanager(as defined in thesys_userrecord) to approve the request.

IfBob Smith ' s user record does not have a manager specified, the systemcannot determine who should approve the request, which may result in the approval step beingskipped.

A. There is a business rule, excluding Bob Smith from any approvals.

While business rules can affect approvals, it isunlikelythat a rule would exist specifically to exclude Bob Smith unless explicitly configured, which is uncommon.

B. Bob Smith does not have a delegate set up on his account.

Delegates areoptionaland only apply when a manager is unavailable. This does not affect whether the approval is skipped.

D. The manager does not have a delegate assigned.

A delegate only comes into play if an approveris out of officeor unavailable. This does not impact whether an approval isskipped entirely.

E. Bob Smith is a VIP.

Being marked as aVIPdoes not automatically bypass approval workflows. Approval processes follow defined rules in workflow configurations.

Flow Designerin ServiceNow allows users to automate workflows withactions. Actions are reusable operations that execute tasks like creating records, sending notifications, and approvals.

A. Wait for Condition

This actionpauses the flowuntil a specified condition is met.

Example:Wait until an Incident is resolved before proceeding with follow-up actions.

B. Ask for Approval

Sends anapproval requestto a user or group.

Example:Ask a manager for approval before escalating an incident.

C. Create Record

Creates a new record in any table.

Example:Create a new Change Request when an Incident reaches a critical priority.

F. Look Up Record

Retrieves records based on specified criteria.

Example:Find the user’s manager based on the requested user’s ID.

D. Wait for Match

There isnocore Flow Designer action called " Wait for Match. "

This is likely confused with " Wait for Condition " , which is the correct action.

E. Look for Update

There isnostandard action named " Look for Update. "

Instead, flows use " Wait for Condition " or " Look Up Record " to detect changes.

The icon highlighted in the image is theReference Icon(iinside a circle). It is used forReference fieldsin ServiceNow forms.

AReference fieldlinks to a record in another table (e.g., theCallerfield in anIncidentform references thesys_usertable).

Clicking theReference Icon (i)opens apreviewof the referenced recordwithout navigating away from the form.

This feature is helpful forquickly viewing user details, CI information, or related records.

A. Drilldown– This term is not used for form field behavior in ServiceNow; " drilldowns " are usually associated with reports.

B. Lookup– While lookups are used to search for values, they do not display previews of referenced records.

C. Quickview– This is not a defined ServiceNow field type.

D. Preview– While the icon allows previewing, the correct term isReference field, not " Preview field. "

E. Snapshot– No such field type exists in ServiceNow.

ServiceNow Reference Fields & Preview

ServiceNow CSA Training Module: " Configuring Forms and Fields – Reference Fields and Their Behavior "

How Reference Fields Work:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow, afilter conditionis used toquery data from tables. It consists of three main components:

1. Column (Field)Represents the database column (or field) that is being filtered.

Example:Priority,State,Assigned To

In ServiceNow UI, this appears as thefirst dropdownin a filter condition.

2. OperatorDefines the comparison condition for the filter.

Examples:is,is not,greater than,contains,starts with

In ServiceNow UI, this appears as themiddle dropdownin a filter condition.

3. ValueSpecifies the criteria being matched against the column.

Example:High,Closed,John Doe

In ServiceNow UI, this is thethird input fieldin a filter condition.

Example of a Filter Condition in ServiceNow UI:Column (Field)

Operator

Value

Priority

is

High

State

is not

Resolved

This filter will returnrecords where:

ThePriorityfield is set toHigh

TheStatefield is NOTResolved

B. Match CriteriaIncorrect–No such term exists in ServiceNow filters.

C. FieldIncorrect– " Field " is another word for " Column " , but " Column " is the correct term in ServiceNow filter conditions.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Filtering Data???? How to Create Filters in ServiceNow

ServiceNow Docs – Query Builder and Operators???? Building Filter Queries

Official ServiceNow Documentation References:

Toaccess reportsin ServiceNow, users navigate to:

???? Reports > View / Run

Displaysall reports availableto the user.

Allowsrunning, modifying, and creating new reports(if permissions allow).

Users canfilter reports by category(e.g., incidents, requests, changes).

Key Features of " View / Run " Module:

B. Reports > Homepage →Incorrect

No such module named " Reports > Homepage. "

C. Self-Service > My Reports →Incorrect

TheSelf-Service moduleis primarily for end users, not for accessing platform-wide reports.

D. Report > Overview →Incorrect

" Overview " providesreporting summariesbut does not list all available reports.

Why Other Options Are Incorrect?

Running and Managing Reports

Official ServiceNow Documentation Reference:

✔Common Services Data Model (CSDM)is aServiceNow best-practice frameworkthatstandardizes how IT services, applications, and infrastructure are structured in the CMDB. It provides ablueprintfor aligning ServiceNow configurations with business and IT operations.

Why CSDM is Important:

Ensures consistency inIT service mapping and asset relationships.

Helps organizationsalign CMDB datawith ITSM, ITOM, and other ServiceNow applications.

Providesdata governance and best practicesto maintain data integrity.

Option B (CMDB)is incorrect because theCMDB is the database that stores configuration items (CIs), but CSDM defines the model for structuring it.

Option C (ITSM)is incorrect because ITSM includes processes like Incident, Problem, and Change Management, but does not provide adata modelblueprint.

Option D (ServiceNow Wiki)is incorrect because ServiceNow no longer uses a wiki for documentation (it has been replaced by theServiceNow Docs Portal).

???? Reference:ServiceNow Common Services Data Model (CSDM) Guide

When importing data into ServiceNow,data integrity and accuracyare critical. ServiceNow recommendscleaning and verifyingdatabefore importingit into the system.

Obsolete or inaccurate datacan cause duplicate or incorrect records.

Pre-cleaningensures onlyrelevant, high-quality datais loaded into ServiceNow.

Improves system performanceby preventing unnecessary data clutter.

Identify and remove obsolete records(e.g., inactive users, old assets).

Fix formatting issues(e.g., date formats, duplicate values).

Verify data mappingsto ensure correct field alignment.

Use a small test importbefore a full-scale import.

Best Practice: Clean Data Before ImportingRecommended Pre-Import Steps:

A. Adjust your Transform maps, after the data is loaded into the target table →Incorrect

Transform Mapsshould be setbefore importing, not after.

Adjusting them afterward may requirereloading data.

B. Use extremely large Import Sets, instead of multiple large Import Sets →Incorrect

Large imports can causeperformance issues.

Best practice: Useincremental importswith data validation.

C. Create a new Import Set table for each new data load →Incorrect

Reusing Import Set tablesis more efficient.

New tables are neededonly for major structural differences.

E. Monitor data quality and clean imported data, using the Data Scrub Workspace →Incorrect

No such featureas " Data Scrub Workspace " exists in ServiceNow.

Datashould be cleaned before importing, not after.

Why Other Options Are Incorrect?

Best Practices for Importing Data

Preparing Data for Import

The fundamental difference between a Client Script and a Business Rule in ServiceNow lies in where they execute and when. A Client Script runs on the client side — that is, in the user ' s browser — and is primarily used to control UI behavior, validate data before submission, and enhance user interaction with forms. Client Scripts can run at different stages (onLoad, onChange, onSubmit), but they always execute within the browser environment.

A Business Rule, on the other hand, runs on the server side and executes when records are inserted, updated, deleted, or queried in the database. Business Rules are used for enforcing data integrity, automating server-side logic, and integrating with other systems. They can be set to run before or after a database action (before insert, after update, etc.).

Therefore, the correct statement is that Client Scripts execute on the client and Business Rules execute on the server.