The Shared Responsibility Model in ServiceNow clearly delineates responsibilities between the cloud service provider (ServiceNow) and the customer. ServiceNow manages the infrastructure, including the physical data centers, networking, hardware, and media disposal and destruction, ensuring proper security of the underlying platform. Hence, Media disposal and destruction and Infrastructure management fall under the provider's responsibility.
The customer is responsible for their data, including backup and restore, access management (authentication and authorization), and encryption configuration on their data. While ServiceNow provides encryption capabilities, the customer must configure and manage encryption keys and access controls.
This model is critical for maintaining security and compliance in cloud environments and is explicitly detailed in ServiceNow's official documentation and cloud security best practices.
References:
ServiceNow Trust and Security Documentation, Shared Responsibility Model section ServiceNow System Administrator Study Guide, Cloud Security Chapter ServiceNow Docs: Shared Responsibility Model

TheActivity Stream icon (Live Feed)allows users tomonitor real-time updateson records assigned to them.
This is particularly useful for task workers who need to trackcustomer responses, status changes, and work progresswithout manually refreshing records.
Navigate toMy Work List(or any list view showing assigned tasks).
Click theActivity Stream (Live Updates) iconat the top of the list.
Areal-time updates frameappears, showing all changes to the listed records.
A). Open an Agent Workspace tab for each record he wants to monitor
WhileAgent Workspaceoffers real-time updates, opening multiple tabs isinefficient and unnecessarywhen live updates can be monitored in a single stream.
B). Select Service Desk > My Work Dashboard
TheMy Work Dashboardprovides an overview of assigned tasks butdoes not show live updates.
C). Click on the eyeglass icon to expand the Monitor frame
There isno "eyeglass icon"used for monitoring updates in ServiceNow.
Reference:ServiceNow CSA Documentation - Using the Activity Stream for Live Updates ServiceNow Product Documentation - Monitoring Tasks in My Work(https://docs.servicenow.com)

In ServiceNow, aGroupis acollection of userswho share common responsibilities and access rights within the system. Groups are primarily used to facilitate:
Role-Based Access Control (RBAC):Assigning roles and permissions collectively to a set of users.
Task Assignment:Groups can be assigned to handle incidents, change requests, and approvals.
Notification Management:Groups can be used for sending system notifications to multiple users at once.
C: A collection of users
Agroupin ServiceNow consists of multiple users who work together on tasks, approvals, or system activities.
Groups simplify user administration by allowing permissions and responsibilities to be assigned collectively instead of individually.
Examples of groups:
Service Desk(handles incident tickets)
Change Advisory Board (CAB)(approves change requests)
HR Team(manages HR cases)
A: An escalation pod
ServiceNow doesnotuse the term"escalation pod"to define a group.
Escalations are handled through priority rules and workflows, not groups.
B: A department
Adepartmentis an organizational unit (e.g., HR, IT, Finance), while agroupis a functional collection of users.
Departments and groups are separate entities in ServiceNow.
D: A collection of subject matter experts
While some groupsmayconsist of SMEs, this isnot the definitionof a group.
Groups can have users of different expertise levels, not just experts.
E: A team of users
Although groups may act as "teams," the officialServiceNow definitionof a group isa collection of users, which is more precise.
"Team" is a more informal term, while "group" is the structured term used in the platform.
References:Official ServiceNow Documentation:Groups and Users
ServiceNow Administration Guide:User and Group Management

When setting adata policyin ServiceNow, it applies to all data entered into the platform, regardless of whether the data comes from:
UI Forms
Import Sets
Web Services (APIs, integrations, etc.)
Where Does the Data Policy Run?Data Policies Run on the Server-Side
Data policies enforcedata consistency and validationat theserver level.
Theyapply uniformly across all data entry points, ensuring that validation rules are enforced before storing data in the database.
A). Client #Incorrect
Data Policies donotrun on the client-side (browser).
Client ScriptsandUI Policieshandle client-side validation.
C). Browser #Incorrect
Data Policies donotoperate within the browser; theywork at the database levelon the server.
D). Network #Incorrect
ServiceNowdoes not enforce policies at the network layer; all validations occur on theapplication server (Server-Side Processing).
Why Other Options Are Incorrect?Key Differences Between Data Policies and Other Validation Methods:
Validation Type
Runs On
Applies To
Purpose
Data Policy
Server
UI, Import Sets, Web Services
Enforces rules across all data sources
UI Policy
Client (Browser)
UI Forms
Dynamically changes form behavior
Client Script
Client (Browser)
UI Forms
Runs JavaScript in the user's browser
Business Rule
Server
Database Transactions
Executes logic when records are inserted, updated, or deleted
Data Policies Overview
Difference Between UI Policies and Data Policies
Official ServiceNow Documentation Reference: