Explanation:

In Salesforce B2B Commerce, to reorder a checkout flow step within a sequence, a developer must adjust the 'next-state' attribute in the configuration of the preceding subflow. This approach allows for dynamic control over the sequence of checkout steps without needing to modify the structure of the main checkout flow itself. The Salesforce B2B Commerce documentation outlines how checkout flows are constructed and how subflows can be managed and resequenced through configuration adjustments, providing a flexible and maintainable way to customize the checkout experience.

Explanation:

To bring picklist values into a Lightning Web Component (LWC), a developer needs to import specific modules from thelwcandlightning/uiObjectInfoApinamespaces. ThegetPicklistValuesfunction from thelightning/uiObjectInfoApimodule is used to fetch Question No : 122 Question No : 123 Salesforce B2B-Commerce-Developer : Practice Test 91 the picklist values based on record type and field metadata. Additionally, importing{ LightningElement, wire }fromlwcis essential for defining the LWC class and using the @wiredecorator to wire thegetPicklistValuesto a property orfunction. Salesforce documentation on LWC and utilizing theuiObjectInfoApiprovides clear guidelines on how to implement this functionality.

Explanation:

To fire a custom event called CustomEvent from the Lightning web component and propagate it up to the DOM, the developer must set two event settings: bubbles and composed. The bubbles setting determines whether the event bubbles up through the component’s ancestors in the DOM tree. The composed setting determines whether the event crosses the shadow boundary and reaches the light DOM. Setting both bubbles and composed to true allows the event to be handled by any element in the DOM that listens for it. The cancelable setting is not required for firing or propagating the event, as it only determines whether the event can be canceled by calling preventDefault() on it. Setting composed to false would prevent the event from reaching the light DOM and limit its propagation to the shadow DOM.

Salesforce References: Lightning Web Components Developer Guide: Create and Dispatch Events, Lightning Web Components Developer Guide: Event Propagation

Explanation:

The correct answer is External Objects. External objects are similar to custom objects, except that they map to data that’s stored outside your Salesforce org12. You can use external objects to access data in real time via web service callouts, without copying the data into your org12. External objects are read-only by default, but you can enable write operations for some data sources12.

Big Objects are not the correct answer. Big objects allow you to store and manage massive amounts of data on the Salesforce platform. However, big objects are not suitable for referencing historical data in another system, as they require importing the data into the org and incur storage costs.

Lightning Out is not the correct answer. Lightning Out is a feature that lets you run Lightning components in any container outside the Salesforce platform. However, Lightning Out does not provide a way to reference historical data in another system, as it is mainly used for embedding Lightning components in other web pages or apps.

External SOQL queries in Apex code are not the correct answer. External SOQL queries are a way to query data from external data sources using SOQL syntax in Apex code. However, external SOQL queries require defining an external data source and an external object first, so they are not a product feature by themselves, but rather a way to use external objects in Apex code.

References:

B2B Commerce on Lightning Experience Developer Guide
B2B Commerce and D2C Commerce Developer Guide
Salesforce Accredited B2B Commerce Developer
Work with External Data Sources
Access External Data With Salesforce Connect
Migrate data from one organization to another
Monitor Login History
[Big Objects]
[Lightning Out]
[External SOQL Queries]

Explanation:

The sizing keys used in the Salesforce B2B Commerce Global APIs perform five distinct operations. Three of these operations are:

Refetch data (used on some Logic classes): This operation indicates that the data should be refetched from the database instead of using the cached data. For example, ccrz.ccServiceCart.getCart(ccrz.ccAPI.SZ_REFETCH) will refetch the cart data and refresh the cache.

Related Query to call (sub queries or direct queries): This operation indicates that the related entities should be retrieved by using sub queries or direct queries. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_SUBQUERY) will use sub queries to fetch the related entities for each product,

while ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_DIRECTQUERY) will use direct queries to fetch the related entities separately.

Object type casting: This operation indicates that the data should be cast to a specific object type. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_SOBJECT) will cast the data to sObjects instead of transformed objects.

Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions