Free AP-201 Practice Test Questions and Answers (2026)

The primary value proposition of Salesforce B2B Commerce is its native architecture on the core Salesforce platform. By being built directly on the platform, it shares the exact same data model, security infrastructure, and administrative tools as Salesforce CRM (Sales and Service Clouds). This native integration directly addresses the CFO's concerns by eliminating the need for costly, complex point-to-point integrations between disparate commerce and CRM systems. It provides a single source of truth for customer data, orders, and pricing, enabling unified governance and allowing organizations to leverage standard Salesforce automation tools (like Flow) seamlessly across both their commerce operations and traditional CRM workflows.

A. B2B Commerce does not eliminate the need for a CRM; rather, it enhances and works in tandem with the existing Salesforce CRM deployment.

C. While deployment speed is a benefit, competing on licensing fees is not the primary architectural value proposition addressing integration complexity.

D. B2B Commerce does not require custom development to integrate with Salesforce CRM because it is natively built on the same platform.

1. Salesforce Help Documentation: "B2B Commerce on Lightning Experience", Section: Architecture and Platform Benefits.

2. Salesforce Official Whitepaper: "The Total Economic Impact of Salesforce B2B Commerce", Section: Cost Savings and Native Integration.

In Salesforce B2B Commerce on Lightning Experience, sending order confirmation emails relies on standard Salesforce platform automation capabilities rather than out-of-the-box commerce-specific checkboxes. To configure this, an administrator must first create an Email Template tailored to the order confirmation details. Next, an Organization-Wide Email Address must be established so the email originates from a generic store address (e.g., [email protected]) rather than an individual user. An Email Alert is then created to link the template and the recipient (the buyer). Finally, an Auto-launched Flow or Record-Triggered Flow is configured to trigger the Email Alert automatically when the Order reaches the appropriate status (e.g., Activated) upon checkout completion.

B. Writing an Apex Trigger is unnecessary because standard declarative tools like Salesforce Flow can easily handle email automation without custom code.

C. There is no standard out-of-the-box 'Buyer Confirmation Email' sub-flow provided in the default checkout flow template that simply needs to be added.

D. There is no simple "Activate Order Confirmation to Buyers" checkbox in the Commerce App Store Administration; it requires platform automation setup.

1. Salesforce Help: "Set Up Order Confirmation Emails", Section: B2B Commerce Checkout Automation.

2. Salesforce Trailhead: "Automate B2B Commerce Checkout", Module: Post-Checkout Automation.

The most effective approach for balancing time-to-market, maintainability, and business value with limited coding experience is to leverage the out-of-the-box B2B Commerce template as a foundation. By utilizing Experience Cloud's declarative design tools, such as the Lightning Design System (LDS) and custom themes, the team can achieve a high degree of UI customization without writing extensive code. Pre-built components for search, cart, and checkout accelerate deployment and ensure platform compatibility. Custom code (like custom Lightning Web Components) should be strictly reserved for unique business requirements that cannot be met declaratively, thereby minimizing technical debt and ensuring long-term maintainability.

A: Building from scratch requires extensive coding expertise, significantly increases time-to-market, and creates massive technical debt for future maintenance.

C: Strictly avoiding customization fails to meet the business requirement for a highly customized buyer interface.

D: Replacing all pre-built components with custom LWC and Apex ignores the low-code requirement and unnecessarily increases maintenance overhead.

E: B2B Commerce on Lightning Experience is a core platform product updated via standard releases, not through managed package upgrades (which applies to legacy CloudCraze).

1. Salesforce Help: "B2B Commerce on Lightning Experience Best Practices", B2B Commerce Documentation, Section: Storefront Customization.

2. Salesforce Trailhead: "B2B Commerce on Lightning Experience Basics", Module: Storefront Design and Customization.

Rebuilding a B2B Commerce search index is an administrative operation that requires the appropriate commerce/search index permissions. If the administrator cannot rebuild the index, a likely cause is that the necessary permission set or permission has not been assigned. Product data issues—such as inactive products, missing catalog associations, missing price book setup, or entitlement configuration—can affect which products appear in search results, but they do not best explain an administrator being unable to perform the rebuild action itself. Therefore, the most direct cause in this scenario is insufficient administrative permission to manage or rebuild the commerce search index.

B. No active categorized products may produce empty search results, but it does not primarily prevent the administrator from rebuilding the index.

C. A missing price book affects product pricing/visibility, not the administrator’s permission to rebuild the index.

D. Entitlement policies control buyer access to products; they are not the basic permission needed to rebuild search indexes.

1. Salesforce Help, “Rebuild the Search Index for a B2B Commerce Store,” prerequisites section for required permissions.

2. Salesforce Help, “Set Up Search for B2B Commerce,” section “Manage Search Indexes.”

3. Salesforce Help, “B2B Commerce Permission Sets,” sections for commerce administrator and search index management permissions.

4. Salesforce Help, “Control Product Visibility with Entitlement Policies,” section explaining entitlement-based buyer access.

In Salesforce B2B Commerce, enabling delegated purchasing and buyer manager capabilities requires proper configuration of Account Relationships and Account Buyer Groups. Account Relationships define the hierarchical or peer-to-peer connections between accounts, allowing users from a managing account to purchase on behalf of a target account. Furthermore, these accounts must be correctly associated with Buyer Groups to inherit entitlements, price books, and store access. Without configuring these native data model elements and ensuring the Experience Cloud portal is mapped for role-based visibility, buyers cannot exercise delegated administration or view related account hierarchies. Proper setup ensures that buyer managers can seamlessly view and manage orders for their subordinate accounts.

A: The 'Buyer Experience' permission set is not a standard requirement for account hierarchies; Account Relationships natively govern this visibility.

C: B2B Commerce is natively built on Experience Cloud; they are fully compatible and do not require a separate package deployment for basic compatibility.

D: B2B Commerce natively supports account hierarchies and delegated purchasing via Account Relationships; custom Apex triggers are entirely unnecessary.

E: Buyer manager capabilities and delegated administration are native, supported features of Experience Cloud-based B2B Commerce (Lightning B2B Commerce).

1. Salesforce Help: "B2B Commerce on Lightning Experience", Section: "Set Up Account Relationships for B2B Commerce", Document ID: sf.b2bcommerceaccountrelationships.

2. Salesforce Help: "Delegated Administration in B2B Commerce", Document ID: sf.b2bcommercedelegatedadmin.

To use an existing Experience Cloud site as a B2B Commerce store, the administrator must use the "Create a Store on Existing Site" feature. This functionality is specifically designed to integrate B2B Commerce capabilities into an already established Experience Cloud site, such as a partner portal or customer community, without requiring the creation of a completely new site from a Commerce template. By navigating to the Commerce app and selecting the Stores tab, the administrator can click the "Create a Store on Existing Site" button. This action establishes the necessary underlying commerce data model, links the store entity to the selected Experience Cloud site, and provisions the required commerce components for use within the Experience Builder, ensuring a seamless integration of commerce features.

A. Dragging and dropping components is impossible until the store entity is actually created and linked to the site to provision the necessary commerce data and components.

C. There is no functionality in the Digital Experience settings to "convert" a site; commerce integration is handled exclusively through the Commerce app.

D. Stores are created and managed directly within the Commerce app workspace, not through the backend Salesforce Setup menu.

1. Salesforce Help Documentation. B2B Commerce and D2C Commerce: Create a Store on an Existing Experience Cloud Site. Section: "Create a Store on an Existing Site". Available at Salesforce Official Documentation.

2. Salesforce Trailhead. B2B Commerce on Lightning Experience Administration. Module: "Set Up a B2B Store", Section: "Create a Store".

In Salesforce B2B Commerce, administrators use Salesforce CMS to manage and deliver product-related information to buyers. The standard CMS content types specifically designed and supported for enriching product details in a B2B store are "Document" and "Image". Images are utilized for product list and detail views, including product banners, thumbnails, and gallery images, which are critical for visual identification. Documents are used to provide supplementary textual product information, such as technical specifications, user manuals, or safety guides. By associating these specific CMS content types with products via the Commerce App, administrators ensure that buyers have comprehensive visual and textual data to make informed purchasing decisions directly within the storefront experience.

B. "File" is a standard Salesforce object (ContentDocument) but not the specific CMS content type used for mapping media to B2B Commerce products.

C. "Asset" represents purchased items or instances of products owned by customers, not a CMS content type used for enriching product catalog information.

1. Salesforce Help Documentation: "Manage Product Media with Salesforce CMS", Section: Supported CMS Content Types for Commerce.

2. Salesforce Trailhead: "Salesforce CMS Basics", Module: Create and Manage Content.

When testing a flow in debug mode, Salesforce allows administrators to execute and validate inactive or draft versions of the flow. If the test succeeds in debug mode but fails in the live B2B store, it indicates the store is not executing the updated logic. This typically occurs for two primary reasons. First, the newly modified version of the checkout flow was saved but never activated, causing the live store to continue running the older active version. Second, the Checkout component within the Experience Builder might be explicitly configured to reference a completely different flow rather than the one that was just updated. Ensuring the correct flow is both active and mapped resolves this.

C: Deactivating and reactivating the entire Experience Cloud store site is completely unnecessary for flow updates to take effect.

D: There is no "Apply Promotions Status" field on the General Settings store page; promotions are enabled via flow and pricing configurations.

1. Salesforce Help: "Flow Builder: Debug a Flow", Section: "Debugging Inactive Flows".

2. Salesforce Help: "Configure the Checkout Component", Section: "Select a Checkout Flow".

In Salesforce B2B Commerce, the presentation of products on search results and category detail pages is managed by the Product List (or Results) component within the Experience Builder. Out-of-the-box, this component provides administrators with two primary layout options: Grid and List. The Grid layout displays products in a multi-column format, emphasizing product images and providing a highly visual browsing experience. The List layout presents products in a single-column, vertical format, which is ideal for displaying more detailed text information, specifications, and bulk ordering options typical in B2B scenarios. Administrators can easily toggle between these two native layouts without requiring custom code.

A. Matrix: Matrix is not a standard out-of-the-box layout option for the Product List component in Experience Builder.

B. Tree: Tree layouts are typically used for category navigation hierarchies, not for displaying product search results.

C. Chart: Charts are used for analytical data visualization, not for rendering product catalog search results.

1. Salesforce Help Documentation. "B2B Commerce Experience Builder Components." Section: "Product List Component Properties."

2. Salesforce Trailhead. "B2B Commerce Storefront Experience." Module: "Customize the Product List Page."

In Salesforce B2B Commerce, content managed within Salesforce CMS must be explicitly shared with the storefront to be visible to buyers. This is achieved by creating a CMS Channel and associating it with the specific Experience Cloud site. If personalized content and recommendations exist in the CMS workspace but fail to render on the live storefront, the most probable root cause is a missing or misconfigured channel association. The administrator must navigate to the CMS Workspace, verify that the Experience Cloud site is added as an active channel, and ensure the content is published to that specific channel. Without this linkage, the storefront cannot retrieve or display the CMS data.

B. Einstein Engagement Scoring requires a separate license: While licensing varies, the core issue of CMS content not displaying points directly to channel configuration, not just Einstein licensing.

C. Product recommendations are powered by third-party machine learning: Salesforce provides native AI recommendations via Einstein; it does not strictly require third-party external services.

D. The custom community theme is incompatible: While custom themes can cause UI issues, missing CMS content is fundamentally a channel and publishing configuration issue in Site Setup.

1. Salesforce Help Documentation: "Salesforce CMS Workspaces and Channels" (Section: Add a Channel to a CMS Workspace).

2. Salesforce Help Documentation: "Deliver CMS Content to Experience Cloud" (Section: Publishing Content to Site Channels).