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

AnUpdate SetinServiceNowis a mechanism for capturing and migratingcustomizations and configurationsfrom one instance to another (e.g.,Development # Test # Production).
What is Captured in an Update Set?Update Sets recordconfiguration changes, such as:
Tables & Database Schema Changes(e.g., new tables, modified fields)
Form Layout & UI Changes(e.g., changes in form views, UI policies)
Schedules(e.g., Scheduled Jobs, Business Rules with scheduled actions)
Client Scripts(e.g., JavaScript running on the client side)
Business Rules, UI Actions, UI Policies
Workflows, Script Includes, ACLs (Access Control Rules)
Email Notifications, Dictionary Entries, Application Menus
What is NOT Captured in an Update Set?Data Records (e.g., Incident, Change Request, CMDB data) Group Memberships & User Data System Properties (some properties may require manual migration) Attachments & Scheduled Reports B: Changes made to tables, forms, views, and fields(Incorrect) Views and Fieldsare part of UI changes, butschedules and client scriptsare also included in Update Sets, makingOption A more complete.
C: Changes made to tables, forms, Business Rules, and data records(Incorrect) Data records (actual table entries like incidents or change requests) are NOT captured in Update Sets.
D: Changes made to tables, forms, groups, and configuration items (CIs)(Incorrect) Groups and CIs (CMDB data) are considered data and are NOT included in Update Sets.
Instead,CIs should be migrated using Import Sets or CMDB data export/import.
Why Other Options Are Incorrect?
Understanding Update Sets
Update Sets Overview
What Gets Captured in Update Sets?
Best Practices for Using Update Sets
References from ServiceNow CSA Documentation:

To rearrange the columns on a list, users can right click on any column header and select Configure > List Layout from the context menu2. This will open a dialog box where users can select the available fields and move them to the selected list using the arrow buttons2. Users can also drag and drop the fields to change the order of the columns2.
References
* How To Configure List and Form Layouts | by ServiceNow Scholar - Medium2