Which two places can the administrator go to set up variation products using the B2B commerce apps navigation menu?
Answer(s): A,D
According to the Product Variations and Attributes page, product variations and attributes are features that allow you to create and manage products that have different versions or options, such as size, color, style, etc. Product variations and attributes can be set up using the B2B Commerce app navigation menu in two places: Products and Product Workspace. Products option allows you to access the product list view, where you can create, edit, delete, clone, or import/export products. Product Workspace option allows you to access the product workspace, where you can view and edit product details, such as name, description, status, visibility, category, image, etc. You can also add product variations and attributes in the product workspace by using the Variation Grouping tab or the Guided Setup tab. Therefore, options A and D are correct. Options B, C, and E are false because Commerce Setup, Entitlement Policies, and Catalogs are not places where you can set up product variations and attributes using the B2B Commerce app navigation menu. Commerce Setup option allows you to install components for your B2B Commerce site, such as reports, dashboards, sample data, etc. Entitlement Policies option allows you to manage entitlement policies for your B2B Commerce site, such as minimum order quantity, maximum order quantity, reorder frequency, etc. Catalogs option allows you to manage catalogs and catalog assignments for your B2B Commerce site. Catalogs are collections of products that are available for a store or a reorder portal.
Product Variations and Attributes, Product Variations and Attributes Overview
In which context does a checkout flow need to run?
Answer(s): B
According to the Checkout Flow page, 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. Therefore, option B is correct. Options A, C, and D are false because they are not the context in which a checkout flow needs to run. System context without sharing- enforces record level access means that the flow runs with the permissions of the Salesforce system user but ignores the sharing rules of your org. This could result in data leakage or unauthorized access during checkout. System context without sharing-access all data means that the flow runs with the permissions of the Salesforce system user and has access to all data in your org regardless of sharing rules or field-level security. This could result in data leakage or unauthorized access during checkout. User or system context-depends on how flow is launched means that the flow runs with either the permissions of the user who launched it or the permissions of the Salesforce system user depending on how it was triggered. This could result in inconsistent or unpredictable behavior during checkout.
Checkout Flow, Checkout Flow Overview
What needs to be done after cloning and saving the out-of-box checkout flow template before it can be used?
Answer(s): C
According to the Checkout Flow page, 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 flow so 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.
Why is the System context with Sharing-Enforces Record Level Accessimportant to B2B Commerce?
Answer(s): A
According to the Checkout Flow page, 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.
What configuration steps are required to send Order confirmation emails to Buyers?
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 SalesforceSetup. 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.
[Order Confirmation Email], Order Confirmation Email Overview
Post your Comments and Discuss Salesforce B2B-COMMERCE-ADMINISTRATOR exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the B2B-COMMERCE-ADMINISTRATOR content, but please register or login to continue.