In theServiceNow Service Catalog module, tables have aOne-to-Many (1:M) relationship, meaning a single record in one table can relate to multiple records in another table. This is especially important for handling Service Catalog requests, as multiple items, approvals, and tasks may be associated with a single request.
One Request can have many Requested Items (REQ # RITM)
ARequest (REQ)is a container for multipleRequested Items (RITM).
When a user submits a catalog request, multiple items (such as a laptop and a phone) can be ordered in the same request.
Table Relationship:sc_request(Request) #sc_req_item(Requested Item)
One Requested Item can have many Approvals (RITM # Approval)
SomeRequested Items (RITM)require approval before being fulfilled.
For example, a laptop purchase might need approvals from both the IT department and a manager.
Table Relationship:sc_req_item(Requested Item) #sysapproval_approver(Approval) One Requested Item can have many Catalog Tasks (RITM # SCTASK) ARequested Item (RITM)can generate multipleCatalog Tasks (SCTASK)for different fulfillment teams.
For example, if an employee requests a new laptop, one task might go to IT to set it up, while another goes to finance for cost approval.
Table Relationship:sc_req_item(Requested Item) #sc_task(Catalog Task)
Breakdown of Correct Answers:Incorrect Answers Explanation:A.One Approval can have many Requests Approvals do not relate to multiple requests. Instead, a request may contain multiple approvals.
E:One Cart can have many Requests
TheCartis only a temporary storage of items before checkout. Once submitted, it generates asingle Request (REQ), not multiple requests.
ServiceNow Product Documentation# "Understanding Service Catalog Tables and Relationships" ServiceNow Data Model# "Request, Requested Item, and Catalog Task Relationships" References from Certified System Administrator (CSA) Documentation:

Reference: https://docs.servicenow.com/bundle/rome-platform-user-interface/page/administer/navigation-and- ui/task/ui16-navigator-tasks.html

When a new table is created inServiceNowby extending another table, it followstable inheritanceprinciples.
This means the newly created table (child table) receives all the fields from its parent table. Additionally, the new table can includecustom fieldsthat are unique to itself.
Here's how inheritance works in ServiceNow when a table is extended:
Fields Inheritance:
The child table automatically inherits all fields from its parent table.
These inherited fieldscannot be removedfrom the child table but can be modified or overridden.
The child table can also have additionalcustom fieldsthat do not exist in the parent table.
Business Rules, Client Scripts, and UI Policies:
Unlike fields, these components arenot automatically inherited.
However, they can still affect the child tableif they are defined on the parent table using conditions that include the child table.
To apply them specifically to the child table, they need to beexplicitly definedfor the new table.
Access Control Rules (ACLs):
ACLs are not automatically inherited.
Each table in ServiceNow has its own set ofAccess Control Rules, which must be explicitly configured for the child table if different permissions are required.
Database Structure:
The child table creates aone-to-one relationshipwith the parent table, meaningall fields in the parent are available in the child table.
The new table is stored as a separate entity but references the parent table's structure.
The child tableinherits all fieldsfrom the parent table.
The child table can also have its owncustom fields.
Business Rules, Client Scripts, UI Policies, and ACLs arenot automatically inherited, meaning options B and D are incorrect.
The tabledoes not archivethe parent table (making option A incorrect).
ServiceNow Product Documentation - Table Inheritance:https://docs.servicenow.com ServiceNow Fundamentals - Table Relationships ServiceNow Developer Portal - Extending Tables ServiceNow Best Practices - Access Controls & Security Rules Why Option C is Correct?References from Certified System Administrator (CSA) Documentation:

In ServiceNow, lists allow users to view, filter, and group records dynamically. If you want to group records based on a particular column (e.g.,Category), you can use the"Group By"functionality.
A: On list Context Menu, select Group By > Category
TheList Context Menu(right-clicking anywhere in the list header) provides an option to group records by a specific column.
Selecting"Group By > Category"organizes records into expandable sections based on the selected field.
This is one of the quickest ways to group records in a list.
E: On the Category column title, click Context menu > Group By Category Each column header in a list has its ownColumn Context Menu(accessible by clicking the three-line menu or right-clicking the column title).
Clicking"Group By Category"on theCategory columnwill instantly rearrange the list based on the values in that column.
B: On the Filter Menu, select Group By > Category
TheFilter Menuis used for setting up filters and conditions, but it doesnotprovide a "Group By" option.
It allows users to filter records but does not change the list structure.
C: Click Group On icon, select Category
There isno"Group On" icon in ServiceNow lists.
Grouping is done through context menus, not a dedicated "Group On" button.
D: On Navigator Filter, type tablename.group.category and press enter
TheApplication Navigator Filteris used for searching applications, modules, and tables-not for modifying list views.
Entering something likeincident.group.categorywill not perform a grouping action on a list.
References:Official ServiceNow Documentation:Grouped Lists
ServiceNow User Interface Guide:List Control Features