In ServiceNow, roles define the level of access a user has within an instance. Roles are stored in the

sys_user_role table.

Key Details About Roles and sys_user_role Table:

Definition of a Role:

A role is a collection of permissions that grant access to different parts of the system.

Example: The admin role grants full access, while the itil role allows incident management access.

sys_user_role Table:

This table stores role records and their associated metadata.

Every role has a unique sys_id, a name, and may be associated with parent roles (role inheritance).

Users are linked to roles through the sys_user_has_role table.

How Roles Work in ServiceNow:

A user assigned a role gains all the permissions associated with that role.

Roles can be hierarchical (one role can inherit permissions from another).

Example: The itil_admin role includes all the permissions of the itil role, plus additional privileges.

Why Option D (sys_user_role) Is Correct?

✅ sys_user_role → The correct table where roles are recorded in ServiceNow.

Why Other Options Are Incorrect?

❌ A. sys_user → Incorrect; this table stores user records, not roles.

❌ B. sys_user_profile → Incorrect; this table does not exist in ServiceNow.

❌ C. sys_user_record → Incorrect; this is not a valid table in ServiceNow.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Docs – Roles and Role Management

https://docs.servicenow.com

ServiceNow Table Schema – sys_user_role

ServiceNow Developer Portal – Role Hierarchy & Best Practices

Assigning work tasks to a Group instead of an individual offers flexibility, better workload

management, and ensures tasks are handled efficiently.

Benefits of Assigning Tasks to a Group:

Group members can choose their tasks from "My Groups Work" ✅

The "My Groups Work" module in ServiceNow allows group members to see all unassigned tasks for

their group and take ownership of available tasks.

This is particularly useful when multiple team members share responsibility for completing tasks.

Groups can assign tasks to users based on on-call schedules ✅

ServiceNow’s On-Call Scheduling feature allows automatic assignment of tasks to available members

based on a predefined schedule.

This ensures that work is distributed fairly among team members who are on shift.

Site support members can pick tasks, based on Location ✅

Tasks can be assigned dynamically based on the location of the request.

This is particularly useful for IT support teams, field service teams, and facilities management teams,

where physical presence is required to complete a task.

Groups can assign tasks to users based on skills ✅

Using Skill-Based Routing, ServiceNow can match tasks to users who have the right skills for the job.

For example, if a request requires expertise in "Windows Server Management," the system will

assign it to a group member with that skill.

Incorrect Answers

E . Group members can avoid tasks that are nearing SLA breach ❌

This is incorrect because ServiceNow prioritizes SLA breaches and usually escalates such tasks rather

than allowing users to avoid them.

F . Groups can assign tasks to users based on availability ❌

While On-Call Scheduling can assign tasks based on availability, ServiceNow does not automatically

assign tasks dynamically based on real-time availability. Availability tracking is not a standard

assignment mechanism in ServiceNow unless customized.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Product Documentation → "Assigning Tasks to Groups"

ServiceNow Product Documentation → "On-Call Scheduling"

ServiceNow Product Documentation → "Skill-Based Routing"

ServiceNow follows a single-instance, single-tenant architecture, not a multiple-tenant architecture.

This means:

Single-Instance:

Each ServiceNow instance is a unique, independent environment for a customer.

All customers have their own dedicated instance with their own custom configurations, data,

workflows, and applications.

ServiceNow instances are hosted in a multi-instance cloud model rather than a multi-tenant model.

Single-Tenant Model (Multi-Instance Architecture):

Unlike multi-tenant architectures (where multiple customers share the same application and

database), ServiceNow provides each customer with a separate, isolated instance.

This ensures data security, performance isolation, and customization flexibility.

Each instance has its own data storage, configuration, and upgrade schedule, reducing risks

associated with shared environments.

Why ServiceNow Uses Multi-Instance Instead of Multi-Tenant:

Security & Data Isolation: Since each customer has an independent instance, there is no risk of data

leakage between tenants.

Customization & Flexibility: Customers can customize their instance freely without affecting others.

Performance & Scalability: Each instance can be scaled independently, ensuring optimal

performance.

Why Option B (False) Is Correct?

ServiceNow does NOT use a multiple-tenant architecture. ❌

ServiceNow follows a single-instance, single-tenant (multi-instance) model. ✅

Each customer has a dedicated instance with isolated resources and configurations. ✅

Why Option A (True) Is Incorrect?

A multi-tenant architecture means multiple customers share the same application/database with

logical separation, which is NOT the case in ServiceNow.

ServiceNow instead provides separate instances for each customer, meaning it is not a true multi-

tenant system.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Product Documentation – Multi-Instance Cloud Model

https://docs.servicenow.com

ServiceNow Community – Single-Tenant vs. Multi-Tenant Explained

ServiceNow Best Practices – Security & Instance Architecture

A UI Action in ServiceNow can be configured to prompt or notify users when an action is completed,

such as submitting an Incident. UI Actions are used to create buttons, links, or context menu items

that trigger specific actions.

How UI Actions Can Prompt a Success Message:

A UI Action (e.g., a "Submit" button on the Incident form) can be configured with a success message

using the gs.addInfoMessage() function.

This message is displayed after the form submission to inform the user that their Incident has been

successfully submitted.

Example of a UI Action Script:

javascript

CopyEdit

gs.addInfoMessage("The incident has been successfully submitted.");

This will display a confirmation message at the top of the page when an Incident is submitted.

Why "True" is the Correct Answer:

✅ UI Actions can display confirmation messages using gs.addInfoMessage() or similar methods.

Why "False" is Incorrect:

❌ UI Actions can be used to provide user feedback, including success messages for actions like

submitting an incident.

In ServiceNow, record numbers are automatically generated and incremented by the system. Each

record created in a table receives a unique identifier based on a predefined number format.

How Record Numbering Works:

Each table that extends the "task" or other core tables has a default numbering format.

Numbering is automatic, meaning users do not have to manually increment numbers.

The numbering format follows a prefix + incremental number (e.g., INC0001001 for incidents,

CHG0002001 for changes).

The system ensures unique sequential numbering within each table.

Configuring Auto-Numbering:

Admins can customize numbering formats by modifying the "Number Maintenance" module:

Navigate to System Definition → Number Maintenance.

Select a table and configure the prefix, length, and starting number.

Changes apply automatically to new records created in that table.

Why "False" is the Correct Answer:

Record numbers do not require manual updates; the system handles it automatically.

Users can change format settings, but cannot manually increment individual record numbers.

ServiceNow prevents duplicate numbers to maintain data integrity.

Why "True" is Incorrect:

Manual incrementing is not required or possible for individual records.

The platform automatically assigns the next sequential number to each record.

Reference from CSA Documentation:

ServiceNow Documentation: Number Maintenance

CSA Exam Guide: Covers automatic record numbering and Number Maintenance settings.

Thus, the correct answer is:

✅ B. False

In ServiceNow, each Knowledge Base (KB) can have unique configurations, including lifecycle

workflows, user criteria, category structures, and management assignments. This flexibility allows

organizations to manage knowledge articles according to different business needs, departments, or

service functions.

Key Aspects of Knowledge Base Customization:

1. Unique Lifecycle Workflows

Each knowledge base can have a custom workflow that defines how articles are created, reviewed,

published, and retired.

Examples of workflow stages: Draft → Review → Published → Retired.

Workflows ensure proper governance and content accuracy before publishing.

2. User Criteria (Access Control)

ServiceNow allows administrators to define User Criteria to control who can read, create, or

contribute to a knowledge base.

Example:

IT Knowledge Base is only accessible to users with the ITIL role.

HR Knowledge Base is only available to HR employees.

3. Category Structures

Each knowledge base can have a unique category hierarchy to organize articles efficiently.

Example:

IT KB Categories: Hardware, Software, Network.

HR KB Categories: Benefits, Policies, Payroll.

4. Management Assignments

Different knowledge bases can have different owners or managers.

Example:

IT KB is managed by IT Support Team.

HR KB is managed by HR Admins.

Why "A. True" is the Correct Answer?

ServiceNow allows multiple knowledge bases with distinct configurations.

Each knowledge base can have its own workflow, user criteria, categories, and managers.

This ensures flexibility and proper governance in knowledge management.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Docs: Knowledge Management Overview

ServiceNow CSA Study Guide – Knowledge Base Administration

ServiceNow Product Documentation: Configuring Knowledge Bases

In ServiceNow, knowledge articles within a Knowledge Base (KB) are grouped by categories to help

users easily find and navigate relevant information.

Key Features of Knowledge Article Categorization:

Hierarchical Structure:

Categories can have parent-child relationships, allowing for subcategories.

Example:

nginx

CopyEdit

IT Support

├── Hardware

│ ├── Laptops

│ ├── Printers

├── Software

│ ├── Windows

│ ├── MacOS

Improved Search & Filtering:

Users can filter knowledge articles by category in the Service Portal, Knowledge Management

homepage, or in the Global Search.

Permissions & Visibility Control:

Categories can have specific user criteria to restrict access to certain articles based on roles or

groups.

Article Organization & Management:

Knowledge managers can reassign articles to different categories if needed.

Why the Answer is True?

Knowledge Base (KB) articles are always assigned to a category for structured organization.

Without categories, articles would be unstructured and difficult to locate.

Reference from ServiceNow CSA Documentation:

Knowledge Management Overview

Knowledge Management in ServiceNow

Creating and Managing Knowledge Categories

Knowledge Base Categories

Final Verification: ✅ Answer is 100% correct and aligned with official ServiceNow Certified System

Administrator (CSA) documentation.

A Data Policy in ServiceNow is used to enforce mandatory and read-only field conditions for data that

is entered manually through forms or imported into the system.

How Data Policies Enforce Mandatory Data on Import:

Data Policies apply to data coming from external sources, such as imports, web services (API), and

integrations.

If a field is set as mandatory in a Data Policy, records cannot be imported unless that field contains a

value.

This ensures data integrity by preventing incomplete or invalid data from entering the system.

Example Scenario:

If an administrator configures a Data Policy to make the "Caller" field mandatory on the Incident

table, any imported incidents without a Caller value will be rejected.

Why "True" is the Correct Answer:

✅ Data Policies enforce mandatory fields for both UI entry and imports.

Why "False" is Incorrect:

❌ If Data Policies did not enforce mandatory fields on imports, incomplete records could enter the

system, leading to data integrity issues.

Reference from CSA Documentation:

ServiceNow Documentation: Data Policies

CSA Exam Guide: Covers Data Policy enforcement for UI forms and imports.

Thus, the correct answer is:

✅ A. True

A server is a computer program running as a service, a physical machine dedicated to executing services, or a system running a database. Types of Servers in ServiceNow & IT Infrastructure: Application Server – Runs the ServiceNow application logic and processes user requests. Database Server – Stores and manages the ServiceNow database, where all records and configurations are maintained. Web Server – Handles HTTP/HTTPS requests and delivers web pages to users. In ServiceNow’s cloud-based architecture, the server infrastructure is maintained by ServiceNow and hosted in highly secure data centers worldwide. Reference from Certified System Administrator (CSA) Documentation: ServiceNow Docs: Understanding ServiceNow Cloud Infrastructure https://docs.servicenow.com/en-US/bundle/utah-platformadministration/page/administer/platform-overview/concept/servicenow-cloud-architecture.html

To filter a long list of records and find those where Short Description contains "email", the best

practice is to use the column search feature:

Steps to Filter a List by "email" in Short Description:

Click the List Magnifier (🔹) to open the column search options.

In the "Short Description" column search box, type:

email

Press Enter to apply the filter.

This method automatically applies a "contains" filter, meaning it will show any records where "email"

appears anywhere in the Short Description field.

Why Other Options Are Incorrect?

A . Click List Magnifier to expand column search, on Short Description, type %email, click enter → ❌

Incorrect

% (percent sign) is not a valid wildcard in ServiceNow's list filters.

C . On Search box, select text, type email, click enter → ❌ Incorrect

The global search box searches across multiple tables, not just the Short Description field.

D . Click List Magnifier to expand column search, on Short Description type 'email, click enter → ❌

Incorrect

Single quotes ('email') are not required in column searches.

Official ServiceNow Documentation Reference:

Using List Filters in ServiceNow

ServiceNow Search Operators