Free Salesforce B2B-Commerce-Administrator Practice Exam with Questions & Answers

To leverage an existing Salesforce Billing product implementation in their B2B Commerce storefront, an administrator shouldD. Create a custom Component in Experience Builder. This custom component can integrate Salesforce Billing functionality into the B2B Commerce storefront, allowing for seamless invoice and payment processing within the commerce experience.

If search filters are not visible on the Category Detail page when viewing the storefront in Spanish, it could be due toThe picklist value's translations not being completed in Translation Workbench (C). The Translation Workbench in Salesforce allows Administrators to provide translations for various UI elements, including picklist values used in search filters. If these translations are incomplete or missing, the filters may not display correctly in the specified language. This issue highlights the importance of comprehensive translation efforts to ensure aseamless multilingual user experience. Browser translation issues (A), site page variations (B), and untranslated category data (D) can also affect localization, but the visibility of search filters is directly tied to the completeness of translations in the Translation Workbench.

When setting up categories for import using the CSV import tool with categories delimited by a single pipe character, the Administrator canC. Split the categories into separate columns with appropriate labelsorD. Replace the pipes with a forward slash. Both methods organize the category data in a format that the import tool can recognize and process effectively.

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.

To allow a user to switch between accounts in the store to purchase for multiple accounts, the necessary tasks includeA. Add the Switch Accounts component to the Store home page,B. Assign the Account Switcher User permission to the purchasing user, andC. Share the Account with the purchasing user. These steps enable a user-friendly mechanism for buyers to manage purchases across different accounts, enhancing the purchasing experience.

The standard B2B Main Checkout Flow template includes sub-flows forShipping Method (A),Billing Address (B), andTaxes (E). These sub-flows are integral to the checkout process, ensuring that shipping, billing, and tax calculations are handled efficiently and accurately during the checkout procedure.

To stop welcome emails from being sent to new members joining the store, an Administrator canDisable the Send welcome email setting in the Administration tab in Experience Builder (D). This setting controls the automatic dispatch of welcome emails upon new user registration, and disabling it prevents these emails from being sent. This action offers a direct way to manage communication preferences within the Experience Builder, aligning the store's engagement strategies with business needs and user expectations. Unchecking Send Email settings (A) and modifying email configurations in Setup (B, C) are also relevant to email management, but the specific control for welcome emails is found within the Experience Builder's Administration settings.

To make a custom field named "Edition" on the product object no longer searchable within the Manage Searchable Fields in a Salesforce B2B Commerce site, the Administrator shouldD. Add the Product field to the Search Field Exclusion list. This action explicitly removes the field from the list of fields that are indexed and considered during search operations, thereby making it non-searchable.

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.

TheSystem Context with Sharing—Enforces Record-Level Access (D)is crucial to B2B Commerce because it ensures that users can only view products and related data that they are authorized to see, maintaining data security and privacy. This setting is particularly important for storefronts where products need to be displayed according to specific customer agreements, contracts, or profiles. It doesn't directly relate to checkout (A), content synchronization (B), orguest browsing (C), but rather to the fundamental aspect of product visibility and access control on the storefront.