In ServiceNow Role Management, a role is a collection of permissions that control what users can see and do within the platform.
Key Characteristics of Role Assignment:
Role Hierarchy (Role Inheritance)
Roles can contain other roles (known as nested roles).
When a user is assigned a parent role, they inherit all child roles within it.
Example:
The ITIL role includes incident_manager and problem_manager roles.
Assigning ITIL to a user automatically grants them all the permissions of the included roles.
Roles Are Assigned by Administrators
Typically, roles are assigned by a System Administrator or an authorized user.
Role-Based Access Control (RBAC)
ServiceNow uses RBAC to control access to applications, records, and actions.
Why the Other Options Are Incorrect?
B . Users can click on the Personalize Role feature to try different roles Incorrect because users cannot manually switch roles unless they have the impersonation privilege.
C . A role is granted to a user by the System Administrator
Partially correct, but not the best answer because roles can also be assigned via groups or automated processes, not just by a System Administrator.
D . Each user has a role in the ServiceNow platform
Incorrect because not all users must have a role.
Example: A self-service user can access the system without having any specific role.
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Docs: Role-Based Access Control (RBAC)
https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/roles/reference/r_RBAC.html ServiceNow CSA Official Training Guide (User & Role Management) This confirms that roles can contain other roles, and when a user is assigned a role, they inherit all roles within it.