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

In ServiceNow, theDictionaryis the component that definesevery table and fieldin the system.

Itstores metadataabout every table and field.

It contains details likedata type, field properties, default values, and relationships.

It is managed through thesys_dictionarytable.

If you navigate toSystem Definition > Dictionary, you can view and edit field properties for any table.

The Dictionary defineswhether a field is mandatory, read-only, or referenceable.

A. Data Atlas– Not a valid ServiceNow concept.

B. Table Class Manager– Managestable extensions and inheritance, but does not define individual fields.

C. Schema– Refers to theoverall structure of a database, but in ServiceNow, theDictionarymanages table and field definitions.

E. Field Map– Used fordata imports and transformations, not for defining tables and fields system-wide.

ServiceNow Dictionary Overview

ServiceNow CSA Training Module: " Understanding Tables and Fields "

What is the Dictionary in ServiceNow?Example:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow, aBreadcrumbis thestring of filter criteriadisplayed at the top of a list when filters are applied. Breadcrumbs help usersnavigate and refine filterswithout having to manually edit conditions.

Navigate to a list view(e.g., Incidents, Requests).

Apply a filter (e.g., " Priority is High " AND " State is New " ).

Abreadcrumb stringappears, displaying the filter conditions.

Users canclick on different parts of the breadcrumbto adjust or remove filter conditions dynamically.

A. Topic

Topics are used inKnowledge Management and Virtual Agentbut do not represent filter criteria.

B. Choice

A Choice refers todropdown optionsin ServiceNow fields, not filters.

D. Menu

Menus provide navigation options, but they do not display filters.

In ServiceNow, when building filter conditions using theCondition Builder, there are three key components:

Field (Filter Criteria):The specific database field you are filtering on.

Operator:A choice list that defines the condition (e.g., " is " , " contains " , " starts with " ).

Value:The value you are checking against.

Among these components,the Operator is always a choice list, as it provides predefined options for filtering. The Operator determines how the Field and Value should be compared. For example:

" State is Active " (where " is " is the Operator)

" Priority is greater than 2 " (where " is greater than " is the Operator)

Other components, such as Filter Criteria (fields) and Match Criteria, do not always function as choice lists.

Within the ServiceNow Instance Security Center (ISC), administrators monitor and manage the security health of their instance. To track inactive users with high-level access, the administrator must consult Security metrics .

1. Security Metrics in the ISC:

The Security Metrics section is designed to provide actionable data regarding user behavior and access compliance. It includes specific, tracked indicators such as " Privileged users who have never logged in " or " Inactive Privileged Users. " By reviewing these metrics, an administrator can identify accounts holding roles like admin or security_admin that pose an unnecessary risk because they are completely unused.

2. Why the other options are incorrect:

A (Security scanner): This tool is used to scan the instance for misconfigurations, weak settings, or non-compliant properties, rather than tracking individual user login behaviors over time.

B (Security posture dashboard): This is an overarching dashboard summarizing the general compliance score and high-level events, but the specific operational lists of inactive user accounts are housed under the detailed metrics.

D (Security hardening): This section provides a list of recommended security properties to enable or adjust (like password policies or ACL strictness) to fortify the instance, not a behavioral report of users.

Assignment Rulesin ServiceNow automaticallyassign tasks(such as incidents, service requests, or change requests) to theappropriate group or individualbased on predefined criteria.

Acritical, high-priority service requestis created.

TheAssignment Rulechecks conditions (e.g., priority, category, requester, etc.).

The systemassignsthe request to the correctassignment group or individual.

How Assignment Rules Work:Example Scenario:

If an incident isPriority 1 (P1)and the category isNetwork, an assignment rule canautomatically route it to the " Network Support " group.

A. User Policy

No such feature exists in ServiceNow for task assignments.

B. UI Policy

UI Policies controlform behavior (visibility, field conditions, etc.), not assignment logic.

C. Predictive Intelligence

Predictive Intelligence usesmachine learningto suggest assignments, butAssignment Rulesare the primary mechanism for automatic task allocation.

InServiceNow Flow Designer, aflowis an automated process that consists of actions, conditions, and triggers.Two key componentsdetermine when a flow should run:

Trigger

Defineswhenthe flow should execute.

Examples:

When arecord is created/updated/deleted.

When anAPI call is received.

On ascheduled basis.

Condition

Specifiesadditional criteriathat must be met for the flow to proceed.

Examples:

If thepriority is High.

If thestatus is Resolved.

Aflowis designed tosend an email notificationwhen ahigh-priority incident is assigned.

Trigger: " Incident table → When a record is updated. "

Condition: " Priority = High AND State = Assigned. "

A. Trigger and Condition Pill

No such term as " Condition Pill " exists in Flow Designer.

B. Scope and Trigger Condition

" Scope " defines theapplication boundary, not when a flow runs.

D. Trigger Criteria and Clock

" Clock " is not usedfor defining flow execution.

E. Condition and Table

Atable does not define when a flow runs; it only stores records.

When designing Service Catalog items,Variable Setsallow you toreuse common fields across multiple catalog items.

Instead ofcreating the same four fields(Requested for, Requested by, Approving manager, Delivery instructions)80 times,

You candefine them once in a Variable Setand apply it to all catalog items.

Best Approach (Correct Answer: A)Advantages of Using a Variable Set:Reusability– The same Variable Set can be added to multiple catalog items.

Consistency– Ensures the four mandatory fields are always included.

Easier Maintenance– Changes to these fields only need to be made inone place.

B. Create a Record Producer that contains the four fields →Incorrect

ARecord Produceris used to create records in a specific table (e.g., Incident, Request, Change).

It isnot designed for defining reusable fieldsacross multiple catalog items.

C. Create a Flow Designer Action with Variable Set Data Pill →Incorrect

Flow Designeris for process automation, not fordefining form variables.

It does not allow you to create reusable fields for catalog item forms.

D. Create an Order Guide and hide variables as needed →Incorrect

Order Guidesare used for ordering multiple catalog items together.

They do not provide a structured way to manage common fields across different catalog items.

E. Create a Variable Set Template →Incorrect

There is no concept of a " Variable Set Template " in ServiceNow.

Variable Setsthemselves act as templates.

Why Other Options Are Incorrect?

Using Variable Sets in Service Catalog

Building Service Catalog Forms

Official ServiceNow Documentation Reference:

ANatural Language Query (NLQ)allows users to filter list data using plain English instead of using the traditional condition builder. NLQ interprets human-readable search terms and translates them into system queries, making it easier for non-technical users to retrieve information without having to understand the underlying database structure.

User-friendly: Users can type a question in normal language (e.g., " Show me all open incidents assigned to me " ).

Automatic Query Conversion: The system translates the NLQ into a structured query that ServiceNow understands.

Faster Search & Filtering: It helps in quickly filtering and finding records without manually setting conditions.

Works on Lists: NLQ is used primarily in list views where users need to filter or search records.

Key Features of NLQ in ServiceNow:Example Usage:If a user enters " Show me all open incidents for John Doe " , the NLQ engine will convert it into a structured query like:

[State = Open] AND [Assigned To = John Doe]

ServiceNow Product Documentation→ " Natural Language Query Overview "

ServiceNow List Filters and Condition Builder→ " Using Natural Language Queries for Filtering "

References from Certified System Administrator (CSA) Documentation:

InServiceNow Access Control Rules (ACLs), if an administrator wants to grant access toall rows and all fieldsof a custom table (e.g.,customertable) to specific roles (customer_table_adminandcustomer_table_user), they should create an ACL rule using theformat:

➡️tablename.*

For theCustomer Table, the correct ACL format is:

➡️customer.*

This rule allows bothcustomer_table_adminandcustomer_table_userfull accessto all fields and records in thecustomertable.

A. customer.all

Incorrect syntax; ServiceNow does not use.allin ACL rules.

C. customer.field

This would applyonly to a specific field, not all rows and fields.

D. customer.none

No such ACL naming convention exists in ServiceNow.

Moving configuration changes between ServiceNow instances (e.g., from Development to Test) involves a strict lifecycle using Update Sets . 13 The correct standard operating procedure to apply a remote update set is Retrieve, Preview, Commit .

1. Retrieve (The First Step):

Before you can do anything, the target instance (e.g., Production) must fetch the completed update set from the source instance (e.g., Development).

Action: You connect to the source instance and click " Retrieve Completed Update Sets. " This pulls the XML file into the sys_remote_update_set table on the target instance. The state becomes Previewed or Loaded .

2. Preview (The Validation Step):

Once retrieved, you must validate the data before committing it to the database.

Action: You select the retrieved update set and click Preview Update Set .

Purpose: This checks for potential conflicts (e.g., trying to update a record that doesn ' t exist or has been modified locally). You must resolve all errors before proceeding.

3. Commit (The Application Step):

After the preview is successful (no errors), the changes are ready to be written to the system.

Action: Click Commit Update Set .

Result: The system writes the changes to the local tables/database. The Update Set state changes to Committed .

Why the other orders are wrong:

You cannot Preview before you Retrieve (you don ' t have the file yet).

You should never Commit before Previewing (this skips the safety check for conflicts).

Activity Formatteris a UI element in ServiceNow forms that logs allupdates, comments, and historyrelated to a task.

It consolidates user interactions and system-generated updates in one place.

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.

TheConfiguration Management Database (CMDB)in ServiceNow is a core component of IT Service Management (ITSM), allowing organizations to track Configuration Items (CIs) and their relationships. There are threekey tablesthat form the foundation of the CMDB:

cmdb (Base CMDB Table):

This is the parent table for all Configuration Items (CIs) in the CMDB.

It contains the foundational structure upon which all other CMDB-related tables are built.

It does not store CI records itself but serves as the primary reference table.

cmdb_ci (CI Base Class Table):

This is thebase classfor all Configuration Items (CIs).

All specific CI classes (such as servers, applications, networks) extend from this table.

It holds general CI attributes that are common across all CI types.

cmdb_rel_ci (CMDB Relationship Table):

This table defines relationships between different Configuration Items.

It stores dependencies and associations between CIs, such as a server hosting an application.

Relationships are critical for impact analysis and dependency mapping.

B. sn_cmdb_bak & E. cmdb_bak:

These tables donotexist in the standard CMDB schema. They may be mistaken for potential backup tables, but they are not official CMDB tables.

D. sn_cmdb & G. sn_cmdb_ci:

Prefix " sn_ " generally indicatesScoped Application Tablesin ServiceNow.

Standard CMDB tables exist in theglobal scopewithout the " sn_ " prefix.

" sn_cmdb " and " sn_cmdb_ci " arenotkey tables in theglobal CMDB architecture.