Free Practice Questions for ServiceNow CSA Exam

In ServiceNow,Client Scriptsare scripts that execute in the user'sweb browserrather than on the server. They are used to enhance user experience by dynamically controlling form behavior, validating user input, or performing real-time updates without requiring a server request.

Types of Scripts in ServiceNow:Script Type

Runs On

Purpose

Client Script

Web browser (client-side)

Modify UI behavior, perform field validations, or respond to user interactions.

Server Script

ServiceNow backend (server-side)

Processes data, enforces business rules, and performs background operations.

Database Script

Database layer

Used for stored procedures or database triggers (not applicable in ServiceNow).

Local Script

Not an actual ServiceNow script type

No such category exists in ServiceNow.

Runsin the web browserwhen a form is loaded, changed, or submitted.

Can manipulate field values, display messages, or enforce rules in real time.

UsesGlideForm (g_form)andGlideUser (g_user)APIs.

Reduces server load by executing logic without sending requests to the backend.

A. Server script:

Runs on theserver-side, not in the browser.

Examples:Business Rules, Script Includes, Scheduled Jobs.

B. Local script:

No such script type in ServiceNow.

C. Database script:

ServiceNow does not allow direct database scripting.

Client Scripts Overview

Scripting Best Practices

Key Features of Client Scripts:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

The ServiceNow platform providespre-built workflowsthat help organizationsautomate processesacross different domains. These workflows are designed to streamline operations, improve efficiency, and enhance user experience. Thethree primary types of workflowsincluded in the platform are:

Employee Workflows– Designed to improve employee experiences, covering HR services, onboarding, workplace services, and more.

Customer Workflows– Focused on customer service management (CSM), case management, field service management, and proactive customer engagement.

IT Workflows– These workflows enable IT Service Management (ITSM), IT Operations Management (ITOM), and IT Business Management (ITBM) for efficient IT operations.

B. Infrastructure Workflows–No specific "Infrastructure Workflows" exist as a built-in category in ServiceNow. Infrastructure processes are generally managed underIT Workflows (ITOM/ITSM).

C. Federal Workflows–Not an official workflow category. Federal agencies useServiceNow’s Government, Risk, and Compliance (GRC) solutions, but this is not classified as a workflow.

D. Manufacturing Workflows–ServiceNow does not have a dedicated "Manufacturing Workflows" category. However, manufacturers often useCustomer and IT Workflowsfor managing operations.

TheForm Designerin ServiceNow allows administrators to create, edit, and configure forms to control how records are displayed and interacted with in the system. It consists of three key components:

Page Header– This section contains controls such as "Save," "Undo," and "Redo." It allows users to manage their changes while designing forms. The Page Header also displays the name of the form being edited.

Field Navigator– This panel provides a categorized list of available fields that can be dragged and dropped onto the form layout. The fields are divided into different sections, such as "Available Fields" and "Existing Fields," helping users to manage the form's data structure effectively.

Form Layout– This is the central workspace where users design the form by arranging fields. Users can add new fields, move existing ones, and configure their properties. The layout determines how the form appears to end-users.

ServiceNow Product Documentation – Form Designer

ServiceNow CSA Training Module:"Configuring Forms and Fields"

"ServiceNow System Administration Guide – Form Customization Best Practices"

References from Certified System Administrator (CSA) Official Documentation:Would you like me to verify and format more questions in the same manner?

When setting up a notification in ServiceNow, you must define three critical elements:

What is the content of the notification?

This includesemail subject, body, variables, and templatesthat define how the notification will be displayed to the recipient.

Under what conditions is the notification sent?

Notifications are triggered based onconditionssuch as:

Record Insert/Update/Delete

Specific field value changes

Events generated by business rules

Who receives the notification?

The recipients can be configured using:

Specific users or groups

Scripted recipients

Users associated with the record (e.g., Caller, Assigned To)

B. The associated knowledge base– Notifications arenot tiedto knowledge bases; they are triggered by records and events.

E. Settings for handling inactive user accounts– While user preferences exist, this is not a required step in notification creation.

ServiceNow Notifications Guide

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

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

In ServiceNow,tagsare used to categorize and organize records for quick access. When managing tags, users can control theirvisibilityby settingwho can see them.

B. Everyone

The tag ispublicand visible to all users in the instance.

Example: AService Desk teamcreates a"High Priority"tag that everyone can use.

C. Groups and Users

Tags can be restricted to specificgroupsorindividual users.

Example: ASecurity Teamcreates a tag only visible toIT Security staff.

E. Me

Tags can beprivate, meaning only the creator (you) can see them.

Example: A user creates a"Follow-up"tag for theirownpersonal tracking.

A. Admins

Incorrect—Admins can manage tags, but "Admins" isnota visibility setting.

Instead, visibility is set toEveryone, Groups, or Me.

D. Roles and Permissions

Incorrect terminology—ServiceNowdoes notprovide a tag visibility setting based on "Roles and Permissions."

Tags are assigned based onspecific users or groups, not roles.

In ServiceNow,User Criteriais the mechanism used to control and determine user access toknowledge bases (KBs) and knowledge articles. User criteria define which users, groups, or roles canread, write, and contributeto a knowledge base or specific articles within it.

How User Criteria Works:User Criteria are applied at both theknowledge baselevel and theknowledge articlelevel to manage access. They can be configured with specific conditions to allow or restrict access based on:

Users(specific users can be added directly)

Groups(access can be granted to a specific user group)

Roles(users with specific roles can be given access)

Advanced conditions(such as department, company, location, etc.)

A knowledge base can havemultiple user criteria, and a single user criterion can apply to multiple knowledge bases.

Read User Criteria– Determines who can view the knowledge base or an article.

Write User Criteria– Determines who can create, edit, or contribute knowledge articles.

Exclusions– You can exclude users or groups from accessing specific knowledge bases or articles even if they meet other conditions.

A. sn_kb_read, sn_article_read:

These are not standard ServiceNow permissions for controlling knowledge access.

In ServiceNow, permissions are managed through roles and user criteria, not direct ACL names like these.

B. Privacy Settings:

ServiceNow does not use "Privacy Settings" as an access control mechanism for knowledge bases.

Privacy settings might be relevant in other contexts, such asuser profiles or system preferences, but not for knowledge access control.

C. Read Access Flag:

There is no "Read Access Flag" in ServiceNow's knowledge management module.

Access is controlled viaUser Criteria, Roles, and Knowledge Base Settings.

Key Features of User Criteria in Knowledge Management:Why Other Options Are Incorrect?Official ServiceNow Documentation References:For more details, refer to the official ServiceNow documentation:

User Criteria for Knowledge Bases

Managing Knowledge Base Access

Knowledge Management User Criteria

In ServiceNow, when working with large lists of records, users canquickly filterrecords based on specific column values using built-in list functionalities.

A. On the list, locate and right-click on the value Hardware, select Show Matching

This is thefastestway to filter a list.

Steps:

Locate a record with theCategory = Hardwarevalue.

Right-clickon the word "Hardware."

Select"Show Matching"from the context menu.

The list is now filtered to display only records withCategory = Hardware.

B. Click Funnel icon, type Hardware, and click enter

TheFunnel icon(Filter) is used to createadvanced filters, but youcannot directly type"Hardware" into it.

You would need to manually create a filter condition:

Category→is→Hardware

C. On the Category column header, right-click and select Show > Hardware

Incorrect terminology—There is no"Show > Hardware"option.

Instead, you would need to useShow Matching(Answer A).

D. Right-click on magnifier, type Hardware, and click enter

There is no"magnifier"(search icon) method that filters records this way.

E. On Breadcrumb, click > icon, type Hardware, and click enter

Breadcrumbsprovide a visual representation ofexisting filters, but you cannotdirectly type values into breadcrumbs.

In ServiceNow, users cancustomizetheir list views byrearranging, adding, or removing columns. This is done through theList Layout Configuration.

B. Right-click on any column header. Context Menu > Configure > List Layout

Thequickestway to modify columns in a list view.

Steps:

Right-click on any column headerin the list.

SelectConfigure > List Layoutfrom the context menu.

Add, remove, or rearrange columns as needed.

ClickSave.

A. Click Personalize List

Incorrect terminology—there is no "Personalize List" option for configuring list columns.

"Personalize" is used for settingpersonal preferences, not list layouts.

C. Click List Context Menu > Personalize List

TheList Context Menudoes not have a "Personalize List" option for column arrangement.

D. Click List Content Menu > Configure > List Layout

Typo in "List Content Menu"—the correct term is"List Context Menu".

However,right-clicking on the column header(Answer B) is the recommended method.

In ServiceNow, theActivitysection on a task record provides areal-time log of all recent updates, including field changes, comments, and system-generated events.

Displays achronological historyof changes made to a record.

IncludesWork Notes,Additional Comments, andField Changes.

Showswho made the changeandwhen it occurred.

Can befilteredto show only specific types of updates (e.g., comments, field changes).

A. Timeline →Incorrect

There is no standard "Timeline" section on a task record.

Visual Task Boards (VTBs)have timelines, but task records useActivity.

B. Journal →Incorrect

ServiceNowdoes nothave a "Journal" section for task records.

Journal fields(e.g., "Additional Comments" and "Work Notes") store specific updates, butActivityprovides the full record history.

C. Audit Log →Incorrect

TheAudit Log (sys_audit table)tracks changes but is not displayed directly on task records.

Admins need tomanually querytheAudit Logfor historical changes.

Activity Stream Overview

Understanding Journal Fields

Key Features of the Activity Section:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

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: