Salesforce B2B-Commerce-Administrator Salesforce Accredited B2B Commerce Administrator (SU24) Exam Practice Test

For investigating additional functionality around international taxation and credit card payments in Salesforce B2B Commerce, an administrator can exploreA. Salesforce Labs add-onsandD. AppExchange connectors. Salesforce Labs provides innovative solutions that can be used as is or customized, while AppExchange connectors offer pre-built integrations that extend the functionality of Salesforce B2B Commerce to meet specific business needs, including payment processing and tax calculations.

To limit the products that a Buyer Group can see, an Administrator can useC. Entitlement Policies. Entitlement Policies in Salesforce B2B Commerce control access to products based on various criteria, including buyer groups. By configuring these policies, an administrator can define which products are visible and available to specific buyer groups, ensuring a tailored and relevant product selection for different segments of buyers.

To quickly provide basic reports like Orders by Date and Total Orders in a new B2B Commerce deployment, the fastest way is toInstall the Commerce Reports under Commerce Setup (B). This feature provides a set of pre-built reports tailored for commerce analytics, allowing Administrators to quickly deploy essential reporting tools to stakeholders. While Salesforce Labs (A) and AppExchange (C) offer valuable resources and templates, Commerce Reports within Commerce Setup are specifically designed for rapid deployment within the B2B Commerce context. Advanced Reports (D) offer more detailed insights but may require additional configuration.

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 a second administrator did not receive the welcome email for B2B Commerce, they can still access the store without changing the setup byLogging in from the Contact page in the Commerce app (C). This method allows administrators with existing Salesforce credentials to access the B2B Commerce environment directly through the Commerce app, bypassing the need for a welcome email. Additionally,Resetting the user's password from Setup and having the user login again (E)is a common workaround for access issues. This approach ensures that the user can reset their password and gain access to the store without relying on the initial welcome email. Checking Debug Logs (A), Enabling Guest Access in Experience Builder (B), and Logging in using the link in the More Information section of the Store page (D) are not standard practices for this particular scenario.

To enable external buyers to view products on the storefront, the entities that typically do not require "Public Read Only" access arePrice Book (A)andProduct Media (D). Price Books, while crucial for defining product pricing, are usually managed and accessed by internal users rather than external buyers directly. Product Media, such as images and videos, are essential for product display but do not necessarily require direct access by external buyers as they are typically embedded within product pages or catalogs.Order Delivery Method (B)andCatalog(C), on the other hand, are more integral to the shopping experience and may require broader access levels to ensure external buyers can view available products and delivery options.

Supporting store-specific products, including an exclusive line of products for "premier" status stores, issupported by the B2B Commerce data model (C). This capability allows for the configuration of product availability and visibility based on store status or other criteria, enabling differentiated product offerings across various store types.

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.

To set up different pricing for different groups of buyers, an Administrator shouldB. Create Price Booksto define different pricing structures andD. Create Buyer Groupsto segment buyers into groups. Price Books can then be assigned to specific Buyer Groups, allowing for differentiated pricing strategies based on the buyer group.

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.

To create variation products for bed items that vary by three different lengths, the Administrator shouldB. Create a custom field length_c, a variation attribute set, and a parent product. The custom field length_c will store the different lengths, the variation attribute set will organize these variations, and the single parent product will represent the base item from which the variations derive.

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.

Before an administrator can see orders, they must:

• D. Give Visible Field-Level Security on the Sales Store field for Orders:This ensures that the administrator has the necessary permissions to view order-related information associated with the store, enabling effective order management and oversight.

This step is crucial for administrators to perform their roles effectively, ensuring access to critical sales and order information.

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.

If a language is deleted from Experience Builder,C. The content is no longer visible but is not deleted. This means that while the content associated with that language will not be displayed in the Experience Builder or the storefront, it remains in the system. This allows for the possibility of re-adding the language at a later time and restoring the visibility of the content without having to recreate it.

CMS content must be in theD. Draftstatus to be editable. This status indicates that the content is in the initial stages of creation or modification and has not yet been finalized for publication. Draft status allows administrators to make changes before the content is reviewed, approved, and published, ensuring that only fully vetted and complete content is made available to end-users.

To enable Activity Tracking in the storefront, an administrator needs toD. Leverage Google Analytics. By integrating Google Analytics with the B2B Commerce storefront, the administrator can track user activities, providing insights into user behavior and improving the overall shopping experience.

A rebuild of the Search Index might be required when:

• A. Add a product to an active Entitlement Policy used in the store:This can change the products available to different user segments, necessitating a search index update.
• C. Remove a product from the store Catalog:This ensures that the removed product no longer appears in search results, keeping the catalog current and relevant.

These actions impact the accuracy and relevance of search results, making it crucial to rebuild the search index to reflect these changes.

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.

At the start of setting up a B2B Commerce storefront, the Administrator needs to configure settings that are crucial for the basic operations of the store. EnablingEnhanced Commerce Orders (B)is essential as it allows for the use of advanced order management features, including complex pricing and discount structures, which are common in B2B transactions.Enable Zero Quantity (C)is also a key setting, especially for B2B scenarios where orders might be created as placeholders or for backorder items, allowing for zero quantity orders to be processed through the system. WhileOptional Price Books for Orders (A)andReduction Orders (D)can be important in certain contexts, they are not typically the initial settings configured during the setup process.

To add additional languages to a B2B Commerce site, an Administrator must take the following three steps:B. Enable Translation Workbench, which is a tool for translating text and customizations into different languages;D. Enable Data Translation, which allows for the translation of data records; andE. Add the Supported Language field to the Store page layout, which specifies which languages are supported by the store.

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.

To use an approved entity in a CRM collection, an Administrator must set up aCRM List view (C). This setup enables the organization of entities such as contacts, accounts, or custom objects within the CRM to be part of targeted collections, facilitating segmentation and targeted actions. The CRM List View provides a framework for defining the criteria and filters that determine which records are included in a collection, supporting personalized and efficient CRM strategies. Global (A), Sales (B), and Service (D) List Views are also used within Salesforce but are tailored for broader or different contexts than CRM collections.

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.

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.

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 performing a search index in Salesforce B2B Commerce, it is crucial that at least one product has aProductCode assigned (D). The ProductCode is a unique identifier for products in Salesforce B2B Commerce, and it is essential for indexing and searching products within theplatform. While images (A) and SKUs (B) enhance product listings and navigation, they are not prerequisites for indexing. Ensuring products are marked as Active (C) is important for them to appear in search results, but the presence of a ProductCode is fundamental to the indexing process itself.

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.

For better navigation within a storefront selling office furniture, the Administrator shouldCreate Product Categories (D). Product Categories allow for the logical grouping of products, such as desks, chairs, and filing cabinets, facilitating easier browsing and discovery for customers.Categories offer a hierarchical structure that can be used to segment products by type, function, or any other relevant classification, enhancing the user experience. Tags (A), Keywords (B), and Filters (C) can also aid in navigation, but Categories provide a fundamental organizational framework that is essential for store structure and navigation.

To ensure that all automated emails are sent from a "no-reply" email address, the Administrator should:

• B. Create an Org-Wide Email Address in Setup:This allows for the configuration of a default email address (such as a "no-reply" address) that will be used for all outgoing emails from the Salesforce org, ensuring consistency and controlling the reply behavior.

In Salesforce B2B Commerce, administrators can enhance product pages by adding various types of content. Out of the box, the options include:

• B. One or more Attachments:Administrators can attach multiple files to a product. These attachments can include manuals, specifications, or additional information relevant to the product.
• C. Up to eight Product Detail Images:This allows for a more comprehensive display of the product from different angles or in different use cases, enhancing the buyer's understanding and visualization of the product.
• E. One or more Product Banner Images:These can be used to highlight key features, promotions, or any other important information related to the product at the top of the product page.

These features are designed to provide a rich, informative, and engaging product experience for the buyers, directly out of the box, without the need for custom development.

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.

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 choose which Category displays in the breadcrumb for Products that are in multiple categories, the Administrator shouldB. Set the Category as the Primary Category. This designation ensures that the chosen category is used for navigation and displayed in the breadcrumb trail, providing a clear path for users.

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.