A price group can be dynamically set by extending the cc_hk_pricing hook. This hook allows modifying the price group based on various factors, such as the user, cart, product, or storefront. For example, the hook can apply a different price group for a specific product category or for a specific user segment.

The Salesforce CLI commandsfdx force:data:tree:exportis used to export data from an org into one or more JSON files1.The-qflag is used to specify the path to a file containing a SOQL query,-xis used to specify the name of the exported file,-dis used to specify the directory where the exported file will be saved, and-pis used to indicate that all records returned by the SOQL query should be exported12.This command allows developers to bulk export data from an org without needing access to Data Loader or Workbench12. Therefore, option A is the correct answer. Please note that the actual SOQL query and the directory path would need to be replaced with the appropriate values for the specific use case.

In Salesforce Experience Cloud, components like CMS Collection and Results Layout are designed to be reusable across different Experience templates, not just limited to B2B Commerce. CMS Collection allows for the display of CMS content in a flexible and dynamic layout, while Results Layout can be used to present search or query results in a customizable format. Salesforce documentation on Experience Cloud components emphasizes the reusability and adaptability of these components across various templates and contexts.

To enable a new payment type for the Checkout flow, three possible configuration metadata descriptors are needed:

*.pay: This descriptor defines the payment type name, label, description, icon, and handler class. For example,CO.pmts.CreditCard.paydefines the payment type for credit card payments.

*.Edit: This descriptor defines the Visualforce page that is used to edit or update an existing payment of this type. For example,CO.pmts.CreditCard.Editdefines the page that allows editing a credit card payment.

*.New: This descriptor defines the Visualforce page that is used to create a new payment of this type. For example,CO.pmts.CreditCard.Newdefines the page that allows creating a new credit card payment. Salesforce Reference:B2B Commerce and D2C Commerce Developer Guide,Payment Configuration Settings

The correct answer isA and C.To use a sophisticated pricing engine hosted as a service outside the org, the developer must make a call to the service and implement the sfdc_checkout.PriceCalculations interface12.The sfdc_checkout.PriceCalculations interface is a standard interface that defines the methods for calculating prices for a cart or an order1.The developer can use this interface to override the default pricing logic and integrate with an external pricing service12.The developer must also make a call to the external service using Apex REST or SOAP callouts3and handle the response data accordingly.

Use External Objects and Implement the sfdc_checkout.CartPriceCalculations are not the correct answers. External objects are a way to access data from external data sources in real time, but they are not suitable for integrating with a pricing service that requires dynamic calculations .The sfdc_checkout.CartPriceCalculations interface is a deprecated interface that was used for calculating prices for a cart only1.It has been replaced by the sfdc_checkout.PriceCalculations interface, which supports both carts and orders1.Reference:

B2B Commerce on Lightning Experience Developer Guide

B2B Commerce and D2C Commerce Developer Guide

Salesforce Accredited B2B Commerce Developer

sfdc_checkout.PriceCalculations Interface

Integrate with Lightning B2B Commerce

Apex REST Callouts

[Apex Web Services and Callouts]

[Work with External Data Sources]

[Access External Data With Salesforce Connect]