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.

In ServiceNow,Pluginsare used to activate additional applications or functionalities within a development instance. A plugin is apackage of features, configurations, and applicationsthat extends the platform’s capabilities.

Plugins introduce new capabilities– They allow you to enable or disable specific functionalities, such as ITSM, CMDB, HR Service Delivery, and Performance Analytics.

Plugins can be installed or activatedfrom theSystem Definition > Pluginsmodule.

Some plugins are available by default, while others require activation by an administrator or ServiceNow support.

Plugins can depend on other plugins, meaning some functionality requires multiple plugins to be activated.

A. App Package:No such term in ServiceNow. Applications in ServiceNow are delivered viaPlugins or App Engine Studio, not " App Package. "

B. Updated Pack:Not a ServiceNow term. ServiceNow updates are delivered aspatches or application updates, not an " Updated Pack. "

C. Patch:Apatchis a minor update or bug fix released by ServiceNow but does not introduce new functionality.

E. App Updated Set:Update Setstrack changes in a development instance but are used formigrating configurationsbetween instances, not for activating functionality.

ServiceNow Plugins Documentation:ServiceNow Docs

Managing and Activating Plugins in ServiceNow(Admin Guide)

Why is the Correct Answer " Plugin " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:

InServiceNow,Visual Task Boards (VTBs)provide aKanban-style interfaceto manage and track work. There arethree main typesof Visual Task Boards, but " Feature " is notone of them.

Freeform Board (Valid Type)

Manually created boards wherecards can be moved freelywithout predefined conditions.

Users canadd and organize tasks as needed.

Example: Personal task management.

Guided Board (Valid Type)

Createdfrom a list viewandlinked to a ServiceNow table(e.g., Incident, Change, Task).

Cards on the boardautomatically updatebased on conditions.

Example: Managing Incidents or Change Requests.

Flexible Board (Valid Type)

Similar toGuided Boards, but allows users tomanually reordertasks within lanes.

Offers moreflexibilitywhile still being linked to a data source.

Example: Sprint Planning or ITSM Workflows.

" Feature " is NOT a Visual Task Board type in ServiceNow.

ServiceNow does use the term " Feature " in Agile Development (for tracking high-level product functionalities), but it is not related to VTBs.

Types of Visual Task Boards in ServiceNow:Why is " Feature " Incorrect?

Why Other Options Are Correct?Guided, Flexible, and Freeformare thethree valid typesof Visual Task Boards in ServiceNow.

Visual Task Boards Overview

ServiceNow Visual Task Boards

Types of Visual Task Boards

Creating and Using VTBs

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:

Virtual Agentis ServiceNow’sAI-powered chatbotthat provides assistance via amessaging interface. It helps users obtain information, make decisions, and complete common tasks without human intervention.

Conversational Interface→ Users interact through chat to get information and perform tasks.

Automated Responses→ Uses predefinedtopicsandnatural language understanding (NLU)to provide relevant answers.

Integration with ServiceNow Applications→ Can create incidents, reset passwords, check order statuses, etc.

Available on Multiple Channels→ Works with Microsoft Teams, Slack, and the ServiceNow portal.

A. Agent Workspace→ A unified interface for agents to manage cases, not an AI chatbot.

B. Chat bot→ A generic term; Virtual Agent is the official chatbot in ServiceNow.

D. Knowledge Chat→ No such feature exists; however, Virtual Agent can integrate with the Knowledge Base.

E. Now Support→ ServiceNow’s customer support portal, not an AI-driven assistant.

In ServiceNow, every record in a table has a unique 32-character identifier calledsys_id. This ID uniquely identifies a record and is stored in thesys_id fieldfor every table.

sys_id is a globally unique identifierassigned to every record in ServiceNow.

It is a 32-character hexadecimal string, ensuring uniqueness across instances.

It remains constant for a record, even if other fields in the record are modified.

sys_id is used in API calls, reference fields, and update setsto track records across environments.

A. sn_rec_id:No such field in ServiceNow.

B. rec_id:Not a valid field in ServiceNow.

C. u_id:Not a standard ServiceNow field. Custom fields may use " u_ " prefix butu_id is not a system field.

E. sn_gu_id:No such field in ServiceNow.

F. sn_sys_id:No such standard field in ServiceNow.

G. id:Generic term, but not a standard field in ServiceNow.

ServiceNow Data Model and sys_id Explained: ServiceNow Docs

sys_id Best Practices for Data Management

Why is the Correct Answer " sys_id " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:Thesys_idis crucial for tracking and managing records efficiently in ServiceNow and plays a key role in integrations, workflows, and automation.

Thecorrect answer is " Flows " , which refers toFlow Designerin ServiceNow.

Flow Designeris ano-code/low-code automation toolthat allows users to automatebusiness logicfor a specific application or process, such as:

Approvals

Task creation

Notifications

Record operations(such as updating or deleting records)

AFlowis a sequence of automated actions that are triggered by specific events.

It ispart of Flow Designer, which is themodern alternative to the legacy Workflow Engine.

It providestrigger-based execution, meaning it can run when a record is created, updated, or upon a specific condition.

B. Action Sequences(Incorrect)

No such term exists in ServiceNow.

C. Action Sets(Incorrect)

No such feature exists in ServiceNow.

D. Task Flows(Incorrect)

This is not a term used in ServiceNow automation.

E. Flow Diagrams(Incorrect)

While Flow Designervisually representsflows, there isno feature named " Flow Diagrams " in ServiceNow.

Flow Designer Overview:https://docs.servicenow.com/bundle/utah-automation/page/administer/flow-designer/concept/flow-designer.html

How to Create and Use Flows:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/task/t_CreateFlow.html

Why " Flows " is the Correct Answer:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

ServiceNow provides multiplesecurity-related modulesthat aSystem Administratorfrequently uses to manage access, authentication, and overall system security.

Why These Options Are Correct?A. System Properties > Security

This module allowsadministrators to configure general security settings, including password policies, session timeout, and encryption settings.

It helps manage security parameters at a system-wide level.

E. System Security > Access Control (ACL)

Access Control Lists (ACLs)define what data users can access, modify, and delete within the instance.

ACLs operate at thetable, field, and record levels, ensuring proper role-based access control (RBAC).

This is one of themost commonly usedsecurity modules by admins.

G. System Security > High Security Settings

High Security Settings (previously known as Security Hardening)enforce strict security controls, such as requiring multi-factor authentication (MFA) and enforcing strict password policies.

It is often used for compliance withsecurity regulationslike HIPAA, GDPR, and ISO 27001.

Why the Other Options Are Incorrect?B. Utilities > Migrate Security

This optiondoes not existin ServiceNow. There is no " Migrate Security " under Utilities.

C. System Security > Security

There is no " System Security > Security " module in ServiceNow. The correct structure isSystem Security > Access ControlorSystem Properties > Security.

D. Self-Service > My Access

This is aself-service modulefor end users to request and review their access.

It isnota tool thatSystem Administratorsuse to manage security settings.

F. Password Management > Security Questions

This is used to configuresecurity questions for password recoverybut isnot a core security modulethat admins frequently use.

General Security Settings in ServiceNow

ServiceNow Access Control (ACL) Best Practices

ServiceNow System Security and Role Management

References to Official Certified System Administrator (CSA) Documentation:

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:

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:

TheServiceNow platformprovides variousinterfacesfor users to interact with the system based on their role and requirements. These interfaces cater to different use cases, such as web-based, mobile, and portal-based access.

Now Mobile Apps (A) –Correct

ServiceNow providesNow Mobile applicationsfor bothiOS and Android.

These apps allow users to access self-service options, request services, check approvals, and complete tasks from mobile devices.

Apps includeNow Mobile, Field Service Mobile, and Mobile Agent.

Service Portals (D) –Correct

Service Portalsprovide auser-friendly web interfacethat allows users tosubmit requests, search for knowledge, and interact with catalog itemsin a simplified way.

Service Portals are customizable and used forself-service and customer-facing interactions.

Now Platform® User Interfaces (E) –Correct

This includes the standardUI16 (Current Web Interface), UI Builder for custom interfaces, and theClassic UIfor legacy systems.

Users can access ServiceNow throughdesktop web browsers, mobile web interfaces, and UI frameworks.

B. Agent Control Center(Incorrect)

No such predefined interface exists in ServiceNow as " Agent Control Center. "

C. Back Office Dashboard(Incorrect)

This is not a standard ServiceNow interface but may be a custom-built dashboard.

F. Field Service Taskboard(Incorrect)

This is afeaturewithinField Service Management (FSM), not a platform-wide interface.

ServiceNow User Interfaces Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/concept/c_NavigationAndTheUserInterface.html

Now Mobile App:https://docs.servicenow.com/en-US/bundle/utah-now-mobile/page/administer/service-now-mobile/concept/now-mobile-overview.html

Types of Interfaces in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

In ServiceNow, theEvent Registryis a module thatstores and defines all system eventsthat can be triggered within the platform. Events in ServiceNow are used to trigger business rules, notifications, workflows, and integrations based on specific system activities.

TheEvent Registry [sysevent_register]table containspredefined and custom event definitions.

It allowsdevelopers and administratorsto definenew custom events.

Events can betriggered manually (via scripts) or automaticallybased on system actions.

Events arenot tied to a specific timeframebut are available for use whenever triggered.

Triggering a Notification

When an incident is assigned, an event such as " incident.assigned " is triggered, which can send an email notification to the assigned user.

Initiating an Automated Workflow

When a new user is onboarded, an event like " user.onboarded " can trigger a workflow to create necessary accounts and permissions.

Logging Custom Events for Reporting

Custom events like " asset.verified " can be used to track when an asset verification process is completed.

Key Features of the Event Registry:Example Use Cases of the Event Registry:

TheEvent Registryisnot a log of completed eventsbut arepository of event definitionsthat can be triggered.

It defines bothdefault and custom eventsthat can be used across different system processes.

It is used forevent-driven automationin ServiceNow.

Why " C. The Event Registry is a module that provides Event definitions " is the Correct Answer?

A. The Event Registry lists all Events that have successfully completed within a 24-hour period – Incorrect

This describes theEvent Log [sysevent]table, not the Event Registry.

B. The Event Registry is a list of all Events that originate through an integration – Incorrect

TheEvent Registryis not specific to integrations; it applies to all events in the system.

D. The Event Registry is a list of all Events that have successfully completed after being Invoked by a script – Incorrect

Events triggered by scripts are logged in theEvent Log, not theEvent Registry.

Explanation of Incorrect Options:

ServiceNow Docs: Understanding the Event Registry

ServiceNow CSA Study Guide – Event Management

ServiceNow Product Documentation: Creating and Managing Events

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,tagsare used to categorize and organize records for quick access. When managing tags, users can control theirvisibilityby settingwho can see them.

B. Everyone

The tag ispublicand visible to all users in the instance.

Example: AService Desk teamcreates a " High Priority " tag that everyone can use.

C. Groups and Users

Tags can be restricted to specificgroupsorindividual users.

Example: ASecurity Teamcreates a tag only visible toIT Security staff.

E. Me

Tags can beprivate, meaning only the creator (you) can see them.

Example: A user creates a " Follow-up " tag for theirownpersonal tracking.

A. Admins

Incorrect—Admins can manage tags, but " Admins " isnota visibility setting.

Instead, visibility is set toEveryone, Groups, or Me.

D. Roles and Permissions

Incorrect terminology—ServiceNowdoes notprovide a tag visibility setting based on " Roles and Permissions. "

Tags are assigned based onspecific users or groups, not roles.

In the ServiceNow Shared Responsibility Model, the customer acts as the data controller . The customer determines why personal information is collected and how that information is processed within its ServiceNow environment. This includes decisions concerning collection, storage, use, sharing, retention, archiving, and destruction of data.

ServiceNow ' s official Shared Responsibility Model specifically identifies the customer as the data controller and states that the customer is responsible for meeting applicable privacy-law requirements in jurisdictions where it operates and collects personal data. The customer also remains the owner of the data stored in its ServiceNow instances.

ServiceNow, by contrast, generally performs the role of the data processor in this relationship. ServiceNow provides the platform and maintains appropriate controls designed to protect customer data while assisting customers in satisfying their data-protection obligations. ServiceNow does not decide the business purposes for which the customer ' s personal data is collected or processed.

Datacenter partners may participate in the infrastructure used to deliver cloud services, but that infrastructure role does not make them the customer ' s data controller within the ServiceNow Shared Responsibility Model.

Therefore, the distinction to remember for CSA purposes is: Customer = Data Controller; ServiceNow = Data Processor.

Study Guide Reference/Topics: Security and Access Control → Shared Responsibility Model → Data Privacy → Data Controller → Data Processor → Customer and ServiceNow Responsibilities.