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

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.

Externally hosted product images must be permitted by Salesforce ' s Content Security Policy before the storefront can retrieve and display them. Salesforce instructs Administrators to register an external image host as a Trusted URL and enable the img-src CSP directive. Trusted URL definitions can also use an asterisk as a wildcard when multiple applicable subdomains must be covered. Therefore, if the imported image URLs are structurally correct but their host or subdomain is not included by the existing trusted-site configuration, adding the appropriate wildcard CSP Trusted Site resolves the resource-loading restriction. Activating the product does not authorize the browser to load content from an external domain, while disabling Lightning Locker or relaxing the entire CSP is unnecessary and creates broader security exposure.

To limit the products that a Buyer Group can see, an Administrator can useC. Entitlement Policies. Entitlement Policies in Salesforce B2B Commerce control accessto products based on various criteria, including buyer groups. By configuring these policies, an administrator can define which products are visible and available to specific buyer groups, ensuring a tailored and relevant product selection for different segments of buyers.

If an Administrator is unable to select images for a Product record despite having set up a CMS workspace, it could be becauseD. CMS channel was neverconfigured to connect the CMS workspace to the store. Without this connection, content from the CMS workspace, including images, is not available for use within the store.

Salesforce Flow supports multiple execution contexts, and the default execution mode is User or System Context—Depends on How Flow Is Launched . In this mode, the flow does not force one universal security context; instead, the mechanism that launches the flow determines whether it executes in user or system context. Salesforce identifies this configuration as DefaultMode in Flow metadata. By comparison, System Context with Sharing explicitly enforces record-level sharing while bypassing some user permissions, and System Context Without Sharing provides broader data access. For a standard checkout flow configured to use the caller ' s appropriate runtime context, the default User or System Context setting is therefore the applicable selection.

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

The issue with the search index not reflecting recent product updates could be due to the automation triggering the search index rebuild too frequently. If the store search index is rebuilt more than five times per hour, as suggested in option(C), it can lead to performance issues and delays in updating the search results. This frequency can overwhelm the system, leading to a queue of rebuild operations that can ' t be processed in a timely manner, causing the search results to become outdated despite the updates to product records.

For investigating additional functionality around international taxation and credit card payments in Salesforce B2B Commerce, an administrator can exploreA. Salesforce Labs add-onsandD. AppExchange connectors. Salesforce Labs provides innovative solutions that can be used as is or customized, while AppExchange connectors offer pre-built integrations that extend the functionality of Salesforce B2B Commerce to meet specific business needs, including payment processing andtax calculations.

B2B Commerce supports product media on both variation parent products and individual child variations. Consequently, administrators must verify media at the correct level when a variation displays an unexpected image. If the child variation has no specific media, the storefront can present the parent ' s image in the variation context, which explains the bottle dis playing the case image. The same visible result occurs when the case image itself has accidentally been associated with the bottle variation. A sibling variation is not the proper source from which another child should inherit its image, and absence of variation media does not mean the category image automatically becomes the variation image as described in option A. Checking the variation ' s Media configuration and its parent relationship isolates these two causes.

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

To meet the requirement that all orders over a certain amount be paid for using a credit card instead of a purchase order, the Administrator should start withB. Add decision logic to hide the option for purchase orders on orders that meet the criteria. This approach involves configuring the checkout flow to dynamically adjust the available payment options based on the order amount, ensuring compliance with the specified payment policy.

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.

CMS content must be in theD. Draftstatus to be editable. This status indicates that the content is in the initial stages of creation or modification and has not yet been finalized for publication. Draft status allows administrators to make changes before the content is reviewed, approved,and published, ensuring that only fully vetted and complete content is made available to end-users.

For Buyer Managers on the storefront, the appropriate profile or permission set is typicallyB2B Commerce User (D). This profile or permission set is designed to provide the necessary permissions for users to perform tasks related to managing purchases, viewing orders, and accessing account-specific pricing and products. The B2B Commerce User role encompasses the functionalities needed by Buyer Managers to efficiently manage their purchasing activities within the B2B Commerce environment.

At the start of setting up a B2B Commerce storefront, theAdministrator needs to configure settings that are crucial for the basic operations of the store. EnablingEnhanced Commerce Orders (B)is essential as it allows for the use of advanced order management features, including complex pricing and discountstructures, which are common in B2B transactions.Enable Zero Quantity (C)is also a key setting, especially for B2B scenarios where orders might be created as placeholders or for backorder items, allowing for zero quantity orders to be processed through the system. WhileOptional Price Books for Orders (A)andReduction Orders (D)can be important in certain contexts, they are not typically the initial settings configured during the setup process.

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 target CMS content at a particular store, an Administrator needs toB.Create CMS content and assign it in Experience Builder. This involves creating content within the CMS workspace and then using Experience Builder to place and assign this content to specific pages or components within the store, ensuring it appears in thedesired location.

To prevent a category from displaying in the navigation menu, the Administrator can useC. Category Exclusion. This feature allows specific categories to be excluded from the navigation menu, even if they are active and contain products. It is a targeted approach to manage the visibility of categoriesin the storefront ' s navigation structure.

To present different user experiences to differentbuyers in a storefront, an Administrator can:

A. Create audiences to define different segments:This allows for the customization of content and experiences based on specific characteristics of user segments.

B. Use page variations:Different page layouts and content can be presented to different audiences, enabling a highly personalized shopping experience for each user group.

To make a custom field named " Edition " on the product object no longer searchable within the Manage Searchable Fields in a Salesforce B2B Commerce site, the Administrator shouldD. Add the Product field to the Search Field Exclusion list. This action explicitly removes the field from the list of fields that are indexed and considered during search operations, thereby making it non-searchable.

Out of the box, an Administrator can control the following aspects of the search settings:

A. Sort Rules:These determine the order in which search results are displayed.

B. Results per Page:This setting controls how many results are shown to the user at one time, impacting the browsing experience.

E. Scheduled Indexing:This allows for the automatic rebuilding of the search index at scheduled intervals, ensuring the search functionality reflects the most up-to-date information.

These settings are crucial for optimizing the search experience, ensuring that users can find what they need efficiently andeffectively.

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.

Valid options fora Price Adjustment Schedule include:

B. Percentage:This allows for discounts or price increases based on a percentage of the original price, providing flexibility in pricing strategies.

C. Range:This option enables the application of different price adjustments based on the quantity or total value of items, allowing for volume discounts or tiered pricing structures.

For an unattended integration that must initiate a search index operation on a fixed schedule, the appropriate design is to use the supported Commerce search-index API and invoke it through scheduled automation. Salesforce exposes Commerce Management REST resources that can create a full or incremental search index for a specified web store. Therefore, the administrator or implementation team should first use the Search Index API documentation to establish the supported request and then schedule an automation process to execute that request at the required weekly time. PimModelBatch is not the supported administrator integration contract for this requirement. A workflow listening for a Platform Event is event-driven rather than inherently satisfying the stated fixed-time weekly schedule. Thus, B and C form the appropriate integration approach.

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

An Administrator can configure an alternative or new checkout flow in theStore tile in the Commerce app (C). This area provides access to store configurations, including checkout process customizations. The Commerce app ' s Store tile allows administrators to define and manage various aspects of the checkout experience, such as payment options, order review, and final confirmation steps, ensuring a seamless and efficient checkout process for users. TheCheckout Button on the Cart page (A),Experience Builder on the Checkout page (B), andProcess Builder Button in Experience Builder (D)are not the primary locations for configuring the checkout flow in Salesforce B2B Commerce.

To defend against session hijacking and cross-site scripting in SalesforceB2B Commerce, an administrator should enableB. Require HttpOnlysetting. This setting helps prevent access to cookie data via client-side scripts, significantly reducing the risk of XSS (Cross-Site Scripting) attacks and protecting session cookies from being hijacked.

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 set up different pricing for different groups of buyers, an Administrator shouldB. Create Price Booksto define different pricing structures andD. Create Buyer Groupsto segment buyers into groups. Price Books can then be assigned to specific Buyer Groups, allowing for differentiated pricing strategies based on the buyer group.

To determine which price is shown to customers with multiple price booksassigned, an Administrator should useC. Pricing Strategies. Pricing Strategies in Salesforce B2B Commerce allow administrators to define rules and criteria for selecting the appropriate price book for a customer, ensuring that the correct prices are displayed based on the customer ' s attributes and the business ' s pricing policies.

To target specific user segments for the homepage, an Administrator should createPage Variations (D). Page variations allow for the customization of content and layout based onaudience segments, such as logged-in users versus guest users, providing a personalized experience based on the user ' s status or other criteria.

To change the layout of search results and category detail pages in Salesforce B2B Commerce, two out-of-the-box options available areD. ListandE. Grid. These layout options allow administrators to present products in a structured list or a grid format, enhancing the user experience by providing clear and organized views of products.

When setting up categories for import using the CSV import tool with categories delimited by a single pipe character, the Administrator canC. Split the categories into separate columns with appropriate labelsorD. Replace the pipes with a forward slash. Both methods organize the category data in a format that the import tool canrecognize and process effectively.

If a language is deleted from Experience Builder,C. The content is no longer visible but is not deleted. This means that while the content associated with that language will not be displayed in the Experience Builder or the storefront, it remains in the system. This allows for the possibility ofre-adding the language at a later time and restoring the visibility of the content without having to recreate it.

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.

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.

When implementing a category hierarchy for a multi-language site with many child categories, an important consideration isC. There is a depth limit for the number of child categories. Salesforce B2B Commerce imposes limits on the depth of the category hierarchy, affecting how deeply nested child categories can be structured within the overall category architecture.

For an object to show up in Salesforce B2B Commerce, it must havetheB2B Commerce license assigned, and no additional add-ons are required for the Buyer Account (C)to appear. The Buyer Account is a fundamental entity in B2B Commerce, representing the customer ' s organization and enabling the management of business-specific data, pricing, and transactions. While Fulfillment Order (A), Billing Schedule (B), and Order (D) are important objects within the B2B Commerce ecosystem, the Buyer Account is crucial for establishing the foundational business relationship in the B2Bcontext.