Free Practice Questions for the Salesforce Administrator AP-201 Exam (2026 Updated)

In the Commerce App, an Administrator can bulk updateB. ProductsandC. Catalogs. Bulk updating allows for efficient management and modification of multiple records at once, streamlining the process of maintaining product listings and catalog structures.

To enable the Order Summary object in Salesforce B2B Commerce, the settings that need to be enabled includeB. Order PreferencesandC. Commerce Features. These settings configure the order management capabilities and activate various commerce functionalities, respectively, enabling a comprehensive overview of orders within the platform.

If a company already has an Experience Cloud Site and is implementing B2B Commerce, an Administrator shouldA. Drag and drop the Commerce components onto the proper pages in Experience Builder. This approach allows for the integration of B2B Commerce functionalities into the existing site by utilizing the modular components available in Experience Builder, tailored to the commerce needs.

QUESTIONNO: 72

Which two options are available for providing an out-of-the-box mobile experience to Salesforce B2B Commerce Buyers?

A. Cloudcraze Mobile

B. Android SDK C

C. Responsive web experience

D. Mobile app via Mobile Publisher

Answer: C, D

For providing an out-of-the-box mobile experience to Salesforce B2B Commerce buyers, the available options includeC. Responsive web experience, which ensures that the storefront adapts to various screen sizes and devices, andD. Mobile app via Mobile Publisher, which allows for the creation of a branded mobile app that offers a native mobile experience to users.

To modify the account or person account associated with the OrderSummary without Salesforce Order Management licenses, it ' s necessary thatC. The OrderLifeCycleType field on the associated OrderSummary is set to UNMANAGED, indicating thatthe order is not being managed by Salesforce Order Management, andD. The user executing this action has either the " Edit Unmanaged Order Summaries " or " B2B Commerce Integrator user " system permission, granting them the ability to make changes to unmanaged orders.

To send Order confirmation emails to Buyers, the necessary configuration steps includeCreating an Email template (A)to define the content and format of the email,Setting up Organization-Wide Addressesto ensure emails are sent from a verified domain,Creating an Email Alertto trigger the email sending process, andAdding an Auto-launched flowto automate the email sending process based on specific criteria or events, such as order confirmation. This setup ensures that buyers receive timely and informative confirmation emails, enhancing the customer experience.

For search functionality, an Administrator can setA. Text,B. Checkbox, andD. Picklistfield types as filterable fields. These field types can be used to create filters that help users refine search results based on specific criteria, enhancing the search experience by allowing for more targeted and relevant results.

For setting up a Priority Pricing Model, the Priority field that determines the priority of pricing is found on theD. Buyer Group Price Bookobject. This field allows administrators to define the precedence of price books for different buyer groups, ensuring that the correct pricing is applied based on predefined priorities.

To set up Tiered Pricing fora product, an administrator needs to configureA. Price Adjustment Schedules. This functionality allows for the creation of pricing tiers that apply different discounts based on the quantity of items purchased, enabling volume-based pricing strategies.

To create variation products for bed items that vary by three different lengths, the Administrator shouldB. Create a custom field length_c, a variation attribute set, and a parent product. The custom field length_c will store the different lengths, the variation attribute set will organize these variations, and the single parent product will represent the base item from which the variations derive.

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.

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

Within the Experience Site Administration Workspace, membership with an Experience Site can be established throughB. Permission Set GroupsandD. Permission Sets. These Salesforce features allow administrators to grant users access to Experience Sites by defining and assigning the appropriate permissions and access levels.

To adjust the duration of a cart checkout session, an Administrator should:

A. Update TTL Properties under Order Settings in Setup:TTL (Time To Live) properties determine the duration for which a session remains active. Adjusting these settings can extend or shorten the checkout session duration.

C. Update the CheckoutTimeToLive property on a Webstore:This directly affects how longa checkout session remains active before timing out, ensuring that customers have adequate time to complete their purchases.

If search filters are not visible on the Category Detail page when viewing the storefront in Spanish, it could be due toThe picklist value ' s translations not being completed in Translation Workbench (C). The Translation Workbenchin Salesforce allows Administrators to provide translations for various UI elements, including picklist values used in search filters. If these translations are incomplete or missing, the filters may not display correctly in the specified language. This issue highlights the importance of comprehensive translation efforts to ensure a seamless multilingual user experience. Browser translation issues (A), site page variations (B), and untranslated category data (D) can also affect localization, but the visibility of search filters is directly tied to the completeness of translations in the Translation Workbench.

To add additional languages to a B2B Commerce site, an Administrator must take the following three steps:B. Enable Translation Workbench, which is a tool for translating text and customizations into different languages;D. Enable Data Translation, which allows for the translation of data records; andE. Add the Supported Language field to the Store page layout, which specifies which languages are supported by the store.

To rebuild the Search Index in the B2B Commerce App, the Administrator should:

C. Click on Search Reindexing in the Quick Actions:This option directly initiates the reindexing process from the store record page, updating the search index to reflect the most current data across products, categories, and content, thereby improving search accuracy and performance.

Store Migration is the B2B Commerce capability used to move a configured storefront between Salesforce environments. Salesforce documents the store-migration process for scenarios such as moving configuration from a sandbox to production. The administrator exports the store configuration, includes the required Store Configuration and Site.com metadata in a change set, deploys that change set to the target environment, and then applies the exported configuration. Store Publish is associated with making storefront changes available rather than transferring configuration between Salesforce orgs. Commerce Importer is intended for commerce data import scenarios, while Migration Toolkit is not the standard B2B Commerce feature identified for this operation. Therefore, Store Migration is the appropriate feature for deploying store configuration from one org to another.

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

The standard B2B Main Checkout Flow template includes sub-flows forShipping Method (A),Billing Address (B), andTaxes (E). These sub-flows are integral to the checkout process, ensuring that shipping, billing, and tax calculations are handled efficiently and accurately during the checkout procedure.

Salesforce provides two standard approaches for delivering B2B Commerce experiences to mobile users. First, the storefront itself is built with responsive Experience Cloud commerce templates and components, allowing buyers to use the web storefront across different screen sizes without requiring a separate mobile implementation. Second, Salesforce supports Mobile Publisher for Experience Cloud , which can transform an LWR-based B2B store into a branded native application for Apple and Google Play while rendering the existing store experience. An Android SDK is not the standard administrator-facing out-of-the-box delivery mechanism described here, and CloudCraze Mobile is not the current native B2B Commerce mobile solution. Therefore, the supported answers are the responsive web storefront and a Mobile Publisher application, making B and C correct.

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

A defining characteristic of B2B commerce is that different business buyers can have contractual access to different products, pricing, and purchasing conditions. Salesforce B2B Commerce implements this through Buyer Groups, Entitlement Policies, and Price Books. An Entitlement Policy acts as a gatekeeper that determines which products and prices a particular buyer segment can access. This supports negotiated contracts and account-specific purchasing relationships that are common in business-to-business selling. B2B storefronts can still provide high-quality user experiences, accept credit cards when configured, and calculate applicable taxes, so options B, C, and D are not inherent differences between B2B and B2C commerce. Product entitlement differentiation is therefore the correct distinction.

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

Before an administrator can see orders, they must:

D. Give Visible Field-Level Security on the Sales Store field for Orders:This ensures that the administrator has the necessary permissions to view order-related information associated with the store, enabling effective order management and oversight.

This step is crucial for administrators to perform their roles effectively, ensuring access to critical sales and order information.

To add a B2B store to an existing site, two conditions required areA. The existing site should use the Build your own (Aura), Customer Portal, or B2B template, ensuring compatibility with B2B Commerce functionalities, andD. The site should not have a store created, as each site can typically support one B2B store.

Salesforce CMS separates content management from the destinations where that content is published. A CMS workspace is the shared repository in which content is created and maintained, while channels identify the endpoints that consume published content. Salesforce documentation explains that content published in a workspace becomes available to the channels associated with that workspace. For Commerce stores, each store can have its own public channel, and those store channels can be added to the same CMS workspace. This design allows the marketing team to maintain shared content once while distributing it independently to both storefronts. Creating separate workspaces would unnecessarily duplicate content administration, while using only one channel would not correctly represent two distinct store publishing endpoints. Therefore, one shared workspace with one channel per store is correct.

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

Salesforce B2B Commerce product imports use the Product2 active status to determine whether a newly created product is active. Salesforce documentation specifies that the Product isActive import column corresponds to Product2.IsActive , and newly created products are inactive by default. Setting this value to true activates the imported product. Therefore, adding the IsActive column and setting it to True is the correct action. The alternatives use field names that do not represent the standard Product2 activation field. After the product is correctly imported, catalog/category assignments, entitlement policies, and an updated commerce search index determine whether an eligible buyer can discover it through storefront search and category pages. Thus, option C correctly addresses the missing activation information in the CSV file.

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

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.

In Salesforce B2B Commerce, administratorscan enhance product pages by adding various types of content. Out of the box, the options include:

B. One or more Attachments:Administrators can attach multiple files to a product. These attachments can include manuals, specifications, or additional information relevant to the product.

C. Up to eight Product Detail Images:This allows for a more comprehensive display of the product from different angles or in different use cases, enhancing the buyer ' s understanding and visualization of the product.

E. Oneor more Product Banner Images:These can be used to highlight key features, promotions, or any other important information related to the product at the top of the product page.

These features are designed to provide a rich, informative, and engaging product experience for the buyers, directly out of the box, without the need for custom development.

To ensure that allautomated emails are sent from a " no-reply " email address, the Administrator should:

B. Create an Org-Wide Email Address in Setup:This allows for the configuration of a default email address (such as a " no-reply " address) that will be used for all outgoing emails from the Salesforce org, ensuring consistency and controlling the reply behavior.

Tostop welcome emails from being sent to new members joining the store, an Administrator canDisable the Send welcome email setting in the Administration tab in Experience Builder (D). This setting controls the automatic dispatch of welcome emails upon newuser registration, and disabling it prevents these emails from being sent. This action offers a direct way to manage communication preferences within the Experience Builder, aligning the store ' s engagement strategies with business needs and user expectations. Unchecking Send Email settings (A) and modifying email configurations in Setup (B, C) are also relevant to email management, but the specific control for welcome emails is found within the Experience Builder ' s Administration settings.

To resolve the issue where a Buyer Manager cannot review the activity of other users due to an errormessage, the administrator shouldD. Verify Membership by Profile under Administration in Experience Builder. This ensures that the user has the appropriate access and membership settings to participate in the B2B Commerce experience and perform their roleeffectively.

To quickly provide basic reports like Orders by Date and Total Orders in a new B2B Commerce deployment, the fastest way is toInstall the Commerce Reports under Commerce Setup (B). This feature provides a set of pre-built reports tailored for commerce analytics, allowing Administrators to quicklydeploy essential reporting tools to stakeholders. While Salesforce Labs (A) and AppExchange (C) offer valuable resources and templates, Commerce Reports within Commerce Setup are specifically designed for rapid deployment within the B2B Commerce context. Advanced Reports (D) offer more detailed insights but may require additional configuration.

To move the B2B store configuration from a sandbox to a production environment, an Administrator shouldA. Add the Store Configuration to a change setandC. Export the store settings with Data Loader. The change set allows for the transfer of configuration settings, while the Data Loader can be used to migrate data related to the store setup, ensuring a smooth transition to the production environment.

After cloning and saving the out-of-the-box checkout flow template, the next step that needs to be done before it can be used isA. Activate the flow. Activation makes the flow available for use, enabling it to be triggered as part of the checkout process in the B2B Commerce store.

To configure Salesforce for a custom domain for a B2B Commerce store, the Administrator shouldA. Create a Custom URL in Setup, defining the custom domain to be used, andC. Configure a custom domain and CDN in Setup, ensuring that the domain is properly linked to the Salesforce environment and content is delivered efficiently via a Content Delivery Network (CDN).

For selling products without physical delivery, the minimum objects involved includeB. CartDelivery Charge Group,C. Cart Delivery Group, andE. Cart Delivery Group Method. These objects allow for the configuration of delivery options that do not involve physical shipping, such as digital delivery or services, by defining how delivery charges are applied and managed within the cart and order processes.

To preventa " Products " category from being displayed as requested by the Store Manager, the Administrator shouldDisable the Display in Menu attribute (A). This action will remove the category from the storefront navigation menu, ensuring it does not appear tostore visitors. This approach allows for flexibility in managing how products and categories are presented on the storefront, aligning with business requirements and preferences. The other options, such asEnable the Do Not Display in Menu attribute (B),Disable the Show in Menu attribute (C), andEnable the Hide in Menu attribute (D), are not standard attributes in Salesforce B2B Commerce for controlling menu display.

To configure the checkout time-to-live in Salesforce B2B Commerce, an Administrator shouldD. Update TTL properties in Order Settings under Setup. This involves accessing the Order Settings in the Salesforce Setup menu and adjusting the Time To Live (TTL) properties, such as CheckoutTimeToLive, todefine the duration for which a checkout session remains active before expiring.

For implementing t-shirts that come in multiple sizes and colors, anAdministrator shouldC. Create Product Variationsfor each size and color combination, andD. Create a T-Shirt Parent Productwhich will serve as the main product record from which all the variations derive. This setup allows for efficient management of product variations while providing a streamlined shopping experience.

The advantages of having Commerce and CRM data together includeA. Personalized experience based on a history of interactions, which allows for tailored shopping experiences based on the customer ' s previous engagements, andC. Reduced number of integrations with other systems, simplifying the architecture and reducing the potential points of failure or data inconsistencies.