Free Practice Questions for Salesforce B2B-Commerce-Developer Exam

 According to the Platform Events Developer Guide, to debug platform events, a developer needs to include the Apex Code and Workflow loglevels in the trace flag entry for the Automated Process entity or the overridden user. The Apex Code log level captures the execution of the Apex trigger that subscribes to the platform event. The Workflow log level captures the execution of the event process or the resumed flow interview that subscribes to the platform event. The other log levels are not relevant for debugging platform events. The Database log level captures database operations, such as DML statements and SOQL queries. The Callout log level captures the details of HTTP requests and responses, such as web service callouts. References: Platform Events Developer Guide, Set Up Debug Logs for Event Subscriptions, Set Up Debug Logging

When implementing an Inventory class for checkout and indicating that inventory is available for all items and amounts in the cart, the correct step is to returnsfdc_checkout.InventoryStatus.Status.SUCCESS. This indicates to the checkout process that the inventory check has passed and theitems are available. Salesforce documentation on customizing inventory validation in the checkout process would detail the expected return types and values, ensuring that developers implement the inventory checks in a manner consistent with the platform'srequirements.

A price group can be dynamically set by extending the cc_hk_pricing hook. This hook allows modifying the price group based on various factors, such as the user, cart, product, orstorefront. For example, the hook can apply a different price group for a specific product category or for a specific user segment.

To override pricing during the checkoutprocess in Salesforce B2B Commerce, a developer must implement a class specifically designed for this purpose, such assfdc_checkout.CartPriceCalculations. This class would provide the necessary framework for custom pricing logic to be applied during checkout, ensuring that any custom pricing requirements are met.

 According to the Lightning Web Components Developer Guide, Shadow DOM is a standard that encapsulates the internal document object model (DOM) structure of a web component. Encapsulating the DOM gives developers the ability to share a component and protect the component from being manipulated by arbitrary HTML, CSS, and JavaScript. Shadow DOM also provides style and behavior isolation for a web component, which means that the styles andscripts defined inside a component do not affect the rest of the page, and vice versa. Therefore, the purposes of the Shadow DOM in a Lightning web component are to encapsulate the internal DOM structure of a web component (A) and to allow components to beshared while protecting them from being manipulated by arbitrary code (B). The other options are incorrect because Shadow DOM does not allow direct access to the document object model of the component ©, nor does it allow older JavaScript libraries to manipulate the tagging structure (D). References: Lightning Web Components Developer Guide, Understand the Shadow DOM Unit

 The connectedCallback is a lifecycle hook that is invoked when a Lightning web component is inserted into the DOM. It is used to perform any initialization tasks that depend on the component being rendered, such as fetching data, setting up event listeners, or creating timers. The connectedCallback can fire more than once, for example, when a component is moved or rerendered. The connectedCallback should not be used to change the state of a component, such as loading values or setting properties. Use getters and setters instead. The other options are incorrect because they do not describe the purpose of the connectedCallback. References: Lifecycle Hooks | Lightning Web Components Developer Guide, connectedCallback() in Lightning Web Component - Salesforce Diaries, Chapter 23: connnectedCallback() in Lightning Web Component

 A developer needs to make a call to a long running web service which is critical to finalizing their checkout process. The developer should consider the following items in their implementation:

A new CORS entry may need to be created in Setup. CORS stands for Cross-Origin Resource Sharing, which is a mechanism that allows web browsers to make requests to servers on different domains. If the web service is hosted on a different domain than the B2B Commerce site, the developer may need to add a CORS entry in Setup to allow the browser to access the web service. This entry specifies the origin, path, and method of the request, as well as any headers or cookies that are allowed1.

A new Named Credential may need to be created in Setup. A Named Credential is a type of metadata that stores the URL and authentication settings of a web service. By using a Named Credential, the developercan avoid hardcoding the web service URL and credentials in their code, and instead reference the Named Credential by name. This makes the code more secure and easier to maintain2.

An Apex method returning a Continuation will need to be created. A Continuation is a special type of Apex object that allowsthe developer to make asynchronous calls to long running web services. By using a Continuation, the developer can avoid blocking the main thread and improve the user experience. A Continuation method must return a Continuation object, specify the web service URL and parameters, and register a callback method that handles the response3.

Option D and Option E are incorrect because they are not relevant to the scenario. Option D suggests that the developer should broker the requests to the web service, which means to use an intermediary service that manages the requests and responses. This may be useful for some scenarios, but it is not required for making a call to a long running web service. Option E suggests that the developer should create a new Remote Site in Setup, which is a way to whitelist the domains that can be accessed from Apex code. However, this is not necessary if the developer uses a Named Credential, which automatically handles the Remote Site setting2. References:

Set UpCORS

Named Credentials

Continuation Class

The defaultbehavior for how the Salesforce B2B Commerce Global APIs transform Salesforce data is to return field names with a lowercase first letter, camelcase convention. For example, the field name ccrz__E_Product__c in Salesforce will be transformed to eProduct inthe API. This is done to follow the JavaScript naming convention and to avoid conflicts with the standard Salesforce fields and relationships. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation

When creating a tax provider, three things that a developer should consider first are: steps to complete in the tax service, how to handle results, and what to implement. Steps to complete in the tax service are the actions that the developer needs to perform to connect to and use the third-party tax service provider’s API or service. These steps may include authentication, authorization, request formatting, response parsing, error handling, and logging. How to handle results are the actions that the developer needs to perform to process and apply the tax calculation results from the tax service to the cart or order. These actions may include creating or updating cart items with type of Charge and charge type of Tax, applying tax adjustments or exemptions, and displaying tax amounts and details on the storefront. What to implement are the methods that the developer needs to define in their custom Apex class that implements the sfdc_checkout.TaxCalculations interface. The interface provides methods for customizing the tax calculation logic for a cart or an order, such as getTaxRatesAndRules, applyTaxAmountsAndAdjustments, and handleTaxErrorsAndExceptions. Whether to use JSON or XML is not something that the developer should consider first, as it is not a critical or relevant factor for creating a tax provider. It may depend on the format that the tax service provider supports or prefers, but itdoes not affect the overall functionality or performance of the tax integration. What events to fire in the Lightning web component is not something that the developer should consider first either, as it is not related to creating a tax provider. It may bean optional feature that the developer can add to enhance the user interface or user experience of their storefront, but it does not affect the core logic or functionality of the tax integration. Salesforce References: B2B Commerce Developer Guide: Tax Integration, [B2B Commerce Developer Guide: Tax Calculations Interface]