CSA Exam Dumps - ServiceNow Certified System Administrator Questions and Answers

In ServiceNow, afilter conditionconsists of three primary components:

Field– The specific column (attribute) in a table that you want to filter by.

Example:State,Priority,Category,Created Date

Operator– Defines the comparison condition between theFieldand theValue.

Example:is, is not, contains, starts with, greater than, less than

Value– The actual data that the filter is looking for.

Example:High (for Priority), New (for State), IT Support (for Category)

Example of a Filter Condition in ServiceNow:If you want to filter Incident records where theStateisNew, the filter condition would be:

Field:State

Operator:is

Value:New

A. Table–

A table is where data is stored, but it isnota component of a filter condition.

Filters are appliedona table but do not include the table itself in the condition.

ServiceNow Docs: Filtering Data in Lists and Reportshttps://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/use/using-lists/concept/filtering-lists.html

ServiceNow CSA Official Training Guide (Filtering and Searching Data)

Why the Other Option is Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms thatField, Operator, and Valueare the three core components of a filter condition.

InServiceNow, the best practice for managingusers, groups, and rolesis based onrole-based access control (RBAC).

Assign Roles to Groups (Correct)

Instead of assigning roles directly to users, it is abest practice to assign roles to groups.

This ensuresbetter role management, easier administration, and scalability.

Example:

The " IT Support " group has the " itil " role.

All users in this group automatically get theitilrole.

Add Users to Groups (Correct)

Users should be assigned togroupsrather thanroles directly.

Groups inherit roles, so when a user is added to a group, they automatically receivethe appropriate access.

Example:

A new Service Desk agent joins the " Service Desk " group and immediately gets the associated roles (itil,incident_manager, etc.).

A. You should never assign roles to groups(Incorrect)

Incorrect: Assigning roles to groups is therecommended best practice.

Managing roles at thegroup levelmakesaccess control more efficient and scalable.

B. You should assign roles to users(Incorrect)

Incorrect: Assigning roles directly to users isnot a best practicebecause it becomes difficult to manage as the organization grows.

Instead, users should beadded to groupsthat have the necessary roles.

Best Practices for Users, Groups, and Roles:Why Other Options Are Incorrect?

Managing Users, Groups, and Roles

ServiceNow Best Practices for Roles & Groups

Role-Based Access Control (RBAC)

User Administration

References from ServiceNow CSA Documentation:

InServiceNow,Access Control Rules (ACLs)define thepermissionsrequired for users to interact with records, fields, or UI actions. ACLs are enforced at thedatabase leveland are evaluatedbefore granting accessto a user.

Access Control rules can be configured usingthree primary permission requirements:

Rolesdefine aset of permissionsassigned to users.

Access Control rules canrequire users to have a specific role(e.g.,admin,itil,catalog_admin) to perform an action on a table, field, or record.

Example:

A rule might state:Only users with theitilrole can read theIncidenttable.

Conditional expressionsallow access based on a specified condition.

These conditions areevaluated at runtime, and access is granted if they are met.

Example:

A condition could be: " Allow access if the record ' s ' State ' field is ' New ' " .

This would mean that users can only modify records if their state is " New " .

Scriptsallow advanced, custom logic to determine access.

ACLs supportserver-side scripts(written in JavaScript) that use thegs.hasRole(),currentobject, or other logic to evaluate whether a user should have access.

Example:

1. Roles (Correct -)2. Conditional Expressions (Correct -)3. Scripts (Correct -)javascript

CopyEdit

// Allow access only if the user is the requester of the record

answer = current.requested_for== gs.getUserID();

Scripts provideflexibilityby allowing complex access conditions beyond simple roles or expressions.

C. Assignment Rules(Incorrect)

Assignment Rulesare used toautomatically assign recordsto users or groups based on conditions.

They do not defineaccess control permissions.

E. User Criteria(Incorrect)

User Criteriais used inService CatalogandKnowledge Base (KB)to control access to catalog items or knowledge articles.

It isnot usedfor ACLs at the table/field level.

F. Groups(Incorrect)

Groupsare collections of users but cannot be directly used in ACLs.

Instead,roles(which are often assigned to groups) are used to define ACL permissions.

Why Other Options Are Incorrect?

ServiceNow Product Documentation - Access Control Rules

Access Control Rules Overview

Defining Access Control Rules

ServiceNow Security Model

Role-Based Access

Scripted ACLs

References from ServiceNow CSA Documentation:

When importing data intoServiceNow, anImport Setis created, and aTransform Mapis used to map data from the Import Set table to a target table (such asincident,cmdb_ci, oruser).

ATransform Mapdefineshow data from an Import Set is transferred to the target table. One of its key characteristics is that it can beused multiple times on the same import setto reprocess data or correct mapping errors.

Import Set Table:

Temporary storage for incoming data.

Data remains in the Import Set table until transformed.

Transform Map:

Areusable mappingthat determines how fields in the Import Set correspond to fields in the target table.

Can be runmultiple timeson the same Import Set data.

Coalesce Fields:

Usedbefore transformationto determine whether toupdate existing records or create new ones.

Key Characteristics of Importing Data in ServiceNow:

You import a CSV file into anImport Set Table.

You apply aTransform Mapto map data to theUser (sys_user) table.

If an issue occurs, you canrerun the Transform Map on the same Import Setinstead of reimporting the file.

Example Scenario:

A. An existing Transform Map can be used one time on the same import set– Incorrect.

Transform Maps can be reusedmultiple times on the same Import Set data.

B. Coalesce fields are used only after running Transform– Incorrect.

Coalesce fields are used before transformationto determine if a record should be updated or inserted.

C. Any user can manage and set up import sets– Incorrect.

Onlyusers with the appropriate roles(such asimport_adminoradmin) can manage Import Sets.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Import Sets and Transform Maps

ServiceNow CSA Study Guide → Data Import and Management

ServiceNow Knowledge Base → Understanding Coalesce Fields in Import Sets

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,User Criteriadefine conditions that determinewhich userscancreate, read, write, and retireknowledge articles in aKnowledge Base (KB). User Criteria help enforceaccess controland ensure that only authorized users can interact with specific knowledge bases.

Control who canread, contribute, edit, or retireknowledge articles.

Based onroles, groups, departments, locations, or custom conditions.

Applied at theKnowledge Base level, affecting all articles within that KB.

Can be combined using " Must match all " or " Match any " logic.

Example 1: Restricting Read Access

A knowledge base for IT Support should be accessibleonly to IT employees.

User Criteria:Department = IT, OR Role = itil

Only IT employees or ITIL users can read articles in this KB.

Example 2: Controlling Who Can Contribute

OnlyHR staffshould be allowed to create or update HR-related knowledge articles.

User Criteria:Group = HR Team, OR Role = knowledge_manager

Only HR Team members and Knowledge Managers can contribute.

User Criteriais the official term in ServiceNow for defining access control conditions for knowledge articles.

It allows precise control over who canread, create, write, or retirearticles.

It is a feature within theKnowledge Management application.

A. User Conditions – Incorrect

No such concept exists in ServiceNow. User Criteria, not " User Conditions, " determine knowledge article access.

B. User Info – Incorrect

" User Info " refers to details stored in thesys_usertable (e.g., name, email) but does not define knowledge permissions.

D. User Permissions – Incorrect

While permissions exist in ServiceNow (via roles and ACLs),User Criteriaspecifically manageKnowledge Baseaccess.

ServiceNow Docs: User Criteria for Knowledge Management

ServiceNow CSA Study Guide – Knowledge Management Permissions

ServiceNow Product Documentation: Configuring Knowledge Base Access

Key Features of User Criteria:Examples of User Criteria:Why " C. User Criteria " is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

Abusiness rulein ServiceNow is a server-side script written inJavaScriptthat executes when a record is inserted, updated, deleted, or queried. Business rules allow for automation and enforcement of business logic without requiring manual intervention.

Business rules arenot tied to formsbut instead runon the server-sidewhen a database operation occurs. They can be configured to execute:

Beforea record is saved (Before Business Rule)

Aftera record is saved (After Business Rule)

Asynchronously(Async Business Rule)

Before a query is run on the database(Query Business Rule)

Explanation of the Correct Answer:B. A business rule can be a piece of JavaScript(Correct)

Business rules are written inJavaScript, allowing administrators to define custom logic that executes on the server.

These scripts can modify data, enforce rules, validate fields, or trigger other workflows.

Example JavaScript snippet for a business rule:

if(current.state== ' 3 ' & & current.priority!= ' 1 ' ) {

current.priority= ' 1 ' ;

gs.addInfoMessage( " Priority set to High because state is Resolved. " );

}

This rule ensures that if an incident ' s state is changed toResolved, its priority is automatically set to High.

Why the Other Options Are Incorrect:A. A business rule must run before a database action occurs (Incorrect)

Business rulescan run before a database action occurs, but they can also executeafterorasynchronously.

Business rules have four execution types:

Before– Runs before the record is inserted/updated in the database.

After– Runs after the record is committed to the database.

Async– Runs in the background after the transaction completes.

Query– Runs before data is returned to a user (modifies query results).

C. A business rule must not run before a database action occurs (Incorrect)

This is false because some business rulesdo run beforea database action (e.g., aBefore Business Rulecan validate data before saving).

D. A business rule monitors fields on a form (Incorrect)

Business rulesdo not monitor form fields directly. Instead, they execute based on database operations.

If real-time monitoring of form fields is needed,Client Scripts(not Business Rules) are used for this purpose.

Automaticallyassigning prioritybased on ticket severity.

Preventing updates to certain records if a condition is not met.

Sending email notifications when a record changes.

Modifying data before it is saved to enforce business policies.

Example Use Cases for Business Rules:

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:

In ServiceNow,Favoritesallow users to quickly accessapplication menus and modulesthat they frequently use. By marking an application menu or module as a favorite, it appears under theFavorites tab in the Application Navigator, making navigation faster and more efficient.

(A) Breadcrumb – Incorrect

Breadcrumbs in ServiceNow show thenavigation pathwithin a list view or form.

They help users filter data quickly but donotstore shortcuts for quick access.

(B) Favorite – Correct

TheFavorite featurein ServiceNow allows users to save frequently used menus and modules for quick access.

Users canadd, remove, and reorderfavorites for better personalization.

Located in theApplication Navigator, favorites appear at the top for easy access.

Favorites can include forms, records, reports, or dashboards.

(C) Tag – Incorrect

Tagsare used toorganize and categorize records(e.g., incidents, problems, change requests).

Tags help users group related records but donotcreate direct menu shortcuts.

(D) Bookmark – Incorrect

ServiceNow doesnotuse the term " Bookmark " for quick access to menus and modules.

While users can bookmark URLs in a web browser, this is different from ServiceNow’s built-inFavoritesfeature.

Explanation of Each Option:

Users cancustomize Favoritesby renaming them or selecting an icon for better visibility.

Admins canpre-configure favoritesfor users based on roles to improve productivity.

Favorites improveuser efficiencyby reducing the number of clicks needed to reach frequently used items.

ServiceNow Docs: Using Favorites in the Application Navigator

https://docs.servicenow.com

ServiceNow Community: Personalizing the Application Navigator with Favorites

https://community.servicenow.com

Additional Notes & Best Practices:References from Certified System Administrator (CSA) Documentation:

ADashboardin ServiceNow is an interface that allows users to display multiplePerformance Analytics (PA) widgets, reports, and other visual elementsin a single, consolidated view.

Provides asingle-screenview of critical data, improvingvisibilityinto key metrics.

Can includereports, Performance Analytics indicators, lists, and interactive filters.

Allows users tocustomize layoutsand adjust widgets based on roles and permissions.

Useful forexecutive summaries, ITSM performance tracking, and real-time operational monitoring.

A. Form–

A Form is used todisplay and input data for a single recordin a table (e.g., an incident, change request, or user record).

It does not provide a multi-widget interface.

B. List–

A List displaysmultiple records from a tablein a tabular format but does not support widgets or Performance Analytics.

D. Timeline–

The Timeline visualization is used for showingtime-based data, such as Change Requests over time, but does not provide multiple reporting widgets in a single interface.

ServiceNow Docs: Dashboards Overviewhttps://docs.servicenow.com/en-US/bundle/utah-performance-analytics-and-reporting/page/use/dashboards/concept/dashboard-overview.html

ServiceNow CSA Official Training Guide (Reporting & Dashboards)

Key Features of a ServiceNow Dashboard:Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:

InServiceNow, anImport Set Tableis atemporary staging areawhere raw data is storedbefore it is transformed and moved into a target table. It is primarily used indata import processesto ensure data integrity and allow transformation before committing data to production tables.

Stores incoming data from external sources(e.g., CSV files, Excel files, APIs, LDAP, etc.).

Acts as a temporary staging areabefore records are mapped and transformed into atarget table(e.g.,incident,cmdb_ci,problem).

Allows validation and error handlingbefore final data migration.

Uses Transform Mapsto determine how fields in the import set relate to fields in the target table.

Key Functions of an Import Set Table:

Data is importedinto anImport Set Tablefrom an external source.

TheImport Set Table temporarily stores the datawithout affecting existing records.

ATransform Mapis applied to move and modify the data before inserting it into the correct table.

Once transformation is complete, the data is transferred to thetarget table, and the Import Set Table can be cleared.

Example Workflow of an Import Set:

(A) A table where data will be placed, post-transformation – Incorrect

Thetarget table(e.g.,incident,cmdb_ci,problem) holds the dataaftertransformation.

TheImport Set Table is only a temporary staging areabefore transformation occurs.

(B) A table that determines relationships – Incorrect

Relationship tables(e.g.,cmdb_rel_ci) definedependencies between recordsbut are not used for data import.

Import Set Tables do not determine relationships between records.

(C) A staging area for imported records – Correct

Import Set Tables temporarily store incoming recordsbefore processing.

The data is transformed and mappedbefore being inserted into the final target table.

This ensuresdata integrity and consistency.

(D) A repository for Update Set information – Incorrect

Update Sets (sys_update_set) store changes to configurations, such as scripts, workflows, and UI policies.

Import Set Tables are used for data imports, not Update Sets.

Explanation of Each Option:

Always review data in the Import Set Table before applying transformationsto avoid incorrect data entry.

Use Transform Mapsto define field mappings between Import Set Tables and target tables.

Monitor Import Logs(sys_import_set_run) for errors or incomplete data.

Delete old Import Set dataperiodically to improve performance and avoid unnecessary storage usage.

Additional Notes & Best Practices:

ServiceNow Docs: Import Set Overview

https://docs.servicenow.com

ServiceNow Community: Best Practices for Import Set Management

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

In theServiceNow Service Catalog, aREQ numberrepresents aRequest (REQ) record, which functions as anorder numberfor a service request. When a user submits a request through the Service Catalog, the system generates aRequest (REQ) record, which tracks the overall order.

REQ (Request Record) – The Order Number

This is theparent recordthat represents the entire order/request submitted by the user.

It contains key details such as the requester, the total cost, approval status, and the overall request state.

Example:REQ0010023

RITM (Requested Item) – The Individual Catalog Item

Each item requested within a REQ has its ownRequested Item (RITM) record.

The RITM tracks the fulfillment of a specific item within the order.

Example:RITM0010456(a single laptop ordered in a request)

TASK (Catalog Task) – The Actions to Complete the Request

Catalog Tasks (TASK) are created under an RITM to handle specific fulfillment steps.

Multiple tasks can exist under a single RITM, assigned to different fulfillment teams.

Example:TASK0013456(a task assigned to IT Support to configure the laptop)

Breakdown of the Service Catalog Request Structure:

Why the Other Options Are Incorrect:B. The stage (Incorrect)

Thestageof a request is part of the request lifecycle (e.g., Approval, Fulfillment, Completed), but it is not represented by theREQ number.

C. The task to complete (Incorrect)

Atask to completeis represented by aCatalog Task (TASK), not theREQ number.

Tasks are specific actions assigned to fulfill an item request.

D. The individual item in the order (Incorrect)

Anindividual itemin a Service Catalog request is represented by aRequested Item (RITM), not theREQ number.

Example Scenario:A user submits a request for anew laptop and a software license:

REQ0012345→ Tracks the overall request (Order Number)

RITM0016789→ Laptop Request

TASK0018901→ IT configures the laptop

RITM0016790→ Software License Request

TASK0018902→ IT assigns the software license

TheUser Menuin ServiceNow is accessible from the top-right corner of the interface by clicking on the user’s avatar or name. This menu provides various options that allow users to manage their sessions, roles, and impersonation settings.

The three correct actions a user can select from the User Menu are:

TheLog Outoption allows users to end their session and securely exit ServiceNow.

It is an essential feature for security and session management.

Location:User Menu > Log Out

Users with appropriate privileges (such as administrators) canelevate their rolesto gain temporary access to higher permissions.

This is primarily used when a user needs elevated access (e.g.,security_admin) to perform specific administrative actions.

Location:User Menu > Elevate Roles

Example:

A system administrator can elevate their role tosecurity_adminto access security-related configurations.

TheImpersonate Userfeature allows an administrator to act as another user without needing their credentials.

This is useful for troubleshooting, testing permissions, and verifying user-specific configurations.

Location:User Menu > Impersonate User

Example:

An admin impersonating a regular user can verify that the correct permissions and UI settings are applied.

1. Log Out ServiceNow (Correct)2. Elevate Roles (Correct, for Admin Users)3. Impersonate Users (Correct, for Admin Users)

Why the Other Options Are Incorrect:A. Send Notifications (Incorrect)

The User Menudoes notinclude an option to send notifications.

Notifications (emails, push notifications, SMS) are managed through:

System Notification > Email > Notifications

Outbound SMS or Messaging Settings

E. Order from Service Catalog (Incorrect)

Users can order items from theService Catalog, butthis action is not available from the User Menu.

Instead, users access the Service Catalog through:

Self-Service > Service Catalog

Requests and Catalog Items pages

F. Approve Records (Incorrect)

Users canapprove recordsif they have approval roles (e.g.,approver), but this action is not directly available from theUser Menu.

Approvals are managed through:

My Approvalsin Self-Service

The Approvals module in theServiceNow application navigator

In ServiceNow Flow Designer, anApplication-based triggeris used to initiate a flow based on events from a specific application. Before using an application-based trigger, you must ensure that the necessaryapplication spokeand any requiredplug-insare activated.

Application Spokes:

Spokes are pre-built integration modules that allow Flow Designer to interact with different applications within ServiceNow.

Each application that provides triggers typically has its own spoke.

Plug-ins:

Some application spokes rely on additional plug-ins for full functionality.

These plug-ins must be enabled before the application-based triggers can be used.

A. Activate application trigger spoke→ Incorrect

There is no generic " Application Trigger Spoke. " Instead, each application has its own spoke that must be enabled.

B. Activate trigger security rules→ Incorrect

Security rules govern access to triggers, but they do not enable the functionality of application-based triggers.

D. Assign Application trigger role [sn_app_trigger_write] to SME→ Incorrect

Roles likesn_app_trigger_writemay provide permissions but do not activate the trigger itself.

E. Activate application plugins only→ Incorrect

While plug-ins may be necessary, you also need to activate the corresponding spoke.

InServiceNow Knowledge Management,User Criteriais used to control access toknowledge bases (KBs)andarticlesbased on user attributes such ascompany, department, group, and roles.

Understanding the Given Criteria:Criteria

Value

Companies

ACME North America

Department

HR

Groups

ACME Manager

Match All

Yes

TheMatch All: Yessetting means thatonly users who meet ALL the specified criteriawill have access.

Who Gets Access?Users must be:

Amember of the ACME Manager group

Part of the HR department

An employee of ACME North America

B. Employees of ACME North America, who are members of HR Department or the ACME Manager group →Incorrect

The " OR " conditionis incorrect becauseMatch All: Yesrequires users to meetALL conditions.

C. Users which are members of either ACME North America, or HR Department, or ACME Manager Group →Incorrect

Again,Match All: Yesmeans usersmust meet all criteria, not just one.

D. Member of the ACME Manager group, and HR department, regardless of geography →Incorrect

Company (ACME North America) is part of the criteria, so itcannot be ignored.

Why Other Options Are Incorrect?

User Criteria for Knowledge Bases

Managing Knowledge Base Access

Official ServiceNow Documentation Reference:

InServiceNow, thePencil (✏) iconis used toeditandcustomizeFavorites in theApplication Navigator.

Open theApplication Navigator.

Locate theFavoritessection.

Click thePencil (✏) iconnext to the favorite you want to edit.

Choose anew iconandcolor.

ClickSaveto apply changes.

B. Star

TheStar iconis used toadd or removea favorite,not editit.

C. Clock

TheClock iconrepresentsRecently Viewed items, not Favorites customization.

D. Triangle

NoTriangle iconis used for modifying Favorites in ServiceNow.