By default, ServiceNow encrypts data in transit using industry-standard Transport Layer Security (TLS) protocols. This ensures that any data transmitted between the client and the ServiceNow platform, or between ServiceNow and integrated systems, is encrypted and protected from interception or tampering.
While ServiceNow also offers options for data at rest encryption and customer-managed encryption keys, these features often require additional configuration or subscription services. Encryption of data in use (while data is being processed in memory) is a more advanced concept and not provided by default.
Thus, encryption of data in transit is the baseline encryption feature included automatically in all ServiceNow instances.
References:
ServiceNow Security Operations Documentation, Encryption section
ServiceNow Trust and Compliance Documentation
ServiceNow System Administrator Study Guide, Security Chapter
ServiceNow Docs: Security and Encryption

In ServiceNow, the Stamp icon (🖃) in the Form Header is used to access Form Templates. Templates allow users to quickly populate fields in a form with predefined values, improving efficiency and consistency.
How to Access Form Templates:
Open a record form (e.g., Incident, Change, or Request form).
Click the Stamp (🖃) icon in the form header.
Select a template from the list.
The form fields will be pre-filled with the template's values.
Why Are Other Options Incorrect?
A . Paperclip ❌
The Paperclip icon is used to attach files to a record, not access templates.
B . Pages ❌
No Pages icon is used for templates in ServiceNow.
D . More Options {...} ❌
The More Options menu provides access to additional record actions, but templates are accessed using the Stamp icon.
Reference:
ServiceNow CSA Documentation - Using Form Templates
ServiceNow Product Documentation - Creating & Applying Form Templates (https://docs.servicenow.com)

InServiceNow,Number Maintenanceis the application used to manage and modify numbering schemes for different tables, including theIncidenttable. Since the default prefix forIncident numbersis"INC", an administrator can modify it to a company-specific prefix (e.g.,"IN") by following these steps:
Navigate to the Number Maintenance Application:
Go toAll # System Definition # Number Maintenance
Search for theIncident table (task.number record for Incident).
Modify the Prefix:
Open the existingIncident numbering record.
Change thePrefixfrom"INC"to"IN".
Ensure theNext Numberfield is correctly set (e.g.,"IN0001001").
Save the Changes:
ClickUpdateto apply the new prefix.
All newly created incidents will now follow the new format (IN0001001).
Existing incidents are NOT affected-only newly created records will reflect the new prefix.
Steps to Change the Incident Number Prefix:Why Option A (Number Maintenance) is Correct?The Number Maintenance application is the correct place to modify prefixes for tables like Incident.
Why Other Options Are Incorrect?B. Create a Business Rule that modifies the prefix before the Insert operation# Incorrect Business Rulesdo not control number generation.
Number generation is managed byNumber Maintenanceat the system level.
C). The prefix of an incident cannot be changed because it is a built-in feature# Incorrect The prefixCAN be changedusing theNumber Maintenanceapplication.
Only existing records retain their original prefix; new records follow the updated format.
D). Submit a Change Request to ServiceNow Technical Support# Incorrect
This isnot necessary, asadministratorscan make this change directly throughNumber Maintenance.
ServiceNow Docs - Number Maintenance Configurationhttps://docs.servicenow.com ServiceNow Learning - Customizing Numbering Schemes ServiceNow Developer Portal - Number Prefix Best Practices References from Certified System Administrator (CSA) Documentation:

InServiceNow's Configuration Management Database (CMDB), thecmdbtable is thebase tablefrom which allConfiguration Item (CI) tablesinherit.
cmdbis the Parent Table of All CMDB-Related Tables
Thecmdbtablecontainsbasic attributesshared by allConfiguration Items (CIs).
Every CI in ServiceNowinherits fromcmdbor one of its child tables.
Hierarchy of CMDB Tables in ServiceNow:
cmdb(Base Table)# Stores general CI data.
cmdb_ci(Stores specific CI details)# Extendscmdbto storedevices, applications, and services.
cmdb_rel_ci(Stores relationships between CIs)# Used totrack dependencies.
Why iscmdbthe Correct Answer?
A:cmdb_dIncorrect- No such standard table exists in ServiceNow's CMDB.
B:ucmdbIncorrect-uCMDB (Universal CMDB)is anHP product, not part of ServiceNow's CMDB.
C:cmdb_rel_ciIncorrect-This table stores CI relationships, but it isnot the base table.
Incorrect Answer Choices Analysis:
ServiceNow Docs - CMDB Core Tables#CMDB Table Structure
ServiceNow Docs - CMDB Best Practices
Official ServiceNow Documentation References:

In ServiceNow Service Catalog, an Order Guide is a feature that allows users to order multiple, related catalog items in a single request, simplifying the ordering process.
Purpose of an Order Guide:
Helps users request multiple items together instead of submitting separate requests.
Ensures that related items are grouped logically (e.g., when onboarding a new employee, an Order Guide can include a laptop, software licenses, and access to required applications).
Uses variables and rules to pre-fill certain values and guide users through the ordering process.
Reduces the number of individual requests and makes fulfillment more efficient.
Explanation of Each Option:
(A) Order Guides restrict the number of items in an order to only one item per request - Incorrect ❌ This is not true because Order Guides allow users to request multiple items at once.
A single request (REQ#) is generated that contains multiple Requested Items (RITMs).
(B) Order Guides provide a list of guidelines for Administrators on how to set up item variables - Incorrect ❌ Order Guides are for users, not just administrators.
They do not provide setup guidelines; instead, they simplify ordering for end-users.
(C) Order Guides provide the ability to order multiple, related items as one request - Correct ✅ This is the primary function of an Order Guide.
Instead of placing separate orders for different catalog items, a user can add all related items to a single request.
Example: Employee Onboarding Order Guide
Laptop
Email account
VPN access
Software (e.g., Microsoft Office, Adobe Suite)
(D) Order Guides take the user directly to the checkout without prompting for information - Incorrect ❌ Order Guides can include user prompts (variables, conditions) before checkout.
Users may be asked for specific details before submitting the request (e.g., laptop specifications, software preferences).
Additional Notes & Best Practices:
Use dynamic variables: Order Guides can ask questions that determine which items should be included in the request.
Improve user experience: Order Guides streamline ordering, ensuring users request all necessary items without forgetting anything.
Enhance fulfillment efficiency: Since multiple items are grouped in one request, IT and fulfillment teams can process them together, reducing delays.
Example Use Cases:
New Hire Onboarding (laptop, software, security badge, phone)
Office Setup Request (desk, chair, monitor, accessories)
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Docs: Order Guides Overview
https://docs.servicenow.com
ServiceNow Community: How to Configure an Order Guide
https://community.servicenow.com