B2B-Commerce-Administrator Exam Questions With Explanations

The best B2B-Commerce-Administrator practice exam questions with research based explanations of each question will help you Prepare & Pass the exam!

Over 15K Students have given a five star review to SalesforceKing

Why choose our Practice Test

By familiarizing yourself with the B2B-Commerce-Administrator exam format and question types, you can reduce test-day anxiety and improve your overall performance.

Up-to-date Content

Ensure you're studying with the latest exam objectives and content.

Unlimited Retakes

We offer unlimited retakes, ensuring you'll prepare each questions properly.

Realistic Exam Questions

Experience exam-like questions designed to mirror the actual B2B-Commerce-Administrator test.

Targeted Learning

Detailed explanations help you understand the reasoning behind correct and incorrect answers.

Increased Confidence

The more you practice, the more confident you will become in your knowledge to pass the exam.

Study whenever you want, from any place in the world.

Salesforce B2B-Commerce-Administrator Exam Sample Questions 2026

Start practicing today and take the fast track to becoming Salesforce B2B-Commerce-Administrator certified.

21184 already prepared
Salesforce 2026 Release
118 Questions
4.9/5.0

What must an Administrator set up in order to use an approved entity ina CRM collection?

A. Global List view

B. Sales List View

C. CRM List view

D. Service List View

C.   CRM List view

Explanation

In Salesforce B2B Commerce, CRM Collections allow administrators to group and target approved entities (such as Accounts, Contacts, or other records) for personalized experiences, promotions, or buyer segmentation in the storefront. To make an approved entity usable within a CRM Collection, the administrator must first create and configure a specific type of List View that defines the criteria, filters, and scope for including those entities in collections. This List View acts as the foundation for selecting and organizing records effectively.

Correct Option

✅ C. CRM List view
This is the required setup. A CRM List View must be created (typically on the relevant object like Account or Contact) with appropriate filters and sharing settings. This List View enables the entity to be approved and pulled into CRM Collections for use in B2B Commerce features like targeted pricing, promotions, or buyer group assignments. Without a properly set up CRM List View, entities cannot be included or referenced in collections.

Incorrect Options

❌ A. Global List view
A Global List View is a broad, organization-wide view available across apps, but it is not specific to CRM Collections in B2B Commerce. It doesn't provide the targeted filtering or approval mechanism needed to use entities within collections — CRM-specific List Views are required instead.

❌ B. Sales List View
Sales List Views are tailored for sales processes (e.g., opportunities, leads) and appear in the Sales app. They are not designed or required for CRM Collections in B2B Commerce, which focus on buyer-facing segmentation rather than sales team workflows.

❌ D. Service List View
Service List Views support service console or case management scenarios. They have no role in enabling approved entities for CRM Collections in B2B Commerce — this area relies on commerce-specific configurations, not service-oriented views.

Summary
To use an approved entity (like Accounts or Contacts) in a CRM Collection within Salesforce B2B Commerce, the administrator must set up a CRM List view on the relevant object. This view defines the records eligible for inclusion, ensuring proper filtering and visibility for storefront personalization and targeting.

Reference:
Salesforce Help – CRM Collections in B2B Commerce (conceptual alignment from exam prep resources and official Commerce admin guides)

An Administrator needs to set up a variation product for the first time in a new org and prepare the search index. 26m 164 Before creating the product, in which two places does the Administrator need to go to establish a variation attribute structure?

A. Commerce Setup

B. Product Workspace

C. Catalogs

D. Object Manager

A.   Commerce Setup
D.   Object Manager

Explanation

Setting up variation products requires creating the attribute structure first to define how variations like size or color differentiate products. This involves configuring product attributes as custom fields and grouping them into sets through specific setup areas before any products can be created. Proper setup ensures the search index recognizes variations correctly for storefront display. ​

✅ Correct Options

✅ A. Commerce Setup
Commerce Setup provides the dedicated Product Settings area where administrators first create individual product attributes (like Color or Size) with display types and value options. After attributes exist, Variation Attribute Sets get created here by grouping up to five attributes together. This structured approach prepares the foundation for variation parent products and ensures storefront consistency. ​

✅ D. Object Manager
Object Manager handles the technical side by navigating to Product Attributes > Fields & Relationships to finalize attribute configurations, reorder values, or adjust field properties after initial Commerce Setup creation. This step validates that attributes function properly as variation differentiators across the org. It's essential for linking attributes to the Product2 object model before search indexing.

​ ❌ Incorrect Options

❌ B. Product Workspace
Product Workspace serves for creating and managing actual products after attributes exist, not for establishing the variation attribute structure itself. Administrators use it to assign pre-created attribute sets to variation parent products. It focuses on product lifecycle tasks rather than foundational attribute definition or field setup. ​

❌ C. Catalogs
Catalogs organize products into hierarchical structures for storefront presentation but don't create or configure variation attributes. Attribute setup happens upstream in Commerce Setup and Object Manager before products populate catalogs. Catalog management occurs after variation structure completes to ensure proper categorization. ​

📌 Key Takeaway
Commerce Setup and Object Manager form the essential duo for building variation attribute structure before product creation. Create attributes and sets in Commerce Setup, then finalize fields via Object Manager for search readiness. Product Workspace and Catalogs handle downstream product management and organization, not initial attribute foundation.

A customer can see a price that is not associated with their buyer group. 28m 48s What could be the cause of this behavior?

A. A price book is associated to the default store buyer group.

B. The price is directly set up on the product.

C. The price book is associated to the user's profile.

D. A price book is directly associated to the storefront.

A.   A price book is associated to the default store buyer group.

Explanation

In Salesforce B2B Commerce, pricing is determined by a hierarchy of Price Books assigned to users through their Buyer Group memberships. If a buyer sees a price they shouldn't, it usually means there is a "fallback" or "global" price book active that the system is using because it takes precedence or acts as a catch-all for all storefront users.

✔️ Correct Option

A. A price book is associated to the default store buyer group: ✔️
Every store has a Default Buyer Group used to manage settings for users who aren't explicitly assigned elsewhere (like Guest users). If a Price Book is linked to this group, its prices become visible to anyone browsing the store. This often causes "unexpected" pricing if an Administrator accidentally leaves a master price book assigned to the default group.

❌ Incorrect Options

B. The price is directly set up on the product: ❌
Salesforce Products do not hold a "price" value directly on the product record itself. Prices must always reside within a Price Book Entry. Even the "List Price" requires a Standard Price Book. Therefore, a user cannot see a price "on the product" without an underlying Price Book being accessible to them.

C. The price book is associated to the user's profile: ❌
Price Book visibility in B2B Commerce is not controlled by the standard Salesforce Profile or Permission Set logic. The commerce engine specifically looks at the Buyer Group and its associated Price Book Entries. Associating a price book with a profile would not influence the prices displayed within the storefront UI.

D. A price book is directly associated to the storefront: ❌
In the B2B Lightning/LWR architecture, Price Books are not linked directly to the WebStore object. Instead, they are linked to Buyer Groups, which are then linked to the Store. While the store has a "Default Buyer Group," the Price Book itself cannot be "directly" attached to the storefront record.

Summary
Unexpected pricing usually occurs when a Price Book is associated with the Default Store Buyer Group. Because this group acts as a universal fallback, any pricing assigned to it becomes visible to all users, potentially bypassing the specific, restricted pricing intended for a buyer’s unique group.

🔗 Reference
Price Books in B2B Commerce - Salesforce Help

Which three configuration aspects must be set up outside the Commerce App in order to deploy and activate the full B2B Commerce experience both for internal and external users?

A. Custom attributes

B. Experience Sites

C. Multi-Factor Authentication

D. Profiles and Permission Sets

E. Salesforce CMS

B.   Experience Sites
D.   Profiles and Permission Sets
E.   Salesforce CMS

Explanation

Correct Options:

✅ B. Experience Sites
Experience Sites, built via Experience Cloud, must be configured in Digital Experiences setup to host the B2B Commerce storefront. This includes creating or linking the site, setting up pages, themes, and membership—enabling both internal previews (e.g., for admins) and external access (for buyers). Without this, the store can't be accessed or published for users.

✅ D. Profiles and Permission Sets
Profiles and permission sets are configured in Setup > Users to control access for internal (e.g., Commerce Business User profile) and external users (e.g., Buyer or Buyer Manager permission sets). This ensures proper object permissions, community membership, and feature access like viewing products or placing orders—critical for activating the experience safely.

✅ E. Salesforce CMS
Salesforce CMS is set up outside the Commerce app in the CMS workspace to create, manage, and deliver content (e.g., images, banners) to the storefront. Assigning CMS channels and workspaces to the store is required for enhanced LWR sites and full content functionality, supporting personalized experiences for internal testing and external buyers.

Incorrect Options:

❌ A. Custom attributes
Custom attributes on objects like Products or Accounts can enhance personalization (e.g., for filtering), but they're optional and often configured in Object Manager or within Commerce app settings. They're not a prerequisite for deploying or activating the core B2B Commerce experience for users.

❌ C. Multi-Factor Authentication
MFA is configured in Setup > Identity for added security on logins, especially for external Experience Cloud users. While recommended, it's not mandatory to deploy or activate the storefront—basic functionality works without it, though production orgs may enforce it org-wide.

Summary
The three essential configurations outside the Commerce app are Experience Sites (for the storefront platform), Profiles and Permission Sets (for user access controls), and Salesforce CMS (for content management). These enable a complete, accessible B2B Commerce experience for internal and external users. My initial inclusion of MFA was incorrect—it's optional; CMS is the key third aspect.

Reference:
Salesforce Help: "Get Started with Salesforce Commerce" (covers prerequisites like sites, profiles, CMS)
Salesforce Help: "Configure Internal Users for Commerce" (profiles/permissions)

How can an Administrator stop welcome emails from being sent when a customer joins the store as a new member?

A. Uncheck the Send Email setting under Self-Registration in the Administration tab in Experience Builder.

B. Add Welcome Emails to the Filtered Emails field in the Emails section of Setup.

C. Disable the Welcome Email setting in the B2B Commerce section of Setup.

D. Disable the Send welcome email setting in the Administration tab in Experience Builder.

D.   Disable the Send welcome email setting in the Administration tab in Experience Builder.

Explanation

In Salesforce B2B Commerce (built on Experience Cloud), welcome emails are automatically sent to new members (buyers who self-register or are added) upon joining the store. This is a site-level setting to notify users of their account creation and provide login details. Administrators can disable this to prevent unwanted emails, especially during testing, bulk onboarding, or when using custom welcome communications.

Correct Option:

✅ D. Disable the Send welcome email setting in the Administration tab in Experience Builder.
In Experience Builder, open the store site > switch to the Administration tab (under Settings or Workspaces > Administration). There you'll find the Send welcome email checkbox (or toggle). Disabling it stops the platform from sending automatic welcome emails to new members when they join/register in the B2B store—simple, direct, and the standard way to control this behavior without custom code.

Incorrect Options:

❌ A. Uncheck the Send Email setting under Self-Registration in the Administration tab in Experience Builder.
While Self-Registration settings exist in the Administration tab (e.g., enabling registration, profile defaults), there is no specific "Send Email" checkbox directly under Self-Registration for welcome emails. The welcome email toggle is a separate site-wide option—not nested under self-reg config—so this doesn't target the correct setting.

❌ B. Add Welcome Emails to the Filtered Emails field in the Emails section of Setup.
Setup > Emails has general deliverability and filtered email options (e.g., for blocking spam-like sends), but no "Filtered Emails" field exists for selectively suppressing welcome emails. This approach is for org-wide email filtering, not store-specific welcome suppression in B2B Commerce.

❌ C. Disable the Welcome Email setting in the B2B Commerce section of Setup.
The B2B Commerce section in Setup handles store configs, payments, shipping, etc., but there is no dedicated "Welcome Email" toggle there. Welcome email control lives in the Experience Cloud/Builder Administration area for the site, not in core Commerce Setup objects.

Summary
To prevent automatic welcome emails when new customers join/register in a B2B Commerce store, go to Experience Builder > Administration tab and disable the Send welcome email setting. This stops the default notification without affecting registration or other emails. Avoid mislocated options in Self-Registration sub-sections or Setup areas—Administration tab is the precise spot for this control.

Reference:
Disable the Welcome Email for Your B2B Commerce Store
Activate Your Store

Prep Smart, Pass Easy Your Success Starts Here!

Transform Your Test Prep with Realistic B2B-Commerce-Administrator Exam Questions That Build Confidence and Drive Success!