Free ServiceNow CSA Exam Dumps August 2026

Access Control Lists (ACLs) in ServiceNow define who can read, write, create, or delete records in the system. ACLs apply to tables, fields, and UI elements.

Option A (Role Assignment Rules) is incorrect because roles grant access but do not define granular security controls.

Option B (Scripted User Rules) is incorrect because there is no such feature in ServiceNow.

Option C (CRUD Rules) is incorrect because CRUD (Create, Read, Update, Delete) permissions are enforced through ACLs.

Option D (User Authentication Rules) is incorrect because authentication rules control login access, not data access.

Reference: ServiceNow Security & Access Control -- ACLs & Security Rules

In ServiceNow, access to applications is controlled by roles. Most applications, such as Incident, Change, and Facilities, require specific roles to access them. However, the Self-Service application is available to all users, including those with the base 'ess' (Employee Self-Service) role, which is assigned to every user by default.

Why 'D. Self-Service' is the correct answer?

The Self-Service application is designed for general users (end users, employees, customers) who do not have elevated permissions. It provides access to:

The Service Catalog (to request IT services, software, and hardware).

The Knowledge Base (to search for articles and solutions).

Viewing and tracking submitted requests and incidents.

Submitting new incidents or requests.

Since it is meant for all users, it does not require any additional roles beyond the default ones given to employees or customers.

Explanation of Incorrect Options:

A . Change -- Incorrect. The Change Management application is typically restricted to ITIL users (users with the itil role) and change managers. End users do not have access to this module.

B . Incident -- Incorrect. While end users can create and view their own incidents via Self-Service, the Incident Management module itself is restricted to IT support staff (users with the itil role or higher).

C . Facilities -- Incorrect. The Facilities application, which includes asset tracking and work orders, is typically restricted to users managing physical assets or facility-related tasks. It is not available to all users by default.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Product Documentation - Self-Service Application Overview

ServiceNow CSA Study Guide - User Roles and Permissions

ServiceNow Docs: Access Control and Application Scope

In ServiceNow, reports can be created from multiple locations within the platform. Reports provide insights into data stored within the system and help visualize trends, patterns, and key performance indicators (KPIs). The two correct locations from which reports can be created are:

1. List Column Heading ( Correct)

ServiceNow allows users to create a report directly from a list view.

This feature is useful when working with records in a table, as it enables quick reporting based on the visible columns.

To generate a report from a list view:

Navigate to a list view (e.g., Incidents, Requests, etc.).

Click on a column heading to access the context menu.

Select Bar Chart, Pie Chart, or other visualization options to generate an instant report.

If needed, refine the report using the reporting interface.

2. View / Run Module ( Correct)

The View / Run module is the primary location for creating and managing reports in ServiceNow.

It allows users to create new reports, modify existing reports, and run pre-built reports.

Users can access the Report Designer from this module, where they can configure:

Data sources (tables)

Report type (bar chart, pie chart, trend, etc.)

Filters and conditions

Visualization settings

To access it:

Navigate to Reports > View / Run in the Application Navigator.

Click Create a Report to start building a new report.

Why the Other Options Are Incorrect:

B. Metrics module (Incorrect)

The Metrics module in ServiceNow is used to track and measure the performance of records over time, but it is not used to create reports.

Metrics focus on data such as time to resolution, SLA compliance, and process efficiency, but reporting is handled separately in the Reports module.

C. Statistics module (Incorrect)

ServiceNow does not have a dedicated Statistics module for report creation.

While reports can generate statistical insights, this is done within the View / Run module and not a standalone 'Statistics module.'

ServiceNow Documentation: Creating and Running Reports

ServiceNow CSA Learning Path: Reporting and Performance Analytics

ServiceNow Docs: Working with Lists and Reports

When creating a custom table in ServiceNow, the platform automatically assigns a table name prefixed with 'u_' to differentiate custom tables from out-of-the-box (OOB) tables.

Naming Convention for Custom Tables:

The default prefix 'u_' is applied to all custom global tables.

The table name follows the format: 'u_' + [custom name].

Example:

If you create a table named 'abc', the system assigns it the table name: u_abc.

Why 'C. u_abc' is Correct?

All custom tables created by users automatically receive the 'u_' prefix.

Prevents conflicts with ServiceNow's internal tables.

Ensures custom tables are easy to identify.

Explanation of Incorrect Options:

A . snc_abc -- Incorrect

'snc_' is not used for custom tables; it is reserved for internal ServiceNow functionality.

B . abc -- Incorrect

Custom tables do not use raw names; they always include a prefix (u_).

D . sys_abc -- Incorrect

'sys_' is reserved for system tables (e.g., sys_user, sys_db_object).

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide -- Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

The History section in the Application Navigator tracks 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 section logs user activity related 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 as Incident List or Change Request List.

Forms ( Option D) -- Any individual record viewed in form view, such as an incident form or user form.

Why is Option B (UI Pages) Correct?

UI Pages do NOT appear in the History section.

UI Pages are special custom pages built with Jelly scripting and used for custom 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

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

Since records are frequently accessed, they are logged in History.

C. Lists

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

Since users navigate through lists frequently, they are logged in History.

D. Forms

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

Since forms are commonly accessed, they are 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.'

To create a new email notification in ServiceNow for users affected by network outages, you must navigate to the Notifications module under System Notification.

Steps to Create a New Notification:

Navigate to: System Notification > Email > Notifications

Click New to 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 an Incident is created or updated with a Network Outage category).

Who Will Receive: Specify affected users.

Message Content: Create the email subject and body using dynamic fields (such as affected user's site).

Save and test the notification.

Why is the Correct Answer 'System Notification > Email > Notifications'?

Notifications are managed in System Notification.

The Notifications module allows you to configure email triggers, recipients, conditions, and templates for system alerts.

Why Not the Other Options?

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

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

D . User Preferences > Email > Notifications: User preferences only enable or disable personal notifications, not create new ones.

E . Click Gear > Notifications > New: The gear icon does not provide access to email notifications.

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

Creating and Managing Email Notifications in ServiceNow: ServiceNow Docs

ServiceNow Notification Configuration Guide

By using System Notification > Email > Notifications, administrators can create a targeted email notification to alert users of network outages effectively.

In Performance Analytics (PA), long-term signals are key performance indicators (KPIs) that help organizations make data-driven decisions for sustained workflow stability. These KPIs provide trends over time, allowing businesses to analyze patterns, predict future performance, and optimize workflows for efficiency.

How Long-Term Signals Help in Workflow Stability:

Track Trends Over Time Identify slow-moving changes and patterns.

Support Predictive Analysis Help in making data-driven strategic decisions.

Reduce Unplanned Changes Avoid reactive decisions by monitoring historical data.

Example KPIs Used in Performance Analytics:

Incident Backlog Over Time Measures incident accumulation to prevent delays.

Change Success Rate Analyzes how well changes are implemented without failures.

Mean Time to Resolution (MTTR) Tracks how long it takes to resolve incidents.

Why 'A. Long-term signals' is Correct:

Long-term signals provide historical trends that help organizations maintain stable workflows.

Why Other Options Are Incorrect:

B . Non-signals No such term exists in Performance Analytics.

C . Anti-signals Not a recognized Performance Analytics term.

D . Stability signals Misleading term; long-term signals are what provide stability insights.

Reference from CSA Documentation:

ServiceNow Documentation: Performance Analytics Overview

CSA Exam Guide: Covers long-term KPI tracking for workflow stability.

Thus, the correct answer is: A. Long-term signals