ServiceNow CSA - ServiceNow Certified System Administrator

AnAccess Control rule (ACL)in ServiceNow defineswho can access dataandwhat actions they can performon that data. Each ACL consists of three primary components:

Object being secured– The specific table, field, or record that the rule applies to.

Operation– The type of action that is being secured (e.g., Read, Write, Create, Delete).

Permissions required– The conditions, roles, or scripts that determine whether access is granted.

ACLs evaluatewhether a user has permissionto access a specific table, field, or action.

Thesecurity rules are processed from most specific to least specific(e.g., field-level > table-level).

Permissions can be granted based onroles, conditions, or custom scriptsusing GlideSystem (gs).

A. Groups, Conditional Expressions, and Workflows(Incorrect)

ACLs do not manageworkflowsor directly control group assignments.

B. Table Schema, CRUD, and User Authentication(Incorrect)

CRUD (Create, Read, Update, Delete) permissions are controlled by ACLs, butUser Authenticationis managed separately through login policies (LDAP, SSO, etc.).

D. security_admin(Incorrect)

security_adminis aspecial elevated rolerequired to modify security settings, but it is not what an ACL specifies.

Access Control Rules Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-security/page/administer/security/concept/access-control-rules.html

Configuring ACLs in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-platform-security/page/administer/security/task/t_CreateOrModifyAnAccessControl.html

How ACLs Work in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Record Producersallow users to create records in tables through a user-friendly interface in the Service Catalog. Since the goal is to enableonly first-line workersto order the T-shirt, we need to control access based on their role.

ARecord Producerin the Service Catalog is the best way to gather user input (size, color, etc.) and create a new order record in the system.

The " Available For " list allows administrators to restrict access to specificusers or roles.

TheFirst Line [sn_first_line]role is explicitly designed to includeonly first-line workerswhile excluding managers.

Why is Option A Correct?Why Are the Other Options Incorrect?B. Create Catalog Item and use the Not Available list to specify the Manager Group

Catalog Itemsare valid for this use case but using the " Not Available For " list is a less effective approach.

If newmanager rolesorgroupsare added in the future, this method won’t automatically exclude them.

It’s better toexplicitly definewho can access the item rather than relying on exclusions.

C. Create Catalog Item and use the Available For list to specify ITIL [itil] role

TheITIL roleis typically assigned to Service Desk personnel and IT staff,not first-line workers.

This approach would allowmany unintended usersto request the T-shirt.

D. Create Order Guide and use the User Criteria list to specify First Line [sn_first_line] role

Order Guidesare used to bundle multiple catalog items and guide users through a complex ordering process.

Since this scenario only involves asingle item (T-shirt request),using an Order Guide is unnecessary.

ServiceNow Service Catalog Management - Record Producers

ServiceNow User Criteria and Access Control Best Practices

ServiceNow CSA Guide - Managing Roles and Access Restrictions

References to Official Certified System Administrator (CSA) Documentation:

Afilter conditionin ServiceNow consists of three essential components that define how data is filtered in lists, reports, and queries. These components determine which records meet specific criteria.

Column (D)– Represents thefieldin the table that is being filtered (e.g., " Priority " in theincidenttable).

Operator (A)– Defines the comparison method, such asis, contains, starts with, greater than, etc.

Value (C)– Specifies thecriteriaused for filtering (e.g., " High " for Priority).

Components of a Filter Condition:Example of a Filter Condition in an Incident Table:PriorityisHigh

Column:Priority

Operator:is

Value:High

B. Match Criteria→ Not a defined component; filtering is based on column, operator, and value.

E. Field→ While " Field " is a general term,ServiceNow officially uses " Column " in filter conditions.

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.

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.

When importing data intoServiceNow, anImport Setis created, and aTransform Mapis used to map data from the Import Set table to a target table (such asincident,cmdb_ci, oruser).

ATransform Mapdefineshow data from an Import Set is transferred to the target table. One of its key characteristics is that it can beused multiple times on the same import setto reprocess data or correct mapping errors.

Import Set Table:

Temporary storage for incoming data.

Data remains in the Import Set table until transformed.

Transform Map:

Areusable mappingthat determines how fields in the Import Set correspond to fields in the target table.

Can be runmultiple timeson the same Import Set data.

Coalesce Fields:

Usedbefore transformationto determine whether toupdate existing records or create new ones.

Key Characteristics of Importing Data in ServiceNow:

You import a CSV file into anImport Set Table.

You apply aTransform Mapto map data to theUser (sys_user) table.

If an issue occurs, you canrerun the Transform Map on the same Import Setinstead of reimporting the file.

Example Scenario:

A. An existing Transform Map can be used one time on the same import set– Incorrect.

Transform Maps can be reusedmultiple times on the same Import Set data.

B. Coalesce fields are used only after running Transform– Incorrect.

Coalesce fields are used before transformationto determine if a record should be updated or inserted.

C. Any user can manage and set up import sets– Incorrect.

Onlyusers with the appropriate roles(such asimport_adminoradmin) can manage Import Sets.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Import Sets and Transform Maps

ServiceNow CSA Study Guide → Data Import and Management

ServiceNow Knowledge Base → Understanding Coalesce Fields in Import Sets

References from Certified System Administrator (CSA) Documentation:

TheHistory sectionin theApplication Navigatortracks recently visited records, lists, and forms within ServiceNow. This feature allows users to quickly navigate back to previously accessed content without searching manually.

What Appears in the History Section?The History sectionlogs user activityrelated to:

Records (Option A)– Recently viewed records from any table, such as incidents, requests, or tasks.

Lists (Option C)– Any list views a user has accessed, such asIncident ListorChange Request List.

Forms (Option D)– Any individual record viewed in form view, such as anincident formoruser form.

Why is Option B (UI Pages) Correct?UI Pages do NOT appear in the History section.

UI Pagesare special custom pages built with Jelly scripting and used forcustom interfaces, portals, and dashboards(e.g., Service Portal pages).

Since they do not represent individual records, lists, or forms,they are not included in the user’s History tracking.

Why Are the Other Options Incorrect?A. Records

Recordsare individual database entries (e.g., specific incidents, change requests, or users).

Since records are frequently accessed, theyare logged in History.

C. Lists

Listsdisplay multiple records from a table (e.g., all open incidents).

Since users navigate through lists frequently, theyare logged in History.

D. Forms

Formsare used to view or edit individual records (e.g., an incident form).

Since forms are commonly accessed, theyare logged in History.

Reference from Certified System Administrator (CSA) Documentation: 📌 ServiceNow Docs – Application Navigator & History

🔗 ServiceNow Application Navigator Documentation

" The History section of the Application Navigator displays a list of the records, lists, and forms that you have recently accessed. "

" Custom UI Pages are not included in History tracking. "

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

ADashboardin ServiceNow is an interface that allows users to display multiplePerformance Analytics (PA) widgets, reports, and other visual elementsin a single, consolidated view.

Provides asingle-screenview of critical data, improvingvisibilityinto key metrics.

Can includereports, Performance Analytics indicators, lists, and interactive filters.

Allows users tocustomize layoutsand adjust widgets based on roles and permissions.

Useful forexecutive summaries, ITSM performance tracking, and real-time operational monitoring.

A. Form–

A Form is used todisplay and input data for a single recordin a table (e.g., an incident, change request, or user record).

It does not provide a multi-widget interface.

B. List–

A List displaysmultiple records from a tablein a tabular format but does not support widgets or Performance Analytics.

D. Timeline–

The Timeline visualization is used for showingtime-based data, such as Change Requests over time, but does not provide multiple reporting widgets in a single interface.

ServiceNow Docs: Dashboards Overviewhttps://docs.servicenow.com/en-US/bundle/utah-performance-analytics-and-reporting/page/use/dashboards/concept/dashboard-overview.html

ServiceNow CSA Official Training Guide (Reporting & Dashboards)

Key Features of a ServiceNow Dashboard:Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:

InServiceNow, the best practice for managingusers, groups, and rolesis based onrole-based access control (RBAC).

Assign Roles to Groups (Correct)

Instead of assigning roles directly to users, it is abest practice to assign roles to groups.

This ensuresbetter role management, easier administration, and scalability.

Example:

The " IT Support " group has the " itil " role.

All users in this group automatically get theitilrole.

Add Users to Groups (Correct)

Users should be assigned togroupsrather thanroles directly.

Groups inherit roles, so when a user is added to a group, they automatically receivethe appropriate access.

Example:

A new Service Desk agent joins the " Service Desk " group and immediately gets the associated roles (itil,incident_manager, etc.).

A. You should never assign roles to groups(Incorrect)

Incorrect: Assigning roles to groups is therecommended best practice.

Managing roles at thegroup levelmakesaccess control more efficient and scalable.

B. You should assign roles to users(Incorrect)

Incorrect: Assigning roles directly to users isnot a best practicebecause it becomes difficult to manage as the organization grows.

Instead, users should beadded to groupsthat have the necessary roles.

Best Practices for Users, Groups, and Roles:Why Other Options Are Incorrect?

Managing Users, Groups, and Roles

ServiceNow Best Practices for Roles & Groups

Role-Based Access Control (RBAC)

User Administration

References from ServiceNow CSA Documentation:

ServiceNow providesfive primary rolesthat define access and permissions within the platform. These roles help structure user responsibilities and ensure that users only have access to the necessary functions.

Thehighest level of accessin ServiceNow.

Can manage all platform features, applications, data, and configurations.

Has control overusers, security settings, system properties, and scripting capabilities.

Example: A ServiceNow admin configuring new workflows, modifying tables, or setting up instance-wide settings.

Manages specific applications or functionalities within ServiceNow.

Includes roles such as:

knowledge_admin(Manages Knowledge Base)

report_admin(Manages Reports)

catalog_admin(Manages Service Catalog)

Example: A Knowledge Base Administrator controlling access to articles and updating knowledge categories.

Users with theITIL rolewho perform IT Service Management (ITSM) tasks.

Cancreate, update, and resolve recordssuch as incidents, problems, changes, and requests.

Example: A service desk agent handling incidents and requests.

Users with theApprover rolecanapprove or reject requests, such as change requests or access requests.

Can view or modify approval records directed to them but cannot fulfill other ITIL tasks.

Example: A manager approving a new software installation request.

Basic userswith no assigned roles.

Cansubmit requests, view their own tickets, and access public pages(e.g., Knowledge Base, Catalog).

Example: An employee submitting a request for laptop repair via the ServiceNow portal.

1. System Administrator (admin)2. Specialized Administrator3. Fulfiller (ITIL Role)4. Approver5. Requester (Employee Self-Service - ESS)

These roles form thefoundation of role-based access control (RBAC)in ServiceNow.

They ensure that usersonly access the data and functions relevant to their job responsibilities.

Additional roles can be assigned based on business needs, but these five cover the core platform functionalities.

Why These Are the Provided Roles in ServiceNow:

ServiceNow Documentation:User Roles in ServiceNow

CSA Exam Guide:CoversSystem Administrator, Specialized Administrator, Fulfiller, Approver, and Requesteras the standard user roles.

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

A. System Administrator, B. Specialized Administrator, C. Fulfiller, D. Approver, E. Requester

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.

InServiceNow, tables are structured in a hierarchical format wheresome tables can extend others, inheriting fields and properties. However, there are specific tables thatdo not extend any other table but can be extended—these are known asBase Tables.

Base Tables:

ABase Tableis a table thatdoes not extend another tablebutcan be extended by other tables.

It serves as afoundationfor creating new tables.

Example:

Task Table (task)– TheIncident, Problem, and Change tablesextend from the Task table.

Configuration Item Table (cmdb_ci)– Used as a base for various CI types.

Core Tables:

Core Tablesare thestandard tablesprovided by ServiceNow.

Theycan be base tables or extended tablesdepending on their role.

Example:

Task (task)andUser (sys_user)are core tables, but onlysome core tables are base tables.

Extended Tables:

Extended Tablesare tables thatinherit fields and functionalityfrom aparent table.

Example:

Incident (incident)extends fromTask (task).

Custom Tables:

Custom Tablesare tables thatdevelopers create for specific business needs.

They may or may not extend another table depending on their design.

Understanding Table Types in ServiceNow

Why Answer " A " is Correct:✔️ " Base Tables " are tables that may be extended by other tables but do not extend another table.

These tablesdo not inherit fieldsfrom any other table.

They provide thefoundation for extensions, making them the top-level tables in ServiceNow’s data hierarchy.

Example: TheTask tableis a base table because it does not extend another table but serves as the foundation for many other tables (e.g., Incident, Problem, Change).

Why the Other Answers Are Incorrect:B. " Core Tables "

IncorrectbecauseCore Tables are standard ServiceNow tables, but theycan be either base or extended tables.

Not all core tables follow the definition of a base table.

C. " Extended Tables "

Incorrectbecause extended tablesinherit fields from parent tables, meaning theydo extend another table.

Example: TheIncident table extends from the Task table, making it anextended table.

D. " Custom Tables "

IncorrectbecauseCustom Tablescan beeither base or extended tablesdepending on how they are created.

If a developer chooses to extend an existing table, then it isnot a base table.

ServiceNow CSA Study Guide – Data Schema & Tables

ServiceNow Docs: Table Hierarchy & Extensions(ServiceNow Documentation)

ServiceNow Data Model Overview (Base Tables & Extended Tables)

References from the Certified System Administrator (CSA) Documentation: