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

The Priority field that determines the priority of pricing is on the Buyer Group Price Book object.The Buyer Group Price Book object is a junction object that links a buyer group to a price book1,5.It has a Priority field that indicates the order in which price books are applied to a buyer group1,5.A priority pricing model is a way of assigning different price books to different buyer groups based on their priority level1, .The lower the priority number, the higher the precedence of the price book1, .Reference:Salesforce Accredited B2B Commerce Administrator Exam Guide, Buyer Group Price Book Object, Priority Pricing Model

Two likely causes of not producing an expected number of hits on the part numbers entered are: part number values can change with each variation product, and the part number value is in a formula field that uses other field values.A variation product is a product that has different variations based on attributes, such as color or size1, [12].A part number is a unique identifier for a product or a variation product1, [13]. If part number values can change with each variation product, then searching for a part number may not return all the relevant results, because some variation products may have different part numbers than their parent products. If the part number value is in a formula field that uses other field values, then searching for a part number may not return any results, because formula fields are not searchable by default.Reference:Salesforce Accredited B2B Commerce Administrator Exam Guide, Product Variations and Attributes, Part Number Field, Formula Field Considerations

To implement the products for a company that sells t-shirts that come in multiple sizes and colors, an administrator should take two steps: create product variations and create a t-shirt parent product. A product variation is a product that has different variations based on attributes, such as size or color. A t-shirt parent product is a product that groups together all the t-shirt variations that share the same attributes. An administrator can use the Product Workbench to create product variations and t-shirt parent products for a store.Reference:Product Variations and Attributes;Product Workbench

To add a B2B store to a site that already exists, an administrator should meet two conditions: the existing site should use the Build your own (Aura), Customer Portal, or B2B template and the site should not have a store created. These are the prerequisites for adding a store to an existing site using the Store Administration workspace. The existing site should not use the Microsite (LWR) template, as it does not support adding a store. The site should not already have a store created, as only one store can be added per site.Reference:Add a Store to an Existing Site

To migrate the store configurations from the development sandbox to the QA sandbox, an administrator should take two steps: export store configuration and apply store configuration. Exporting store configuration creates a JSON file that contains all the store settings, such as name, URL, catalog, price book, etc. Applying store configuration imports the JSON file to another sandbox and updates the store settings accordingly.Reference:Export Store Configuration;Apply Store Configuration

To create a content collection that automatically updates when new content is added, an administrator should take two steps: create a dynamic content collection and create criteria rules to filter content. A dynamic content collection is a collection that automatically includes content based on criteria rules, such as content type, tag, category, etc. A criteria rule is a rule that defines how to filter content for a dynamic content collection based on one or more conditions.Reference:Dynamic Content Collections;Criteria Rules

The two types of data that are supported by the Multilevel Navigation Menu component in B2B Commerce are system link and data source. A system link is a link that points to a predefined page or action on the storefront, such as home page, cart page, login page, etc. A data source is a link that points to a custom page or external URL on the storefront, such as a landing page, a blog page, etc.Reference:Multilevel Navigation Menu Component

To override the tax calculation logic in B2B Commerce for Visualforce, a developer must implement the sfdc.commerce.CheckoutTaxCalculations interface. This interface defines two methods: calculateTax and calculateTaxForCart. The calculateTax method takes a CC Cart Delivery Group Method record as an input and returns a CC Cart Item record of type Tax. The calculateTaxForCart method takes a CC Cart record as an input and returns a list of CC Cart Item records of type Tax. These methods are invoked by the B2B Commerce for Visualforce framework during checkout to calculate the tax amount for each cart delivery group and the entire cart respectively.Reference:Add a Tax Calculation Service,Calculate Tax at Checkout, B2B Commerce for Visualforce Developer Guide

When a shipping integration is enabled in B2B Commerce for Visualforce, the cart delivery group method record is used to store the selected shipping method for each cart delivery group. After the shipping integration returns the shipping cost for each cart delivery group, a cart item record of type Shipping is created with the cart delivery group method record as its parent. This cart item record represents the shipping charge for the corresponding cart delivery group and is displayed in the order review section of the checkout page.Reference:Specify Shipping Group Options for LLI Checkout,Specify Shipping Options for Standard Checkout,CartDeliveryGroupMethod