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

InServiceNow, thepersonal_listrole allows users toadd or remove fields from a list viewwithout requiring full administrator privileges.

Modify List Layout (Columns & Fields)

Users canadd, remove, or rearrange columnsin list views.

Save Personal List Preferences

Customizations applyonly to the user, unless they have additional permissions to modify system-wide settings.

Does NOT Allow System-Wide Changes

Unlike theadminrole,personal_listonly affectspersonal viewsof lists, not global configurations.

A. personalize.control(Incorrect)

No such role exists in ServiceNow.

C. ui_page_admin(Incorrect)

This role allows users tomanage UI Pages, but it does not provide list customization permissions.

D. ui_action_admin(Incorrect)

This role is used tomanage UI Actions(buttons, links, and client-side scripts), not list view configurations.

Key Capabilities of thepersonal_listRole:Why Other Options Are Incorrect?

Role-Based List Customization

ServiceNow List Personalization

User Roles and Permissions

ServiceNow User Roles

References from ServiceNow CSA Documentation:

In ServiceNow, users can log into theService Portalusingcertificate-based authentication methods. The two commonly supported methods are:

ACACis a smart card issued by theU.S. Department of Defense (DoD).

It is used by military personnel, contractors, and government employees for secure authentication.

ServiceNow supportsCAC authenticationby integrating with external identity providers.

APIV cardis used byU.S. federal agenciesfor authentication.

It followsFederal Information Processing Standard (FIPS) 201for identity verification.

ServiceNow allows users to log in using PIV authentication, ensuringsecure accessto government and enterprise systems.

1. Common Access Card (CAC) – (Correct Answer)2. Personal Identity Verification (PIV) – (Correct Answer)

Both CAC and PIV are widely recognized certificate-based authentication methodsused in ServiceNow for secure user authentication.

They provide multi-factor authentication (MFA)and meet federal security standards.

Why " C. CAC " and " E. PIV " are the Correct Answers?

A. Extended Validation Access (EVA) – Incorrect

No such authentication method exists in ServiceNow.Extended Validation (EV) certificatesare used for website security, not user authentication.

B. Organization Verification Card (OVC) – Incorrect

Not a recognized ServiceNow authentication method.

D. Domain Authentication Card (DAC) – Incorrect

No such authentication method exists in ServiceNow.

Explanation of Incorrect Options:

ServiceNow Docs: Common Access Card (CAC) Authentication

ServiceNow Docs: Personal Identity Verification (PIV) Authentication

ServiceNow CSA Study Guide – Authentication Methods in ServiceNow

References from Certified System Administrator (CSA) Documentation:

InServiceNow, Favorites allow users to quickly access frequently usedmodules, records, lists, or reports. Favorites can be customized, including renaming them, changing their icons, or modifying their colors.

Changing the Label of a FavoriteTorename or edit a Favorite, you must use thePencil icon (✏️), which indicatesedit mode.

Navigate to theApplication Navigatoron the left-hand side.

Locate theFavoritessection.

Hover over the favorite item you want to rename.

Click on thePencil icon(✏️) to open the edit menu.

Update thelabel(name) and other properties like color or icon.

ClickSaveto apply changes.

A. Clock(Incorrect)

TheClock icontypically representsrecently accessed items, not Favorites.

B. Hamburger(Incorrect)

TheHamburger menu (☰)represents navigation menus but is not used to edit Favorites.

D. Three dots(Incorrect)

TheThree dots (⋮)often indicate a menu with additional options but do not specifically edit Favorites.

E. Triangle(Incorrect)

NoTriangle iconis used for renaming Favorites.

F. Star(Incorrect)

TheStar icon (⭐)is used toadd or removeFavorites, but not to rename them.

ServiceNow Favorites Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/task/t_CreateFavorites.html

Steps to Change the Label of a Favorite:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

InServiceNow, anUpdate Setis a mechanism used tocapture customizationsmade in an instance andmove them to another instance(e.g., from development to production). However, certain elements arenot included in an Update Set by default.

Homepages (A) –Correct

Homepages are stored asuser-specific or global content, and they are not included in update sets by default.

To migrate them, you need tomanually export/importthem or use thesys_portal_page_settable.

Data (B) –Correct

Update Setsdo not include actual data, such as incident records, user records, or CMDB data.

Onlyconfiguration changes(like fields, forms, and workflows) are captured.

Data migration must be handled separately usingData Export or Integration methods.

Published Workflows (C) –Correct

Once a workflow ispublished, it is stored as a runtime instance and not automatically included in an Update Set.

To capture it, you mustmanually updatethe workflow before moving it in an Update Set.

Report Definitions (H) –Correct

Reports and their configurations are not automatically included in Update Sets.

You mustmanually include themby marking them as " Captured in Update Set. "

D. Business Rules(Captured in Update Sets)

E. Schedules(Captured in Update Sets)

F. Database changes(Captured in Update Sets)

G. Related Lists(Captured in Update Sets)

I. Scheduled Jobs(Captured in Update Sets)

J. Client Scripts(Captured in Update Sets)

K. Views(Captured in Update Sets)

ServiceNow Update Sets Overview:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/c_UpdateSets.html

ServiceNow Update Set Best Practices:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/update-set-best-practices.html

Items NOT Included in Update Sets (By Default):Items That ARE Included in Update Sets (By Default):Official References from Certified System Administrator (CSA) Documentation:

InServiceNow IntegrationHub, third-party API integrations within aFlow Designerflow are known asspokes. Aspokeis a scoped application containingFlow Designer actions and subflowsthat allow the flow to interact with external systems or ServiceNow applications.

Spokes in IntegrationHub

Aspokeis a collection ofpredefinedandcustomactions, subflows, and data streamsused to integrate with external systems.

Spokes provide ano-code/low-codeapproach to integrating third-party applications.

Examples ofprebuilt spokesavailable in ServiceNow include:

Slack Spoke(for Slack API integrations)

Microsoft Teams Spoke(for Teams integration)

Jira Spoke(for integrating with Atlassian Jira)

How Spokes Work

When a flow needs to interact with an external system (e.g., sending data to Jira or retrieving information from Slack), itcalls an action from a spoke.

Each spoke containsmultiple predefined actionsthat execute API requests or perform tasks like creating records, updating data, or fetching information.

Comparison with Other Options

A. an action→ Incorrect

Actions are individual steps in a flow, not the complete integration package. Actions exist inside spokes.

C. a connection→ Incorrect

Aconnectionis a configuration that stores authentication details (e.g., API keys, OAuth tokens) used by a spoke.

D. an integration step→ Incorrect

No such term as “integration step” exists in ServiceNow IntegrationHub.

ServiceNow Docs - IntegrationHub Overview:https://docs.servicenow.com/en-US/bundle/utah-integrationhub/page/integrate/integrationhub/concept/integrationhub-overview.html

ServiceNow Docs - Spokes in Flow Designer:https://docs.servicenow.com/en-US/bundle/utah-integrationhub/page/administer/integrationhub-spokes/concept/available-spokes.html

Key Concepts Related to IntegrationHub and SpokesOfficial References from the Certified System Administrator (CSA) Documentation:

InServiceNow,UI Actionsare used to addinteractive elementslikebuttons, links, and context menu itemsto forms and lists. They can triggerscripts, workflows, or other actionswhen clicked.

Form Buttons– Buttons that appear on a form (e.g.,Save, Update, Resolve Incident).

List Buttons– Buttons that appear in a list view and perform actions on multiple records.

Related Links– Links that appear in theRelated Linkssection of a form and provide quick navigation or actions.

Common Types of UI Actions:SinceForm Buttons, List Buttons, and Related Linksare alltypes of UI Actions, they arevalid UI Actions.

Search is a built-in system functionalitythat allows users to find records but doesnot involve UI Actions.

UI Actionsexecute predefined actions, whereasSearch simply retrieves and filters data.

ServiceNow search functions (Global Search, List Search, and Quick Search)arenot part of UI Actions.

B. Form Buttons→Valid UI Action

Appears on forms (e.g.,Submit, Save, Update).

C. List Buttons→Valid UI Action

Used in list views for bulk actions (e.g.,Close All, Approve Selected).

D. Related Links→Valid UI Action

Provides quick links in forms (e.g.,View CI Details, Reopen Ticket).

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

ServiceNow CSA Official Training Guide (UI Actions & User Interface Customization)

Why " Search " is NOT a UI Action?Why the Other Options Are UI Actions?References from Certified System Administrator (CSA) Documentation:

In ServiceNow,UI PoliciesandData Policiesserve different but complementary purposes in controlling data behavior and enforcing business rules.

UI Policies are client-side rules that dynamically change form behavior based on user interactions.

They enable administrators to show/hide fields, make fields read-only, or set fields as mandatory dynamically.

UI Policies only apply when a user is interacting with a form through the ServiceNow UI (Client-side execution).

These policies do not enforce rules if data is added via an Import Set, API, or background script.

Data Policies enforce rulesserver-side, meaning they applyregardless of how data is entered(e.g., form submission, Import Sets, SOAP/REST API calls, or Business Rules).

They ensure data integrity by making fields mandatory, setting read-only properties, or applying other restrictions.

Data Policies can apply conditions globally, unlike UI Policies, which work only in the UI context.

UI Policies:Data Policies:Key Differences:Feature

UI Policy

Data Policy

Scope

Affects only forms (Client-side)

Affects all data entry points (Server-side)

Execution Location

Runs in the browser

Runs on the server

Triggers

User interaction on the form

Any data entry method (Forms, Import Sets, API, etc.)

Enforcement

Works only when using the UI

Applies even when data is added outside the UI

" Data Policies run regardless of how data is entered into ServiceNow " →Correct, because Data Policies enforce rules whether the data is entered via UI, API, Import Sets, or other means.

" UI Policies are used for form interactions " →Correct, because UI Policies apply only to client-side form behavior.

Option A: Incorrect. UI Policies are not set by web services; they are applied when interacting with forms.

Option B: Incorrect. While some Data Policies can be converted into UI Policies, the reverse is not true in all cases.

Option D: Incorrect. UI Policies and Data Policies operate independently, and Data Policies do not depend on UI Policies running first.

Why Option C is Correct:Why Other Options are Incorrect:

In ServiceNow,list filtersallow users to define and apply specific conditions to refine data displayed in a list view. If an administrator or user wants to make alist filter available to everyone, they need to:

Assign a Name→ The filter must be named so users can identify and reuse it.

Set Visibility→ The filter’s visibility needs to be adjusted to“Everyone”, a specificgroup, or anindividual user.

Save→ The filter must be saved for it to be accessible in future sessions.

Apply a filterin a list view using the filter conditions.

Click theSavebutton.

Provide anamefor the filter.

UnderVisibility, select one of the following:

Me (Private)→ Only the creator can use the filter.

Everyone (Public)→ All users can access the filter.

Group→ Assign the filter to a specific group.

ClickSaveto store the filter.

Steps to Make a List Filter Available to Everyone:

Why " B. Assign a Name, Set Visibility, and Save " is Correct:Assign a Name→ The filter needs an identifiable name for users.

Set Visibility→ Determines whethereveryone, a group, or just the creatorcan see the filter.

Save→ Saves the filter for future use.

A. Make active, set visibility, and save→Filters do not have an " Active " state; they just need to be saved with the correct visibility settings.

C. Assign a group, set visibility, and save→Assigning a group isoptionalbut does not apply to everyone.

D. Make active, assign a name, and save→ " Make active " is not required; visibility settings control availability.

Why Other Options Are Incorrect:

ServiceNow Documentation:Creating and Sharing List Filters

CSA Exam Guide:CoversList Filters and visibility settings.

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

B. Assign a Name, Set Visibility, and Save

When youimpersonatea user in ServiceNow for testing, you temporarily assume their permissions and role-based access. Toreturn to your own user session, thebestway is toEnd Impersonation.

Click on theUser Menu (top right corner).

Select " End Impersonation " .

You will immediately return to your original user session.

A. Turn your computer off and on again→ Unnecessary and does not affect session management.

B. Clear browser cache→ Cache clearing is not required; impersonation is session-based.

D. Log out and back in→ While this works, it isnot the bestmethod becauseEnd Impersonationis a faster and direct solution.

InPerformance Analytics (PA),long-term signalsarekey performance indicators (KPIs) that help organizations make data-driven decisions for sustained workflow stability. These KPIs providetrends over time, allowing businesses to analyze patterns, predict future performance, and optimize workflows for efficiency.

Track Trends Over Time→ Identify slow-moving changes and patterns.

Support Predictive Analysis→ Help in making data-driven strategic decisions.

Reduce Unplanned Changes→ Avoid reactive decisions by monitoringhistorical data.

Incident Backlog Over Time→ Measures incident accumulation to prevent delays.

Change Success Rate→ Analyzes how well changes are implemented without failures.

Mean Time to Resolution (MTTR)→ Tracks how long it takes to resolve incidents.

How Long-Term Signals Help in Workflow Stability:Example KPIs Used in Performance Analytics:

Why " A. Long-term signals " is Correct:Long-term signals provide historical trends that help organizations maintain stable workflows.

B. Non-signals→No such term exists in Performance Analytics.

C. Anti-signals→Not a recognized Performance Analytics term.

D. Stability signals→Misleading term; long-term signalsare what provide stability insights.

Why Other Options Are Incorrect:

ServiceNow Documentation:Performance Analytics Overview

CSA Exam Guide:Coverslong-term KPI tracking for workflow stability.

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

A. Long-term signals

InServiceNow Knowledge Management, thepublishing and retiring process for knowledge articlesis managed throughWorkflows. These workflows define the steps an article must go through before it is published, updated, or retired.

Submission:

A user creates a knowledge article and submits it for approval.

Approval Process:

Based on the workflow, an article may require manager or SME (Subject Matter Expert) approval.

Publishing:

Once approved, the article ispublishedand made available in the Knowledge Base.

Updating & Versioning:

If edits are needed, the article enters adraft or reviewstate.

Retirement:

When an article is no longer needed, it follows the workflow toretire or archiveit.

Knowledge Approval Publish(requires approval before publishing)

Knowledge Instant Publish(automatically publishes the article)

Knowledge Retire(handles retiring or archiving articles)

A. Approval Policies(Incorrect)

ServiceNow does not use a separate " Approval Policy " for knowledge articles; approvals are managed within the workflow.

B. Approval Definitions(Incorrect)

There is no such specific feature in ServiceNow. Approvals are configured within workflows, not separate definitions.

C. Workflow Designer(Incorrect)

TheWorkflow Designeris a tool used tocreate workflows, but it does not control the publishing process directly. The workflows themselves do.

E. State Lifecycle(Incorrect)

While knowledge articleshave a lifecycle (Draft → Review → Published → Retired), this is controlledby workflows, not by an independent " State Lifecycle " feature.

Knowledge Workflows Overview:https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/knowledge-management/reference/r_KnowledgeWorkflows.html

ServiceNow Knowledge Management Process:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/knowledge-management/concept/knowledge-management-overview.html

How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

ASchema Mapin ServiceNow provides avisual representationof a table ' s relationships, including itsextensions, references, and dependencies. This is useful for administrators and developers to understandhow data is structuredwithin an instance.

Navigate to System Definition > Tables

Select the desired table(e.g.,incident,task,cmdb_ci, etc.)

Scroll to the " Related Links " sectionat the bottom of the form

Click " Show Schema Map "

How to Access the Schema Map for a Table:This will open agraphical representationof the table, showing:

Tables thatextend fromthe selected table

Tables thatreferencethe selected table

Fields that establish relationships

A. System Dictionary > Show Schema Map; Select Table

The Schema Map isnot accessed via the System Dictionary.

C. System Definition > Show Schema Map; Select Table

There is nodirect " Show Schema Map " menuunder System Definition; you must go throughTablesfirst.

D. System Definition > Dictionary: Select Table; Go to Related Links and click Show Schema Map

TheDictionarymodule does not provide a Schema Map option directly for tables.

Schema Maps Overview

Viewing Table Relationships with Schema Map

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

InServiceNow Flow Designer,local flow variablesare accessed in theData Panel as data pills.

Local Flow Variables:

These aretemporary variablesthat storedataduring the execution of a flow.

Can be used topass valuesbetween actions within the same flow.

Accessing Local Variables in the Data Panel:

TheData Panelcontainsdata pills, which representstored values.

Flow variables appear asblue data pillsthat can bedragged and droppedinto different actions.

Example: A variable storingUser IDcan be dragged into an " Assign Task " action to assign a task dynamically.

Why Data Pills?

Data pills act astokensrepresenting values that update dynamically during flow execution.

Ensuresreusabilityandautomationacross multiple actions.

How Flow Variables Work in Flow Designer:Why Option D (As data pills) is Correct?Flow variables appear as " data pills " in the Data Panel, which can be dragged into flow actions.

Why Other Options Are Incorrect?A. As newly generated icons→ Incorrect

No " icons " are generated; flow variables are represented asdata pills.

B. As scratchpad variables→ Incorrect

Scratchpad variablesexist inBusiness Rules, butnot in Flow Designer.

C. As new tabs→ Incorrect

Flow variables donot appear as tabs; they appear in theData Panel as data pills.

ServiceNow Docs – Flow Designer: Using Data Pillshttps://docs.servicenow.com

ServiceNow Learning – Working with Flow Variables and Data Panel

ServiceNow Developer Portal – Flow Designer Best Practices

References from Certified System Administrator (CSA) Documentation: