ServiceNow Updated CSA Exam Questions and Answers by dean

TheHistory sectionin theApplication Navigatortracks recently visited records, lists, and forms within ServiceNow. This feature allows users to quickly navigate back to previously accessed content without searching manually.

What Appears in the History Section?The History sectionlogs user activityrelated to:

Records (Option A)– Recently viewed records from any table, such as incidents, requests, or tasks.

Lists (Option C)– Any list views a user has accessed, such asIncident ListorChange Request List.

Forms (Option D)– Any individual record viewed in form view, such as anincident formoruser form.

Why is Option B (UI Pages) Correct?UI Pages do NOT appear in the History section.

UI Pagesare special custom pages built with Jelly scripting and used forcustom interfaces, portals, and dashboards(e.g., Service Portal pages).

Since they do not represent individual records, lists, or forms,they are not included in the user’s History tracking.

Why Are the Other Options Incorrect?A. Records

Recordsare individual database entries (e.g., specific incidents, change requests, or users).

Since records are frequently accessed, theyare logged in History.

C. Lists

Listsdisplay multiple records from a table (e.g., all open incidents).

Since users navigate through lists frequently, theyare logged in History.

D. Forms

Formsare used to view or edit individual records (e.g., an incident form).

Since forms are commonly accessed, theyare logged in History.

Reference from Certified System Administrator (CSA) Documentation:????ServiceNow Docs – Application Navigator & History

????ServiceNow Application Navigator Documentation

"The History section of the Application Navigator displays a list of the records, lists, and forms that you have recently accessed."

"Custom UI Pages are not included in History tracking."

When setting adata policyin ServiceNow, it applies to all data entered into the platform, regardless of whether the data comes from:

UI Forms

Import Sets

Web Services (APIs, integrations, etc.)

Where Does the Data Policy Run?Data Policies Run on the Server-Side

Data policies enforcedata consistency and validationat theserver level.

Theyapply uniformly across all data entry points, ensuring that validation rules are enforced before storing data in the database.

A. Client →Incorrect

Data Policies donotrun on the client-side (browser).

Client ScriptsandUI Policieshandle client-side validation.

C. Browser →Incorrect

Data Policies donotoperate within the browser; theywork at the database levelon the server.

D. Network →Incorrect

ServiceNowdoes not enforce policies at the network layer; all validations occur on theapplication server (Server-Side Processing).

Why Other Options Are Incorrect?Key Differences Between Data Policies and Other Validation Methods:Validation Type

Runs On

Applies To

Purpose

Data Policy

Server

UI, Import Sets, Web Services

Enforces rules across all data sources

UI Policy

Client (Browser)

UI Forms

Dynamically changes form behavior

Client Script

Client (Browser)

UI Forms

Runs JavaScript in the user's browser

Business Rule

Server

Database Transactions

Executes logic when records are inserted, updated, or deleted

Data Policies Overview

Difference Between UI Policies and Data Policies

Official ServiceNow Documentation Reference:

When importing data into ServiceNow via anImport Set, the system determines whether to update existing records or create new ones based on theCoalescefield setting.

If noCoalesce Fieldis defined,ServiceNow treats every imported row as a new record.

The import process doesnotcheck for existing records, meaning no records in the target table are updated.

This can result induplicate entriesif the imported data includes records that already exist in the target table.

ACoalesce Fieldis used tomatchincoming data to existing records.

If a matching record is found, it is updated instead of inserting a new one.

If no matching record is found, a new record is created.

Behavior When No Coalesce Field is Specified:How Coalescing Works:Incorrect Answers Explanation:A.All rows are rejected from the import, as coalesce field is required

This is incorrect because the import does not require a coalesce field to proceed. The system will still import all rows.C.Duplicate rows are rejected from the import

Without a coalesce field, duplicates arenotrejected. Instead, every row is inserted as a new record, even if it already exists in the target table.D.All rows are treated as new records, but errors will be flagged in the import log

Errors are only flagged in cases ofdata mismatches, validation failures, or incorrect mappings, not just because coalescing is missing.

ServiceNow Documentation→ "Importing Data - Coalescing Best Practices"

ServiceNow Import Set Documentation→ "Understanding Import Set Behavior Without Coalescing"

References from Certified System Administrator (CSA) Documentation:

InServiceNow Knowledge Management, several features help supportcontinuous improvementof knowledge articles by allowing users to providefeedback, ratings, and flag issues. These features ensure that knowledge remainsaccurate, relevant, and usefulover time.

B. Add Comments

Allows users to provide feedback directly on knowledge articles.

Comments help knowledge managers refine content based on user suggestions.

D. Tag as Helpful

Users can mark an article as helpful, indicating that it provided useful information.

Helps knowledge managers assess the article’s effectiveness.

E. Flag Article

Users can flag an article if they find inaccuracies or outdated content.

Flags alert knowledge managers to review and update the content.

F. Rate with Stars

Users can rate an article using astar-based rating system(e.g., 1 to 5 stars).

This helps knowledge managers understand which articles arehigh-quality vs. low-quality.

A. Submit KB Errata

No such built-in feature exists in ServiceNow Knowledge Management.

C. CC Click Frowning Icon

No such feature exists. ServiceNow provides a"Helpful"or"Flag"option instead.