InServiceNow,Rolesare used to control access toApplications and Moduleswithin the platform. ARoleis a set of permissions that define what actions a user can perform and which records they can access.
Grant Access to Applications and Modules:
If a userdoes not have the required role, theycannot see or accessan application/module.
Control Record-Level and Field-Level Access:
SomeAccess Control Rules (ACLs)depend on roles topermit or restrictdata visibility.
Assign Multiple Roles to a User:
A user can havemultiple rolesbased on job responsibilities.
Example Roles in ServiceNow:
admin- Full access to all system features.
itil- Can manage incidents, problems, and changes.
catalog_admin- Manages the Service Catalog.
asset- Manages assets and CI records.
Key Functions of Roles in Access Control:
Navigate to:All # Users and Groups # Users
Open a user record
Scroll to the Roles related list
Click Edit and add roles
How to Assign Roles to Users:
A: Access Control Rules- Incorrect.
Access Control Rules (ACLs)definerecord-level and field-levelsecurity, but they donot control access to applications and modulesdirectly.
B: UI Policies- Incorrect.
UI Policiescontrol the visibility and behavior of form fields,not module or application access.
D: Assignment Rules- Incorrect.
Assignment Rulesautomatically assigntasks(e.g., Incidents, Requests) to groups or users, but theydo not control access.
Explanation of Incorrect Answers:
ServiceNow Product Documentation # Roles and Permissions
ServiceNow CSA Study Guide # User and Role Management
ServiceNow Knowledge Base # Controlling Access to Applications and Modules References from Certified System Administrator (CSA) Documentation:

TheConfiguration Management Database (CMDB)inServiceNowstores information aboutconfiguration items (CIs)and theirrelationships.
cmdb (Configuration Management Database)The main parent table for all CMDB-related data.
Storescore configuration item (CI) data.
Other CMDB-related tables inherit from this table.
cmdb_ci (Configuration Items Table)Stores individual configuration items (CIs).
Every CI (e.g., servers, network devices, software) is stored in this table or one of its child tables.
This tableextendscmdb.
cmdb_rel_ci (CI Relationships Table)Stores relationships between CIs.
Defines how CIsconnect to each other(e.g., "server hosts application").
Helps withService Mapping and Impact Analysis.
The Three Key CMDB Tables:
A: omadb_rel_ciIncorrect- Not a standard ServiceNow CMDB table.
B: sn_emdbIncorrect-sn_emdbisnot a CMDB tablein ServiceNow.
C: sn_emdb_ciIncorrect- No such table inServiceNow CMDB architecture.
E: sn_emdb_bakIncorrect- No suchbackup tablein ServiceNow CMDB.
G: emdb_bakIncorrect- No suchServiceNow CMDB tableexists.
Incorrect Answer Choices Analysis:
ServiceNow Docs - CMDB Core Tables#CMDB Tables Overview
ServiceNow Docs - Understanding CI Relationships#CMDB Relationship Tables Official ServiceNow Documentation References:

InServiceNow, theNumber Maintenanceapplication is used toconfigure and modify numbering formats for specific tables. This application allows administrators to control how records are numbered across different modules.
Customization of Number Formats
Administrators can defineprefixes, number sequences, and suffixesfor records in different tables.
Example:INC0001001forIncidents,REQ0002001forRequests.
Resetting or Adjusting Number Sequences
You can manually adjust the numbering sequence if needed.
Example: Resetting incident numbering to start from a specific value.
Supports Multiple Tables
Works for standard tables likeIncidents, Problems, Requests, Change Requests, etc.
Can also be configured forcustom tables.
Application Navigation
Path:
Go toAll # System Definition # Number Maintenance
Locate the table and modify its numbering settings.
Key Features of Number Maintenance:Why Option A (Number Maintenance) is Correct?"Number Maintenance" is the official ServiceNow application for managing number formats per table.
Why Other Options Are Incorrect?B. System Maintenance- Incorrect; no such module in ServiceNow manages numbering formats.
C: Table Maintenance- Incorrect; this does not exist as an application in ServiceNow.
D: Record Maintenance- Incorrect; not a valid ServiceNow feature for modifying number formats.
ServiceNow Docs - Number Maintenance Configurationhttps://docs.servicenow.com ServiceNow Learning - Customizing Numbering Schemes ServiceNow System Definition - Number Format Best Practices References from Certified System Administrator (CSA) Documentation:

In ServiceNow, Application Scope is a fundamental concept used to protect applications by identifying and restricting access to application artifacts (such as tables, scripts, and business rules). 3
1. The Concept of Scope:
Every application in ServiceNow has a scope.4
* Global Scope: This is the default scope for the baseline ServiceNow instance. Legacy applications and general configurations usually live here.
* Private/Scoped Applications: These are distinct namespaces (e.g., x_acme_book_mgmt ). 5
2. Why Option D is Correct (Availability and Protection):
The primary purpose of a private scope is to define boundaries. It acts as a protective layer that does two main things:
* Protection: It prevents code in the Global scope or other Scoped applications from modifying your application ' s data or logic without explicit permission. 6
* Availability (The Answer): It allows the developer to explicitly define which parts of the application are public. By default, artifacts in a private scope are hidden from other applications. 7 The developer must configure " Cross-scope privileges " or set specific " Access " settings (e.g., making a Script Include " Accessible from: All application scopes " ) to determine what is available for use by others. 8
3. Why the other options are incorrect:
* A: Scope does the opposite; it restricts access by default, rather than granting " all access. "
* B: Scope does not determine the functionality of core services; it acts as a container for custom or store- bought applications.
* C: Scope prevents other applications from changing your tables, but it allows the application to change its own tables and logic. 9 Reference:
ServiceNow Application Development documentation defines Application Scope as a way to ensure the application does not interrupt core business services and prohibits other applications from interfering with its normal functioning.10

In ServiceNow, tasks (such as Incidents, Change Requests, and Service Requests) can be assigned toindividual usersorgroupsto manage workload distribution efficiently.
A: Groups
Groups in ServiceNow represent a collection of users with common roles or responsibilities.
Tasks are often assigned to groups first, allowing any member to take ownership.
Example:
IT Support Groupfor handling incident tickets.
Change Advisory Board (CAB)for approving changes.
B: Users
Individual users can receive task assignments directly.
Assigned users are responsible for completing or updating the task.
Example:
A specificService Desk Agentassigned to resolve an incident.
C: Departments
Departments in ServiceNow representorganizational divisions(e.g., HR, IT, Finance), but they donotreceive task assignments.
Assignments are made to groups or individuals within departments, not the department itself.
D: Teams
"Teams" is not a structured entity in ServiceNow for task assignments.
While some organizations may informally refer to groups as "teams," the platform recognizesGroupsandUsersas valid task recipients.
References:Official ServiceNow Documentation:Assigning Tasks
ServiceNow Administration Guide:Users and Groups