CSA ServiceNow Certified System Administrator Free Practice Exam Questions (2025 Updated)

Performance Analytics (PA) is the best solution for the manager's requirements because it provides:

Snapshot of Sales Performance Data– PA allows the creation of historical and real-time dashboards to track sales performance against targets.

Trend Analysis Over Time– With PA, historical data is captured and can be visualized in trend reports, showing patterns over time.

Forecasting Capabilities– PA includes predictive intelligence that can project future trends based on past performance, helping managers make data-driven decisions.

A. Scheduled Reports, a custom snapshot table, and a Trend report– While reports and snapshots provide historical data, they do not offer forecasting capabilities.

B. Scheduled Reports and Excel– Excel is static and does not provide built-in forecasting or trend analysis.

C. Scheduled Reports, a custom snapshot table, and a Projection report– This approach is manual and lacks the dynamic analytics that PA provides.

E. Key Performance Indicators (KPIs)– KPIs track metrics but do not inherently provide trend analysis or forecasting.

In ServiceNow,scripts that run in the browser (client-side)includeUI PoliciesandClient Scripts. These scripts execute on theuser’s web browser, allowing real-time interaction with forms and fields without requiring a server request.

Executed in the user’s browserwhen a form is loaded, saved, changed, or submitted.

Used forreal-time form validation, auto-population, and dynamic UI changes.

Written inJavaScriptand runs on the client side.

Applyrulesto make fieldsmandatory, visible, or read-onlydynamically.

Moreefficientthan Client Scripts because theydon’t require scriptingin most cases.

A. Script Include Scripts– Theserun on the server, not in the browser. They are reusable functions that can be called from different scripts.

B. Business Rule Scripts– Business Rulesexecute on the server-side, triggered by database operations (Insert, Update, Delete).

C. Access Control Scripts– These areserver-side security rules(ACLs) that restrict user access to records and fields.

ServiceNow Client Scripts and UI Policies

ServiceNow CSA Training Module:"Client-Side Scripting in ServiceNow"

1. Client Scripts:2. UI Policies:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

UI Policiesare the preferred method to dynamically control the visibility, read-only state, or mandatory status of form fieldswithout requiring a page reload.

Best Practicesuggests usingUI Policiesover Client Scripts whenever possible because UI Policies execute on the client side and are easier to manage.

Theydo not require scriptingin most cases and provide asimple rule-based approach.

Explanation of Incorrect Options:

Client Scripts (A)→ Used for executing JavaScript logic in the browser, but making fields mandatory or hidden should be done via UI Policies.

Business Rules (C)→ Run on the server-side and do not directly affect form fields in real-time.

UI Actions (D)→ Used for creating buttons, links, or context menu actions;not for modifying field properties.

Scripts that run in thebrowser (client-side)help controlUI behavior, form validation, and field interactionsin real-time without needing a server request.

Types of Client-Side Scripts in ServiceNow:Client Scripts

Run directly in the user's browser.

Used for form validation, auto-populating fields, or UI interactions.

Example:

javascript

CopyEdit

functiononLoad() {

g_form.setValue('priority','2');

}

UI Policies

Controlfield visibility, mandatory status, and read-only statedynamically.

Example: Ifcategory = Hardware, makeSerial Number field mandatory.

B. Access Control Scripts →Incorrect

Access Control Lists (ACLs)runserver-side, not in the browser.

C. Script Includes →Incorrect

Script Includesrunserver-sideand are used for reusable functions and API logic.

D. Business Rules →Incorrect

Business Rulesalso run on theserver, not in the browser.

Why Other Options Are Incorrect?

Client Scripts Overview

UI Policies in ServiceNow

Official ServiceNow Documentation Reference:

By default, ServiceNow encrypts data in transit using industry-standard Transport Layer Security (TLS) protocols. This ensures that any data transmitted between the client and the ServiceNow platform, or between ServiceNow and integrated systems, is encrypted and protected from interception or tampering.

While ServiceNow also offers options for data at rest encryption and customer-managed encryption keys, these features often require additional configuration or subscription services. Encryption of data in use (while data is being processed in memory) is a more advanced concept and not provided by default.

Thus, encryption of data in transit is the baseline encryption feature included automatically in all ServiceNow instances.

TheCatalog Admin [catalog_admin]role:

Inherits permissions from both:catalog role(Basic Service Catalog access)user_criteria_admin role(User Criteria management)

Has additional permissions to:Create and manage Catalog Items and ServicesConfigureCatalog Categories, Order Guides, and Variables

A. Item Admin [sn_item_admin] →Incorrect

This role does not inherituser_criteria_adminpermissions.

It isspecific to managing Catalog Itemsbut does not have full Catalog Admin permissions.

B. Sys Admin [sys_admin] →Incorrect

Thesys_adminrole has full system access but is notService Catalog-specific.

D. Catalog Author [sn_catalog_write] →Incorrect

TheCatalog Authorrole canedit catalog itemsbutcannot create new ones.

Why the Other Options Are Incorrect?

ServiceNow Catalog Roles

Official ServiceNow Documentation Reference:

A record-based trigger is a component thatcauses a flow to run after a record has been created or updated in a specified table1. It allows users to define conditions and actions for the flow based on the record’s state and values1. For example, a record-based trigger can start a flow when a new incident is created or when an existing incident is updated with a certain priority1.

References

Flow trigger types - Product Documentation: San Diego - ServiceNow1

InServiceNow Knowledge Management, articles are typicallyrestrictedto specific users or roles. However,if you want an article to be accessible without requiring login, you must enable thePublic setting.

Navigate toKnowledge Base Settings.

Enable thePubliccheckbox.

Save the changes.

The article is nowviewable by anyone, even without logging into ServiceNow.

A. The View All setting

No such setting exists for public access in ServiceNow.

B. The Allow role

"Allow roles" restricts accessto specific roles, but does not make the article public.

C. The ESS role

TheESS (Employee Self-Service) roleallows accessto logged-in users, not public users.

When an analyst needs to build a new report in ServiceNow, the best place to start isReports > Create New. This option provides a structured interface forselecting data sources, choosing visualization types, applying filters, and generating reports.

Steps to Create a New Report in ServiceNow:

Navigate toReports > Create New.

Select a data source (table) for the report.

Choose a report type (Bar Chart, List, Pie Chart, etc.).

Apply filters and groupings to refine the data.

Preview and save the report.

A. Report Dashboard > Create New– Dashboards display multiple reports but do not provide a direct interface for creating a new report.

B. Reports > Getting Started– This is ahelpful guide, but it is not where reports are created.

C. Performance Analytics > Reports– Performance Analytics focuses onadvanced trend analysis and KPIs, not general reporting.

D. Self-Service > Reports– This allows end-users toview and run reports, but it is not meant for creating new reports.

ServiceNow Reports and Dashboards

ServiceNow CSA Training Module:"Creating and Managing Reports in ServiceNow"

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

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.

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