Explanation

In Salesforce B2B Commerce, external buyers (via Experience Cloud) access the storefront as community/guest-like users. To view products, prices, and associated media securely without owning records, certain core objects require Organization-Wide Defaults (OWD) external access set to Public Read Only in Sharing Settings. This grants read visibility to unauthenticated or external users for catalog browsing, product details, pricing, and images—ensuring the storefront loads correctly while preventing edits or unauthorized access.

Correct Options:

✅ C. Catalog
The Catalog object defines the product collection for the store. Setting its external OWD to Public Read Only allows external buyers to access the catalog structure and see which products are available in their assigned buyer group. Without this, the storefront may fail to display the product hierarchy or categories properly for buyers.

✅ D. Product Media
Product Media (often linked via Electronic Media Group or related objects) handles images, videos, and other assets attached to products. Public Read Only access ensures external buyers can view product images and media in listings, detail pages, and search results—critical for a visual shopping experience.

✅ E. Price Book
Price Books contain pricing information assigned to products for buyer groups or stores. External access set to Public Read Only enables buyers to see applicable prices (list, sale, tiered) during browsing and checkout. This is essential for displaying accurate pricing without requiring individual record sharing.

Incorrect Options:

❌ A. Accounts
Accounts represent buyer companies but are not directly tied to product visibility on the storefront. External buyers access products via buyer groups and entitlements—not by reading Account records broadly. Accounts typically remain Private or controlled via role/account sharing, not Public Read Only for product viewing.

❌ B. Order Delivery Method
Order Delivery Method relates to shipping/fulfillment options during checkout, not product browsing or initial visibility. It's irrelevant to enabling product views on the storefront—buyers see products before reaching delivery selection, so this object's sharing doesn't impact product display.

Summary
To allow external buyers to browse and view products (including details, images, and prices) on the B2B Commerce storefront, set external OWD to Public Read Only on Catalog, Product Media, and Price Book. These objects form the foundation of product discovery and pricing. Accounts and Order Delivery Method don't require this for product visibility—focus on catalog-related objects during sharing setup. Always test storefront access after changes.

Reference:
Salesforce Help: "Sharing Settings for Commerce, Location, and Location Group Objects" (details OWD for Catalog as Public Read/Write internal but Private external in some contexts; Product Media/Electronic Media Group as Public Read Only)
Salesforce Help: "Configure External Sharing Settings for Storefront Users" (covers Public Read Only for key CC-prefixed and related objects enabling storefront access)

Explanation

Tiered pricing, also known as volume pricing, applies different price breaks or discounts based on the quantity purchased. This requires a pricing rule that defines specific price points or adjustments for set quantity ranges (tiers).

✅ A. Price Adjustment Schedules
Price Adjustment Schedules are the native feature for creating tiered or volume pricing. Administrators can define multiple tiers, each with a minimum quantity and a corresponding discount or fixed price, which automatically applies during checkout.

❌ B. Priority Pricing
Priority Pricing refers to the order in which multiple pricing rules (like promotions and adjustments) are evaluated and applied. It determines which rule wins, but it is not the tool for defining the tiered quantity brackets themselves.

❌ C. Stepped Pricing
While this is a descriptive term for tiered pricing, it is not the official name of the feature within Salesforce B2B Commerce. The correct configuration object is the Price Adjustment Schedule.

❌ D. Promotions Flow
Promotions Flow is used to set up and manage promotional rules (like buy-one-get-one) and discount codes. It is not designed for the specific structure of quantity-based tiered pricing on a single product's base price.

Summary:
To implement quantity-based tiered discounts, configure a Price Adjustment Schedule. This feature allows you to define multiple price points for different quantity thresholds on a product.

Reference:
Salesforce Help: Create a Price Adjustment Schedule

Explanation

In Salesforce B2B Commerce, categories are controlled for storefront visibility using the Show in Menu attribute. If a category appears in the storefront navigation but shouldn’t, the Administrator must disable this attribute. This hides the category from the menu without removing it from the catalog, allowing products to remain active while controlling display.

🟢 Correct Option

🟢 C. Disable the Show in Menu attribute
Disabling Show in Menu hides the category from the storefront navigation menu. The category and its products remain active in the catalog but are not visible to buyers browsing the store. This is the standard method to control category visibility in B2B Commerce.

🔴 Incorrect Options

🔴 A. Disable the Display in Menu attribute
“Display in Menu” is not an official B2B Commerce attribute. Selecting this option would not affect storefront navigation, making it invalid.

🔴 B. Enable the Do Not Display in Menu attribute
There is no out-of-the-box “Do Not Display in Menu” attribute in B2B Commerce. This option does not exist in the product catalog or category settings.

🔴 D. Enable the Hide in Menu attribute
Similarly, “Hide in Menu” is not a standard attribute for categories. B2B Commerce uses Show in Menu, not “Hide in Menu,” to control visibility.

Summary
To hide a category from the storefront menu without removing it from the catalog, the Administrator should disable the Show in Menu attribute. Other options reference non-existent attributes and will not work.

Reference
Salesforce B2B Commerce Administration Guide – Configure Category Visibility
Salesforce Help: Manage Categories in a B2B Commerce Store

Explanation

Experience Builder is the primary workspace for modifying the UI/UX of a B2B storefront. Because B2B Commerce is built on the Experience Cloud platform, it can be accessed through the standard site management menu in Salesforce Setup. Additionally, to keep the workflow integrated, Salesforce provides a direct link within the Commerce App itself, allowing administrators to move from product management to page design without losing their place.

✅ Correct Options

Option A:
The All Sites menu (found under Digital Experiences in Setup) is the traditional gateway to all sites in an org. Next to the name of each storefront, there is a link for "Builder." Clicking this opens Experience Builder in a new tab, allowing for immediate modifications to the site’s layout, theme, and components before finalizing a Change Set.

Option E:
The Store tile within the Commerce App serves as the dedicated cockpit for a specific store. When you open a Store's record in the app, the "Storefront" or "Experience" tab typically features a prominent "Experience Builder" button. This provides a direct path for commerce administrators to jump into the visual editor while they are already managing store data.

❌ Incorrect Options

Option B:
Experience Cloud Configuration is not a standard, top-level menu item in Salesforce Setup. While there are many individual settings under "Digital Experiences," there is no specific "Configuration" link that serves as a direct launcher for the Experience Builder interface across all sites.

Option C:
All Communities is the legacy name for the site management page. In modern Lightning Experience and B2B Commerce (especially LWR/Aura), this menu has been rebranded to All Sites under the Digital Experiences header. Using the current terminology of the AP-201 exam, "All Sites" is the correct path.

Option D:
Digital Experiences is the parent menu folder in Salesforce Setup. While you must click this folder to see the "All Sites" link, the folder itself does not provide a direct link to the Builder. You must navigate one level deeper into the sub-menu to actually find the launcher for the Experience Builder.

📝 Summary
An Administrator can reach Experience Builder by navigating to Setup > Digital Experiences > All Sites and clicking the "Builder" link. Alternatively, for a more commerce-centric workflow, they can simply open the Store tile within the Commerce App and use the direct builder button provided in the store administration workspace.

🔗 Reference
Salesforce Help: Navigate to Experience Builder

Explanation

C. ✅ Correct Option: At least one product must be marked Active.
For a search index to run, at least one product should be Active. Indexing processes active products, making them searchable. This is a prerequisite for performing a search index.

B. ❌ Incorrect Option: All products must have a SKU assigned.
SKUs are important for product management and identification, but not the requirement for starting an index. SKUs are needed for product identification, but indexing can be initiated without all products having SKUs.

A. ❌ Incorrect Option: All products must have at least one image assigned.
Images aren't required for indexing. Products can be indexed without images, impacting display but not indexing. Images enhance product presentation.

D. ❌ Incorrect Option: At least one product must have a ProductCode assigned.
ProductCode isn't the requirement for indexing. It's an optional field for product management and categorization.

Summary:
At least one product must be marked Active for an Administrator to perform a search index. Active products are required for indexing and making products searchable.

Reference:
Salesforce Help: Search Index Requirements