The required amount of test code coverage when deploying an Apex class is 75%. This means that at least 75% of the Apex code must be covered by unit tests, and all of those tests must complete successfully. Verified Reference: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying_ant_deploy.htm

Once the administrator has activated the integration between B2C Commerce and Order Management, orders being placed by customers will be sent to Order Management if the order status is set to Active or New. These are the two order statuses that indicate that an order has been created or confirmed by a customer, and that it needs to be processed by Order Management. Verified Reference: https://help.salesforce.com/s/articleView?id=sf.order_management_order_api.htm&type=5

The Product Eligibility Flag is a custom field on the Product object that indicates whether a product is eligible for a specific selling channel. An administrator can use this field to control what inventory is exposed on different channels, such as web, mobile, or store. For example, if a product has the Product Eligibility Flag set to Web Only, it will not be available for other channels. Reference: Order Management Objects, [Product Eligibility Flag]

Three statements that are true about change sets are:
Sending a change set between two orgs requires a deployment connection. A deployment connection is a link between two orgs that allows one org to send change sets to another org.
Change sets can only be sent between orgs that are affiliated with a production org. A production org is an org that is used for live operations and data, and it can have one or more sandbox orgs that are used for development and testing. Change sets can only be sent from a sandbox org to its associated production org, or from one sandbox org to another sandbox org that shares the same production org.
Change sets can contain only modifications made through the Setup menu. A change set is a collection of metadata components that can be deployed from one org to another. Metadata components are customizations that are made through the Setup menu, such as custom objects, fields, workflows, etc.
Verified Reference: https://help.salesforce.com/s/articleView?id=sf.changesets_about.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.changesets_components.htm&type=5

The best way for a user to view the information exchanged between the payment platform and the external payment gateways is to navigate to Payment Gateway Logs related list on the corresponding Order Payment Summary. A Payment Gateway Log is a record that captures the request and response messages between the payment platform and the external payment gateways, such as Stripe, PayPal, etc. A Payment Gateway Log has a lookup relationship to the Order Payment Summary object, which represents a payment made for an order or part of an order. A user can use the Payment Gateway Logs related list on the Order Payment Summary page to view the details of the payment transactions, such as the request and response payloads, status codes, timestamps, etc. Verified Reference: https://help.salesforce.com/s/articleView?id=sf.order_management_payment_gateway_log.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm&type=5