Free Practice Questions for ServiceNow CSA Exam

InServiceNow, theService Catalogis a centralized portal where users can request IT services, hardware, software, and other business-related items. Within theService Catalog, the fundamental components are known asService Catalog Items.

Definition of Service Catalog Items:

AService Catalog Itemrepresents a specific service, product, or action that a user can request from theService Catalog.

It is thecore componentthat defines what users can request.

Examples include:

Requesting anew laptop

Submitting anaccess request

Ordering asoftware installation

Why They Are the "Building Blocks" of the Service Catalog:

All Service Catalog requests are based on catalog items—without them, the catalog has no offerings.

Each item has associated workflows, approvals, and fulfillment processesthat define how the request is handled.

They form the foundationof the Service Catalog because every service request must be tied to an item.

Understanding Service Catalog Items

Why Answer "B" is Correct:✔️"They are the building blocks."

Service Catalog Itemsserve as the fundamental componentsof the catalog.

They define what services and products are available for request.

Withoutcatalog items, the Service Catalog would not function as intended.

Why the Other Answers Are Incorrect:A. "They run behind the scenes."

Incorrectbecause Service Catalog Items arevisible to usersin the Service Catalog portal.

While workflows and fulfillment processes may operate in the background, the items themselves arenot hidden.

C. "They are optional."

Incorrectbecause Service Catalog Items aremandatoryfor a functioning Service Catalog.

Thecatalog is useless without catalog items, making them essential, not optional.

D. "They provide options."

Incorrectbecause while Service Catalog Items can havevariables(such as dropdown selections or checkboxes), their primary role isnot just to provide options but to define the services available.

ServiceNow CSA Study Guide – Service Catalog & Request Management

ServiceNow Docs: Service Catalog Overview(ServiceNow Documentation)

ServiceNow Tables & Data Model (sc_catalog, sc_cat_item, sc_request, sc_task)

References from the Certified System Administrator (CSA) Documentation:

In ServiceNow, afilter conditionconsists of three primary components:

Field– The specific column (attribute) in a table that you want to filter by.

Example:State,Priority,Category,Created Date

Operator– Defines the comparison condition between theFieldand theValue.

Example:is, is not, contains, starts with, greater than, less than

Value– The actual data that the filter is looking for.

Example:High (for Priority), New (for State), IT Support (for Category)

Example of a Filter Condition in ServiceNow:If you want to filter Incident records where theStateisNew, the filter condition would be:

Field:State

Operator:is

Value:New

A. Table–

A table is where data is stored, but it isnota component of a filter condition.

Filters are appliedona table but do not include the table itself in the condition.

ServiceNow Docs: Filtering Data in Lists and Reportshttps://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/use/using-lists/concept/filtering-lists.html

ServiceNow CSA Official Training Guide (Filtering and Searching Data)

Why the Other Option is Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms thatField, Operator, and Valueare the three core components of a filter condition.

InServiceNow Knowledge Management,flagging an articleis a feature that allows users toreport errors or issueswithin a knowledge article. This helps maintain article accuracy and ensures that outdated or incorrect information is addressed by knowledge managers.

Error Reporting

Users can flag an article if they findincorrect, outdated, or misleading information.

Knowledge managers receive anotificationabout flagged articles and can review them for updates.

Article Quality Control

Helps improve knowledge base content by allowing users topoint out inaccuracies.

Ensures that knowledge articles remainrelevant and useful.

Notifying Knowledge Managers

Flagged articles appear in theKnowledge Base Administration module, allowing managers totrack and resolve flagged issues.

A. To mark an article to read later

Incorrect: There isnobuilt-in "read later" feature in ServiceNow Knowledge Management.

Instead, users canbookmarkan article for quick access.

B. Allow a user to submit feedback about an article

Incorrect:

Feedback is submitted through theFeedback feature, which allows users to rate articles and provide comments.

Flaggingis specifically forerror reporting, not general feedback.

Key Purposes of Flagging an Article:Why Other Options Are Incorrect?

Flagging Knowledge Articles

Flagging an Article for Review

Managing Flagged Articles

Knowledge Management Administration

References from ServiceNow CSA Documentation:

InServiceNow,Dot-Walkingis a technique used to retrieve information fromreferenced fields across different tables. It allows users to access data stored inrelated records without writing complex scripts.

When a field references another table,dot notation (.)is used totraversethe relationship and retrieve additional information from the referenced table.

It works informs, lists, reports, workflows, business rules, and scripts.

How Dot-Walking Works:Example 1: Retrieving User Information from an Incident RecordLet's say we have anIncidenttable where thecaller_idfield references theUser (sys_user) table.

If we need to retrieve the caller’semail address, we use:

caller_id.email

Here’s how it works:

caller_id→ References thesys_usertable

email→ Retrieves theemail field from the sys_user record

Example 2: Retrieving Department Name of an Incident CallerTo get thedepartmentof the caller, we use:

caller_id.department.name

caller_id→ References theUser table

department→ References theDepartment table

name→ Retrieves thedepartment name

(A) Table-Walking – Incorrect

There isno such termas "Table-Walking" in ServiceNow.

The correct term for referencing related fields isDot-Walking.

(B) Sys_ID Pulling – Incorrect

Thesys_idis a unique identifier for each record in ServiceNow, butpulling sys_ids alone does not retrieve referenced field data.

Dot-Walking allows access to fields in related tables, not just the sys_id.

(C) Dot-Walking – Correct

Dot-Walking is the correct techniqueused in ServiceNow to access referenced fields across tables.

It is used in scripting, reporting, workflows, Business Rules, and UI Policies.

(D) Record-Hopping – Incorrect

There isno such featureas "Record-Hopping" in ServiceNow.

The correct method for referencing data in related tables isDot-Walking.

Explanation of Each Option:

Dot-Walking reduces the need for complex queriesand makes scripting easier.

Use it in filters, reports, and workflowsto dynamically retrieve related data.

Limit excessive Dot-Walking in large tablesto avoid performance issues.

Alternative for scripts: If Dot-Walking does not work in advanced scripts, use GlideRecord queries to retrieve referenced records manually.

Additional Notes & Best Practices:

ServiceNow Docs: Understanding Dot-Walking

https://docs.servicenow.com

ServiceNow Community: Best Practices for Dot-Walking

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

To create anew email notificationin ServiceNow for users affected bynetwork outages, you must navigate to theNotifications moduleunderSystem Notification.

Navigate to:System Notification > Email > Notifications

ClickNewto create a new notification.

Configure the notification with the following:

Name:"Network Outage Notification"

Table:Select the relevant table (e.g.,Incident, Task)

When to Send:Define the trigger (e.g., when anIncident is created or updatedwith a Network Outage category).

Who Will Receive:Specifyaffected users.

Message Content:Create the email subject and body usingdynamic fields(such as affected user’s site).

Save and test the notification.

Notifications are managed in System Notification.

TheNotifications moduleallows you to configureemail triggers, recipients, conditions, and templatesfor system alerts.

B. Administration > Notification Overview:No such module in ServiceNow.

C. System Properties > Email > Settings:This configuresemail server settings, not individual notifications.

D. User Preferences > Email > Notifications:User preferences onlyenable or disablepersonal notifications, not create new ones.

E. Click Gear > Notifications > New:The gear icondoes not provide accessto email notifications.

Creating and Managing Email Notifications in ServiceNow:ServiceNow Docs

ServiceNow Notification Configuration Guide

Steps to Create a New Notification:Why is the Correct Answer "System Notification > Email > Notifications"?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingSystem Notification > Email > Notifications, administrators can create a targetedemail notificationto alert users ofnetwork outageseffectively.

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:

InServiceNow Reporting,Function Fieldsare used toperform calculations, manipulate text, and transform datain a report. These fields allow users to applyarithmetic operations, coalescing, concatenation, and length calculationson existing data.

Arithmetic Operations– Performaddition, subtraction, multiplication, and divisionon numeric fields.

Coalesce– Combine multiple fields into one (useful for handling NULL values).

Concatenation– Join multiple string fields together (e.g., combining first and last names).

Length Calculation– Measure the length of a text field (e.g., checking character count in a description field).

Function fields aredesigned specifically for calculations and data transformationsin reports.

They allowadvanced data processing without requiring scripting.

A. Sourcing Fields→Incorrect

"Sourcing Fields" isnot a valid termin ServiceNow reporting.

C. Computational Fields→Incorrect

While this term sounds relevant,ServiceNow does not use "Computational Fields" in reporting.

D. Calculation Fields→Incorrect

"Calculation Fields" is not an official ServiceNow reporting term.

Function fields handle calculations, not a separate category called "Calculation Fields."

Key Functions of Function Fields:Why is "B. Function Fields" the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Function Fields in Reportinghttps://docs.servicenow.com/en-US/bundle/utah-performance-analytics-and-reporting/page/use/reporting/concept/c_FunctionField.html

References from Certified System Administrator (CSA) Documentation:This confirms that"Function Fields" is the correct answerfor performingarithmetic, coalescing, concatenation, and length calculationsin reporting.

AMany-to-Many (M2M) relationshipin ServiceNow allows two or more tables to be relatedbi-directionally, so that related records are visible in arelated liston both tables.

Unlike aOne-to-Many (1:M)relationship (where only one table references another), M2M relationshipslink records in both directions.

This is achieved through anintermediary table, known as aMany-to-Many table, which stores the relationships.

A Many-to-Many table contains:

Areference fieldfor each of the tables being linked.

The relationship records, which connect records between the two tables.

Suppose you want to relateIncidentstoProblemsand vice versa.

Instead of adding a reference field in each table, you create anm2m_incident_problemtable.

Now, an Incident can be linked tomultipleProblems, and each Problem can be linked tomultipleIncidents.

These relationships will be visible asrelated listsin both tables.

How Many-to-Many Relationships Work in ServiceNow:Example of a Many-to-Many Relationship:

Incorrect Answer Choices Explanation:A. Database View– Used tocombine data from multiple tablesfor reporting but does not establish abi-directional relationshipbetween tables.

C. One to Many (1:M)– Asinglerecord in one table relates tomultiplerecords in another, but the relationship isnot bi-directional.

D. Extended– Refers totable inheritance, where a table inherits fields from its parent table, not a Many-to-Many relationship.

Many-to-Many Relationships in ServiceNow

Understanding Table Relationships

Official CSA Documentation Reference:

TheApplication Navigatorin ServiceNow allows users to quickly filter and locateapplications, modules, and menusby typing keywords in thefilter field.

When you type"service"into the filter field,only modules containing the word "service"in theirname or pathwill be displayed.

Analysis of Each Option:Option

Contains "service"?

Appears in Navigator?

A. Configuration > Business Services

"Business Services" contains "service"

Appears

B. Self-Service > Knowledge

"Self-Service" contains "service"

Appears

C. Service Portal > Widgets

"Service Portal" contains "service"

Appears

D. Incident > Assigned to me

Does NOT contain "service"

Does NOT appear

Since"Incident > Assigned to me"doesnotcontain the word"service", itwould NOT appearin theApplication Navigatorwhen filtering by"service".

Configuration > Business Services

The"Business Services"module underConfigurationincludes the word"service".

Self-Service > Knowledge

The"Self-Service"application contains the word"service", so this module appears.

Service Portal > Widgets

The"Service Portal"module contains the word"service", making it visible.

Incident > Assigned to me

Thisdoes NOT contain "service"in its path, so it willnotappear.

Why the Other Options Appear in the Application Navigator?

ServiceNow Docs: Using the Application Navigatorhttps://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation/concept/c_NavigatingThePlatform.html

References from Certified System Administrator (CSA) Documentation:This confirms that"Incident > Assigned to me" would NOT appearin the Application Navigator when filtering by"service".

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.