B2B-Commerce-Administrator Salesforce Accredited B2B Commerce Administrator(SP23) Questions and Answers

If the checkout process fails in the B2B store after adding the promotions subflow to the checkout flow template, the two possible reasons could beA. A new version of the checkout flow template has not been activated, meaning the changes have not been applied; andB. The Checkout page on the Experience Builder site is currently configured to run a different Checkout flow template, which does not include the promotions subflow.

An Administrator can configure an alternative or new checkout flow in theStore tile in the Commerce app (C). This area provides access to store configurations, including checkout process customizations. The Commerce app's Store tile allows administrators to define and manage various aspects of the checkout experience, such as payment options, order review, and final confirmation steps, ensuring a seamless and efficient checkout process for users. TheCheckout Button on the Cart page (A),Experience Builder on the Checkout page (B), andProcess Builder Button in Experience Builder (D)are not the primary locations for configuring the checkout flow in Salesforce B2B Commerce.

To safely authorize a payment gateway, an Administrator needs toB. Create a Named Credentialin Salesforce Setup. Named Credentials provide a secure way of storing authentication details, including endpoint URLs, usernames, passwords, and token endpoints, which are essential for securely connecting to external payment gateway APIs.

To configure the store to use a new payment gateway, an Administrator needs toUpdate the payment gateway settings on the Payment and Billing subflow (A). This involves configuring the new gateway's details and parameters within the relevant settings, ensuring that the store's payment processing is correctly aligned with the new gateway.

If an Administrator is having trouble rebuilding the search index, a potential cause could bethe necessary permissions have not been given to the Administrator (A). Proper permissions are required to execute search index rebuilds, and without these permissions, the Administrator may encounter difficulties in initiating or completing the rebuild process.

Before the checkout flow is usable, the following two tasks need to be completed:A. Configure the Checkout flow in Flow Builder, which involves setting up the logic and steps for the checkout process; andD. Add the checkout flow to the Checkout Page in Experience Builder, which integrates the configured flow into the actual checkout page that users interact with during the purchasing process.

To defend against session hijacking and cross-site scripting in Salesforce B2B Commerce, an administrator should enableB. Require HttpOnlysetting. This setting helps prevent access to cookie data via client-side scripts, significantly reducing the risk of XSS (Cross-Site Scripting) attacks and protecting session cookies from being hijacked.

When implementing a category hierarchy for a multi-language site with many child categories, an important consideration isC. There is a depth limit for the number of child categories.Salesforce B2B Commerce imposes limits on the depth of the category hierarchy, affecting how deeply nested child categories can be structured within the overall category architecture.

Within the Commerce app, the two workspaces available areProduct (A)andContent Management (E). The Product workspace is dedicated to managing product catalogs, details,and variations, providing tools for Administrators to curate and organize their product offerings. Content Management is a workspace focused on the creation, management, and deployment of content across the commerce site, including marketing materials, informational content, and other web content. While Search (B), Commerce Reports (C), and Pricing (D) are critical aspects of B2B Commerce, they are typically managed through other sections or setups rather than being categorized as separate workspaces within the Commerce app.

To create personalized experiences for different groups of buyers, an Administrator can use the following criteria types to create audiences for a component on a Store page:

• B. Permission Set:This allows for content personalization based on the permissions granted to the user, enabling targeted content delivery.
• C. Profile:Users with different profiles can be presented with tailored content, ensuring relevance and enhancing the user experience.
• E. User's Location:Personalizing content based on the user's geographical location can significantly improve relevance and engagement.

To add a B2B store to an existing site, two conditions required areA. The existing site should use the Build your own (Aura), Customer Portal, or B2B template, ensuring compatibility with B2B Commerce functionalities, andD. The site should not have a store created, as each site can typically support one B2B store.

To ensure customers can only purchase products in increments of five, an Administrator must complete the following steps:B. Create Purchase Quantity RulesandC. Connect the product to a Quantity Rule. Purchase Quantity Rules define the increments in which products can be purchased, and connecting these rules to specific products enforces the desired purchasing increments.

Using Experience Builder, an Administrator can update theCustomer's Logo (B),Button Size (C), andText Color (D)to change the look and feel of the theme of their B2B Commerce site. These options allow for significant customization of the visual aspects of the site, aligning the design with the company's branding and design preferences.

To ensure content collections automatically update with new content, an administrator should:

• A. Create Content Rule records and associate them to a collection:Content Rules define criteria for content inclusion, ensuring that new content meeting these criteria is automatically added to the collection.
• B. Create a Dynamic Content Collection:Unlike static collections, dynamic collections automatically update based on predefined rules or criteria, ensuring the collection stays current with the latest content without manual intervention.

This setup allows for a more dynamic and responsive content management approach, where collections reflect the most current content relevant to the defined criteria, enhancing the user experience and content relevance.

The field type that cannot be added as a Searchable field isC. Formula. Formula fields are calculated fields that do not store data themselves but rather display data based on the formula's logic and the values of other fields. Due to their dynamic nature and lack of stored data, they cannot be indexed or made searchable like other static field types.

To move the B2B store configuration from a sandbox to a production environment, an Administrator shouldA. Add the Store Configuration to a change setandC. Export the store settings with Data Loader. The change set allows for the transfer of configuration settings, while the Data Loader can be used to migrate data related to the store setup, ensuring a smooth transition to the production environment.

To set up Tiered Pricing for a product, an administrator needs to configureA. Price Adjustment Schedules. This functionality allows for the creation of pricing tiers that apply different discounts based on the quantity of items purchased, enabling volume-based pricing strategies.

By enabling Commerce in Setup, the object added to the data model isB. Store. The Store object is a fundamental component of Salesforce B2B Commerce, representing the digital storefront where products and services are offered to customers. It serves as the central entity around which various commerce functionalities are configured and managed.

Out of the box, an Administrator can control the following aspects of the search settings:

• A. Sort Rules:These determine the order in which search results are displayed.
• B. Results per Page:This setting controls how many results are shown to the user at one time, impacting the browsing experience.
• E. Scheduled Indexing:This allows for the automatic rebuilding of the search index at scheduled intervals, ensuring the search functionality reflects the most up-to-date information.

These settings are crucial for optimizing the search experience, ensuring that users can find what they need efficiently and effectively.

When turning on Digital Experiences during B2B Commerce setup, two potential risks includeDigital Experiences extending portal access to external members (A)andthe possibility of external members having permissions to view records they should not be able to view (B). Proper configuration and management of access rights and permissions are crucial to mitigate these risks, ensuring that external members only have access to appropriate information and functionalities.

An administrator should activate person accounts in a B2B Commerce org forA. To set up B2B2C Commerce in an existing B2B Commerce org, allowing the organization to cater to both business and individual consumers, andD. To enable individual buyers, providing a more tailored shopping experience for solo entrepreneurs or individual purchasers.

To deploy and activate the full B2B Commerce experience for internal and external users, the three configuration aspects that must be set up outside the Commerce App includeB. Experience Sites, which involves configuring the digital experience platforms for users;C. Multi-Factor Authentication, which is a security measure to verify user identities; andD. Profiles and Permission Sets, which are essential for defining access controls and permissions for different types of users within the system.

Through the Commerce App's Import feature, an Administrator can populate:

• A. Images:Product images can be imported to visually represent each product.
• B. Price Book:This includes importing pricing information associated with each product, allowing for accurate pricing display and calculations within the commerce site.
• D. Description:Product descriptions provide detailed information about each product, which can be imported to enrich product listings and inform potential buyers.

This import functionality streamlines the process of populating product catalogs with essential information, ensuring a comprehensive and informative shopping experience for customers.

The Multilevel Navigation Menu Component in B2B Commerce supportsSystem Link (A)andExternal URL (C)as types of data. System Links are used to navigate within the B2B Commerce application, facilitating a seamless user experience by linking to internal pages or resources. External URLs allow the integration of links to external websites, which can be crucial for providing additional product information, manufacturer details, or external resources.Data Source (B)andEvent (D)are not typically supported by the navigation menu component as they serve different purposes in the context of B2B Commerce.

To meet the requirement that all orders over a certain amount be paid for using a credit card instead of a purchase order, the Administrator should start withB. Add decision logic to hide the option for purchase orders on orders that meet the criteria. This approach involves configuring the checkout flow to dynamically adjust the available payment options based on the order amount, ensuring compliance with the specified payment policy.

To target CMS content at a particular store, an Administrator needs toB. Create CMS content and assign it in Experience Builder. This involves creating content within the CMS workspace and then using Experience Builder to place and assign this content to specific pages or components within the store, ensuring it appears in the desired location.

For Buyer Managers on the storefront, the appropriate profile or permission set is typicallyB2B Commerce User (D). This profile or permission set is designed to provide the necessary permissions for users to perform tasks related to managing purchases, viewing orders, and accessing account-specific pricing and products. The B2B Commerce User role encompasses the functionalities needed by Buyer Managers to efficiently manage their purchasing activities within the B2B Commerce environment.

The limit on the category hierarchy in terms of child records in B2B Commerce isC. 5.0. This means that within the category structure, a parent category can have up to five levels of child categories beneath it. This hierarchical structure allows for organizing products into categories and subcategories, providing a clear and navigable structure for users.

When moving a store from Sandbox to Production, the three components an Administrator needs to consider as part of the Change Sets includeB. Store Configuration Component, which contains the store's setup and configuration settings;C. Custom Objects and Fields, which are used to extend the functionality and store custom data; andE. Process Builder Flows, which automate business processes within the store. These components are crucial for ensuringthe store's functionality and customizations are retained when moving to the production environment.

To ensure that guest users have read access to the Product object, an Administrator shouldB. Modify the guest user profile to provide access to the Product object. This involves adjusting the permissions within the guest user profile settings to grant read access specifically to the Product object, ensuring that guest users can view product details without compromising data security.

To use images housed on an external host for a B2B storefront, an Administrator shouldA. Create an External Content Host record for the image host. This record specifies the external domain where the images are stored, allowing Salesforce B2B Commerce to securely access and display these images within the storefront.

To prevent a "Products" category from being displayed as requested by the Store Manager, the Administrator shouldDisable the Display in Menu attribute (A). This action will remove the category from the storefront navigation menu, ensuring it does not appear to store visitors. This approach allows for flexibility in managing how products and categories are presented on the storefront, aligning with business requirements and preferences. The other options, such asEnable the Do Not Display in Menu attribute (B),Disable the Show in Menu attribute (C), andEnable the Hide in Menu attribute (D), are not standard attributes in Salesforce B2B Commerce for controlling menu display.