InServiceNow, anUpdate Setis a mechanism used tocapture customizationsmade in an instance andmove them to another instance(e.g., from development to production). However, certain elements arenot included in an Update Set by default.
Homepages (A) -Correct
Homepages are stored asuser-specific or global content, and they are not included in update sets by default.
To migrate them, you need tomanually export/importthem or use thesys_portal_page_settable.
Data (B) -Correct
Update Setsdo not include actual data, such as incident records, user records, or CMDB data.
Onlyconfiguration changes(like fields, forms, and workflows) are captured.
Data migration must be handled separately usingData Export or Integration methods.
Published Workflows (C) -Correct
Once a workflow ispublished, it is stored as a runtime instance and not automatically included in an Update Set.
To capture it, you mustmanually updatethe workflow before moving it in an Update Set.
Report Definitions (H) -Correct
Reports and their configurations are not automatically included in Update Sets.
You mustmanually include themby marking them as "Captured in Update Set." D: Business Rules(Captured in Update Sets) E: Schedules(Captured in Update Sets) F: Database changes(Captured in Update Sets) G: Related Lists(Captured in Update Sets) I: Scheduled Jobs(Captured in Update Sets) J: Client Scripts(Captured in Update Sets) K: Views(Captured in Update Sets) ServiceNow Update Sets Overview:https://docs.servicenow.com/en-US/bundle/utah-application-development
/page/build/system-update-sets/concept/c_UpdateSets.html
ServiceNow Update Set Best Practices:https://docs.servicenow.com/en-US/bundle/utah-application- development/page/build/system-update-sets/concept/update-set-best-practices.html Items NOT Included in Update Sets (By Default):Items That ARE Included in Update Sets (By Default):
Official References from Certified System Administrator (CSA) Documentation:

InServiceNow Access Control Rules (ACLs), if an administrator wants to grant access toall rows and all fieldsof a custom table (e.g.,customertable) to specific roles (customer_table_adminandcustomer_table_user), they should create an ACL rule using theformat:
##tablename.*
For theCustomer Table, the correct ACL format is:
##customer.*
This rule allows bothcustomer_table_adminandcustomer_table_userfull accessto all fields and records in thecustomertable.
A: customer.all
Incorrect syntax; ServiceNow does not use.allin ACL rules.
C: customer.field
This would applyonly to a specific field, not all rows and fields.
D: customer.none
No such ACL naming convention exists in ServiceNow.
Reference:ServiceNow CSA Documentation - Creating and Managing ACL Rules ServiceNow Product Documentation - Table-Level and Field-Level ACLs(https://docs.servicenow.com)

ServiceNow supports multiple authentication methods to verify user identities before granting access to an instance. The three valid authentication methods from the given options are:
Local Database Authentication
This is the default authentication method used in ServiceNow.
User credentials (username and password) are stored in the ServiceNow database.
Authentication is handled directly by ServiceNow without relying on external identity providers.
This is useful for small implementations or instances where external authentication is not required.
LDAP (Lightweight Directory Access Protocol)
LDAP allows ServiceNow to integrate withcorporate directory services, such as Microsoft Active Directory, to authenticate users.
Users authenticate using theircorporate credentials, reducing the need to maintain separate user accounts in ServiceNow.
ServiceNow connects to an LDAP server and verifies credentials without storing passwords in the ServiceNow database.
SSO (Single Sign-On)
Single Sign-On enables users to log into ServiceNow using an external identity provider (IdP).
ServiceNow supports various SSO protocols, including:
SAML 2.0 (Security Assertion Markup Language)
OAuth 2.0
OpenID Connect
Kerberos
This allows users to authenticate once and gain access to multiple applications, improving security and user experience.
A: XML feed-
XML feeds are used for data exchange,not authentication.
ServiceNow can consume XML feeds for integrations but does not use XML feeds to authenticate users.
E: FTP authentication-
FTP (File Transfer Protocol) is used for transferring files between systems and isnot a valid authentication methodin ServiceNow.
ServiceNow Docs: User Authentication Methodshttps://docs.servicenow.com/en-US/bundle/utah-platform- administration/page/administer/security/concept/user-authentication-methods.html ServiceNow CSA Official Training Guide (User Authentication & Security) Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:
These references confirm thatLocal Database, LDAP, and SSOare valid authentication methods in ServiceNow.

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:

In ServiceNow, theApprover [approver-user] roleis specifically designed for users who need toauthorize requestsbut should not have any other permissions or administrative access to the platform.
Canapprove or reject requests(e.g., Change Requests, Service Catalog Requests).
No additional platform permissions(cannot create, modify, or view records beyond approvals).
Assigned automatically tousers designated as approversin approval workflows.
AnIT Managerreceives an approval request for a new laptop.
Themanager logs in and sees only the approval request(no other system access).
Theyapprove/rejectthe request without modifying any records.
Key Features of the Approver Role:Example Use Case:
B: Authorize [authorize-user] #Incorrect
No such role exists in ServiceNow.
C: Reviewer [reviewer_user] #Incorrect
No such role exists in ServiceNow.
D: Approver Group [approval_group] #Incorrect
Approval groupsallow multiple users to approve a request collectively, but it is not a standalone role.
Theapprover-user roleis the correct answer for individual approvals.
E: Verification [verify_user] #Incorrect
No such role exists in ServiceNow.
Why Other Options Are Incorrect?
Approval Configuration
User Roles in ServiceNow
Official ServiceNow Documentation Reference: