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

InServiceNow, theTask (task) tableis aparent tablethat provides a common structure forwork-related records. Several core tablesinherit from the Task table, meaning theyreuseits fields, business rules, and workflows.

The following tables arechildren of the Task tablein thebase system:

Incident (incident)

Used for managingbreak/fix issuesreported by users.

Inherits fields likeAssigned To, State, Priorityfrom the Task table.

Problem (problem)

Used forroot cause analysisof recurring incidents.

Inherits Task table properties, making it easy to relate problems to incidents.

Change Request (change_request)

Used tomanage changes in IT infrastructure(e.g., software updates, hardware replacements).

Inherits fields likeAssignment Group, Description, Statefrom the Task table.

D. Config

No such table named " Config " exists as a child of the Task table. Configuration-related data is stored inCMDB tables.

E. Dictionary

TheDictionary (sys_dictionary)table storesmetadata about database fields, not task-related records.

F. cmdb

TheCMDB (cmdb) table is not a child of the Task table. It storesConfiguration Items (CIs)like servers, routers, and software, which are separate from task-based workflows.

In ServiceNow,impersonating a userallows administrators or authorized users to temporarily assume another user’s identity. This is useful fortroubleshooting, testing permissions, and verifying user experiences.

admin (A)

Users with theadminroleautomaticallyhave impersonation privileges.

Admin userscan impersonate any user in the system.

Example: A system admin impersonates aService Desk Agentto test access restrictions.

impersonator (E)

Theimpersonatorrole allows a user to impersonate otherswithout full admin privileges.

This role is useful forsupport teams or testerswho need to verify user permissions.

Example: A QA tester is given theimpersonatorrole to test different roles in the system.

B. sys_admin

No such role assys_adminin ServiceNow—this is likely amistyped version of " admin " .

C. security_admin

security_adminis used forelevating privilegesto modify high-security settings, not for impersonation.

D. sys_user

Thesys_usertablestores user recordsbut isnot a role.

Regular userscannotimpersonate others unless they have theimpersonatororadminrole.

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:

Natural Language Query (NLQ)in ServiceNow allows users tofilter a list by typing a natural language phrase, making it easier to search and retrieve data without manually building filters.

For example, users can type:

➡️ " Show me all open incidents assigned to John Doe "

➡️ " Incidents created this week "

The platforminterprets the phraseand automaticallyapplies the correct filterto the list.

A. Automatically select a filter, based on keywords–NLQ does not automatically select filters based on keywords; instead, itprocesses full phrasesinto a filter.

C. Predict the filter desired by the user–NLQ does not predict filters but rather converts typed queries into list filters.

D. Speak to the condition builder–NLQ does not interact with the condition builder directly; it translates text queries into filters.

E. Set list filter, using audible commands–NLQ does not supportvoicecommands, onlytypedqueries.

In ServiceNow, when defining afilter condition, theelement being filteredis called aField.

Afieldis an individual piece of data within atable(e.g.,Caller,State,Priorityin theIncidenttable).

The available fields in a filter depend on:

The table being filtered

User access rights (roles and permissions)

The columns (fields) available on the table

Understanding Fields in Filter Conditions:Example of a Filter Condition:css

CopyEdit

[ State ][ is ] [ In Progress ]

State→ This is aFieldin the table.

is→ This is theOperatorused for filtering.

In Progress→ This is theValuebeing compared.

A. Attribute– Attributes aremetadataabout a field but do not define filter conditions.

B. Label– The label is thedisplay nameof a field but is not used in filtering.

D. Column– While fields arestored as columnsin a database, in filtering, they are referred to asFields.

E. Data Element– This is a general term, not specific to filter conditions.

ServiceNow Filtering and Conditions

ServiceNow CSA Training Module: " Using Filters and Queries in ServiceNow "

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

In the ServiceNow Configuration Management Database (CMDB), the mechanism that enables the tracing of connections between different Configuration Items (CIs) is Relationships .

1. The Role of Relationships in CMDB:

The CMDB is not just a flat list of assets; its true power lies in its ability to map how different components interact. A Relationship defines the dependency or connection between two CIs. For example, a " Web Server " CI might run on a " Linux Server " CI, and an " Email Service " might depend on that " Web Server. "

2. The cmdb_rel_ci Table:

Technically, these connections are stored in a specific table called the CI Relationship table (cmdb_rel_ci). This table acts as a bridge, storing three key pieces of information for every connection:

Parent: The upstream item (e.g., the Service or Application).

Child: The downstream item (e.g., the Server or Database).

Type: The nature of the connection (e.g., " Runs on, " " Depends on, " " Hosted on, " " Members of " ).

3. Dependency Views:

While the Relationship is the underlying data enabler, ServiceNow visualizes these relationships using Dependency Views (formerly known as Business Service Management or BSM maps). Dependency Views use the relationship data to graphically display the infrastructure. By looking at a Dependency View for a Server, you can trace the lines (relationships) upward to see exactly which Business Services will be impacted if that Server goes down.

4. Why the other options are incorrect:

Transform Map: This is a component of the Import Set process. It is used to map source data (from a spreadsheet or XML) to target fields in a ServiceNow table during data import. It does not define infrastructure dependencies.

Automapping Utility: This is not a standard ServiceNow architectural term. While ServiceNow has a " Service Mapping " product that automates the discovery of relationships, " Automapping Utility " is not the specific feature name, nor is it the fundamental element that enables tracing.

Service Tracer: This is a fictitious term and does not exist in the ServiceNow platform.

To manipulate a form in real-time while the user is viewing it (the browser session), you use a Client Script.

1. Requirement Analysis:

" When Caller field is populated... " : This describes an event happening in the browser before the data is sent to the database. This requires an onChange Client Script. When the " Caller " value changes, the script executes (often using GlideAjax to fetch server data) to populate the " Location " field dynamically.

" Add notice... when record is submitted " : This describes an action triggered when the user clicks " Save " or " Submit. " This requires an onSubmit Client Script. The script can validate data or display a message using g_form.addInfoMessage() before the form data is finalized.

2. Why other options are incorrect:

A (UI Script): UI Scripts are typically used to create reusable libraries of JavaScript that can be called from other scripts, or for global UI modifications. They are not the standard tool for specific table-level form logic like " When Caller changes on Incident. "

B (Server script): Server scripts (like Business Rules) run after the browser sends data to the database. While a Business Rule could set the location after the fact, it cannot update the screen in real-time while the user is still typing, nor can it easily show a message " at the top of the page " during the submit process in the same way.

D (JavaScript): While Client Scripts are written in JavaScript, " JavaScript " is a language, not the specific ServiceNow feature/object used to configure this behavior.

To display reminder messages or alerts to users as they interact with forms in ServiceNow, Client Scripts are used. Specifically, an onSubmit Client Script can be configured to display a message or perform validation just before the form is submitted by the user. This script runs on the client (browser) and can prevent submission or prompt the user with informational messages.

Business Rules execute on the server and cannot directly interact with the user interface in real-time. Policies and Data Policies enforce data consistency but do not provide user messages or reminders during form submission.

Therefore, the Client Script is the correct mechanism to display a reminder message dynamically as the incident is submitted.

ServiceNow features a built-in collaboration mechanism known as User Presence . This feature is designed to prevent collisions (two people overwriting each other ' s work) and promote real-time awareness when multiple users are on the same form.

1. User Presence Avatar (Option E):

When multiple users open the same record (like an Incident), a User Presence icon immediately appears in the form header (typically at the top right). This icon displays the avatar or initials of the other user(s) currently viewing the record. If you hover over the avatar, you can see their name.

2. Field-Level Indicators (Option C):

User Presence is not just about who is looking; it also shows what they are doing. If another user actively types into a field or changes a drop-down value, a small " presence indicator " (a colored icon or dot) appears to the left of that specific field on your screen in real-time. This warns you that the field is being modified by someone else before you attempt to edit it yourself.

3. Why the other options are incorrect:

A: The Work Notes list is for logged journal entries, not real-time presence detection.

B & D: While ServiceNow has chat features (like Connect Chat or Sidebar), these do not automatically launch or force notification pop-ups merely because two people open the same record.

In ServiceNow’sConfiguration Management Database (CMDB), threekey tablesform the foundation for storing and managingConfiguration Items (CIs)and theirrelationships.

cmdb_ci (E) - CI Base Class Table

This is thebase classfor allConfiguration Items (CIs)in the CMDB.

Every CI (e.g., servers, applications, network devices) extends from this table.

Stores general attributes like name, serial number, and asset tag.

cmdb (G) - CMDB Parent Table

This is theparent tablefor all CMDB-related tables.

Itdoes not store CI records directlybut serves as a reference structure.

All CMDB tables, includingcmdb_ci, inherit from this table.

cmdb_rel_ci (C) - CMDB Relationship Table

This tablestores relationshipsbetween different CIs.

Example: Aserver hosts an application, or adatabase is dependent on a storage unit.

Helps withimpact analysis and dependency mapping.

A. sn_cmdt_bak

No such table in standard ServiceNow CMDB.

B. sh_emdb_ci

Typo or incorrect table name—not part of the ServiceNow CMDB model.

D. cmdb_bak

" bak " suggests abackup table, but there isno standard " cmdb_bak " in ServiceNow.

F. sh_eomdb

Not a recognized CMDB table in ServiceNow.

UI Policies execute on the Client-side (browser).

Purpose: They are used to dynamically change the behavior of information on a form based on user interaction or data values.

Actions: They primarily control three attributes of a field:

Mandatory (Required)

Visible (Hidden/Shown)

Read-only (Editable/Locked)

Execution: Because they run in the browser, they provide immediate feedback to the user without needing to query the server or reload the page.

In ServiceNow,metricsare essential tools used to track and measure key performance indicators (KPIs) related to IT Service Management (ITSM) processes. They help organizations assess how effectively they are meeting their objectives by collecting data over time.

Definition of a Metric:

Ametricin ServiceNow refers to a method of measuring and evaluating the performance and effectiveness ofIT service management processesover time.

It allows organizations to track changes in records and measure how long specific conditions exist within a workflow.

Key Characteristics of a Metric:

It is used toassess process performanceandevaluate efficiencywithin IT services.

It providesquantifiable datato analyze trends and improvements in Service Management.

Common use cases include trackingincident resolution times,change request approvals, andSLA compliance.

Understanding ServiceNow Metrics:Why Answer " C " is Correct:✔️ " A metric is used to measure and evaluate the effectiveness of IT service management processes. "

This definition aligns precisely with how ServiceNow definesmetrics—theytrack, measure, and analyzethe efficiency of various ITSM processes over time.

Metrics help organizations understand service performance trends and make data-driven decisions.

Why the Other Answers Are Incorrect:A. " A metric is a report gauge used on homepages to display real-time data. "

Incorrectbecausegaugesare UI elements thatvisualizedata from reports or metrics but are not themselves metrics. Metricscollect and measuredata, whereasgaugesdisplay the information.

B. " A metric is a time measurement used to report the effectiveness of workflows and SLAs. "

Incorrectbecause whiletime-based metricsexist (e.g., tracking how long an incident stays in a particular state), metrics in ServiceNow arebroaderand not limited to time measurement alone.

D. " A metric is a comparative measurement used to report the effectiveness of workflows and SLAs. "

Incorrectbecause metrics are not necessarilycomparative; they areabsolute measuresof process effectiveness. Metrics provideraw performance data, which can later be compared or analyzed over time.

ServiceNow CSA Study Guide – Reporting & Performance Analytics

ServiceNow Docs: Metrics Definition & Configuration(ServiceNow Docs - Metrics)

ServiceNow Performance Analytics & Reporting Overview

References from the Certified System Administrator (CSA) Documentation:

In ServiceNow,rolesdefine the level of access a user has within an instance.Roles are stored in thesys_user_roletable.

Definition of a Role:

Aroleis a collection ofpermissionsthat grant access to different parts of the system.

Example:Theadminrole grants full access, while theitilrole allows incident management access.

sys_user_role Table:

This tablestores role recordsand their associated metadata.

Every role has aunique sys_id, aname, and may be associated withparent roles(role inheritance).

Users are linked to roles through thesys_user_has_roletable.

How Roles Work in ServiceNow:

A user assigned a role gainsall the permissionsassociated with that role.

Roles can behierarchical(one role can inherit permissions from another).

Example:Theitil_adminrole includes all the permissions of theitilrole, plus additional privileges.

Key Details About Roles and sys_user_role Table:Why Option D (sys_user_role) Is Correct?sys_user_role→ The correct table where roles are recorded in ServiceNow.

Why Other Options Are Incorrect?A. sys_user→ Incorrect; this table stores user records, not roles.

B. sys_user_profile→ Incorrect; this table does not exist in ServiceNow.

C. sys_user_record→ Incorrect; this is not a valid table in ServiceNow.

ServiceNow Docs – Roles and Role Managementhttps://docs.servicenow.com

ServiceNow Table Schema – sys_user_role

ServiceNow Developer Portal – Role Hierarchy & Best Practices

References from Certified System Administrator (CSA) Documentation: