Explanation:

To verify changes by using an external service, a developer can use either of these two ways:

Create an Apex class that implements the sfdc_checkout.CartShippingCharges interface and defines the getShippingCharges method. This method takes a Cart object as an input parameter and returns a list of CartDeliveryGroupMethod objects with the updated shipping charges. The developer then needs to register the Apex class as the Shipping Calculation Integration in the store administration. This way, the store can call the external service to calculate the shipping charges for each delivery group in the cart.

Create an Apex class that defines a method to retrieve the shipping charges from an external service and update the Cart Delivery Group Method object. The developer then needs to invoke this method from a trigger on the Cart Delivery Group Method object. This way, the store can update the shipping charges whenever the delivery group method is inserted or updated.

The other options are not valid ways to verify changes by using an external service. Creating a flow using an action is not supported for B2B Commerce, and creating a trigger on the Cart Delivery Group object will not update the shipping charges for each delivery group method.

References:

Integrate with External Services
CartShippingCharges Interface
CartDeliveryGroupMethod Object

Explanation:

It is preferable to extend the Salesforce B2B Commerce remote invocation object instead of using the standard Salesforce remote action invocation manager for two reasons: The APEX method called by the remote action will be passed as a Salesforce B2B Commerce context object, which contains useful information such as the current user, cart, storefront, and configuration settings. This can simplify the development and testing of the remote action. The Salesforce B2B Commerce logger can be utilized in the remote action, which allows logging messages and errors to the debug log or to a custom object. This can facilitate debugging and troubleshooting of the remote action.

Explanation:

The out of the box Salesforce B2B Commerce page that can give instructions to web crawlers from accessing specific Salesforce B2B Commerce pages is cc_RobotsTxt. This is a Visualforce page that generates a robots.txt file, which is a text file that tells web crawlers which pages or files they can or can’t request from a site. The page uses the configuration settings CO.RobotsTxtAllow and CO.RobotsTxtDisallow to specify which paths are allowed or disallowed for web crawlers. For example, User-agent: * Disallow: /CCCart will instruct web crawlers to not access the CCCart page. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Robots.txt File

Explanation:

The Global API Data-Sizing convention flag that prevents an API request from propagating to further requests when provided as a Boolean parameter with a value of true is ccrz.ccAPI.SZ_ASSC. This flag indicates that only one API request should be executed with the specified sizing block, and any subsequent requests should use their own default sizing blocks. For example, ccrz.ccServiceCart.getCart(ccrz.ccAPI.SZ_L,true) will use the SZ_L sizing block for retrieving the cart data, but any other requests that are triggered by this method will use their own default sizing blocks.

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

Explanation:

The recommended method for increasing the number of required autocomplete characters that are typed before autocomplete works is to override the autoComplete.search_input.minLength value in the CCRZ.uiProperties file. This file contains various properties that control the behavior and appearance of the user interface components. The autoComplete.search_input.minLength property specifies the minimum number of characters that must be entered before the autocomplete feature is triggered.

The default value is 3, but it can be changed to any desired value by overriding it in the CCRZ.uiProperties file.

Salesforce References: B2B Commerce and D2C Commerce Developer Guide, UI Properties