Explanation
According to the Lightning Web Components Developer Guide, Lightning Out is a technique that allows developers to run Lightning web components outside of Salesforce servers, such as in a Node.js app running on Heroku or a department server inside the firewall. Lightning Out uses a script tag to load the Lightning web components framework and the custom components into the web container. Lightning Out also handles authentication, event handling, and data access between the web container and the Salesforce org. Slot elements, Heroku, and Lightning Canvas are not techniques for exposing Lightning web components outside of an org in another web container. References: Lightning Web Components Developer Guide, Use Components Outside Salesforce, B2B Commerce and D2C Commerce Developer Guide

Explanation
The event that should be triggered when user facing info, warning or error messages need to be displayed on a Visualforce page is pageMessage. This event is triggered by the displayPageMessage method of the CCRZ.util class, which is a utility class that provides various helper methods for common tasks. The event can be used to display a message on the page with a specified type, title, and text. For example, CCRZ.util.displayPageMessage('error', 'Oops!', 'Something went wrong.') will trigger the pageMessage event and display an error message on the page. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Events, Util Class

Explanation
To create custom Lightning web components (LWCs), a developer must take two steps: authorize an org for an SFDX project and deploy a custom component. Authorizing an org for an SFDX project allows the developer to connect to a Salesforce org, such as a scratch org, a sandbox, or a production org, and use it as a development environment. Deploying a custom component allows the developer to push the LWC code from the local project to the org and make it available for use. Creating an Apex class is not a required step for creating custom LWCs, as not all LWCs need to use Apex. Cloning an LWC is not a required step either, as it is an optional way to create a new LWC based on an existing one. Salesforce References: Lightning Web Components Developer Guide: Authorize an Org for Development, Lightning Web Components Developer Guide: Deploy Your Component

Explanation
To indicate that inventory is available for all items and amounts in the cart, the developer should return sfdc.checkout.InventoryStatus.Status.SUCCESS. The sfdc.checkout.InventoryStatus.Status.SUCCESS is a constant value that represents a successful inventory status. It means that the inventory class has checked the availability of all the products in the cart and confirmed that they are in stock and can be fulfilled.
Thedeveloper should use this value as the return value of the checkInventory method, which is a method that implements the sfdc.checkout.InventoryCheck interface. The checkInventory method is invoked during the checkout flow to validate the inventory availability of the products in the cart. Returning TRUE is not a valid way to indicate inventory availability, as it is not a valid inventory status value. Returning sfdc_checkout.IntegrationStatus.Status.SUCCESS is not a valid way either, as it is not an inventory status value, but rather an integration status value. Returning sfdc.checkout.InventoryStatus.SUCCESS is not a valid way either, as it is not a valid syntax for accessing the inventory status value. Salesforce References: B2B Commerce Developer Guide: Inventory Integration, B2B Commerce Developer Guide: Inventory Status Enum, B2B Commerce Developer Guide: Inventory Check Interface