B2B-Commerce-Developer Exam Questions

Explanation:

To view the fields available for the Product Detail Page, the developer should type CCRZ.productDetailModel in the Developer Tools Console in the browser. This will display the product detail model object, which contains the product data and attributes that are rendered on the page. The other options are either not valid or not relevant for the Product Detail Page.

Explanation:

To pass HTML from a parent component to a child component, the child component needs to have a element in its template. A slot is a placeholder for markup that a parent component passes into a component’s body. Slots are part of the Web Component specification. The parent component can use the slot name or the default slot to specify which HTML content goes into which slot of the child component. The other options are not valid elements for passing HTML from parent to child. References: Slots Pass HTML Markup From Parent TO CHILD In Lightning Web Component How parent component pass HTML to child component in Angular?

Explanation:

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:

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

Explanation:

Option B is the correct answer because it describes the fastest route to establishing the data needed for checkout development when setting up a new store. The developer can use sfdx setup scripts to deploy a Lightning B2B testing environment that includes checkout flows, sample products, and a buyer. This way, the developer can quickly and easily test and customize the checkout flow using Experience Builder or Flow Builder. The other options are incorrect because they either require more time, manual steps, or additional tools to set up the data for checkout development. For example, importing a previously exported store archive or using data loader would require the developer to have access to the source data and the target org, and to map the fields and objects correctly. Selecting Add Sample Data when setting up the store would only provide a limited amount of data that may not be sufficient for checkout development. References: Create a B2B Commerce Org and Checkout Flow, B2B Commerce on Lightning Experience Developer Guide, B2B Commerce and D2C Commerce Developer Guide

Explanation:

Two advantages of using Lightning Data Service are that it combines and de-duplicates server calls and that it loads record data progressively. Lightning Data Service is a service that provides access to Salesforce data and metadata in Lightning web components. It optimizes performance and minimizes server round trips by caching data on the client side and sharing data across components. It also combines and de-duplicates server calls by batching requests for the same record or object and returning a single response. It also loads record data progressively by returning available cached data first and then fetching updated data from the server asynchronously. Communicating with other components and converting between different data formats are not advantages of using Lightning Data Service, as they are not related to its functionality or features.

Salesforce References: Lightning Web Components Developer Guide: Lightning Data Service, Lightning Web Components Developer Guide: Work with Salesforce Data

Explanation:

The event that is invoked by any CCRZ Salesforce B2B Commerce View after the view is rendered is view:*:rendered. This event is triggered by the render method of the CCRZ.View class, which is the base class for all views in the framework. The event can be used to perform any actions or logic that depend on the view being rendered, such as initializing widgets, binding events, or updating the user interface.

Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Events, View Class

Explanation:

Salesforce B2B Commerce API sizing blocks can support multiple API sizing requests in three ways:

When different entities are specified in the method invocation. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M, ccrz.ccAPI.SZ_L) will use the SZ_M sizing block for the product entity and the SZ_L sizing block for the related entities.

SZ_ASSC is used. This flag indicates that the associated entities should use the same sizing block as the primary entity. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M, ccrz.ccAPI.SZ_ASSC) will use the SZ_M sizing block for both the product entity and the related entities.

SZ_ASSC is not used. This flag indicates that the associated entities should use the default sizing block, which is SZ_M, unless otherwise specified. For example, ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M) will use the SZ_M sizing block for the product entity and the SZ_M sizing block for the related entities.

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

Explanation:

Three actions that a developer must take, in a B2B Commerce store, to accept credit card payments using a client’s chosen payment provider are: create a named credential for authentication with the payment provider, create an Apex class that implements the sfdc_checkout.PaymentGatewayAdapter interface, and create a PaymentProviderGateway record for the custom payment provider class. Creating a named credential for authentication with the payment provider allows the developer to securely store and manage authentication information, such as username, password, token, or certificate, for connecting to the payment provider’s API or service. Creating an Apex class that implements the sfdc_checkout.PaymentGatewayAdapter interface allows the developer to define custom logic for processing credit card payments using the payment provider’s API or service. The interface provides methods for validating credit card information, authorizing payments, capturing payments, voiding payments, and refunding payments. Creating a PaymentProviderGateway record for the custom payment provider class allows the developer to register the custom payment provider class as a payment gateway in the store and associate it with a payment method.

Creating a RegisteredExternalService record for the custom payment provider class is not a required action, as this is only used for registering external services that are not related to payment processing, such as tax or shipping services. Creating an Apex class that implements the commercepayments.PaymentGatewayAdapter interface is not a required action either, as this is only used for D2C Commerce stores, not B2B Commerce stores. Salesforce References: B2B Commerce Developer Guide: Payment Integration, B2B Commerce Developer Guide: Payment Gateway Adapter Interface, B2B Commerce Developer Guide: Payment Provider Gateway Object

Explanation:

Salesforce documentation clarifies the interoperability between Aura and Lightning Web Components (LWCs). An Aura component can indeed contain another Aura component, as well as a LWC, allowing for a mix of component technologies in a single application. However, due to the architectural and design principles of LWCs, a LWC cannot contain an Aura component. This is because LWCs are designed to be lightweight and leverage web standards, which makes them not fully compatible with the older Aura component framework in terms of containment.