Salesforce AP-201 Dumps

To ensure customers can only purchase products in increments of five, an Administrator must:

A. Connect the product to a Quantity Rule:This involves creating a Quantity Rule that specifies the allowed increments for product quantities and then associating this rule with the specific products.

D. Create Purchase Quantity Rules:This step involves defining the rules that govern purchase quantities, including setting the required increments, which in this case would be increments of five.

These steps ensure that when customers add products to their cart, they can only do so in the specified increments, aligning with the company ' s sales strategy and operational requirements.

For the most efficient process, the following Related Lists should be added to the Account page layout:

B. Community Membership:This provides visibility into the user ' s access and roles within the commerce community, facilitating management and support.

D. Carts:This allows for quick access to the user ' s current and past shopping carts, enabling support and analysis of shopping behavior.

These additions enhance the administrative capabilities, providing quick access to essential information for managing accounts and supporting users within the B2B Commerce platform.

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.

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.

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

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.

To provideproduct-related information, an administrator can use:

A. Document:This could include product manuals, specifications, or any other document that provides detailed information about the product.

D. Image:High-quality images can be used to visually represent the product, its usage, or any specific features, contributing to a better understanding of the product for the buyer.

These content types are instrumental in delivering comprehensive product information, enhancing the buyer ' s journey by providing allnecessary details to make an informed purchase decision.

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.

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.

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.

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.

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.

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

To ensure that guest users have read access to the Product object, an Administrator shouldB. Modify the guest user profile to provide access to the Product object. This involves adjusting the permissions within the guest user profile settings to grant read access specifically to the Product object, ensuring that guest users can view product details without compromising data security.

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.

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

By enabling Commerce in Setup, the object added to the data model isB. Store. The Store object is a fundamental component of Salesforce B2B Commerce, representing the digital storefront where products and services are offered to customers.It serves as the central entity around which various commerce functionalities are configured and managed.

Catalogs and stores are top-level commerce configuration records and are established individually rather than treated as ordinary rows in the product bulk-import process. Salesforce ' s B2B Commerce import functionality is specifically designed to bulk import products and related information, including category and price-book associations. By contrast, Salesforce documents a separate process for creating a catalog and assigning it to a store, and store creation itself is handled through the Commerce store setup process. A B2B store can have one assigned catalog at a time, although a catalog can be associated with more than one store. Because products and related pricing information are supported through bulk commerce-data import mechanisms, they do not fit the “must load individually” requirement in this question. Therefore, Catalogs and Stores are the correct selections.

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

Before the checkout flow is usable, the following two tasks need to be completed:A. Configure the Checkout flow in Flow Builder, which involves setting up the logic and steps for the checkout process; andD. Add the checkout flow to the Checkout Page in Experience Builder, which integrates the configured flow into the actual checkout page that users interact with during the purchasing process.

B2B Commerce uses the Salesforce product data model, so existing Product records do not need to be copied into a separate Commerce Products object or processed through a Product Converter. To make existing products discoverable in a B2B storefront, they must participate in the store ' s merchandising structure by being associated with the appropriate catalog and categories. Buyer visibility must also be established through entitlement configuration. Salesforce documents that entitlement policies determine which products and product-related information a buyer group can access, and products are explicitly assigned to those policies. This architecture allows an organization to reuse the same core Product records across sales and commerce processes while applying storefront-specific categorization and buyer access. Therefore, assigning the existing products to the commerce catalog/categories and applicable entitlement policy is correct.

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

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 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.

The out-of-the-box integrations provided with Salesforce B2B Commerce includeA. Inventory, Pricing, Tax. These integrations allow for real-time access to inventory levels, dynamic pricing models, and accurate tax calculations, providing a seamless and efficient commerce experience.

Salesforce B2B Commerce uses Salesforce CMS workspaces to manage and associate product media with commerce stores. Salesforce specifically states that when images are imported globally for all stores through a CSV file, the import must identify a CMS workspace where those imported images are linked. If an appropriate CMS workspace does not already exist, the Administrator must create one before beginning the global image import. An external image host can hold the physical image files, but creating such a host is not the required prerequisite identified by the global import process. Likewise, Image Catalog and Media Catalog are not the required Salesforce CMS containers for this operation. Therefore, creating a CMS Workspace is the required step before performing the global image import.

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

To create personalized experiences for different groups of buyers, an Administrator can use the following criteria types to create audiences for a component on a Store page:

B. Permission Set:This allows for content personalization based on the permissions granted to the user, enabling targeted content delivery.

C. Profile:Users with different profiles can be presented with tailored content, ensuring relevance and enhancing the user experience.

E. User ' s Location:Personalizing content based on the user ' s geographical location can significantly improve relevance and engagement.

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.

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 ensure customers can only purchase products in increments of five, an Administrator must complete the following steps:B. Create Purchase Quantity RulesandC. Connect the product to a Quantity Rule. PurchaseQuantity Rules define the increments in which products can be purchased, and connecting these rules to specific products enforces the desired purchasing increments.

Before creating a storefront in a new Salesforce sandbox for B2B Commerce, an Administrator should configure the following settings:A. Enable Digital Experiencesto use web-based engagement platforms,B. Enable Commerceto activate commerce functionalities, andC. Enable Ordersto manage sales orders within the commerce environment.

TheSystem Context with Sharing—Enforces Record-Level Access (D)is crucial to B2B Commerce because it ensures that users can only view products and related data that they are authorized to see, maintaining data security and privacy. This setting is particularly important for storefronts where products need to be displayed according to specific customer agreements, contracts, or profiles. It doesn ' t directly relate to checkout (A), content synchronization (B), or guest browsing (C), but rather to the fundamental aspect of product visibility and access control on the storefront.

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.

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 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.

For successful operation of B2B on Lightning Experience checkout, the following preferences need to be enabled:

A. Enable Account Relationships:This allows for the management ofcomplex account hierarchies and relationships, which is crucial for B2B transactions that often involve multiple entities within the same organization.

D. Enable Orders:This is fundamental for the checkout process, as it allows for the creation and management of customer orders within the Lightning Experience, providing a seamless checkout process.

To add a B2B Commerce store to an existing site, the Administrator could use theA. Customer Account PortalorB. Build Your OwnExperience Cloud templates. The Customer Account Portal templateprovides a framework for account management and commerce functionalities, while the Build Your Own template offers flexibility in designing a custom experience that can include B2B Commerce features.

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.

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

To enable external buyers to view products on the storefront, the entities that typicallydo not require " Public Read Only " access arePrice Book (A)andProduct Media (D). Price Books, while crucial for defining product pricing, are usually managed and accessed by internal users rather than external buyers directly. Product Media, such as images and videos, are essential for product display but do not necessarily require direct access by external buyers as they are typically embedded within product pages or catalogs.Order Delivery Method (B)andCatalog (C), on the other hand, are more integral to the shopping experience and may require broader access levels to ensure external buyers can view available products and delivery options.

Within the Commerce app, the two workspaces available areProduct (A)andContent Management (E). The Product workspace is dedicated to managing product catalogs, details, and variations, providing tools for Administrators to curate and organize their product offerings. Content Management is a workspace focused on the creation, management, and deployment of content across the commerce site, including marketing materials, informational content, and other web content. While Search (B), Commerce Reports (C), and Pricing (D) are critical aspects of B2B Commerce, they are typically managed through other sections or setups rather than being categorized as separate workspaces within the Commerce app.

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.

To configure the store to use a new payment gateway, an Administrator needs toUpdate the payment gateway settings on the Payment and Billing subflow (A). This involves configuring the new gateway ' s details and parameters within the relevant settings, ensuring that the store ' s payment processing is correctly aligned with the new gateway.

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.

From the Commerce App menu, three objects that are accessible includeA. Accounts,C. Buyer Entitlements, andE. Buyer Groups. These objects are integral to managing the relationships, entitlements, and groupings of buyers within the B2B Commerce environment, facilitating the administration of commerce activities.

To leverage an existing Salesforce Billing product implementation in their B2B Commerce storefront, an administrator shouldD. Create a custom Component in Experience Builder. This custom component can integrate Salesforce Billing functionality into the B2B Commerce storefront, allowing for seamless invoice and payment processing within the commerce experience.