CSA Practice Questions

In ServiceNow, when importing data from an external source (e.g., CSV, Excel, or an external

database), the records first go into a staging area before being transformed and inserted into their

final destination table.

The Correct Table: Import Set Row Table

The Import Set Row Table (sys_import_set_row) is where records are temporarily stored during an

import.

This table holds raw data from the Import Set Table (sys_import_set), allowing transformation and

validation before writing to the target table.

Import Process Flow:

Load Data → Records are loaded into the Import Set Row Table (sys_import_set_row).

Transform Data → A Transform Map processes and moves data to the target table.

Clean Up → Processed records are removed from the staging table after transformation.

Why Other Options Are Incorrect?

A . Transform Table → ❌ Incorrect

No such table called "Transform Table" exists in ServiceNow.

Transformation happens via Transform Maps, not a separate table.

B . Staging Table → ❌ Incorrect

The term "staging table" is a general concept but not an actual table name in ServiceNow.

D . Temp Table → ❌ Incorrect

ServiceNow does not use a "Temp Table" for imports.

Temporary data is held in sys_import_set_row, not a table named "Temp Table."

Official ServiceNow Documentation Reference:

Import Sets Overview

Understanding Import Set Row Table

In ServiceNow, Visual Task Boards (VTBs) provide a Kanban-style interface to manage and track work.

There are three main types of Visual Task Boards, but "Feature" is not one of them.

Types of Visual Task Boards in ServiceNow:

Freeform Board (✅ Valid Type)

Manually created boards where cards can be moved freely without predefined conditions.

Users can add and organize tasks as needed.

Example: Personal task management.

Guided Board (✅ Valid Type)

Created from a list view and linked to a ServiceNow table (e.g., Incident, Change, Task).

Cards on the board automatically update based on conditions.

Example: Managing Incidents or Change Requests.

Flexible Board (✅ Valid Type)

Similar to Guided Boards, but allows users to manually reorder tasks within lanes.

Offers more flexibility while still being linked to a data source.

Example: Sprint Planning or ITSM Workflows.

Why is "Feature" Incorrect?

"Feature" is NOT a Visual Task Board type in ServiceNow.

ServiceNow does use the term "Feature" in Agile Development (for tracking high-level product

functionalities), but it is not related to VTBs.

Why Other Options Are Correct?

✅ Guided, Flexible, and Freeform are the three valid types of Visual Task Boards in ServiceNow.

Reference from ServiceNow CSA Documentation:

Visual Task Boards Overview

ServiceNow Visual Task Boards

Types of Visual Task Boards

Creating and Using VTBs

✔ UI Policies are the best way to implement dynamic form behavior such as making fields

mandatory, hiding/showing fields, and setting values based on conditions.

Breaking Down the Requirements:

Making "Resolution Code" mandatory when "State" is changed to "Resolved"

This requires a UI Policy that:

Condition: State = Resolved

Action: Set "Resolution Code" field to Mandatory = True

Hiding the "Major Incident" checkbox unless the logged-in user has the "Major Incident Manager"

role

This requires another UI Policy that:

Condition: User does NOT have the role major_incident_manager

Action: Hide the field

Why the Other Options Are Incorrect:

Option A (Dictionary Design) ❌

The dictionary defines the structure of fields but does not control dynamic form behavior like field

visibility or conditions.

Option B (Field Limiter) ❌

There is no such feature called "Field Limiter" in ServiceNow.

Option D (UI Design) ❌

"UI Design" is not a recognized concept in ServiceNow. UI Policies are used for form behavior

changes.

Option E (Form Constraint) ❌

There is no "Form Constraint" feature in ServiceNow; ACLs and UI Policies control field behavior

instead.

Reference: ServiceNow UI Policy Documentation (Platform Configuration)

In ServiceNow, a filter condition is used to query 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 the first dropdown in a filter condition.

2. Operator

✅ Defines the comparison condition for the filter.

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

In ServiceNow UI, this appears as the middle dropdown in a filter condition.

3. Value

✅ Specifies the criteria being matched against the column.

Example: High, Closed, John Doe

In ServiceNow UI, this is the third input field in 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 return records where:

The Priority field is set to High

The State field is NOT Resolved

Incorrect Answer Choices Analysis:

B . Match Criteria

❌ Incorrect – No such term exists in ServiceNow filters.

C. Field

❌ Incorrect – "Field" is another word for "Column", but "Column" is the correct term in ServiceNow

filter conditions.

Official ServiceNow Documentation Reference:

ServiceNow Docs – Filtering Data

🔹How to Create Filters in ServiceNow

ServiceNow Docs – Query Builder and Operators

🔹Building Filter Queries

The three-bar icon in the Form header of ServiceNow is commonly referred to as the Hamburger

icon. It provides access to additional form actions through a context menu.

Functions of the Hamburger Icon in ServiceNow:

Opens a drop-down menu with options such as:

Configure Form Layout

Configure Form Design

Insert and Stay

View History

Export Options

Helps users access quick actions without navigating away from the form.

Why is it Called a "Hamburger Icon"?

The icon consists of three horizontal lines, resembling a hamburger (bun-patty-bun).

This naming convention is widely used in web and mobile UI design.

Incorrect Answer Choices

❌ A. Pancake Icon – No such term exists in ServiceNow UI terminology.

❌ B. Additional Actions or Context Menu – While the icon does provide additional actions, "Context

Menu" refers to right-click options or three-dot menus, not the three-bar menu.

❌ D. Cake Icon – No such UI term exists in ServiceNow or general UI design.

Official CSA Documentation Reference:

Understanding the ServiceNow Form Header

ServiceNow UI Overview

The Application Navigator (App Navigator) search field in ServiceNow allows users to quickly find

applications, modules, and favorites by typing relevant keywords. It helps in easy navigation by

filtering available options as the user types.

The four correct answers describe what the App Navigator search field can return:

1. Names of Applications and Modules (✅ Correct)

The search field can return both applications and their respective modules in the left navigation

panel.

Example: Searching for "Incident" will return:

Application: "Incident"

Modules: "All", "Open", "Resolved", "Create New"

2. Names of Modules (✅ Correct)

Modules are specific functionalities within an application.

Searching by a module name directly will display results that match the keyword.

Example: Searching for "Create New" will return modules like:

"Create New Incident"

"Create New Change Request"

3. Names of Applications (✅ Correct)

The search field supports finding full applications by their name.

Example: Typing "Change" will display the Change Management application and its related modules.

4. Favorites (✅ Correct)

If a user has marked specific modules or applications as Favorites, they will appear in search results.

This helps users quickly access commonly used features.

Why the Other Options Are Incorrect:

❌ E. History Records (Incorrect)

The History tab in the navigation panel shows recently accessed records, but it is not searchable

through the App Navigator.

Instead, users can find history under:

History Module (System Settings > History)

Recent History Tab in the left navigation

❌ F. Titles of Dashboard Gauges (Incorrect)

Dashboard Gauges are visual elements on Performance Analytics or Reporting Dashboards and are

not searchable in the App Navigator.

Instead, dashboards and reports are found under:

Self-Service > Dashboards

Performance Analytics > Dashboards

Example Use Case:

A ServiceNow user wants to quickly access the "All Incidents" module.

They type "incident" into the App Navigator search.

The search results return:

Incident (Application)

All (Module)

Assigned to Me (Module)

Resolved (Module)

This allows for quick navigation without manually expanding application menus.

Reference:

ServiceNow Documentation: Application Navigator Overview

ServiceNow CSA Learning Path: Using the Application Navigator

ServiceNow Docs: Favorites and Navigation

To import articles into a Knowledge Base (KB) in ServiceNow, a user must have the

"sn_knowledge_import" role. This role grants permission to bulk import knowledge articles from

sources like spreadsheets, text files, or external databases.

Key Roles in Knowledge Management:

sn_knowledge_import ✅ – Required to import articles into a KB.

sn_knowledge_contribute ❌ – Allows users to write and edit articles but not import them.

sn_knowledge_admin – Grants full admin control over KB settings.

Why Are Other Options Incorrect?

A . Can contribute ❌

"Can Contribute" grants permission to write/edit articles but not import them.

B . sn_knowledge_contribute ❌

This role only allows creating and modifying articles. It does not grant import access.

D . Can import ❌

No such role or permission exists in ServiceNow.

Reference:

ServiceNow CSA Documentation – Knowledge Management Roles & Permissions

ServiceNow Product Documentation – Importing Knowledge Articles (https://docs.servicenow.com)

Scripts that run in the browser (client-side) help control UI behavior, form validation, and field

interactions in 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

function onLoad() {

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

}

✅ UI Policies

Control field visibility, mandatory status, and read-only state dynamically.

Example: If category = Hardware, make Serial Number field mandatory.

Why Other Options Are Incorrect?

B . Access Control Scripts → ❌ Incorrect

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

C . Script Includes → ❌ Incorrect

Script Includes run server-side and are used for reusable functions and API logic.

D . Business Rules → ❌ Incorrect

Business Rules also run on the server, not in the browser.

Official ServiceNow Documentation Reference:

Client Scripts Overview

UI Policies in ServiceNow

ServiceNow provides multiple security-related modules that a System Administrator frequently uses to manage access, authentication, and overall system security. Why These Options Are Correct? ✅ A. System Properties > Security This module allows administrators to configure general security settings, including password policies, session timeout, and encryption settings. It helps manage security parameters at a system-wide level. ✅ E. System Security > Access Control (ACL) Access Control Lists (ACLs) define what data users can access, modify, and delete within the instance. ACLs operate at the table, field, and record levels, ensuring proper role-based access control (RBAC). This is one of the most commonly used security modules by admins. ✅ G. System Security > High Security Settings High Security Settings (previously known as Security Hardening) enforce strict security controls, such as requiring multi-factor authentication (MFA) and enforcing strict password policies. It is often used for compliance with security regulations like HIPAA, GDPR, and ISO 27001. Why the Other Options Are Incorrect? ❌ B. Utilities > Migrate Security This option does not exist in ServiceNow. There is no "Migrate Security" under Utilities. ❌ C. System Security > Security There is no "System Security > Security" module in ServiceNow. The correct structure is System Security > Access Control or System Properties > Security. ❌ D. Self-Service > My Access This is a self-service module for end users to request and review their access. It is not a tool that System Administrators use to manage security settings. ❌ F. Password Management > Security Questions This is used to configure security questions for password recovery but is not a core security module that admins frequently use. Reference to Official Certified System Administrator (CSA) Documentation: General Security Settings in ServiceNow ServiceNow Access Control (ACL) Best Practices ServiceNow System Security and Role Management

In ServiceNow Service Catalog, the User Criteria feature is used to specify which users are eligible to

access (view or order) a Service Catalog Item. User Criteria allows administrators to define rules that

determine whether a user can see or request a catalog item based on attributes such as roles,

groups, departments, and locations.

How User Criteria Works:

User Criteria is created to define the conditions (e.g., users in the IT department can order a laptop).

It is then applied to Catalog Items, Categories, or Access Control Rules.

If a user meets the criteria, they can see and order the item. If not, it remains hidden.

Why the other options are incorrect:

A . Can Read Role → Incorrect. There is no such feature named "Can Read Role" in ServiceNow

Service Catalog.

B . Catalog User Role → Incorrect. ServiceNow does not have a predefined "Catalog User Role."

However, the catalog_admin role can manage catalog items, but it does not control access for end

users.

C . Can Order Tab → Incorrect. This is not a valid ServiceNow feature. Ordering permissions are

controlled through User Criteria.

Reference:

User Criteria for Service Catalog

ServiceNow CSA Training Material