Explanation:

✅ A – Document
Documents can be associated with products to provide buyers with downloadable product-related information such as specification sheets, manuals, or installation guides. In B2B Commerce, Documents are supported for exposing reference content to buyers directly from the product detail experience, making them suitable for informational use cases.

✅ D – Image
Images are a core supported product content type in B2B Commerce. They are used to visually represent products on listing and detail pages, helping buyers understand product appearance, features, and variations. Images are essential for merchandising and buyer decision-making.

❌ B – File
Files are primarily designed for internal collaboration and general content sharing across Salesforce. They are not the supported mechanism for surfacing product-related content to buyers in a B2B Commerce storefront, which is why they are not the correct choice here.

❌ C – Asset
Assets represent customer-owned products and are used for service, warranty, and entitlement tracking after purchase. They are not content types and cannot be used to provide pre-purchase product-related information to buyers.

Summary:
Salesforce B2B Commerce supports Documents and Images for providing buyers with product-related information. Files and Assets serve different purposes and are not designed for exposing product content in the storefront.

Reference:
Salesforce Official Documentation – Product Media and Content in B2B Commerce

Explanation

An Administrator wants to use a custom domain for a B2B Commerce store instead of the default domain. To achieve this, they need to configure Salesforce to allow for a custom domain, enhancing brand identity and user experience, and ensuring a seamless customer journey.

A. Create a Custom URL in Setup.
✅ Correct Option: Creating a Custom URL in Setup allows administrators to define a custom domain for the B2B Commerce store, providing a branded experience for customers and reinforcing the company's online identity. This step is essential for establishing a unique web presence. It also enables administrators to manage multiple domains from a single interface.

C. Configure a custom domain and CDN in Setup.
✅ Correct Option: Configuring a custom domain and CDN (Content Delivery Network) in Setup enables administrators to manage the custom domain and optimize content delivery for the store, improving performance and security. A CDN also helps reduce latency and enhance the overall shopping experience. This setup is crucial for high-traffic stores.

B. Add the custom domain to the B2B store in Experience Builder.
❌ Incorrect Option: While Experience Builder is used to customize the store's look and feel, adding a custom domain is done through Setup, making this option incorrect for configuring a custom domain. Experience Builder focuses on design and layout, not domain management. Administrators should use Setup for domain configuration.

D. Enable Custom URL Redirect in the Administration panel of the store.
❌ Incorrect Option: Custom URL Redirects are used for redirecting specific URLs, not for configuring a custom domain for the entire store, serving a different purpose altogether. This feature is useful for managing URL changes or promotions. It doesn't replace custom domain setup.

Summary:
To use a custom domain, administrators should create a Custom URL in Setup and configure a custom domain and CDN in Setup, ensuring a branded, optimized, and secure experience for customers.

Reference:
Salesforce B2B Commerce Admin Guide (Custom Domains)

Explanation:

An Administrator aims to customize the B2B Commerce storefront to enhance branding by adding the company name and logo to the user profile menu. This task involves configuring the storefront’s user interface to reflect organizational identity. Salesforce B2B Commerce provides tools to modify storefront components, ensuring a tailored user experience. The correct approach requires identifying the specific tool or setting that governs the user profile menu’s appearance within the storefront environment.

Correct Option:

✔️ C. Modify the settings for the User Profile Menu component:
The User Profile Menu component in Salesforce B2B Commerce allows Administrators to customize elements like the company name and logo. By accessing the component’s settings in Experience Builder, the Administrator can upload the logo and update text fields to reflect the company’s branding, ensuring a seamless and professional user experience on the storefront.

Incorrect Options:

❌ A. Edit the User Profile Menu in Profile Builder:
Profile Builder is not a Salesforce B2B Commerce tool. It doesn’t exist in the platform’s ecosystem for configuring storefront components. The user profile menu is managed through Experience Builder, not a separate profile-building tool, making this option incorrect for the task.

🚫 B. Modify the User Profile Lightning Record Page in Experience Builder:
Lightning Record Pages are used for internal Salesforce records, not storefront components. The user profile menu in the B2B Commerce storefront is a distinct UI element, configured via the User Profile Menu component, not a record page, rendering this option unsuitable.

🛑 D. Make changes to the User Profile Menu in Setup:
Setup is used for system-wide configurations, not for customizing storefront UI components like the user profile menu. Experience Builder handles storefront-specific customizations, such as branding elements, making this option incorrect for achieving the desired outcome.

Reference:
Salesforce B2B Commerce Experience Builder

Explanation

In Salesforce B2B Commerce, variation products let you offer the same base item (e.g., bed sheet) in different options like lengths (31", 36") under one parent record, avoiding duplicates. The correct setup is: create a custom field on Product2 for the variation value, build a Variation Attribute Set to define the attribute and its values, and assign the set to a single parent product. The system then manages child variations automatically for storefront selection.

Correct Option

✅ B. Create a custom field length_c, a variation attribute set, and a parent product.
This follows the standard process:

Add a custom field (Length__c) on Product2 (usually a picklist).
Create a Variation Attribute Set, link it to the field, and define values (31", 36", etc.).
Assign the set to one parent product only.
This enables proper child variation records and storefront functionality.

Incorrect Options

❌ A. Create a custom field length_c, a variation attribute set, and three parent products.
Wrong — variations use one parent product only. Multiple parents create duplication, complicate management, pricing, and inventory, and break the intended variation model.

❌ C. Create a custom field length_c and a parent product with length selected as variation field.
Incomplete. The custom field is needed, but without a Variation Attribute Set to configure values and behavior, child variations won’t generate or display correctly.

❌ D. Create a custom object ProductWithLength_c, a custom field, and a parent product.
Incorrect and unsupported. B2B Commerce uses the standard Product2 object — custom objects disrupt catalog, search, pricing, cart, and checkout features.

Summary
For products varying by length: create a custom field on Product2, set up a Variation Attribute Set with the values, and assign it to one parent product. This parent-child approach keeps the catalog efficient and user-friendly.

Reference:
Salesforce Help – Create Attributes for Product Variations in B2B and D2C Stores

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