Explanation:

Two APIs that an admin can suggest so that customers can initiate order cancellations and returns from the B2C Commerce storefront and have their action carry out the cancel and return operations in Order Management are:

Connect APIs. These are RESTful APIs that expose resources in Order Management, such as orders, payments, shipments, etc. They allow customers to perform CRUD (create, read, update, delete) operations on these resources from external systems, such as B2C Commerce. REST APIs. These are HTTP-based APIs that enable developers to access data in Order Management using standard HTTP methods, such as GET, POST, PUT, PATCH, and DELETE. They allow customers to interact with Order Management resources using JSON or XML formats.

Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_connect_api.htm &type=5

https://help.salesforce.com/s/articleView?id=sf.order_management_rest_api.htm &type=5

Explanation: Based on some changes in Universal Containers’ Commerce engine, new Orders are expected to have two additional attributes at the header level. In Order Management, besides Order, the other object that also needs to be extended is Order Summary. An Order Summary is a record that stores information about an order, such as the total amount, the number of items, and the fulfillment status. An Order Summary is created by a process called Create Order Summary Process, which runs whenever an order is created or updated. The process calls a flowcalled Create OrderSummary Flow, which calculates the order summary fields and creates or updates the order summary record. To extend an object in Order Management, an administrator can create custom attributes on that object that match the API name and data type of the corresponding attributes in B2C Commerce. References: Order Management Objects

Explanation: To set up a mock payment gateway in a new org, an administrator should take the following steps:
Create a Payment Provider: This is a custom metadatatype that defines the configuration and behavior of a payment gateway. A payment provider specifies the name, type, class, and endpoint of the payment gateway.
Create a Named Credential: This is a Salesforce feature that securely stores authentication information for connecting to external services. A named credential specifies the URL, identity type, authentication protocol, and certificate of the payment gateway.
Create a Payment Gateway: This is a custom object that represents an instance of a payment provider. A payment gateway references a payment provider and a named credential, and defines additional settings such as currency, mode, and timeout.

Explanation: The Order Summary object is a custom object that stores information about an order, such as the total amount, the number of items, and the fulfillment status. The Order Summary object is created by a process called Create Order Summary Process, which runs whenever an order is created or updated. The process calls a flow called Create OrderSummary Flow, which calculates the ordersummary fields and creates or updates the order summary record. The process and the flow are part of the Order Management package and must be installed and activated for the order summary object to be created.