Free Practice Questions for ServiceNow CSA Exam

In ServiceNow, theglobal search baris located in theBanner Frame, which is thetopmost sectionof the user interface. Theglobal search featureallows users to search across multiple tables and records within the platform.

Searches across multiple record types(Incidents, Knowledge Articles, Change Requests, etc.).

Auto-suggests resultsas you type.

Filters resultsbased on user roles and permissions.

Uses indexingto improve search speed and efficiency.

Key Features of the Global Search in the Banner Frame:

Why "B. Banner frame" is Correct:TheBanner Framecontains theglobal search bar, which enables users to search across all available records in ServiceNow.

A. Application Navigator→The Application Navigator is used forbrowsing modules and applications, not for performing a global search.

C. List pane→The List Pane only displaysrecords from a specific table, and its search is limited to that list view.

D. Content frame→The Content Frame displaysforms, lists, and dashboards, but does not provide a global search function.

Why Other Options Are Incorrect:

ServiceNow Documentation:Global Search in ServiceNow

CSA Exam Guide:CoversBanner Frame and its functions, including Global Search.

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

B. Banner frame

In ServiceNow,Import Setsallow administrators toimport and transform datafrom external sources into ServiceNow tables. The platform supports multiple file formats for importing data, includingXML, CSV, and Excel.

XML (Extensible Markup Language)

Used for structured data exchange between systems.

ServiceNow canimport XML filescontaining records formatted according to its schema.

CSV (Comma-Separated Values)

One of the most common formats for bulk data imports.

ServiceNow can processCSV filesand map them to target tables.

Excel (XLS/XLSX)

ServiceNow allows direct imports fromMicrosoft Excel spreadsheets.

Users can upload Excel files via the Import Set UI.

Supported Data Formats for Import Sets:

Import Data:The user uploads a supported file (XML, CSV, or Excel) into an Import Set table.

Mapping:The imported data is mapped to target tables using aTransform Map.

Transformation & Processing:Data is transformed, validated, and inserted into the correct destination tables.

How Import Sets Work in ServiceNow:

A. CSS, SOAP, and Excel→CSS is a styling language, and SOAP is a protocol, not a data format.

C. SOAP, REST, and XML→SOAP and REST areweb service protocols, not file formats used for import sets. XML is valid but alone is insufficient.

D. XML, SOAP, and CSS→SOAP and CSS are incorrect as they are not standard import file formats.

Why Other Options Are Incorrect:

ServiceNow Documentation:Importing Data into ServiceNow

CSA Exam Guide:Coverssupported data formats for Import Sets (XML, CSV, and Excel).

InServiceNow, theTask [task]table is acore tablethat provides aset of standard fieldsused by multiple tables that extend it, including:

Incident [incident]

Problem [problem]

Change Request [change_request]

Service Request [sc_request]

These tablesinherit fieldsfrom theTasktable, ensuring consistency inassignments, state management, and workflows.

Standard Fields:

Assigned To

Assignment Group

Priority

State

Created By / Updated By

Short Description / Description

Extensibility:

TheIncident, Problem, and Change tablesallextendthe Task table, inheriting its fields.

Developers canadd additional fieldswhile keeping core task properties intact.

TheTask table is the primary tablefor work-related records in ServiceNow.

Itstandardizes fieldsacross multiple ITSM modules.

B. Assignment [assignment]→Incorrect

There isno standard "Assignment" tablein ServiceNow.

Assignments are managed through theTask tablevia theAssigned To and Assignment Group fields.

C. Service [service]→Incorrect

There isno generic "Service" tablethat acts as a core table for ITSM processes.

Service-related items are stored in different tables, such ascmdb_ci_service(for service records).

D. Workflow [workflow]→Incorrect

TheWorkflow tableis used for managing automated workflows anddoes not store task-related records.

Key Features of the Task Table:Why is "A. Task [task]" the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Task Table Overviewhttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/incident-management/concept/task-table.html

References from Certified System Administrator (CSA) Documentation:This confirms thatthe Task table is the core table that extends to Incident, Problem, and other related tables.

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:

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:

InServiceNow, theService Catalogis the primary module where users canorder services and productsoffered by various departments. The Service Catalog provides acentralized portalfor users to browse and requestIT, HR, Facilities, Finance, and other departmental servicesin a structured and automated way.

TheService Catalogis aself-service interfacewhere users can request predefined services, products, and resources.

It acts as adigital storefrontfor an organization's internal and external services.

Each service request follows aworkflowthat may includeapprovals, task assignments, and fulfillment processes.

Service Offerings:

Users can requesthardware (laptops, mobile devices, monitors), software, access permissions, or HR-related services (e.g., PTO requests, onboarding).

Structured Request Fulfillment:

Each request follows aworkflowwith assigned tasks to the appropriate fulfillment teams.

Example: A request for anew laptopis routed toIT Supportfor approval and processing.

Automation and Approvals:

Some catalog items requiremanagerial or departmental approvalsbefore fulfillment.

Example: Requesting access torestricted applicationsmight need approval from anIT admin.

Integration with Incident, Change, and Asset Management:

The Service Catalog can triggerchange requests, incidents, and asset updatesas part of the fulfillment process.

Access Through the Self-Service Portal:

Users can access theService Catalogvia theSelf-Service Portalfor quick and easy navigation.

What is the Service Catalog?Key Features of the Service Catalog:

Why Option A (Service Catalog) is Correct?TheService Catalogis the correct place toorder services and productsoffered by different departments in ServiceNow.

It provides astructured and automatedway to request, approve, and fulfill service requests.

Why Other Options Are Incorrect?B. Self-Service– TheSelf-Service Portalprovides access to the Service Catalog but is not where services are ordered directly.

C. Service Department– No such module exists in ServiceNow. Departments use theService Catalogto provide services.

D. Customer Service– TheCustomer Service Management (CSM)module is forexternal customers, not internal service requests.

ServiceNow Docs – Service Catalog Overviewhttps://docs.servicenow.com

ServiceNow Learning – Self-Service & Service Catalog Best Practices

References from Certified System Administrator (CSA) Documentation:

Thesix methods available for user authenticationin ServiceNow are:

Local Database– The user authenticates using a username and password stored in theinstance database.

Multifactor Authentication (MFA)– The user provides their username, password, and apasscode(e.g., from Google Authenticator).

LDAP (Lightweight Directory Access Protocol)– The user authenticates using credentials stored in a corporateLDAP directory.

SAML 2.0 (Security Assertion Markup Language)– The user is authenticated via an externalSAML Identity Provider (IdP).

OAuth 2.0– The user authenticates via anOAuth identity provider(such as Google, Microsoft, or Facebook).

Digest Token Authentication– The user authenticates using anencrypted tokenrather than directly submitting a password.

Thus, the correct answer is:

A, B, C, D, E, F

ServiceNow supports multiple authentication methods to provideflexibility, security, and integration capabilitieswith external identity providers.

Local Database Authentication:

ServiceNow storesusernames and passwordsin the internal database.

Users authenticate directly with the instance.

This method is commonly used when no external authentication provider is configured.

Multifactor Authentication (MFA):

Enhances security by requiringtwo authentication factors:

Username and password(stored in the database).

Passcodefrom a registered device (such as Google Authenticator, Microsoft Authenticator).

MFA helpsprevent unauthorized accesseven if credentials are compromised.

LDAP Authentication:

Allows users toauthenticate against an external LDAP directory(such as Microsoft Active Directory).

The user must have amatching record in the ServiceNow user table ([sys_user]).

ServiceNowdoes not store passwordswhen using LDAP; it only validates credentials against the directory.

SAML 2.0 Authentication:

Users authenticate via aSAML Identity Provider (IdP)such asOkta, Microsoft Azure AD, or Ping Identity.

ServiceNow acts as aService Provider (SP)and does not store passwords.

ProvidesSingle Sign-On (SSO)capabilities.

OAuth 2.0 Authentication:

Allows authentication viaOAuth providers(Google, Facebook, Microsoft, etc.).

Users do not need to store passwords in ServiceNow; instead, authentication is delegated to theOAuth identity provider.

Digest Token Authentication:

Uses anencrypted token(instead of a plaintext password) to authenticate users.

Often used forAPI-based authenticationor scenarios where passwords should not be transmitted over the network.

Each method aligns with ServiceNow's authentication mechanisms as per official documentation.

ServiceNow supports a hybrid authentication approach, allowing multiple methods to coexist.

ServiceNow Docs – Authentication Methodshttps://docs.servicenow.com

ServiceNow Security Best Practices – Authentication & Access Controls

ServiceNow Developer Portal – SSO & OAuth Authentication

Why These Are the Correct Methods?References from Certified System Administrator (CSA) Documentation:

InServiceNow, aRecordrepresents all thedata saved within a particular form. Each record corresponds to a single entry in atableand contains multiplefieldsstoring different pieces of information.

ARecordis asingle instanceof data stored in a ServiceNowtable.

When a user fills out and submits aform, arecord is createdor updated in the respective table.

Each record has a uniqueSys ID(a 32-character identifier).

Example:

AnIncidentrecord contains fields such asNumber,Caller,Short Description, andPriority.

AChange Requestrecord contains fields likeChange Number,Requested By, andAssignment Group.

A. Fields

Fieldsare individualdata pointswithin a record.

Example: TheCallerandPriorityfields in anIncidentrecord.

B. Form

AFormis auser interfaceto enter and display data, but it does not store data itself.

It is just a way tointeract with records.

D. Lists

AListdisplaysmultiple recordsfrom a table, but each row in a list represents asingle record.

Lists are used for filtering, sorting, and searching records but do not represent a single data entry.

Key Concepts:Why Other Options Are Incorrect?

ServiceNow Data Model - Records and Tables

Understanding Records and Forms

Forms vs. Records vs. Fields

ServiceNow Forms and Records

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

Service Catalog variables in ServiceNow are used to capture user input when they request catalog items, record producers, or order guides. These variables help customize user interactions and drive automation within Service Catalog workflows.

Key Characteristics of Service Catalog Variables:

Global by Default:

When a Service Catalog variable is created, it isglobal by default, meaning it can beused across multiple catalog itemsunless scoped to a specific item.

This helps inreusabilityof variables across different catalog items, reducing redundancy.

However, administrators candisable the "Global" checkboxif they want the variable to be specific to one catalog item.

Types of Service Catalog Variables:

Variables can besingle-line text, choice lists, reference fields, checkbox, multi-line text, and more.

They allow administrators to collect structured data from users during item requests.

Reusability Across Catalog Items:

Global variables can be used across multiple catalog itemswithout creating duplicate variables.

This is useful when multiple items require the same type of user input (e.g., location, department).

Visibility and Dependency:

ServiceNow allowsUI policiesandcatalog client scriptsto control the behavior of these variables dynamically.

Admins can configurevisibility, mandatory status, or dependenciesbased on user selections.

Explanation of Other Options (Why They Are Incorrect):

Option A (Service Catalog variables can only be used in Record Producers) – Incorrect

While Service Catalog variablescanbe used in Record Producers, they arenot limitedto them.

Variables can also be used inCatalog Items, Order Guides, and Requested Items (RITM).

Option B (Service Catalog variables can only be used in Order Guides) – Incorrect

Service Catalog variablescanbe used in Order Guides, but they arenot restrictedto them.

Order Guides allow multiple items to be ordered together, but variables can be used independently in Catalog Items and Record Producers as well.

Option C (Service Catalog variables cannot affect the order price) – Incorrect

Service Catalog variablescan affect pricingthroughVariable Price Mapping.

If configured, variables (like dropdowns or checkboxes) can be linked to aprice adjustment, impacting the total cost of the request.

For example, selecting "Additional Storage" in a cloud server request could add extra costs dynamically.

Official Reference from ServiceNow Certified System Administrator (CSA) Documentation:

ServiceNow Documentation – Service Catalog Variables: ServiceNow Variables Guide

ServiceNow CSA Exam Guide: Covers Service Catalog fundamentals, including variable behavior and reusability.