Salesforce Certified B2B Commerce Administrator Practice Test - Questions Answers, Page 2

The correct answer is C. import id from '@salesforce/experience/Id' because this is the syntax for importing information about the current Experience Builder site from the @salesforce/experience scoped module.The id property returns the ID of the current site1. The other options are incorrect because they use different scoped modules or properties that do not exist or do not return the site ID.Reference:Current Community

Lightning Out because this is a technique that allows developers to use Lightning web components outside of Salesforce servers, such as in a Node.js app running on Heroku or a department server inside the firewall2.Lightning Out uses a standalone Aura dependency app to host the Lightning web components and expose them to an external web container2. The other options are incorrect because they are not techniques for exposing Lightning web components outside of an org.Slot elements are a way to create reusable components with dynamic content3.Heroku is a cloud platform that supports various languages and frameworks, but it does not directly expose Lightning web components4.Lightning Canvas is a framework that enables developers to integrate third-party applications into Salesforce5, but it does not support Lightning web components6.Reference:Use Components Outside Salesforce,Slot Elements,Heroku,Lightning Canvas Developer's Guide,Lightning Web Components in Visualforce, Aura, and Lightning Out

According to theCheckout Flowpage, checkout flow is a feature that allows you to customize the steps and actions that occur when a user places an order on your B2B Commerce site. Checkout flow is a type of flow that can be created or modified using Flow Builder in Salesforce Setup. To create a checkout flow from scratch or from an existing template, you need to do the following steps:

Navigate to Flow Builder in Salesforce Setup.

Click New Flow or Open a Template.

Select Checkout Flow as the flow type.

Add or edit elements for each step of your checkout process.

Save your flow with a unique name and description.

Activate your flowso that it can be used on your B2B Commerce site. Therefore, option C is correct.

Option A is false because changing the permission on the existing checkout flow is not a step that needs to be done after cloning and saving the out-of-box checkout flow template before it can be used. The permission on the existing checkout flow template is already set to system context with sharing-enforces record level access by default and does not need to be changed.

Option B is false because renaming the existing checkout flow in place is not a step that needs to be done after cloning and saving the out-of-box checkout flow template before it can be used. Renaming the existing checkout flow template would overwrite the original template and prevent you from using it again. You should clone the existing checkout flow template and save it with a new name instead.

Option D is false because adding a version letter is not a step that needs to be done after cloning and saving the out-of-box checkout flow template before it can be used. Adding a version letter is an optional step that can help you keep track of the changes you make to your checkout flow over time, but it is not required for using your checkout flow on your B2B Commerce site.Reference:Checkout Flow, Checkout Flow Overview

According to theCheckout Flowpage, checkout flow is a feature that allows you to customize the steps and actions that occur when a user places an order on your B2B Commerce site. Checkout flow is a type of flow that runs in the system context with sharing-enforces record level access. System context with sharing-enforces record level access means that the flow runs with the permissions of the Salesforce system user but respects the sharing rules of your org. This ensures that the flow can access all the necessary data and functionality for checkout but also respects the security and visibility settings of your org. One of the reasons why system context with sharing-enforces record level access is important to B2B Commerce is that it is required to check out. Checking out is the final step of the checkout process where the user confirms their order details, payment method, shipping address, and shipping method. To check out, the flow needs to run in system context with sharing-enforces record level access so that it can create an order record, update the cart status, send an order confirmation email, and perform any other actions that are configured for checkout. Therefore, option A is correct. Options B, C, and D are false because system context with sharing-enforces record level access is not required for guest browsing, synchronizing content, or viewing products in the storefront. Guest browsing is a feature that allows anonymous users to browse your site without logging in or creating an account. Synchronizing content is a feature that allows you to sync content assets between Salesforce CMS and B2B Commerce. Viewing products in the storefront is a feature that allows users to see the products that are available for purchase on your site.Reference:Checkout Flow, Checkout Flow Overview

According to the [Order Confirmation Email] page, order confirmation email is a feature that allows you to send an email notification to buyers when they place an order on your B2B Commerce site. Order confirmation email can be configured using Process Builder and Email Alerts in Salesforce Setup. To configure order confirmation email, you need to do the following steps:

Create an email template that contains the information and format that you want to use for your order confirmation email. You can use merge fields to include dynamic data from your order records, such as order number, order date, order total, etc.

Set up organization-wide addresses that specify the email address and display name that you want to use as the sender of your order confirmation email. You can use different organization-wide addresses for different stores or reorder portals.

Create an email alert that defines the email template, organization-wide address, recipient type, and recipient field that you want to use for your order confirmation email. You can use different email alerts for different stores or reorder portals.

Add an auto-launched flow that triggers when an order is created or updated and has a status of Submitted. The flow should include a Send Email element that references the email alert that you created for your order confirmation email. Therefore, option C is correct. Options A, B, and D are false because they are not configuration steps that are required to send order confirmation emails to buyers. Creating a trigger on order creation, implementing the SendOrderConfirmation interface from Apex code, locating the existing 'Send Order Confirmation Email' sub-flow, adding it to the last step, and checking the box called 'Send order confirmation Email to buyer' in the Commerce Apps store Administration are alternative or outdated methods that are not recommended or supported for sending order confirmation emails to buyers.Reference:[Order Confirmation Email], Order Confirmation Email Overview

According to theProduct Categoriespage, product categories are collections of products that are grouped together based on common characteristics, such as type, function, style, etc. Product categories can be used to organize your products and make them easier to find and browse on your B2B Commerce site. To categorize a variant product, you need to assign the variant's parent product directly to the category. A variant product is a product that has different versions or options, such as size, color, style, etc. A variant product has a parent product and a basic product. A parent product is a product that contains all the variation attributes and variation groups for a variant product. A basic product is a product that contains the common attributes and specifications for a variant product. Therefore, option C is correct. Options A, B, and D are false because assigning the variant product, the variant's basic product, or the variant's expanded product to the category will not categorize the variant product correctly. An expanded product is a product that contains all the attributes, specifications, images, and prices for a specific variation of a variant product.Reference:Product Categories, Product Categories Overview

According to theSearchable Fieldspage, searchable fields are fields on the Product object that can be used as filters or facets for search results on your B2B Commerce site. Searchable fields can help users narrow down their search results and find the products that match their criteria. Three of the field types that an administrator can set as searchable fields for search are text, picklist, and picklist (multi-select). Text field type allows users to enter any alphanumeric characters as search terms. Picklist field type allows users to select one value from a predefined list of values as a search term. Picklist (multi-select) field type allows users to select multiple values from a predefined list of values as search terms. Therefore, options B, D, and E are correct. Options A and C are false because currency and checkbox are not field types that an administrator can set as searchable fields for search. Currency field type allows users to enter numeric values with decimal places and currency symbols as search terms. Checkbox field type allows users to select true or false values as search terms.Reference:Searchable Fields, Searchable Fields Overview

According to theSearchable Fieldspage, searchable fields are fields on the Product object that can be used as filters or facets for search results on your B2B Commerce site. Searchable fields can help users narrow down their search results and find the products that match their criteria. Three of the field types that an administrator can set as searchable fields for search are picklist (multi-select), picklist, and checkbox. Picklist (multi-select) field type allows users to select multiple values from a predefined list of values as search terms. Picklist field type allows users to select one value from a predefined list of values as a search term. Checkbox field type allows users to select true or false values as search terms. Therefore, options A, B, and E are correct. Options C and D are false because date and geolocation are not field types that an administrator can set as searchable fields for search. Date field type allows users to enter date values in a specific format as search terms. Geolocation field type allows users to enter latitude and longitude values as search terms.Reference:Searchable Fields, Searchable Fields Overview

There are a few reasons why a Salesforce B2B Commerce Community User may not see entitled Products after authenticating to the storefront:

Account Group of user's Account does not have any Price lists associated to it.In order for a user to see entitled Products, their Account Group must have at least one Price List associated to it.

Entitled pricelists are associated to a different community.If the user's Account Group is associated to a different community than the Price Lists that they are entitled to, they will not be able to see those Products.

Products in the pricelists are marked 'in Creation' Status.Products that are in Creation status are not yet available for purchase, and therefore will not be visible to users.