Free Practice Questions for Salesforce B2B-Commerce-Developer Exam

The correct syntax for looping through a series of child components which are tiles is option A. Option A uses the for:each directive to iterate over acollection of items and render a template block for each item. The for:each directive requires an expression that evaluates to an array or an iterable object and an item alias that represents the current item in the iteration. The item alias can be used toaccess the item’s properties or pass them to child components. In option A, the expression is appTiles, which is an array of objects that represent app tiles, and the item alias is appTile, which represents the current app tile object in the iteration. The appTile object’s properties, such as name, description, and icon, are passed to the app-tile child component using attributes. Option B is incorrect because it uses an invalid syntax for the for:each directive. The for:each directive requires a colon (:)after the for keyword, not an equal sign (=). Option C is incorrect because it uses an invalid syntax for the for:each directive. The for:each directive requires an item alias that represents the current item in the iteration, not a key alias that represents the current index in the iteration. Option D is incorrect because it uses an invalid syntax for the template tag. The template tag requires a closing tag (</template>), not a self-closing tag (<template/>). Salesforce References: Lightning Web Components Developer Guide: Iterate Over a Collection, Lightning Web Components Developer Guide: Template Syntax

A Lightning Web Component can contain an Aura component, and an Aura component can contain a Lightning Web Component. This interoperability allows for a smoother transition from Aura to LWC and enables developers to utilize the strengths of both frameworks. However, nesting a Lightning Web Component within an Aura component which in turn contains a Lightning Web Component (Option C) is not a standard practice. For more information, refer to the Salesforce documentation on using Aura and Lightning Web Components together:Salesforce Aura and LWC Interoperability Documentation.

A method to resolve if the current storefront customer is a Salesforce B2B Commerce guest user in an apex class is to use ccrz.cc_CallContext.isGuest. This property will return true if the current user is a guest user, or false otherwise. For example, if(ccrz.cc_CallContext.isGuest){ // do something for guest user } will execute some logic only for guest users. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Call Context

Three advantages of using ccLog over the Salesforce standard System.debug class are:

There is no need to use string concatenation to easily tag log statements with asubject. ccLog allows passing a subject parameter to the log method, which will prepend the subject to the log message. For example, ccLog.log('This is a message', 'Subject') will log [Subject] This is a message.

There is no need to create a User Trace Flag. ccLog can be enabled by setting the value of CO.logToken to true in CCAdmin, which will activate logging for all users who access the storefront.

There is no need to manually set a cookie to debug with the Site Guest User. ccLog can be enabled for the Site Guest User by appending #ccLog= to the end of the storefront URL in order to get logs in the inspector console. For example, https://my-storefront.com/#ccLog=debug  will enable logging for the Site Guest User with the debug level. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Logging

The handlebars helper expression that is used in Salesforce B2B Commerce pages and components to toggle the display of a block of markup is {{#ifConfig ‘Field__c’}} … {{/ifConfig}}. This expression will evaluate the value of the configuration setting with the API name Field__c and render the block of markup if the value is true, or skip it if the value is false. For example, {{#ifConfig 'CO.showMiniCart'}}

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 isa 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 tothe 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 aprice 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]