More modules and metadata can be added to Salesforce B2B Commerce by creating custom configuration settings. Configuration settings are custom settings that store various values and parameters that affect the functionality and appearance of the storefront. They are organized into modules, which group related settings together. To create a custom configuration setting, the user needs to create a custom setting record in Salesforce and specify its module, name, value, and description. The custom setting will then appear in CCAdmin under the specified module. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Configuration Settings

* The correct answer is A 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 callouts3 and 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. References:
* 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]

Explanation
The connectedCallback is a lifecycle hook that is invoked when a Lightning web component is inserted into the DOM. It is used to perform any initialization tasks that depend on the component being rendered, such as fetching data, setting up event listeners, or creating timers. The connectedCallback can fire more than once, for example, when a component is moved or rerendered. The connectedCallback should not be used to change the state of a component, such as loading values or setting properties. Use getters and setters instead. The other options are incorrect because they do not describe the purpose of the connectedCallback. References: Lifecycle Hooks | Lightning Web Components Developer Guide, connectedCallback() in Lightning Web Component - Salesforce Diaries, Chapter 23:
connnectedCallback() in Lightning Web Component

Explanation
Version related upgrades are passed on to subscriber API extensions/overrides by using the "delegate" keyword, which allows inherited method calls access to the most recently specified service version. For example, delegate.getCart() will invoke the getCart() method of the latest service version that is available for the current storefront. This way, extensions and overrides can leverage the new features and enhancements of the upgraded service versions without modifying their code.