Free Salesforce B2B-Commerce-Developer Practice Exam with Questions & Answers

• The correct answer is External Objects. External objects are similar to custom objects, except that they map to data that’s stored outside your Salesforce org12. You can use external objects to access data in real time via web service callouts, without copying the data into your org12. External objects are read-only by default, but you can enable write operations for some data sources12.
• Big Objects are not the correct answer. Big objects allow you to store and manage massive amounts of data on the Salesforce platform. However, big objects are not suitable for referencing historical data in another system, as they require importing the data into the org and incur storage costs.
• Lightning Out is not the correct answer. Lightning Out is a feature that lets you run Lightning components in any container outside the Salesforce platform. However, Lightning Out does not provide a way to reference historical data in another system, as it is mainly used for embedding Lightning components in other web pages or apps.
• External SOQL queries in Apex code are not the correct answer. External SOQL queries are a way to query data from external data sources using SOQL syntax in Apex code. However, external SOQL queries require defining an external data source and an external object first, so they are not a product feature by themselves, but rather a way to use external objects in Apex code. References:
• B2B Commerce on Lightning Experience Developer Guide
• B2B Commerce and D2C Commerce Developer Guide
• Salesforce Accredited B2B Commerce Developer
• Work with External Data Sources
• Access External Data With Salesforce Connect
• Migrate data from one organization to another
• Monitor Login History
• [Big Objects]
• [Lightning Out]
• [External SOQL Queries]

The static method invocation that is used to initialize ccrz.cc_CallContext with information from ccrz.cc_RemoteActionContext and return an instance of ccrz.cc_RemoteActionResult in an Apex @RemoteAction method is ccrz.cc_CallContext.initCallContext(ccrz.cc_RemoteActionContext). This method takes in a ccrz.cc_RemoteActionContext object as a parameter and returns a ccrz.cc_RemoteActionResult object. The ccrz.cc_RemoteActionContext object contains information about the current storefront, user, cart, price list, currency, locale, and session. The ccrz.cc_RemoteActionResult object contains information about the status, result, and errors of the remote action. The other methods are not valid or do not exist. Salesforce References: B2B Commerce Developer Guide: cc_CallContext Class, B2B Commerce Developer Guide: cc_RemoteActionContext Class, B2B Commerce Developer Guide: cc_RemoteActionResult Class

Two ways that events fired from Lightning web components can be handled are programmatically adding event listeners and attaching handlers to DOM elements. Programmatically adding event listeners is a way of handling events by using JavaScript code to register functions that are invoked when an event occurs. The developer can use methods such as addEventListener or @wire to add event listeners to components or services that fire events. Attaching handlers to DOM elements is a way of handling events by using HTML attributes to bind functions that are invoked when an event occurs. The developer can use attributes such as onclick or onchange to attach handlers to DOM elements that fire events. Adding callbacks to components is not a valid way of handling events fired from Lightning web components, as it is not related to event handling, but rather to asynchronous programming. Listening for all possible events at the document root is not a valid way either, as it is not efficient or recommended for event handling, as it can cause performance issues or conflicts with other event listeners. Salesforce References: [Lightning WebComponents Developer Guide: Handle Events], [Lightning Web Components Developer Guide: Communicate with Events]

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 the Lightning 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

Composition is a key pattern in building Lightning Web Components (LWCs). This approach involves creating small, reusable components that can be assembled to form more complex interfaces. This pattern promotes modularity, reusability, and maintainability in the development of web components, aligning with web standards and best practices.

To handle the subscription lifecycle of a message channel in a Lightning web component, the developer should implement the subscribe() and unsubscribe() methods from the lightning/messageService module. The subscribe() method returns a subscription object that represents the connection to the message channel. The developer can use this object to unsubscribe from the message channel later. The unsubscribe() method takes a subscription object as a parameter and removes the listener from the message channel. The developer should call the unsubscribe() method when the component is disconnected from the DOM, such as in the disconnectedCallback() lifecycle hook, to avoid memory leaks and performance issues.

The other options are not correct because:

• B. stopListener() is not a valid method for handling the subscription lifecycle of a message channel. There is no such method in the lightning/messageService module or the Lightning web component framework.
• C. startListener() is not a valid method for handling the subscription lifecycle of a message channel. There is no such method in the lightning/messageService module or the Lightning web component framework.

References:

• Subscribe and Unsubscribe from a Message Channel
• Lifecycle Hooks
• Use message channel in both direction

An essential requirement for a Salesforce B2B Commerce theme to show up in the theme section in CC Admin is that the theme needs to have “theme” in the name of the Static Resource. For example, a theme named “MyTheme” will not appear in CC Admin, but a theme named “MyTheme_theme” will. This is how the framework identifies which static resources are themes and which are not. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Themes

In the context of Salesforce debug logs, code units represent discrete units of work within a transaction. Apex classes (B), Web service invocations (C), and Workflow invocations (E) are considered code units as they encapsulate specific operations or sets of logic that can be executed as part of a transaction. Validation rules (A) and the loading of Lightning components (D) are not considered discrete units of work in the same way, as they are part of the declarative interface and front-end framework, respectively. For more details on how Salesforce handles transactions and debug logs, refer to the Salesforce Developer Documentation:Salesforce Developer Documentation on Transactions and Debug Logs.

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, unless another sizing block is specified as a parameter. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Data Sizing Conventions

The product will not appear on the Portal and therefore cannot be added to the cart. A product is assigned to the entitlement policy but is missing from the Price Book related to the Buyer Group. The entitlement policy has View products and View prices in catalog checked. An entitlement policy is a set of rules that determines which products and prices a buyer group can access in the storefront. A buyer group is a group of buyers that share the same business relationship with the seller. A price book is a collection of prices for products that are available for purchase in the storefront. A product is a record that represents an item that can be sold in the storefront. To make a product visible and purchasable in the storefront, it must be assigned to both an entitlement policy and a price book that are related to the buyer group. If a product is assigned to an entitlement policy but not to a price book, it will not appear on the Portal and therefore cannot be added to the cart, regardless of the entitlement policy settings. The product will appear on the Portal with Price Unavailable status and can also be added to the cart is not a correct answer, as it contradicts the behavior of a product that is not in a price book. The product will appear on the Portal with Price Unavailable status but cannot be added to the cart is not a correct answer either, as it also contradicts the behavior of a product that is not in a price book. The product will not appear on the Portal but can be searched since it is part of the entitlement policy is not a correct answer either, as it also contradicts the behavior of a product that is not in a price book. Salesforce References: [B2B Commerce Developer Guide: Entitlement Policy Object], [B2B Commerce Developer Guide: Buyer Group Object], [B2B Commerce Developer Guide: Price Book Object], [B2B Commerce Developer Guide: Product Object]