Free Practice Questions for Salesforce B2B-Commerce-Developer Exam

Custom labels are text values that can be translated into any language that Salesforce supports. They are useful for displaying language-specific text in Lightning web components. To use custom labels in a LWC, the developer needs to create them in the Setup menu and assign them to a language and a value. Then, the developer can import them in the LWC using the @salesforce/label scoped module. For example, if the developer has a custom label named welcomeHeader, they can import it as follows:

import welcomeHeader from'@salesforce/label/c.welcomeHeader';

Then, they can use it in the HTML template or the JavaScript file of the LWC. For example, in the HTML template, they can use it as follows:

HTMLAI-generated code. Review and use carefully. More info on FAQ.

The custom label will automatically display the translated value based on the user’s language preference. The developer can also use the lightning-formatted-text component to format the custom label value with HTML tags.

The other options are not correct because:

A. Importing static resources for the text values is not a recommended way to translate text values in a LWC. Static resources are files that are stored in Salesforce and can be referenced by applications. They are not designed for storing language-specific text values and they do not support automatic translation based on the user’s language preference.

B. Using a CustomLabel xml file in the LWC to add the text values there is not a valid option. Custom labels are not stored in xml files, but in the Setup menu. They cannot be added directly to the LWC, but they need to be imported using the @salesforce/label scoped module.

D. Creating acustom Metadata object for the text values and querying it in the LWC is not a feasible option. Custom Metadata objects are records that store configuration data that can be deployed and packaged. They are not intended for storing language-specific text values and they do not support automatic translation based on the user’s language preference. Querying them in the LWC would also require an Apex class and a wire service, which would add unnecessary complexity to the solution.

References:

Use Custom Labels in Lightning Web Components

Custom Labels

Internationalizing Your Lightning Web Component (LWC)

To introduce new screenbehavior in a checkout flow step, a developer should clone the appropriate subflow and replace the Lightning web components in it. A subflow is a reusable flow that can be invoked from another flow as an element. A checkout flow is a flow that defines thesteps and components for the checkout process in the storefront. A checkout flow consists of several subflows, each of which corresponds to a checkout step, such as Cart, Shipping Address, Payment, or Order Summary. To introduce new screen behavior in a checkout flow step, a developer should clone the subflow that matches the checkout step they want to modify and replace the Lightning web components in the cloned subflow with their custom components. The developer can then update the checkoutSteps.xml fileto point to the cloned subflow instead of the original subflow. Modifying the property mappings in checkoutSteps.xml is not a valid way to introduce new screen behavior in a checkout flow step, as it only affects how data is passed between subflows, not how screens are displayed or rendered. Editing the default subflow directly is not a valid way either, as it can cause conflicts or errors with other stores or environments that use the same default subflow. Adjusting next-state in previous subflow configuration is not a valid way either, as it only affects how subflows are transitioned or navigated, not how screens are displayed or rendered. Salesforce References: B2B Commerce Developer Guide: Checkout Flow, B2B Commerce Developer Guide: Checkout Subflows, B2B Commerce Developer Guide: Customize Checkout Steps

To enable the ability to add new shipping and billing addresses during checkout, a developer should enable Buyer Managed Contact Point Addresses within the Shipping Address standard component in the Checkout subflow. The Buyer Managed Contact Point Addresses is a feature that allows customers to add, edit, or delete their shipping andbilling addresses during checkout. The developer can enable this feature by setting the buyerManagedContactPointAddressesEnabled attribute to true in the Shipping Address standard component in the Checkout subflow.The Shipping Address standard component is a component that displays and collects the shipping address information for the cart or order. The Checkout subflow is a subflow that defines the steps and components for the checkout process in the storefront. Creating a new shipping address checkout subflow that utilizes the Buyer Managed Contact Point Addresses component is not a valid way to enable this feature, as there is no such component as Buyer Managed Contact Point Addresses. Enabling Buyer Managed Contact Point Addresses within Commerce Administration is not a valid way either, as this feature is not configurable in Commerce Administration. Creating a Lightning web component that enables this functionality and replaces the current shipping address screen within the Checkout subflow is not a valid way either, as this is unnecessary and complicated when there is already a standard component that supports this feature. Salesforce References: [B2B Commerce Developer Guide: Buyer Managed Contact Point Addresses], [B2B Commerce Developer Guide: Shipping Address Component], [B2B Commerce Developer Guide: Checkout Subflow]

The difference between Gross Layout Overrides and Subscriber Templates is that Subscriber Templates allow for modification of the header and the footer, while Gross Layout Overrides allow for modification everything inside the header and footer. Subscriber Templates are custom Visualforce pages that can replace the standard header and footer components on a page. Gross Layout Overrides are custom Visualforce pages that can replace the default layout of a page, such as the number of columns, the position of widgets, or the content of sections. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Subscriber Templates, Gross Layout Overrides

 A developer has written the logic to import products from an enterprise resource planning(ERP) platform into B2B storefront products. The imported products are in Salesforce, but they are not visible in the store. The developer forgot to assign the storefront to the imported products. A storefront is a logical grouping of products, categories, and price books that defines what products are available for purchase in a B2B Commerce site1. A product must be associated with at least one storefront to be visible in the store2. The developer can use the Data Loader to insert or update the storefront assignments for the imported products3.

Option A, Option C, and Option D are incorrect because they are not required for the products to be visible in the store. An entitlement policy is a set of rules that determines the availability of products based on the buyer’s account, contract, or order history4. An account is a record that represents a business or person involved in a business transaction. A promotion is a marketing tool that offers discounts or incentives to buyers. These are optional features that can be used to customize the B2B Commerce experience, but they are not necessary for the products to be visible in the store. References:

Storefronts

Product Visibility

Insert new Products and custom Price Books via Data Loader

Entitlement Policies

[Accounts]

[Promotions]

Handlebar Templates are defined in the uiProperties file in the cloudcraze managed package. This file contains various properties that control the behavior and appearance of the user interface components. The handlebarTemplates property defines a map of template names and template contents that are used by the handlebars.js templating engine to generate HTML from JSON data. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, UI Properties, Handlebars Templates

To implement specific styling for a standard component on a single page of the B2B Commerce store using an Aura template, a developer should create a custom theme layout Aura component that imports the custom CSS file and set up the page to use this theme layout. A theme layout is a type of Aura component that defines the header and footer of a page in the storefront. Atheme layout can also import custom CSS files from static resources and apply them to the page. A developer can create a custom theme layout Aura component that imports the custom CSS file that contains the specific styling for the standard component and assign it to the page that needs the custom styling. This way, the custom styling will only affect the standard component on that page and not on other pages that use a different theme layout. Using a custom CSS file in a static resource and adding the import using the Edit Head Markup Editor in the Experience Builder is not a valid way to implement specific styling for a standard component on a single page, as it will affect all pages that use the same template. Creating a custom content layout Lightning web component that imports the custom CSS file and setting up the page to use this content layout is not a valid way either, as it will not affect the standard component that is outside of the content layout. Using the Override CSR Editor in the Experience Builder and adding the desired CSS to change the styles is not a valid way either, as it will affect all pages that use the same template. Salesforce References: B2B Commerce Developer Guide: Theme Layout Component, B2B Commerce Developer Guide: Content Layout Component, B2B Commerce Developer Guide: Override CSR Editor

The correct syntax to render a property in a Lightning webcomponent template is to surround the property with curly braces: {property}. This syntax allows you to access the property value from the JavaScript class of the component and display it in the HTML template. The other options are incorrect because they either use invalid characters or do not follow the standard syntax for rendering a property in a Lightning web component template. References: Use JavaScript Properties in Templates | Lightning Web Components Developer Guide

Two Salesforce B2B Commerce Visualforce pages that must be enabled at a Salesforce Community level to make the out of the box SEO functionality available are:

CCSizeIndex: This page generates a sitemap.xml file, which is a file that lists all the pages and resources on a site that can be crawled by web crawlers. The page uses the configuration settings CO.SiteMapIncludeProducts and CO.SiteMapIncludeCategories to specify which products and categories shouldbe included in the sitemap.

CCCatSiteMap: This page generates a category sitemap file, which is a file that lists all the categories on a site that can be crawled by web crawlers. The page uses the configuration setting CO.SiteMapCategoryDepth to specifyhow many levels of subcategories should be included in the category sitemap. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Sitemap Files