Free ServiceNow CSA Practice Exam with Questions & Answers | Set: 5

In ServiceNow,tablesare fundamental components of the platform's database structure. A table consists ofrecords (rows)andfields (columns)that store data.

Arecordis an individual entry in a table, similar to a row in a traditional database.

Each record represents a single entity (e.g., an incident, a user, a request).

Records are stored uniquely in the system and are identified by aSys ID(a globally unique identifier).

Afieldis an attribute of a record, like a column in a database.

Each field has a specificdata type(e.g., string, integer, date, reference).

Fields define what type of information can be stored in a record.

1. Records (Rows) – Correct Option2. Fields (Columns) – Correct OptionExample:TheIncident [incident]tableSys ID

Number

Short Description

Caller

State

123abc

INC001

System crash

John D

New

456def

INC002

Network issue

Jane S

Open

Records:INC001, INC002 (each row is a record).

Fields:Number, Short Description, Caller, State (each column is a field).

B. Lists – Incorrect

Listsare aviewof table data but are not a part of the table itself.

A list displays multiple records from a table but does not define the structure of a table.

C. Forms – Incorrect

Formsare user interfaces used to view or edit single records.

A form allows users to interact with the data stored in a table but is not part of the table structure itself.

ServiceNow Docs: Tables and Records

ServiceNow CSA Study Guide – Understanding Tables, Records, and Fields

ServiceNow Product Documentation: List and Form Views

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

In ServiceNow, when applying filters, theFunnel iconopens the condition builder, allowing users to set criteria for displaying records.

Understanding the requirement:

The user wants to seeIncidents where the state is ClosedORIncidents where the Assignment Group is Network.

The key word here isOR, meaning records satisfyingeithercondition should be displayed.

Steps to apply this filter in ServiceNow:

Click theFunnel iconto open the condition builder.

Define thefirst condition→ SelectState = Closed.

Click theORbutton (since we want records meeting either condition).

Define thesecond condition→ SelectAssignment Group = Network.

PressEnterto apply the filter.

Since the user wantseither condition to be true,ORis the correct logical operator.

PressingEnterafter defining the second conditionexecutes the filter.

A. Define the first condition; click AND button; define second condition; click Run:Incorrect becauseANDwould requireboth conditions to be true simultaneously, which is not what the user wants.

B. Define the first condition; click AND button; define second condition; press enter:Same issue as option A—AND willnarrow the resultsinstead ofexpanding them.

D. Define the first condition; click > icon on breadcrumb, define second condition; click Run:Thebreadcrumb navigationis used to modify filtersafter applying them, not to create them initially.

E. Define the first condition; click > icon on breadcrumb, define second condition; press enter:Same issue as option D—breadcrumb navigation is for modifying, not for initial filter creation.

Using Filters and Condition Builder in ServiceNow:ServiceNow Docs

ServiceNow Querying and Filtering Best Practices

Why is the Correct Answer "C"?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:UsingORensures both conditions are considered independently, displaying incidents that are eitherClosedor assigned toNetwork.

In ServiceNow, ataskis a record that represents work that needs to be completed. It follows a lifecycle where it is:

Created– A task is generated, either manually or automatically (e.g., an incident, change request, or problem record).

Worked Upon– Users perform necessary actions, update statuses, and progress the task towards resolution.

Closed– Once completed, the task reaches a closed state, indicating that no further action is needed.

Tasks in ServiceNow are derived from theTask [task]table.

Common task-based records includeIncidents, Change Requests, Problems, and Service Requests.

Tasks follow a defined workflow and state transitions (e.g., New → Work in Progress → Resolved → Closed).

Key Features of a Task:

A. Report:

A report is a visualization of data and does not follow a lifecycle involving work or closure.

B. Workflow:

A workflow definesprocess automationand the movement of tasks, but it is not something that gets "worked upon" directly like a task.

C. Event:

Events are system-generated triggers that notify or automate actions, but they do not have a structured lifecycle like a task.

Why Other Options Are Incorrect:

ServiceNow Documentation:Task Management in ServiceNow

CSA Exam Guide:Coverstask recordsas fundamental entities that go through a lifecycle.

Reference from CSA Documentation:Thus, the correct answer isD. Task.

In ServiceNowKnowledge Management, access to knowledge articles is controlled through access settings in theKnowledge Baserecord. The"Can Read"tab is used to specify which users, groups, or roles canview knowledge articlesin a particular Knowledge Base.

????Why "Can Read"?

TheCan Readlist defines theusers, groups, or roles that can access and view articlesin a specific Knowledge Base.

This ensures thatsensitive or restricted knowledge is only available to authorized users.

If no restrictions are set in theCan Readtab, the knowledge base ispublicly accessibleto all users.

????Steps to Configure "Can Read" Permissions:

Navigate toKnowledge Management > Knowledge Bases.

Open a specificKnowledge Base record.

Go to theCan Readtab.

Add the users, groups, or roles that should be able to read the articles.

Save the record.

????Incorrect Options Explained:

A. Access List– No such tab exists in Knowledge Management.

B. Can Access– Incorrect name; the correct tab isCan Read.

C. Accessible to– Does not exist in the Knowledge Base settings.

????Reference:

ServiceNow Knowledge Management User Roles

Managing Knowledge Base Access

To filter records in alist view, users can:

Click on thefilter icon.

Applyconditionsto refine the displayed records.

✔UI Policiesare the best way to implement dynamic form behavior such asmaking fields mandatory, hiding/showing fields, and setting values based on conditions.

Making "Resolution Code" mandatory when "State" is changed to "Resolved"

This requires aUI Policythat:

Condition:State = Resolved

Action:Set "Resolution Code" field toMandatory = True

Hiding the "Major Incident" checkbox unless the logged-in user has the "Major Incident Manager" role

This requires anotherUI Policythat:

Condition:User does NOT have the rolemajor_incident_manager

Action:Hide the field

Option A (Dictionary Design)

The dictionary defines the structure of fields butdoes not control dynamic form behaviorlike field visibility or conditions.

Option B (Field Limiter)

There is no such feature called "Field Limiter" in ServiceNow.

Option D (UI Design)

"UI Design" is not a recognized concept in ServiceNow.UI Policiesare used for form behavior changes.

Option E (Form Constraint)

There is no "Form Constraint" feature in ServiceNow; ACLs and UI Policies control field behavior instead.

In ServiceNow, a useronlysees modules and records they have permission for, based onroles and group memberships. If an IT user can only seeSelf-Service, it's likely because theylack the required rolesfor IT tasks.

B. His user account does not belong to any groups that contain the ITIL role

TheITIL roleis assigned viauser groups(e.g., "Service Desk," "IT Support").

If the user is not in anITIL role group, theywill notsee IT-related modules.

D. His user account does not have the ITIL role

TheITIL role (itil)is required to accessIncidents, Changes, Tasks, and Service Catalog Management.

Without it, the useronlyseesSelf-Serviceoptions (e.g., requesting services, reporting issues).

A. His user account failed LDAP authentication

If LDAP authentication failed, the userwould not be able to log in at all.

The issue here isrole-based access, not authentication.

C. His user account was not approved by his manager

User approval may be required for account creation, butit does not affect role permissions.

E. His user account is not logged in properly

If the user was not logged in properly, theywould not see any homepage at all.

The issue here islimited access due to missing roles.

In ServiceNow,tablesfollow an inheritance model, where tables can be extended from other tables. The distinction betweenBase Class tablesandParent Class tablesis as follows:

Base Class Table:

ABase Class table is not extended from any other table.

It exists at the top level in the table hierarchy.

Example:Task [task],Configuration Item [cmdb_ci]are base tables.

Parent Class Table:

AParent Class table may be extended from another tablebut also has tables extending from it.

It acts as a bridge between the base table and other extended tables.

Example:Change Request [change_request]extends fromTask [task], makingTaskthe base class andChange Requesta parent class to other change-related tables.

A. Base Class tables always have tables extended from them, Parent tables do not have tables extended from them.

Incorrect because not all base tables have extensions.

Parent tablesdohave extended tables.

C. Extended tables can be extended from Parent tables or Base tables, but they cannot be extended from both.

Incorrect because extended tables caninheritfrom other extended tables in a multi-level hierarchy.

D. Extended tables are always extended from Parent tables, Extended tables are usually extended from Base tables.

Incorrect becauseextended tables can come from either Base or Parent tables, not just Parent tables.

Table Inheritance in ServiceNow

Extending Tables

Definitions:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

Knowledge Management (KM)in ServiceNow is the process that enables users tocreate, categorize, review, approve, and browse important informationin acentralized repositorythat is shared across the organization.

Key Features of Knowledge Management:Centralized knowledge basefor storing important information.

Categorization and taggingfor easy search and retrieval.

Approval workflowsto ensure content accuracy.

Role-based access control(User Criteria) for managing visibility.

Integration with Self-Service and Service Catalogfor user assistance.

Example Use Case:A company’sIT support teamdocuments solutions to common IT issues. Employees cansearch the Knowledge Basefor solutions before opening a ticket, reducing the number of support requests.

A. Self-Service Management →Incorrect

Self-Serviceallows users to submit requests and incidents but doesnot manage knowledge articlessystematically.

C. Knowledge-Centered Management →Incorrect

No such term as"Knowledge-Centered Management"in ServiceNow.

The correct industry term isKnowledge-Centered Service (KCS), but ServiceNow usesKnowledge Management (KM).

D. Information Portal Management →Incorrect

No such concept in ServiceNow; portals provide UI access but do not manage structured knowledge bases.

E. Business Information Management →Incorrect

Business Information Management (BIM)focuses onbusiness data strategy, notknowledge sharing.

Why Other Options Are Incorrect?

Knowledge Management Overview

Creating and Managing Knowledge Articles

Official ServiceNow Documentation Reference: