When a user places an order for an item or service from the Service Catalog in ServiceNow, the system generates a Request (REQ). This is a core component of Request Management within the IT Service Management (ITSM) module. Understanding the Request Process in ServiceNow: User Places an Order: The user selects an item from the Service 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): This Request (REQ#) acts as the umbrella record that tracks the order as a whole. It is stored in the sc_request table. Creation of Requested Items (RITM#): Each item within the request generates a Requested Item (RITM#), stored in the sc_req_item table. 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 more Catalog Tasks (SCTASK#) in the sc_task table. These tasks define the steps required to fulfill the request (e.g., procurement, approval, and configuration). Explanation of Incorrect Answers:
A . A Change Request – Incorrect. A Change 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. An Order Guide is 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. A Service Level Agreement (SLA) may be associated with the request or tasks, but it is not automatically generated when a request is placed. Reference from Certified System Administrator (CSA) Documentation: 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