Pass the ServiceNow Certified System Administrator CSA Questions and answers with ExamsMirror

AnUpdate Setin ServiceNow is a mechanism thattracks and packages customizations and configuration changesso they can be transferred between instances (e.g., fromDevelopmenttoTestorProduction).

It is primarily used ininstance migrationandchange management, ensuring that changes made in one environment can beapplied consistentlyin another.

Tracks Customizations– Records changes to system configurations, such as Business Rules, Client Scripts, UI Policies, and Workflows.

Facilitates Deployment– Enables controlled migration of changes from one ServiceNow instance to another.

Reduces Manual Effort– Instead of manually reconfiguring settings in different environments, administrators can package updates into asingle unit.

Version Control– Ensures that onlyintended changesare moved between instances.

Key Features of Update Sets:

Why the Correct Answer is A:A. An Update Set allows administrators to group a series of changes into a named set and then move this set as a unit to other systems(Correct)

This accurately describes the primary function of anUpdate Set.

Administratorsgroupmultiple changes into anUpdate Set, export it, and apply it to another instance.

Example Workflow:

Admin makes configuration changes(e.g., modifies a Business Rule, updates a Workflow).

Update Set captures those changesin a structured format.

The Update Set is exportedfrom the Development instance.

The Update Set is importedinto the Testing/Production instance and applied.

Why the Other Options Are Incorrect:B. By default, an Update Set includes customizations, Business Rules, and homepages(Incorrect)

Update Setsdo include customizations and Business Rules, but theydo notinclude homepages by default.

Dashboards and homepagesrequire a separate process usingsys_portal_page and sys_ui_page tables.

C. An Update Set is a group of customizations that is moved from Production to Development(Incorrect)

Update Sets are typically movedfrom Development to Test/Production, not the other way around.

Best practice is to make changes inDevelopment, test them inTest/UAT, and then deploy them toProduction.

D. By default, the changes included in an Update Set are visible only in the instance to which they are applied(Incorrect)

This is misleading becausean Update Set can be exported and applied to multiple instances.

Once an Update Set isimported and committed, its changes become active in that instance.

Best Practices for Using Update Sets:✔Always preview an Update Set before committing itto ensure it contains the correct changes.

✔Use Named Update Sets, not the default "Default Update Set," to track changes effectively.

✔Ensure all related changes are included(e.g., dependencies such as script includes and tables).

✔Test Update Sets in a sub-production instancebefore applying them inProduction.

In ServiceNow’sService Catalog, the display sequence of variables within aCatalog Itemis controlled by theOrder field in the Variable form. TheOrder fielddetermines the position in which the variables appear when a user fills out a catalog item. Lower values appear first, and higher values appear later.

(A) The Default Value field in the Catalog Item form – Incorrect

TheDefault Valuefield sets an initial value for a variable but doesnotcontrol the display sequence. It is used to pre-fill a value when the form loads.

(B) The Sequence field in the Catalog Item form – Incorrect

There isno such fieldcalled "Sequence" in the Catalog Item form. The field that determines the sequence of variables is theOrderfield in the Variable form.

(C) The Order field in the Variable form – Correct

Each variable in a catalog item has anOrder field.

Variables with a lower order number are displayedbeforethose with a higher order number.

If multiple variables have the same order value, ServiceNow orders them based oninternal system processing order.

(D) The Choice field in the Variable form – Incorrect

TheChoice fieldapplies only toMultiple Choice, Select Box, and Radio Buttonvariables, determining the selectable options for users. It doesnotcontrol the display sequence of variables in a catalog item form.

Explanation of Each Option:

It is a best practice to useincremental numbering (e.g., 100, 200, 300, etc.)for order values instead of consecutive numbers (e.g., 1, 2, 3). This makes it easier to insert new variables later without having to renumber existing ones.

The order values are respectedunless a layout configuration (e.g., multi-column form layout)changes the positioning.

ServiceNow Docs: Creating and Configuring Service Catalog Variables

https://docs.servicenow.com

ServiceNow Community Best Practices for Service Catalog Variables

https://community.servicenow.com

Additional Notes & Best Practices: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,Tables & Columnsis the module that allows administrators to view and managefield settingsfor a table. This module provides a list of tables in the system along with details about theircolumns (fields), data types, and attributes.

Displaysall fields (columns)within a selected table.

Showsdata types, attributes, and configurationsof each field.

Allows admins toadd, modify, or removefields.

Provides details onrelationships between tables(e.g., reference fields, one-to-many relationships).

Navigate to:System Definition > Tables & Columns

Select a table to view itsfield settings.

B. Access Control – Incorrect

This module managessecurity rules (ACLs)for accessing records but does not display table field settings.

C. Columns and Fields – Incorrect

No such module exists in ServiceNow.

D. Tables and Fields – Incorrect

The correct module name is"Tables & Columns", not "Tables and Fields".

ServiceNow Docs: System Definition – Tables & Columns

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Managing Fields in a Table

Key Features of the "Tables & Columns" Module:How to Access Tables & Columns in ServiceNow:Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

InServiceNow, aListis a visual representation ofmultiple records from a table. Lists allow users to view, filter, sort, and interact with records in a structured tabular format.

Displays multiple recordsfrom a table.

Columns represent fieldsof the table.

Users can personalize the list(e.g., adjust columns, apply filters, and sort).

Common Actions:

Inline editing

Searching

Exporting data

Grouping and filtering

A. View

AViewdefines how data is displayed, but it is not a list itself.

Example: Differentform viewscan be created for the same table.

B. Dashboard

ADashboardis a visual representation of reports and performance analytics.

It doesnot display raw table recordsdirectly.

C. Panel

No such term as "Panel" exists in ServiceNow for displaying records from a table.

Key Features of Lists:Why Other Options Are Incorrect?

Lists Overview

ServiceNow Lists Documentation

Personalizing Lists

List Personalization Guide

References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (CSA) documentation.

InServiceNow, when working with forms (such as Incident, Change, or Task forms), users can perform different actions tosave records. The two key operations in this context areInsertandUpdate.

Creates a new record in the database.

Saves the record and exits the form(returns to the list view or the previous screen).

The form is cleared after inserting the record.

It doesnotmodify an existing record; instead, it generates anew record with a new unique sys_id.

Example:

A user creates a newIncident, fills in details, and clicksInsert.

The systemsaves the new Incident and exitsto the list view.

Saves changes to an existing record.

Remains on the form after saving.

It doesnot create a new record; itmodifies the existing recordin place.

Example:

A user opens an existing Incident, changes the Priority, and clicksUpdate.

The systemsaves the changes but keeps the user on the form.

1. Insert Operation (Correct Description in Option C)2. Update Operation (Correct Description in Option C)

Why the Other Options Are Incorrect:A. Insert creates a new record and Update saves changes, both remain on the form (Incorrect)

Insert does not remain on the form; it exits after creating a new record.

B. Insert creates a new record and Update saves changes, both exit the form (Incorrect)

Update does not exit the form; it remains on the form after saving.

D. Insert saves changes and remains on the form, Update saves changes and exits the form (Incorrect)

Insert exitsafter creating a new record.

Update remains on the form, not exits.

Insert and Stay: This is avariation of Insert, whichcreates a new record but keeps the form openfor additional edits.

Submit vs. Insert:

Submitis typically used when submitting a form for workflow processing (e.g., Service Catalog Requests).

Insertexplicitly saves a record as a new entry.

Additional Notes:

Example Scenario in Incident Management:Action

Result

Click "Insert"

Creates anewIncident andexitsthe form.

Click "Update"

Saves changes to theexistingrecord andstays on the form.

Themain UI components of the ServiceNow platformare designed to provide a structured and user-friendly experience for interacting with the system. These core UI elements include:

Banner Frame– Displays key information such as the logo, user profile, settings, and global search.

Application Navigator– Provides access to different modules and applications within ServiceNow.

Content Frame– Displays the main content area where users interact with forms, lists, and dashboards.

A. Banner Navigator– Incorrect terminology; the correct term isBanner Frame.

C. Application Frame– No such UI component exists in ServiceNow.

E. Content Menu– This is not a primary UI component; the correct term isContent Frame.

Why Other Options Are Incorrect:

ServiceNow Documentation:User Interface Overview

CSA Exam Guide:CoversBanner Frame, Application Navigator, and Content Frameas the three primary UI components.

Reference from CSA Documentation:Thus, the correct answer is:

B. Banner Frame, D. Application Navigator, F. Content Frame

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:

n ServiceNow, theList Editorallows users to edit field values directly within a list without opening the record in a form. This feature is particularly useful for making quick modifications to multiple records without the need to open each one individually.

Users navigate to a list view of records (e.g., an incident list).

If a field is editable via the List Editor, clicking on it will allow inline editing.

After making changes, users can pressEnteror click outside the field to save.

Inline Editing:Users can modify fields directly from the list.

Multi-Row Editing:Certain fields support bulk updates.

Security Controls:Admins can control which fields are editable via List Editor through dictionary settings.

Audit and History Tracking:Changes made via List Editor are logged for tracking purposes.

A. Data Editor:No such term as "Data Editor" exists in ServiceNow.

B. Edit Menu:This does not refer to inline editing; instead, it's a general menu for editing options.

D. Form Designer:Used for configuring form layouts, not for inline editing.

ServiceNow Product Documentation → Lists and List Editing

ServiceNow CSA Exam Guide → Covers List Editor as a core feature of instance configuration.

How List Editor Works:Key Features of List Editor:Why Other Options Are Incorrect:Reference from CSA Documentation:This verifies thatList Editoris the correct answer.

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:

InServiceNow Knowledge Management, knowledge articles must be in a specificstatebefore they can be visible to end users. The correct state that allows users to view the article isPublished.

Understanding Knowledge Article StatesKnowledge articles in ServiceNow go through alifecyclethat includes the following states:

Draft– The article is being created or edited and isnot visibleto end users.

Review– The article is under internal review by approvers before publication. It remainshiddenfrom users.

Published– The article isapproved and publicly availableto users who have access to the Knowledge Base.

Retired– The article is no longer relevant or has been replaced. It isnot visibleto end users.

OnlyPublishedarticles appear in the Knowledge Base and can be accessed by users.

Articles inDraft, Review, or Retiredstates arenot visibleto the general audience.

B. Drafted– Articles inDraftare still being written or edited andcannot be accessed by users.

C. Retired– Retired articles are considered obsolete and areno longer displayedin the Knowledge Base.

D. Reviewed– Articles inRevieware under approval butare not yet visibleto users.

ServiceNow Docs: Knowledge Article Stateshttps://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/knowledge-management/concept/knowledge-article-states.html

ServiceNow CSA Official Training Guide (Knowledge Management Lifecycle & Publishing Workflow)

Why is "Published" the Correct Answer?Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that aknowledge article must be in the "Published" stateto be visible to users in the Knowledge Base.

TheConfiguration Management Database (CMDB)in ServiceNow is a centralized repository that stores information aboutConfiguration Items (CIs), which can includeboth tangible and intangible business assets.

Tangible assets: Physical devices like servers, network components, and workstations.

Intangible assets: Software, applications, cloud services, licenses, and business services.

Relationships and Dependencies: CMDB maintains the relationships between CIs to help with impact analysis, change management, and troubleshooting.

What is Stored in the CMDB?CMDB plays a crucial role inIT Service Management (ITSM), ensuring that organizations haveaccurate and up-to-dateasset data for better decision-making.

(A) The CMDB contains data about tangible and intangible business assets – Correct

TheCMDB tracks and manages both physical (tangible) and virtual (intangible) assets.

Examples oftangible assets: Servers, routers, desktops, mobile devices.

Examples ofintangible assets: Cloud services, software applications, business services.

(B) The CMDB contains the Business Rules that direct the intangible, configurable assets used by a company – Incorrect

Business Rules are not stored in the CMDB.

Business Rules in ServiceNow are part of the platform’s automation framework and control system behavior but donotdefine configuration items.

(C) The CMDB archives all Service Management PaaS equipment metadata and usage statistics – Incorrect

TheCMDB does not function as an archive; it maintains real-time, active data about CIs.

Usage statistics are stored in performance analytics and reporting tools, not in the CMDB.

(D) The CMDB contains ITIL process data pertaining to configuration items – Incorrect

While CMDBsupports ITIL processes, it doesnot store ITIL process datadirectly.

ITIL process data (e.g., incident, problem, change records) is stored inITSM modules, not in the CMDB itself.

CMDBdoes contain CI relationshipsthatsupportITIL processes likeIncident, Problem, and Change Management.

Explanation of Each Option:

CI Classes & Hierarchy: ServiceNow CMDB uses a hierarchical structure with variousCI Classes(e.g.,cmdb_ci,cmdb_ci_server,cmdb_ci_database).

CMDB Health Dashboard: Ensures data accuracy withcompleteness, compliance, and correctnessmetrics.

Relationship Management: CIs in the CMDB are linked to show dependencies, which iscrucial for impact analysisin change and incident management.

Discovery & Service Mapping: ServiceNow’sDiscovery and Service Mappingtools helpautomate CI data collection.

Additional Notes & Best Practices:

ServiceNow Docs: CMDB Overview

https://docs.servicenow.com

ServiceNow Community: Best Practices for CMDB Data Accuracy

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

UI Policies and UI Actionsare both part of theServiceNow user interface customizationbut serve different purposes.

Used todynamically change form field behaviorsbased on specific conditions.

Canmake fields read-only, mandatory, or hiddenwithout requiring scripts.

Runson the client-side (browser)to improve performance and responsiveness.

Example:

If theCategoryisHardware, theSerial Numberfield becomesmandatory.

Used tocreate buttons, links, and context menu actions.

Can executescriptsto perform specific actions when clicked.

Runs on theserver-side or client-sidedepending on configuration.

Example:

A"Save" buttonthat becomesvisible only to users with a specific role.

UI Policy(not UI Action) is responsible for making fieldsread-only, mandatory, or hidden.

UI Action(not UI Policy) is responsible for making aSave button visiblefor specific users.

ServiceNow Docs: UI Policy Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_UIPolicies.html

ServiceNow Docs: UI Action Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_UIActions.html

UI Policy:UI Action:Why Option A is Incorrect?References from Certified System Administrator (CSA) Documentation: