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