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

To implement specific styling for a standard component on a single page of the B2B Commerce store using an Aura template, a developer should create a custom theme layout Aura component that imports the custom CSS file and set up the page to use this theme layout. A theme layout is a type of Aura component that defines the header and footer of a page in the storefront. Atheme layout can also import custom CSS files from static resources and apply them to the page. A developer can create a custom theme layout Aura component that imports the custom CSS file that contains the specific styling for the standard component and assign it to the page that needs the custom styling. This way, the custom styling will only affect the standard component on that page and not on other pages that use a different theme layout. Using a custom CSS file in a static resource and adding the import using the Edit Head Markup Editor in the Experience Builder is not a valid way to implement specific styling for a standard component on a single page, as it will affect all pages that use the same template. Creating a custom content layout Lightning web component that imports the custom CSS file and setting up the page to use this content layout is not a valid way either, as it will not affect the standard component that is outside of the content layout. Using the Override CSR Editor in the Experience Builder and adding the desired CSS to change the styles is not a valid way either, as it will affect all pages that use the same template. Salesforce References: B2B Commerce Developer Guide: Theme Layout Component, B2B Commerce Developer Guide: Content Layout Component, B2B Commerce Developer Guide: Override CSR Editor

Two components in a B2B store template that a developer can use to customize a storefront page are My Lists and Product List.My Lists is a standard component that displays and manages lists of products that customers can create, save, or share in the storefront. A developer can use this component to enable customers to organize their favorite or frequently purchased products into lists and access them easily. Product List is a standard component that displays and filters products from one or more product lists in the storefront. A developer can use this component to showcase products from different categories or collections and allow customers to browse or search for products based on various criteria. Order List is not a component in a B2B store template, but rather an object that stores information about orders placed by customers in the storefront. Address List is not a component either, but rather an object that stores information about addresses associated with customers in the storefront. Salesforce References: [B2B Commerce Developer Guide: My Lists Component], [B2B Commerce Developer Guide: Product List Component], [B2B Commerce Developer Guide: Order List Object], [B2B Commerce Developer Guide: Address List Object]

To have a Contact Us page in the storefront that is a web-to-lead form and has the same look and feel as all the pages in the application, the requirement can be fulfilled by creating a Subscriber Page (CC Page). This is a custom Visualforce page that can be added to the storefront and use the standard header and footer components. The page can also include a web-to-lead form that submits data to Salesforce as leads. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Subscriber Pages

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 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]

Two different types of services that Salesforce B2B Commerce APIs leverage are:

Logic services which are responsible for implementing business logic associated with entities. These services are defined inthe logic classes, such as ccrz.ccLogicCart, ccrz.ccLogicOrder, or ccrz.ccLogicProduct. Theseclasses provide methods for validating inputs, performing calculations, applying rules, or updating data for each entity.

Data services which are responsible forquerying and transforming data from entities. These services are defined in the service classes, such as ccrz.ccServiceCart, ccrz.ccServiceOrder, or ccrz.ccServiceProduct. These classes provide methods for creating, reading, updating, and deleting data foreach entity. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Service Classes, Logic Classes

 Executing dynamic SOQL inside a without sharing classwith a bind variable from PageReference.getParameters(), PageReference.getCookies(), or cc_RemoteActionContext class will open up a major security hole because these sources of input are not sanitized and can be manipulated by malicious users to inject SOQL queries that bypass the sharing rules and access data that they are not supposed to see. For example, a user can modify the URL parameters or cookies to include a SOQL query that returns sensitive data from the database. To prevent this, it is recommended to use static SOQL or escape the bind variables before executing dynamic SOQL.

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 Apexclass 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

 A developer should use Jest to author automated tests for custom Lightning web components. Jest is a powerful tool with rich features for writing JavaScript tests. It is the recommended testing framework for Lightning web components by Salesforce1. Jest allows the developer to write unit tests in local JavaScript files, run them from the command line or Visual Studio Code, and debug them using breakpoints and watch expressions2. Jest also provides features such as mocking, code coverage, snapshots, and asynchronous testing3.

Option A, Option B, and Option D are incorrect because they are not testing tools, but rather development tools. Visual Studio Code is an integrated development environment(IDE) that supports Lightning web components development with extensions and plugins4. Salesforce CLI is a command line interface that allows the developer to create, deploy, and manage Lightning web components projects5.Salesforce Developer Console is a web-based tool that provides code editing, debugging, and testing features for Apex and Visualforce, but not for Lightning web components. References:

Test Lightning Web Components

Write Jest Tests

Jest Documentation

Visual Studio Code

Salesforce CLI

[Salesforce Developer Console]

The use of a standard Visualforce control such as apex:form is discouraged in Salesforce B2B Commerce page includes and subscriber pages because the CCRZ JavaScript object is not accessible within an apex:form control. The CCRZ JavaScript object is a global object that provides access to various B2B Commerce functions and properties, such as logging, utilities, events, and configuration. Using an apex:form control would prevent the developer from using the CCRZ JavaScript object and its features. Visualforce does not “scope” controls that are present on a page and scope of the control will be set to “ccrz”, as this is not a valid statement. Apex:form does not render DOM components slowly, as this is not a performance issue. JavaScript events are supported within an apex:form control, as this is not a limitation. Salesforce References: B2B Commerce Developer Guide: CCRZ JavaScript Object, B2B Commerce Developer Guide: Page Includes