Explanation
Two ways that an administrator can query Order Summaries using APIs in Workbench are:
Platform API. The Platform API is a set of REST and SOAP APIs that allow developers to access data and functionality in Salesforce from external systems. The Platform API includes various resources and operations for querying, creating, updating, or deleting records in Salesforce, such as Order Summaries.
The administrator can use the Platform API in Workbench by selecting the REST Explorer or SOAP Explorer tabs, and entering the appropriate request URL and parameters.
Composite API. The Composite API is a type of REST API that allows developers to execute multiple subrequests in a single HTTP request. The Composite API includes various resources and operations for batching, tree, sObject collections, or transactions in Salesforce, such as Order Summaries. The administrator can use the Composite API in Workbench by selecting the REST Explorer tab, and entering the appropriate request URL and JSON body.
Verified References:
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm

Explanation
Two steps that are required to add an item to the Actions & Recommendations panel on the Order Summary record page are:
Drag the Actions & Recommendations component on the page. The Actions & Recommendations component is a standard component that displays actions and recommendations based on business logic for records in Lightning Experience or Salesforce mobile app. The administrator can use the Lightning App Builder to drag and drop the Actions & Recommendations component onto the Order Summary record page layout.
Create a new sub-flow. A sub-flow is a type of flow that can be invoked by another flow as an element.
A sub-flow can contain logic and actions that are specific to a certain scenario or use case, such as order fulfillment or payment processing. The administrator can use Flow Builder to create a new sub-flow that defines the actions and recommendations for Order Summaries, and then add it to the Actions & Recommendations component on the record page.
Verified References:
https://help.salesforce.com/s/articleView?id=sf.om_actions_recommendations.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_subflow.htm&type=5

Explanation
The correct time and way for creating an Invoice is at any point after the Fulfillment Order is created, by customizing flow "Create Invoice". This flow is a core action that creates an Invoicerecord from a Fulfillment Order record, and updates the status of both records accordingly. The administrator can customize this flow to suit their business needs, such as adding conditions, actions, or subflows. Verified References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_create_invoice.htm&

Explanation
The correct statement about Person Accounts and Contacts is that Person Accounts are appropriate for B2C transactions while Account-Contact model is appropriate for B2B transactions. A Person Account is a type of account that represents an individual consumer, rather than a business or organization. A Person Account combines the features and fields of both the Account and Contact objects, and it does not require a Contact record to be associated with it. A Person Account is suitable for B2C transactions, where the customers are individual consumers who purchase products or services for personal use. An Account-Contact model is a type of data model that represents a business or organization as an account, and its employees or affiliates as contacts. An account can have many contacts associated with it, but a contact can only belong to one account.
An Account-Contact model is suitable for B2B transactions, where the customers are businesses or organizations that purchase products or services for professional use. Verified References:
https://help.salesforce.com/s/articleView?id=sf.accounts_person.htm&type=5https://help.salesforce.com/s/article

Explanation
Three things that the administrator can do to get more details for debugging when encountering an unhandled fault error are:
Create a fault connector. A fault connector is a special type of connector that handles errors that occur in a flow element, such as an assignment, a loop, or an action. A fault connector can route the flow to another element or end the flow with an error message.
Add a Display Text component which includes {! SFIow.FaultMessage}. A Display Text component is a screen component that displays text on a screen element in a flow. The {! SFIow.FaultMessage} is a system variable that contains information about the error that occurred in the flow, such as the element name, error type, and error message.
Create an error connector. An error connector is a special type of connector that handles errors that occur in a screen element, such as invalid user input or required fields being left blank. An error connector can route the flow to another screen element or end the flow with an error message.
Verified References:
https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_fault.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screen_component_display_text.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_error.htm&type=5