Pass the Salesforce B2B-Commerce-Developer B2B-Commerce-Developer Questions and answers with ValidTests

To make an integration available for selection in Salesforce B2B Commerce, a developer must create aRegisteredExternalServicerecord. This can be accomplished using tools like Workbench, whichallow for direct interaction with Salesforce's backend database. By registering the external service, the integration becomes selectable within the B2B Commerce setup, allowing it to be associated with specific stores or contexts. Salesforce documentationon integrating external services with B2B Commerce provides step-by-step instructions on registering these services to enable seamless integration and functionality within the platform.

 The correct way to demonstrate the passing of a message from the grandchild component to the grandparentcomponent in LWC is to use the PubSub library. The PubSub library is a utility that enables Lightning web components to communicate across the DOM tree without using intermediaries. The grandchild component can publish a message to a channel, and the grandparent component can subscribe to that channel and receive the message. This way, the communication is decoupled and does not depend on the component hierarchy. Option B shows the correct syntax for using the PubSub library to pass a message from the grandchild component to the grandparent component. Option A is incorrect because it uses the @api decorator to expose a property on the grandchild component, which is not a valid way to communicate with the grandparent component. Option C is incorrect becauseit uses the @wire decorator to wire a property on the grandchild component to a function on the grandparent component, which is also not a valid way to communicate with the grandparent component. Option D is incorrect because it uses the @track decorator to track a property on the grandchild component, which is not a valid way to communicate with the grandparent component. References: Communicate Across the DOM |Lightning Web Components Developer Guide, Child to grandparent communication in LWC, PubSub Library for Lightning Web Components

Two guidelines for logging that are used within the core Salesforce B2B Commerce product are:

The close method of ccrz.ccLog must be called at the end of the remote action. This method will flush the log messages to the browser console or to a custom object, depending on the logging mode. If this method is not called, the log messages may not be displayed or saved properly.

No calls to ccrz.ccLog can be made before cc_CallContext.initRemoteContext is executed. This method will initialize the call context object, which contains information such as the current user, cart, storefront, and configuration settings. These information are required for logging, so calling ccrz.ccLog before initializing the call context will result in an error. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Logging

When including additional JavaScript files in a Lightning Web Component, it is required that these files are ECMAScript 6 (ES6) modules and have unique names within the component's folder. This ensures proper module resolution and avoids namespace conflicts. Salesforce LWC documentation provides guidelines on organizing component resources, including JavaScript modules, to ensure they are correctly recognized and utilized within the LWC framework.

The equivalent of this code in a Lightning web component is option B. Option B uses the @api decorator to expose firstName as a public property of theLightning web component and communicate it with other components or services. The @api decorator is a decorator that marks a property or method as public, which means that it can be accessed by other components or services that use or consume this component. The @api decorator also makes the property reactive, which means that it can track changes and update the component accordingly. In option B, firstName is exposed as a public property using the @api decorator and passed to the child element using an attribute. Option A is incorrect because it uses an invalid syntax for exposing firstName as a public property. The @api decorator should be used before the property declaration, not after it. Option C is incorrect because it uses an invalid syntax for exposing firstName as a public property. The @api decorator should be used with parentheses, not without them. Option D is incorrect because it uses an invalid syntax for exposing firstName as a public property. The @api decorator should be used with camel case,not with hyphens. Salesforce References: Lightning Web Components Developer Guide: Communicate with Properties, Lightning Web Components Developer Guide: Decorators

The default Global API Data-Sizing convention flag that is used by the API’s unless otherwise specified is CCRZ.ccAPI.SZ_M. This flag indicates that the medium sizing block should be used for retrieving data, which includes the most commonly used fields and related entities. For example, ccrz.ccServiceProduct.getProducts() will use the SZ_M sizing block by default, unlessanother sizing block is specified as a parameter. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions

In Lightning Web Components, the decorators@api,@track, and@wireplay crucial roles. The@apidecorator is used to expose public properties and methods, making them accessible to other components. The@trackdecorator is used to mark private properties as reactive, so the UI updates when their valueschange. The@wiredecorator is used to wire Apex methods or Salesforce data to the component. Salesforce documentation on LWC development extensively covers these decorators, explaining their usage and best practices.

To retrieve metadata about a specific picklist, a developer should use the getPicklistValues wire adapter. The getPicklistValues wire adapter imports data from the @salesforce/ui-api module and returns an object that contains information such as the picklist’s label, value, default value, validity, and controlling field values. The getPicklistMetadataValues wire adapter does not exist. The getPicklistMetadata wire adapter does not exist either. The getPicklist wire adapter does not exist either. Salesforce References: [Lightning Web Components Developer Guide: getPicklistValues], [Lightning Web Components Developer Guide: Import User Interface API]

Lightning Data Service (LDS) is a Salesforce UI API layer that empowers developers to perform CRUD operations and manage Salesforce data without the need for custom Apex controllers. LDS is designed to improve performance, user interface consistency, and developer productivity by handling data operations and sharing rules, thus reducing the need for server-side code. For more details, refer to the Salesforce documentation on Lightning Data Service:Salesforce Lightning Data Service Documentation.

 To implement the use of athird-party service for either tax, shipping, or pricing calculation in a B2B Commerce store, a developer must complete these three tasks:

Create an Apex class that implements the appropriate interface for the calculation type. For example, for tax calculation, the developer must implement the sfdc_checkout.CartTax interface and define the getTax method. This method takes a Cart object as an input parameter and returns a list of CartTax objects with the calculated tax amounts.

Create a named credential forauthentication with the external service. A named credential specifies the URL of a callout endpoint and its required authentication parameters. The developer can use the named credential in the Apex class to make the callout to the external service and handle the response.

Register the Apex class as the integration in the store administration. The developer must specify the Apex class name in the corresponding field for the calculation type. For example, for tax calculation, the developer must enter the Apex class name in the Tax Calculation Integration field. This way, the store can invoke the Apex class to perform the calculation for each cart.

The other options are not valid tasks for implementing the use of a third-party service. Creating a flow to callthe external service directly is not supported for B2B Commerce, and creating an Apex class with an invocable method is not required for the calculation integration. References:

Integrate with External Services

CartTax Interface

Named Credentials

[Store Administration]