Salesforce Certified B2B Commerce Administrator Practice Test - Questions Answers

According to theProduct Variations and Attributespage, 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.Reference:Product Variations and Attributes, Product Variations and Attributes 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. 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.Reference:Checkout Flow, Checkout Flow Overview

To set up a storefront from scratch, the developer can use the sfdx commerce:store:quickstart:setup command, which performs all the necessary steps to create a storefront, push store sources, create buyer users, import products, and create and search index. The command requires a definition file that specifies the store name, template name, and other parameters. For example, a store-scratch-def.json file could look like this:

{ ''storeName'': ''test-store'', ''templateName'': ''b2c-lite-storefront'', ''orgName'': ''Test Org'', ''edition'': ''Developer'', ''features'': [''Communities'', ''B2BCommerce''], ''settings'': { ''communitiesSettings'': { ''enableNetworksEnabled'': true } } }

The developer can then run the command as follows:

sfdx commerce:store:quickstart:setup ---definitionfile store-scratch-def.json

This will create a test-store storefront using the b2c-lite-storefront template in a scratch org named Test Org with Developer edition and B2B Commerce features enabled. The other options are not correct because:

sfdx commerce:store:quickstart:create -templatename 'b2c-lite-storefront' is an invalid command. There is no quickstart:create command in sfdx commerce:store.

sfdx commerce:store:create ---store-name test-store is a valid command, but it only creates a storefront with a default template. It does not push store sources, create buyer users, import products, or create and search index.

sfdx commerce:store:open ---store-name test-store is a valid command, but it only opens an existing storefront in a web browser. It does not set up a storefront from scratch

One possible reason for the custom fields in the Order Summary to be empty in the export file is that the developer does not have access to the fields. Data Loader respects the sharing and security settings of Salesforce objects and fields. Therefore, if the developer does not have access to view or edit the custom fields in the Cart and Order Summary objects based on their profile or role permissions, the fields will not be included in the export file. The other options are not likely causes because:

A misspelling in one of the custom fields would not affect the mapping from Cart to Order Summary or the export of Order Summary data. It would only affect the display of the field label or API name.

The Cart to Order action does support the mapping of custom fields as long as certain patterns are followed.To be automatically mapped, the custom field needs to exist in the Cart, Order and OrderSummary objects and have the same API name, supported data type and field configuration1.

The developer can export Order Summary records by using Data Loader or Data Export Service. Data Loader is a client application that can export data for one or more standard or custom objects. Data Export Service is a web-based tool that can export data for all objects in an org on a weekly or monthly basis.

One product feature that could allow NTO to reference historical data in another system from the Salesforce user experience as read-only, without importing the data into the org or incurring storage costs, is External Objects. External Objects are similar to custom objects, except that they map to data that's stored outside your Salesforce org. External Objects let you access data from external sources in real time via web service callouts. You can use External Objects to integrate Salesforce with other systems and create relationships with other Salesforce objects. You can also use standard Salesforce features such as global search, lookup relationships, reports, and dashboards with External Objects. The other options are not correct because:

Big Objects are a type of custom object that can store and manage massive amounts of data on the Salesforce platform. Big Objects do not reference external data sources, but rather store data within the org. Big Objects also incur storage costs based on the number of records and fields.

Lightning Out is a feature that lets you run Lightning components outside of a Lightning Experience container. Lightning Out does not reference external data sources, but rather embeds Lightning components into other web pages or apps.

External SOQL queries in Apex code are a way to query external data sources using SOQL syntax. External SOQL queries do not reference historical data from another system, but rather current data from a connected app. External SOQL queries also require importing data into the org via Apex code.

Commerce Product Data Import is a tool that allows developers to import product data from a CSV file into the B2B Commerce Cloud platform. It supports importing data for related objects, such as ProductCatalog, ProductCategory, Product2, and ProductCategoryProduct, while preserving their relationships. It also supports scheduling the import process to run at a specified time or frequency, which can be useful for demo purposes. Commerce Product Data Import does not require any additional licenses or third-party tools to use.Reference:

Import Products

Commerce Product Data Import

To check user permissions in Lightning web components, a developer can import two scoped modules: @salesforce/customPermission and @salesforce/hasPermission. The @salesforce/customPermission module allows the developer to access the custom permissions assigned to the current user. The @salesforce/hasPermission module allows the developer to check if the current user has a specific permission, such as View Setup or Customize Application. These modules can be used to conditionally render or enable components based on the user's permissions.Reference:

[Check User Permissions in Lightning Web Components]

[Custom Permissions]

[User Permissions and Access]

The correct answer is B. this.template.addEventListener('notification', this.handleNotification); because the event listener needs to be created on the parent component programmatically. The event listener should be added to the template of the parent component, and the event type should be 'notification'. The event listener should also have a callback function, which is handleNotification in this case.Reference: [Create a Lightning Web Component]

The connectedCallback is a lifecycle hook in Lightning web component. It fires when a component is inserted into the DOM. It runs once when the component is inserted. connectedCallback in Lightning Web Component flows from parent to child.It can be used to perform actions such as initializing variables, fetching data, or setting event listeners1.Reference:connectedCallback() and disconnectedCallback(),connectedCallback() in Lightning Web Component,What is connectedCallback in LWC?