To allow a user to switch between accounts in the store to purchase for multiple accounts, the necessary tasks includeA. Add the Switch Accounts component to the Store home page,B. Assign the Account SwitcherUser permission to the purchasing user, andC. Share the Account with the purchasing user. These steps enable a user-friendly mechanism for buyers to manage purchases across different accounts, enhancing the purchasing experience.

To migrate Store configurationsfrom a development sandbox to a QA sandbox, an Administrator shouldUse Data Migration (A)to transfer configuration data and related records between environments.Export Store Configuration (D)is also a crucial step as it allows the Administrator to create a deployable package of the store ' s settings, which can then be imported into the QA environment.Apply Store Configuration (B)andPublish the Store (C)are actions taken after the configurations have been successfully migrated and are part of the setup process in the new environment, rather than the migration process itself.

The field type that cannot be added as a Searchable field isC. Formula. Formula fields are calculated fields that do not store data themselves but rather display data based on the formula ' s logic and the values of other fields. Due to their dynamic nature and lack of stored data, they cannot be indexed or made searchable like other static field types.

The limit on the category hierarchy in terms of child records in B2B Commerce isC. 5.0. This means that within the category structure, a parent category can have up to five levels of child categories beneath it. This hierarchical structure allows for organizing products into categories and subcategories, providing a clear and navigable structure for users.

Multi-Factor Authentication adds an additional authentication factor beyond a username and password, substantially strengthening account-login security. Salesforce describes MFA as requiring users to provide two or more pieces of evidence to establish their identity, reducing the risk associated with compromised credentials, phishing, and account takeover. B2B Commerce is built on the Salesforce Platform and supports Salesforce MFA capabilities. Profiles, permission sets, and permission set groups primarily determine authorization—what applications, objects, fields, and functions an authenticated user can access. They do not, by themselves, provide an additional authentication factor during sign-in. Because the requirement specifically asks for an extra security layer for user authentication on the storefront, Multi-Factor Authentication is the appropriate configuration.

================

An Administrator can directly access Experience Builder to make changes to a storefront fromA. All SitesandD. Digital Experiences. These areas within Salesforce provide entry points to the Experience Builder, where administrators can modify the design and layout of storefronts, including components and pages.

An Experience Cloud customer user associated with a B2B Commerce store can access the storefront through the credentials and login information provided as part of the welcome-email process. Salesforce also provides administrators with the Log in to Experience as User action from the external user ' s Contact record, which is particularly useful for validating storefront configuration and troubleshooting access. Salesforce documentation confirms that external Experience Cloud users are represented through contacts or person accounts and that the login-as action is available from the Contact record when appropriate permissions and site membership are configured. A Contact Address record contains address information rather than an authentication entry point, while the Account record itself does not provide the equivalent customer-user login action. Therefore, the Welcome Email and Contact are the two applicable locations.

================

To deploy and activate the full B2B Commerce experience for internal and external users, the three configuration aspects that must be set up outside the Commerce App includeB. Experience Sites, which involves configuring the digital experience platforms for users;C. Multi-Factor Authentication, which is a security measure to verify user identities; andD. Profiles and Permission Sets, which are essential for defining access controls and permissions for different types of users within the system.

To enable an existing Account for the storefront and checkout, the Administrator shouldA. Assign the Account to theappropriate Buyer Group, ensuring the account is associated with the correct group for product access and pricing, andC. Add Shipping and Billing Addresses to the Contact Point Address object, which is necessary for processing orders and shipping products.

On the Buyer Access page, the following guest browsing related optionsare visible:

B. Buyer Groups:This option allows administrators to view and manage different buyer groups, facilitating tailored experiences for different segments of buyers.

C. Currency of the Guest Buyer Profile:This shows the currency settings for guest buyers, ensuring that products and transactions are displayed in the appropriate currency for a seamless browsing experience.

E. Guest Buyer Profile Name:This identifies the profile used for guest buyers, allowing administrators to customize and manage access and experiences for unauthenticated users browsing the store.

These options play a crucial role in managing and customizing the experience for both guest and authenticated buyers, enhancing the flexibility and effectiveness of the B2B Commerce platform.