Free B2B Commerce Administrator Practice Test Questions (2026)

Explanation

A company sells products to industrial customers and only wants the customers to purchase products in increments of five. To implement this, administrators need to configure specific rules to enforce this requirement, ensuring a smooth buying experience and adherence to business policies.

A. Connect the product to a Quantity Rule.
✅ Correct Option: Connecting the product to a Quantity Rule allows administrators to define specific rules for product quantities, ensuring customers can only purchase in specified increments, like 5, 10, or 15 units, maintaining consistency across transactions.

D. Create Purchase Quantity Rules.
✅ Correct Option: Creating Purchase Quantity Rules defines the specific increments (in this case, 5) that customers must adhere to when purchasing products, allowing for flexible quantity management and streamlined order processing.

B. Enable Purchase Increment Rules.
❌ Incorrect Option: There is no such feature as "Purchase Increment Rules" in Salesforce B2B Commerce; Quantity Rules are used instead to manage purchase increments, making this option invalid.

C. Create a cart validation.
❌ Incorrect Option: Cart validations are used to enforce business rules at checkout, but aren't directly related to enforcing purchase increments, making it an incorrect choice for this scenario, as it serves a different purpose.

Summary:
To implement purchase increments of 5, administrators must create Purchase Quantity Rules and connect the product to a Quantity Rule, ensuring customers buy products in required increments, streamlining sales processes and reducing errors.

Reference:
Salesforce B2B Commerce Admin Guide (Quantity Rules)

Explanation:

In Salesforce B2B Commerce, product presentation plays a key role in customer experience. Admins can enrich product records with images, banners, and attachments. Out-of-the-box options define what can be directly associated without customization, ensuring products appear detailed and engaging for buyers.

✅ Correct Option: B. One or more Attachments (📎)
Admins can attach documents like spec sheets or PDFs to products. Attachments add depth and serve as supporting material for customer decisions.

✅ Correct Option: C. Up to eight Product Detail Images (🖼️)
Each product can include multiple detailed images—up to eight—providing visual clarity from different angles or use cases. This helps replicate the in-store product inspection experience.

✅ Correct Option: E. One or more Product Banner Images (🏷️)
Banner images highlight products on storefront pages. Multiple banners allow for flexibility in marketing and presentation across categories or promotions.

❌ Incorrect Option: A. Only one Product Detail Image (🚫)
Limiting to one image is not accurate—Salesforce supports multiple detail images (up to eight), not just one.

❌ Incorrect Option: D. Only one Product List Image (⚠️)
Although products can have list images, Salesforce doesn’t enforce a “one-only” restriction. The key out-of-the-box limits concern detail and banner images, not list images.

Reference:
Salesforce B2B Commerce Product Content

Explanation

B2B Commerce search settings let admins control exactly which product fields buyers can search through. The Manage Searchable Fields interface uses visual icons to toggle searchability status clearly. Checkmark icons mark fields as searchable; clicking them removes search indexing. Changes apply after search index rebuild, optimizing performance by excluding unnecessary fields like textbook editions from search results. ​

Correct Option: B. Click on the checkmark icon next to Edition to change the icon to a plus sign (+).
✅ In Manage Searchable Fields, searchable fields show checkmark icons. Clicking the checkmark next to "Edition" deselects it, changing to plus sign indicating not searchable. Navigate Store > Settings > Search > Searchable Fields > Manage. Save changes trigger index rebuild, removing Edition from all storefront search functionality immediately.

​ Incorrect Option: A. Click on the plus (+) icon next to Edition to change the icon to a minus sign (-).
❌ Plus icons already indicate non-searchable fields—clicking them doesn't exist in interface. Manage Searchable Fields uses checkmark (searchable) to plus (not searchable) toggle only. No minus sign functionality appears in B2B Commerce search configuration screens.

Incorrect Option: C. Click on the plus (+) icon next to Edition to change the icon to a checkmark icon.
❌ This reverses the process—clicking plus would make field searchable, opposite of requirement. Administrators click existing checkmarks to disable searchability. Direction matters: checkmark-to-plus removes from index; plus-to-checkmark adds to index.

Incorrect Option: D. Add the Product field to the Search Field Exclusion list.
❌ No "Search Field Exclusion list" exists in B2B Commerce. Searchability toggles directly through Manage Searchable Fields icons. Product field itself can't be excluded (always searchable); only specific fields like custom "Edition" toggle individually through visual interface.

Summary
Click checkmark icon in Manage Searchable Fields to disable field searchability. Edition field changes to plus icon, excluded from search index after rebuild. Clean interface prevents accidental search configuration errors.

Reference
Salesforce Help: Mark Product Fields as Searchable or Not Searchable for a B2B Commerce Store

Explanation:

Salesforce B2B Commerce storefronts facilitate business transactions, enabling seamless purchasing for organizations. Users interacting with these storefronts typically hold roles responsible for procurement and vendor management. These individuals navigate the platform to browse catalogs, place orders, and manage accounts. Their job functions align with strategic purchasing decisions, ensuring efficient supply chain operations. Identifying the correct job titles requires understanding roles that directly engage with B2B purchasing processes on digital commerce platforms like Salesforce.

Correct Options:

✅ A. Purchasing directors:
Purchasing directors oversee procurement strategies, making high-level decisions on vendor selection and bulk orders. They interact with B2B Commerce storefronts to approve purchases, manage budgets, and ensure compliance with organizational policies. Their role involves accessing account-specific pricing and catalogs, a core feature of Salesforce B2B Commerce, making this a fitting job title for frequent storefront interaction.

✅ C. Wholesale buyers:
Wholesale buyers specialize in acquiring goods in bulk for resale or internal use. They use B2B Commerce storefronts to browse catalogs, compare pricing, and place large orders. Their role requires leveraging storefront features like negotiated pricing and order history, aligning perfectly with Salesforce B2B Commerce’s functionality for streamlined purchasing processes.

✅ E. Purchasing managers:
Purchasing managers handle day-to-day procurement activities, including placing orders and managing supplier relationships. They actively use B2B Commerce storefronts to access account-specific pricing, manage carts, and track orders. Their operational role makes them frequent users of the platform, ensuring efficient purchasing aligned with organizational needs.

Incorrect Options:

❌ B. Equipment technicians:
Equipment technicians focus on maintaining and repairing machinery, not procurement. They rarely interact with B2B Commerce storefronts, as their role centers on technical operations rather than purchasing or vendor management. Salesforce B2B Commerce is designed for buyers, not technical staff, making this job title irrelevant for storefront interactions.

🚫 D. Project managers:
Project managers oversee project execution, focusing on timelines and resources, not direct purchasing. While they may influence procurement decisions, they don’t typically use B2B Commerce storefronts for transactions. Their role is more strategic and less aligned with the hands-on purchasing functions of Salesforce’s platform.

Reference:
Salesforce B2B Commerce Overview

Explanation

When adding a B2B Commerce store to an existing Salesforce site, specific prerequisites must be met. The site must be built on compatible templates that support B2B Commerce functionality, and the site should not already have a store configured. These conditions ensure proper integration and prevent conflicts.

✔️ Option A: The existing site should use the Build your own (Aura), Customer Portal or B2B template
This is correct because B2B Commerce stores require compatible site templates that support commerce functionality. Build your own (Aura), Customer Portal, and B2B templates provide the necessary framework and components for B2B Commerce operations. These templates ensure proper store integration and functionality within the existing site structure.

✔️ Option D: The site should not have a store created
This is correct because each Salesforce site can only have one store associated with it. If a store already exists on the site, you cannot add another B2B store. The site must be store-free to successfully add a new B2B Commerce store, preventing configuration conflicts and ensuring clean implementation.

❌ Option B: The existing site should only use the Microsite (LWR) template
Microsite (LWR) template is not the exclusive requirement for adding B2B stores. While LWR templates can support commerce, limiting to only Microsite excludes other valid templates like Aura-based and Customer Portal templates that also support B2B Commerce functionality effectively.

❌ Option C: The site should already have a store created
This is incorrect because sites can only have one store. If a store already exists, you cannot add another B2B store to the same site. The requirement is the opposite—the site must not have an existing store for successful B2B store addition.

📌 Summary
To add a B2B store to an existing site, use compatible templates (Aura, Customer Portal, or B2B) and ensure no store currently exists on the site.

🔗 Reference
Salesforce Help - Add a B2B Store to an Existing Experience Cloud Site

Explanation:

Buyer Managers in a Salesforce B2B Commerce storefront oversee purchasing activities, such as placing orders and managing accounts. They require specific permissions to access and perform actions on the storefront. Salesforce provides profiles and permission sets tailored for B2B Commerce roles, ensuring users have appropriate access. Identifying the correct profile or permission set involves understanding the permissions needed for Buyer Managers to effectively interact with the storefront’s purchasing features.

Correct Option:

🌟 D. B2B Commerce User:
The B2B Commerce User profile grants Buyer Managers the necessary permissions to access the storefront, place orders, view account-specific pricing, and manage carts. This profile is designed for external users like Buyer Managers, enabling them to perform core purchasing tasks efficiently within the Salesforce B2B Commerce environment, making it the correct choice.

Incorrect Options:

❌ A. Commerce User:
The Commerce User profile is a generic term and not specific to Salesforce B2B Commerce. It may apply to other Salesforce products, but for B2B Commerce storefronts, the B2B Commerce User profile is explicitly required for Buyer Managers, making this option incorrect.

🚫 B. B2B Commerce Super User:
The B2B Commerce Super User profile is designed for administrative tasks, such as managing storefront settings, not for standard buyer activities. Buyer Managers need purchasing permissions, not administrative access, so this profile is unsuitable for their role.

🛑 C. Account Switcher User:
The Account Switcher User permission allows users to switch between accounts, typically for sales reps or admins, not Buyer Managers. This permission is irrelevant for standard purchasing tasks on the storefront, making it an incorrect choice for Buyer Managers.

Reference:
Salesforce B2B Commerce User Permissions

Explanation:

Why B is correct:
Org-Wide Email Addresses (OWEAs) are a standard Salesforce feature used to centralize the "From" address for outgoing emails. Once configured and verified by Salesforce, an Administrator can set this OWEA as the default address for various automated processes, including B2B Commerce transactional emails (like order confirmations). This ensures all automated emails originate from a consistent, branded, "no-reply" address.

Why A is incorrect:
"Domain Email Address" is not a standard term or feature within Salesforce Store Manager. The correct location for configuring this is in Salesforce Setup, not the Commerce-specific Store Manager.

Why C is incorrect:
While the goal is to create a "no-reply" address, there is no specific standalone feature named "No-Reply Email Address" in Setup. The correct feature that serves this purpose is the "Org-Wide Email Address."

Why D is incorrect:
"System Email Address" is not a configurable feature within the Store Manager. System emails are typically handled by the broader Salesforce platform, and their "From" address is controlled by the Org-Wide Email Address settings in Setup.

Reference:
Salesforce Help: "Set Up Org-Wide Email Addresses"

Explanation

Experience Builder in Salesforce B2B Commerce (LWR sites) provides a no-code way to customize the site's theme and appearance directly. Admins access Theme settings to adjust branding elements like logos, colors, fonts, and component styles (including buttons). These changes apply globally or per-page, helping match the company's brand without custom CSS or code—perfect for quick look-and-feel updates requested by management.

Correct Options:

✅ B. Customer's Logo
Upload and replace the customer's logo directly in Experience Builder under Theme > Branding Sets. This updates the logo in the header/footer across the site (or specific pages), instantly refreshing the brand identity—super straightforward and one of the most common theme customizations.

✅ C. Button Size
In recent releases (e.g., Summer '23+), Experience Builder's Theme panel lets admins adjust button size (and shape) via branding properties or component styles. This fine-tunes button dimensions for better UX and visual consistency without developer help.

✅ D. Text Color
Admins can change text color (headings, body text, links) in the Theme > Text or Color palette sections of Experience Builder. This includes precise color picking or palette generation from the logo, making it easy to align text with brand guidelines.

Incorrect Options:

❌ A. Mobile Width and Size
Mobile responsiveness in B2B Commerce LWR sites is handled automatically via breakpoints and fluid layouts—no direct "Mobile Width and Size" setting exists in Experience Builder's theme tools. Layouts adapt to devices; custom mobile tweaks require page/component adjustments or advanced CSS, not a simple theme option.

❌ E. All of the button colors
While some button colors (e.g., primary/action button) can be updated via theme palettes or component styles, all button colors aren't controlled in one unified place. Different states (hover, active, secondary buttons) may need separate tweaks or custom CSS—it's not a single "all button colors" option in standard Experience Builder theme settings.

Summary
Experience Builder empowers Admins to update the site's theme look and feel by changing the Customer's Logo, Button Size, and Text Color through Branding Sets, Theme palettes, and component properties. These are quick, no-code adjustments for branding alignment. Mobile dimensions aren't directly configurable here (handled responsively), and button colors aren't all adjustable in one spot—focus on these three for common theme requests.

Reference:
Customize the Theme of Your Experience Builder Site
Add Style to Your Experience Builder Site with Themes
Fine-Tune Your LWR Sites with New Branding Properties (covers button size, colors, text)

Explanation:

🟢 In Salesforce B2B Commerce, while you can create a large number of categories, there is a known limitation regarding the depth of the category hierarchy. This is a critical consideration for performance and data management. Exceeding a certain depth can negatively impact storefront performance, particularly on category and product list pages, as the system needs to traverse the entire tree to render the navigation and breadcrumbs.

Why the other options are incorrect:

🔴 A. Only 50 categories can be localized per language: This is incorrect. There is no such specific limit on the number of categories that can be localized per language.

🔴 B. There is a limit of 50 categories total across all languages: This is incorrect. Salesforce B2B Commerce can handle thousands of categories. This limit is not valid.

🔴 D. There is a limit of 100 categories total across all languages: This is also incorrect. Similar to option B, the platform is designed to support a much larger number of categories. The total number of categories is not the primary constraint; the depth of the hierarchy is.

Explanation

Enabling multi-account switching requires configuring the storefront UI, user permissions, and account access. Administrators must add the switcher component, assign proper permissions, and share accounts to allow users like sales reps to purchase on behalf of multiple organizations seamlessly.

✅ Correct Options

A. Add the Switch Accounts component to the Store home page.
The Switch Accounts component provides the user interface for account switching. Adding this component to the storefront page layout makes the functionality visible and accessible. Without it on the page, users lack the interface element needed to select and switch between accounts.

B. Assign the Account Switcher User permission to the purchasing user.
The Account Switcher User permission set enables multi-account switching capability. This permission allows users to view and use the account switcher interface to toggle between accounts. Without this permission assigned, the switching feature remains inactive even with proper sharing and components configured.

C. Share the Account with the purchasing user.
Account sharing grants users access to additional buyer accounts. Using Salesforce sharing rules or manual sharing, administrators provide users visibility to specific accounts. This sharing enables users to view and select from multiple accounts when using the switcher, establishing the necessary account relationships.

❌ Incorrect Options

D. Assign the Buyer Manager permission to the purchasing user.
Buyer Manager permissions are for managing users and settings within a single organization, not switching between multiple accounts. This permission set handles internal account administration tasks like managing team members and addresses, serving a different purpose than multi-account purchasing capabilities.

E. Create an External Managed Account record.
External Managed Account records aren't required for basic account switching functionality. The core requirements focus on UI components, permissions, and sharing. While used in certain scenarios, these records add unnecessary complexity for standard account switching implementations.

📌 Summary
Enable account switching by adding the Switch Accounts component, assigning Account Switcher User permission, and sharing target accounts. These three steps provide complete multi-account purchasing functionality.

🔗 Reference
Salesforce B2B Commerce - Account Switcher Configuration