InReport Designer, theDatasection is used to specifygrouping and calculationsto be performed on the report ' s dataset.
Youselect the tablefrom which the report will pull data.
You definefiltersto limit the dataset.
You specify " Group By " fieldsto categorize data.
You applyaggregations (SUM, COUNT, AVG, etc.)to perform calculations on fields.
A). Style- Controlsvisual appearance(colors, fonts, chart type, etc.) but doesnot handle data grouping or calculations.
B). Format- Used forformattingelements but doesnot control grouping or data calculations.
D). Configure- There is no " Configure " section inReport Designer; settings are managed under other sections.
E). Group By- While " Group By " is usedwithintheDatasection, it is not a separate section itself.
ServiceNow Report Designer - Data Configuration
ServiceNow CSA Training Module: " Creating and Configuring Reports "
What Happens in the " Data " Section?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Thethree-bar iconin theForm headerof ServiceNow is commonly referred to as theHamburger icon. It provides access toadditional form actionsthrough acontext menu.
Opens adrop-down menuwith options such as:
Configure Form Layout
Configure Form Design
Insert and Stay
View History
Export Options
Helps users accessquick actionswithout navigating away from the form.
The icon consists ofthree horizontal lines, resembling ahamburger(bun-patty-bun).
This naming convention is widely used in web and mobile UI design.
Functions of the Hamburger Icon in ServiceNow:Why is it Called a "Hamburger Icon"?
Incorrect Answer Choices Explanation:A. Pancake Icon- No such term exists in ServiceNow UI terminology.
B). Additional Actions or Context Menu- While the icondoesprovide additional actions, "Context Menu" refers to right-click options or three-dot menus, not the three-bar menu.
D). Cake Icon- No such UI term exists in ServiceNow or general UI design.
Understanding the ServiceNow Form Header
ServiceNow UI Overview
Official CSA Documentation Reference:

InServiceNow,UI Policiesallow administrators todynamically control form fieldsbased on conditions without using scripts. With UI Policies, you can change thebehaviorof a field by making it:
Read-only# The user canviewthe field butcannot edit it.
Mandatory# The field becomesrequired, and the usermustfill it out before submitting the form.
Hidden# The field isremoved from visibilityon the form.
Explanation of Each Option:A. Read-only-Correct
A UI Policy can make a fieldread-only, meaning users canseethe field butcannot modifyits value.
Example: A field likeRequest Number (REQ0001)is typicallyread-onlyafter submission.
B). Write-only-Incorrect
ServiceNowdoes nothave a "write-only" field setting in UI Policies.
If a field iseditable, users canboth read and write; if it's hidden or read-only, writing is not possible.
C). Necessary-Incorrect
There isno "Necessary"field state in ServiceNow UI Policies.
If the intent is to make a field required, the correct term is"Mandatory".
D). Mandatory-Correct
UI Policies can make a fieldmandatory, requiring the user toenter a valuebefore submitting the form.
Example: AnIncident Descriptionfield might be mandatory before an incident is submitted.
E). Empty-Incorrect
UI Policiescannot directly enforce an "empty" state. However, adefault valuecould be cleared using aclient script, but this isnot a UI Policy feature.
F). Hidden-Correct
UI Policies canhide a field, making it invisible on the form.
Example: A"Manager Approval"field may be hiddenuntila certain condition (e.g., request cost > $1000) is met.
Final answer:Read-only
Mandatory
Hidden
ServiceNow Docs - UI Policies and UI Policy Actionshttps://docs.servicenow.com ServiceNow Learning - Form Configuration & UI Policies ServiceNow Developer Portal - Controlling Form Behavior with UI Policies References from Certified System Administrator (CSA) Documentation:

When a user places an order for an item or service from theService Catalogin ServiceNow, the system generates aRequest (REQ). This is a core component ofRequest Managementwithin the IT Service Management (ITSM) module.
User Places an Order:
The user selects an item from theService Catalog(e.g., a laptop, software, or an access request).
The order may consist of multiple items, depending on the selection.
ServiceNow Generates a Request (REQ):
ThisRequest (REQ#)acts as the umbrella record that tracks the order as a whole.
It is stored in thesc_requesttable.
Creation of Requested Items (RITM#):
Each item within the request generates aRequested Item (RITM#), stored in thesc_req_itemtable.
For example, if the user orders a laptop and a software license, two RITM records are created under the same Request.
Tasks (SCTASK#) Are Created:
Each Requested Item (RITM) may trigger one or moreCatalog Tasks (SCTASK#)in thesc_tasktable.
These tasks define the steps required to fulfill the request (e.g., procurement, approval, and configuration).
A). A Change Request- Incorrect. AChange Request (CHG#)is created only if the requested item involves changes to the infrastructure, such as a server upgrade. Not all catalog items require a change request.
B). An Order Guide- Incorrect. AnOrder Guideis a tool within the Service Catalog that helps users order multiple related items at once. However, it does not get generated when an order is placed.
D). An SLA- Incorrect. AService Level Agreement (SLA)may be associated with the request or tasks, but it is not automatically generated when a request is placed.
ServiceNow Product Documentation # Service Catalog # Request Fulfillment ServiceNow CSA Study Guide # Service Catalog and Request Management ServiceNow Tables Reference # sc_request, sc_req_item, sc_task Understanding the Request Process in ServiceNow:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation: