Get Salesforce B2B-Commerce-Administrator Exam Dumps

Answer : D

To implement a custom child checkout component to modify out-of-the-box functionality in an LWR checkout flow, the developer must implement the CheckoutStep interface. This interface defines the contract between the child component and the parent Checkout component, and allows the child component to communicate with the checkout flow. The developer must implement the methods of this interface, such as getStepName, getStepLabel, getStepStatus, validateStep, and so on. The developer can also use the @wire(CheckoutApi) decorator to access the checkout API methods and data.Reference:

Customize Your Checkout Flow for a B2B Store (LWR)

CheckoutStep Interface

Answer : B, D

To integrate a new shipping provider to use during checkout in a storefront, a developer must take the following two steps:

Create an Apex class that uses the integration framework. The integration framework is a set of interfaces and classes that enable developers to create custom integrations with external services, such as shipping providers, payment gateways, and tax calculators.The developer must implement the sfdc_checkout.ShippingCalculationService interface and its methods to calculate shipping costs and options based on the shipping address and cart items1.

Enter the integration class name and version in the store administration. The store administration is a user interface that allows developers and administrators to configure various settings for a storefront, such as payment methods, shipping methods, tax methods, and store information.The developer must enter the name and version of the custom Apex class that implements the shipping calculation service in the Shipping Methods section of the store administration2.Reference:1: Integration Framework - Trailhead3,2: Add a Shipping Calculation Service for Commerce Stores - Salesforce Help4

Answer : A, B, D

When creating a tax provider class using the interfaces available in the Buyer Experience SDK, the developer should consider the following things first:

Steps to complete in the Tax Service. The developer should decide what steps are required to calculate and apply taxes to an order, such as validating the address, requesting a tax quote, committing the tax transaction, and so on. The developer should also consider how to handle errors or exceptions that may occur during these steps.

How to handle results. The developer should determine how to process and store the results returned by the tax provider, such as the tax amount, the tax rate, the tax code, and any other relevant information. The developer should also decide how to display these results to the buyer and the seller in the storefront and the order management system.

What to implement. The developer should implement the ITaxProvider interface and its methods, such as getTaxQuote, commitTaxTransaction, cancelTaxTransaction, and so on. The developer should also implement any custom logic or configuration required by the tax provider, such as authentication, headers, parameters, endpoints, and so on.Reference:

Create a Tax Provider

Buyer Experience SDK Developer Guide

Answer : B, D

When tax implementation is enabled in B2B Commerce, two things happen with the Cart during checkout:

Previous entries are copied to another object. The Cart object stores the products and quantities that the customer has added to their shopping cart. When tax implementation is enabled, these entries are copied to another object called CartItemTaxableItem.This object stores additional information about each cart item, such as its taxable amount, tax code, tax rate, and tax amount7.

New entries are written to the Order Summary. The Order Summary object stores the summary information of an order, such as its total amount, subtotal amount, shipping amount, and discount amount.When tax implementation is enabled, new entries are written to this object to store the tax information of an order, such as its total tax amount, tax jurisdiction, and tax breakdown8.Reference:7: CartItemTaxableItem Object Reference - Salesforce Help,8: OrderSummary Object Reference - Salesforce Help

Answer : A, C, E

To accept credit card payments using a client's chosen payment provider, a developer must take the following three actions in a B2B Commerce store:

Create a named credential for authentication with the payment provider. A named credential is a Salesforce feature that defines the URL of a callout endpoint and its required authentication parameters.By creating a named credential for the payment provider, the developer can securely store the credentials and use them in Apex code without hardcoding them1.

Create an Apex class that implements the commercepayments.PaymentGatewayAdapter interface. This interface defines the methods that a custom payment provider class must implement to process credit card payments in B2B Commerce.The developer must implement the methods such as authorize, capture, refund, and void to handle the payment transactions with the payment provider's API2.

Create a PaymentProviderGateway record for the custom payment provider class. This record is a custom metadata type that defines the properties of the payment provider, such as its name, label, description, and Apex class name.By creating this record, the developer can register the custom payment provider class with B2B Commerce and make it available for selection in the Payment Gateway Settings page3.Reference:1: Named Credentials - Trailhead4,2: Implementing Custom Payment Providers - Salesforce Developers Blog5,3: Integrate Payments into a B2B Commerce Store with Ease - Salesforce Developers Blog6