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

In ServiceNow, the"Service Desk > My Groups Work"module is designed to display tasks assigned to a groupbut not yet assigned to an individual user.This means that even if an IT manager oversees theNetworkandHardwareassignment groups, they will not see any tasks in this listif all tasks have already been assigned to specific individualswithin the group.

Let’s break down whyoption Ais the correct answer and why the other options are incorrect:

The"My Groups Work"list only shows tasks that are assigned to thegroupbut have not been assigned to a specificindividualwithin the group.

If all tasks are assigned to specificteam members, then the manager will not see any tasks in this list.

The IT manager can verify this by navigating to theTask List(e.g., Incidents, Changes, or Requests) and filtering by theNetworkandHardwareassignment groups.

Explanation for Correct Answer (A):

Theitil roleallows users toview, create, update, and resolve incidents, changes, problems, and other ITSM tasks.

However, not having this role wouldrestrict accessto various ITSM functionalities, but itdoes notimpact whether tasks appear inMy Groups Work.

If the manager lacks theitilrole, they might have trouble accessing or modifying tasks, but this wouldn't explain why they don’t see anything in the list.

TheService Desk groupis a separate entity in ServiceNow, typically associated with incident handling and user support.

TheMy Groups Workmodule isnot restricted to the Service Desk group—it displays work assigned toany groupthe user belongs to.

Since the manager is responsible for theNetwork and Hardwaregroups, being part of theService Deskgroup is irrelevant.

If the manager wasnot a memberof these groups, they wouldn't seeany group-related tasksat all.

However, the question states that the manager isresponsible for these groups, so it’s reasonable to assume they are either a member or at least agroup managerwith visibility.

Even if they were just a manager and not an officialgroup member, they would still be able to see the tasks assigned to the groups.

TheAssignment Group managerfield is an informational field that indicates who manages a group.

This fielddoes not controlwhat is displayed in theMy Groups Workmodule.

Even if this field were empty, it wouldn’t prevent a manager (who is a group member) from seeing unassigned tasks.

Explanation for Incorrect Answers:(B) The manager does not have the itil role.(C) The manager is not a member of the Service Desk group.(D) The manager is not a member of the Network and Hardware groups.(E) The Assignment Group manager field is empty.

ServiceNow CSA Guide - User Interface and Navigation

ServiceNow ITSM Fundamentals - Incident and Task Management

ServiceNow Role-Based Access Controls and Group Management

ServiceNow KB Articles - My Groups Work Module

References to Official Certified System Administrator (CSA) Documentation:

In ServiceNow,Tagsare used tocategorize, flag, and quickly locate recordswithin the system. Tags help users organize records for easy retrieval and filtering.

User-created or system-defined tagsallow for custom categorization of records.

Tags can beapplied to any record, such asincidents, changes, knowledge articles, or tasks.

Users canfilter records based on tagsfor quick access.

Tags arepersonal(for individual users) orglobal(shared across users).

Incident Management:

A user can tag"High Priority"incidents for quick reference.

Knowledge Base Articles:

Articles related topassword resetcan be tagged as"Password Issues"for easier searchability.

Service Catalog Requests:

Users can tag frequently used catalog items as"Common Requests".

Key Features of Tags in ServiceNow:Example Use Cases of Tags:

Tags categorize and organize records, making them easy to find.

They act ascustom labelsthat help users filter and retrieve records efficiently.

They arebuilt-in featuresin ServiceNow and can be managed from theTag Management module.

Why "C. Tags" is the Correct Answer?

A. Search – Incorrect

TheSearch functionhelps users find records but does not categorize or flag them.

B. Favorites – Incorrect

Favoritesallow users tobookmark frequently accessed modules and reports, but they do not categorize records.

D. Bookmarks – Incorrect

Bookmarksare not a native ServiceNow feature for categorizing records;Favoritesserve this function instead.

Explanation of Incorrect Options:

ServiceNow Docs: Using Tags to Organize Records

ServiceNow CSA Study Guide – Navigating and Searching in ServiceNow

ServiceNow Product Documentation: Managing and Filtering Tagged Records

References from Certified System Administrator (CSA) Documentation:

TheServiceNow Virtual Agentis an AI-powered chatbot that assists userswithin a messaging interface(such as Microsoft Teams, Slack, or Service Portal). It helpsautomate resolutions and guide usersthrough common IT and HR issues.

Incident Auto-ResolutionallowsVirtual Agenttoautomatically detect, intercept, and resolve incidentsbefore they reach a human agent.

It appliesmachine learning (ML) and predefined rulesto determine whether a ticketcan be resolved through automation.

If an issuematches a known solution, the Virtual Agentprovides the resolution stepsto the user.

If self-resolution fails, the ticket isescalated to an agent.

It is anofficial feature in ServiceNow Virtual Agent.

It allows the chatbot tointercept incidentsand attempt resolution before escalation.

B. Ticket Resolver→Incorrect

"Ticket Resolver" isnot an official ServiceNow feature.

C. Virtual Agent Helper→Incorrect

No feature called "Virtual Agent Helper" exists in ServiceNow.

D. Web Intelligence→Incorrect

Web Intelligenceisnot related to ServiceNow Virtual Agent.

What is Incident Auto-Resolution?Why is "A. Incident Auto-Resolution" the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Virtual Agent & Incident Auto-Resolutionhttps://docs.servicenow.com/en-US/bundle/utah-virtual-agent/page/administer/virtual-agent/concept/incident-auto-resolution.html

References from Certified System Administrator (CSA) Documentation:This confirms that"Incident Auto-Resolution" is the correct answer, as it allowsVirtual Agent to intercept and resolve submitted incidents automatically.

Access Control rules in ServiceNow define who cancreate, read, write, or deleterecords in a table or specific fields. These rules are applied at thetable or field leveland follow a specificnaming convention:

TableName.FieldName

Naming Convention for Access Control Rules:

If an Access Control rule applies to a specifictable, its format isTableName(e.g.,incident).

If it applies to a specificfield, it followsTableName.FieldName(e.g.,incident.major_incident).

Major Incident is a field in the Incident table:

Theincidenttable represents the ITSMIncident Management module.

Major Incidentis aspecific fieldwithin theincidenttable.

To apply anAccess Control Ruleto this field, the rule name must beincident.major_incident.

A. Incident.Major_Incident:Incorrect because ServiceNow Access Control rulesdo not use uppercase table or field names—they are alwayslowercase.

B. incident=>major_incident:Incorrect syntax—ServiceNow does not use=>in Access Control names.

C. incident<=>major_incident:Incorrect syntax—ServiceNow does not use<=>in rule naming conventions.

D. incident||major_incident:Incorrect syntax—ServiceNow does not use||(logical OR) in Access Control naming.

ServiceNow Access Control Rules Guide:ServiceNow Docs

How to Create and Manage Access Control Rules in ServiceNow

Why is the Correct Answer "incident.major_incident"?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingincident.major_incident, we correctly definefield-level securityfor theMajor Incidentfield in theIncident table.

InServiceNow, you can add additional fields to a form using either:

Form Layout(for quick field additions)

Form Designer(for a drag-and-drop UI approach)

Context Menu > Configure > Form Layout (B)

This allows administrators toadd or remove fieldsin a simplelist-based interface.

Used when only minor modifications are needed.

Context Menu > Configure > Form Design (C)

Opens theForm Designer, adrag-and-drop UI editorfor configuring forms.

Allows users torearrange fields, sections, and tabseasily.

A. Context Menu > Form > Layout(Incorrect)

The correct path isConfigure > Form Layout, not "Form > Layout."

D. Right-click on header > Add > Field(Incorrect)

Right-clicking the form headerdoes not provide an option to add fields directly.

E. Context Menu > Form > Designer(Incorrect)

The correct option isConfigure > Form Design, not "Form > Designer."

F. Right-click on header > Configure > UX Dashboard(Incorrect)

UX Dashboards areused for analytics and reporting, not form configuration.

Form Layout in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/task/t_ConfigureFormLayout.html

Form Designer Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_FormDesigner.html

Correct Methods:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

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:

AUI Policyis the preferredno-codeapproach in ServiceNow to dynamically control themandatory, read-only, or visibilitystate of form fields based on specified conditions. Unlike Client Scripts, which require JavaScript coding, UI Policies provide aneasy-to-configure, rule-based solution.

They allow administrators tocontrol form behaviorwithout scripting.

They arefaster and more efficientthan Client Scripts.

Theyrun on the client-side, meaning changes occur dynamically as users interact with the form.

Defineconditions(e.g., "Priority is High").

Setactions(e.g., make "Due Date" mandatory, read-only, or hidden).

Apply the UI Policy to the form automatically when the condition is met.

A. UI Action→ UI Actions create buttons, links, or context menu items; they do not control form fields.

B. Client Script→ While Client Scripts can achieve similar functionality, they require JavaScript coding, making them alow-coderather than ano-codesolution.

C. UI Script→ UI Scripts are reusable JavaScript libraries, not designed for controlling form fields.

D. UI Rule→ No such feature exists in ServiceNow.

InServiceNow,Number Maintenanceis the application used to manage and modify numbering schemes for different tables, including theIncidenttable. Since the default prefix forIncident numbersis"INC", an administrator can modify it to a company-specific prefix (e.g.,"IN") by following these steps:

Navigate to the Number Maintenance Application:

Go toAll → System Definition → Number Maintenance

Search for theIncident table (task.number record for Incident).

Modify the Prefix:

Open the existingIncident numbering record.

Change thePrefixfrom"INC"to"IN".

Ensure theNext Numberfield is correctly set (e.g.,"IN0001001").

Save the Changes:

ClickUpdateto apply the new prefix.

All newly created incidents will now follow the new format (IN0001001).

Existing incidents are NOT affected—only newly created records will reflect the new prefix.

Steps to Change the Incident Number Prefix:Why Option A (Number Maintenance) is Correct?The Number Maintenance application is the correct place to modify prefixes for tables like Incident.

Why Other Options Are Incorrect?B. Create a Business Rule that modifies the prefix before the Insert operation→ Incorrect

Business Rulesdo not control number generation.

Number generation is managed byNumber Maintenanceat the system level.

C. The prefix of an incident cannot be changed because it is a built-in feature→ Incorrect

The prefixCAN be changedusing theNumber Maintenanceapplication.

Only existing records retain their original prefix; new records follow the updated format.

D. Submit a Change Request to ServiceNow Technical Support→ Incorrect

This isnot necessary, asadministratorscan make this change directly throughNumber Maintenance.

ServiceNow Docs – Number Maintenance Configurationhttps://docs.servicenow.com

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow Developer Portal – Number Prefix Best Practices

References from Certified System Administrator (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's System Import Sets, administrators canimport data from external sources(such as CSV, Excel, or databases) intoany tablewithin the platform usingTransform Maps.

ATransform Mapdefines how data from an Import Set table is mapped to fields in atarget table (destination table).

Administrators can select any tablein the system as the destination, including bothstandard and custom tables.

Thedestination table is not limitedto Task-related tables (Incident, Problem, Change, etc.).

Users can also applycoalesce rulesto determine if records should be updated or inserted during the transformation.

ServiceNowallows administrators to select any tableas the destination when setting up a Transform Map.

This includes standardITSM tables (Incident, Problem, Change, Task, Service Catalog)as well ascustom tablescreated by administrators.

There areno restrictionson which table can be a destination.

A. "The Task table is the only table that can be a destination"→Incorrect

TheTasktable is widely used, but it isnot the only tablethat can receive imported data.

B. "Only Incident, Problem, Change, Task, and Service Catalog tables can be destinations"→Incorrect

These are common ITSM tables, butany table in the systemcan be selected as a destination.

C. "Only the Incident, Problem, and Change tables can be destinations"→Incorrect

This istoo restrictivebecause other tables, including custom ones, can also be used.

Navigate to:System Import Sets > Create Transform Map

Select the Import Set Tableas thesource.

Choose any available tablein ServiceNow as thedestination.

Definefield mappingsbetween the source and target table.

Configurecoalesce rulesto update or insert records.

ServiceNow Docs: Creating and Using Transform Mapshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/import-sets/concept/c_TransformMap.html

ServiceNow CSA Official Training Guide (Import Sets & Data Management)

Key Points About Transform Maps & Data Import:Why is "D. Any ServiceNow table" the Correct Answer?Why the Other Options Are Incorrect?How to Configure a Transform Map in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms thatany ServiceNow tablecan be adestination tablefor imported data when using Transform Maps inSystem Import Sets.

InServiceNow, afilter conditionis used to definesearch criteriafor records in a table. A filter consists ofthree primary components:

Field→ The database field to be evaluated (e.g.,priority,state,assigned_to).

Operator→ Specifies how the field should be compared to a value (e.g.,is,contains,greater than).

Value→ The expected data in the field (e.g.,High,Resolved,John Doe).

Filter Condition:PriorityisHigh

Field:Priority

Operator:is

Value:High

Another Example:Stateis notResolved

Field:State

Operator:is not

Value:Resolved

Example of a Filter Condition:Why Option A is Correct?Field, Operator, and Valueare the correct components used to create a filter condition.

Why Other Options Are Incorrect?B. Condition, Operator, and Value→ Incorrect because"Condition"is a result of aField + Operator + Value, not a separate component.

C. Field, Condition, and Value→ Incorrect because"Condition"is not a direct component.

D. Variable, Field, and Value→ Incorrect becausevariablesare used in forms, not in filter conditions.

ServiceNow Docs – Creating and Applying Filtershttps://docs.servicenow.com

ServiceNow Learning – Query Builder and Conditions

ServiceNow Best Practices – Using Filters in Lists and Reports

References from Certified System Administrator (CSA) Documentation:

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

TheFlow Designermodule in ServiceNow is used to create and manageautomationsthat involve business logic such asapprovals, tasks, notifications, and integrations. It provides ano-code/low-codeenvironment where users can define automated workflows without needing to write scripts.

Automates Processes– Handles approvals, notifications, and task assignments.

No-Code Interface– Users can build workflows using adrag-and-dropinterface.

Replaces Legacy Workflows– Flow Designer is themodernalternative to Workflow Editor.

Integrates with Spokes– Can connect to other systems usingIntegration Hub.

Triggers– Define when a flow starts (e.g., record changes, schedules, API calls).

Actions– Define what happens (e.g., create a task, send an email, update a record).

Conditions– Add logic to control execution paths.

B. Process Automation > Flow Administration→ Used formanaging existing flows, not creating new ones.

C. Process Automation > Workflow Editor→ This is thelegacyworkflow automation tool, replaced by Flow Designer.

D. Process Automation > Process Flow→ No such module exists in ServiceNow.

E. Process Automation > Active Flows→ Displaysalready running flows, but does not allow new flow creation.

InServiceNow, theSubmit buttonappears whencreating a new record, but it is not visible when editing an existing record. Instead, when editing an existing record, theUpdate buttonis used.

Creating a New Record:

When a user opens a form to create anew record, theSubmit button appears.

ClickingSubmitsaves the record and closes the form.

Example: When creating anew Incident, Change Request, or User record, the Submit button is visible.

Editing an Existing Record:

When a useropens an existing record, theUpdate button replaces the Submit button.

ClickingUpdatesaves the changes but does not create a new record.

Example: Editing anexisting Incident recorddoes not show a Submit button, only Update.

Changing a Reference Field in an Existing Record:

Updating areference field(like Assigned To or Caller) in an existing record does not trigger aSubmitbutton—onlyUpdateis available.

Saving an Old Record:

TheSavebutton may be available when a user makes changes but does not want to exit the form.

When Does the Submit Button Appear?When Does the Submit Button NOT Appear?Why Option B (When Creating a New Record) is Correct?The Submit button appears only when a new record is being created.

Why Other Options Are Incorrect?A. When saving an old record→ Incorrect

TheSave buttonappears when modifying an existing record but does not replaceSubmit.

C. When changing the reference field in an existing record→ Incorrect

Editing a reference field doesnotmake the Submit button appear. OnlyUpdateis available.

D. When updating an existing record→ Incorrect

TheUpdate buttonappears instead ofSubmitwhen modifying an existing record.

ServiceNow Docs – Forms and Form Buttonshttps://docs.servicenow.com

ServiceNow Learning – Creating and Editing Records

ServiceNow Developer Portal – Understanding Form Actions (Submit vs. Update)

References from Certified System Administrator (CSA) Documentation: