Pass the Salesforce Administrator AP-201 Questions and answers with ExamsMirror

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

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 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 use an approved entity in a CRM collection, an Administrator must set up aCRM List view (C). This setup enables the organization of entities such as contacts, accounts, or custom objects within the CRM to be part of targeted collections, facilitating segmentation and targeted actions. The CRM List View provides a framework for defining the criteria and filters that determinewhich records are included in a collection, supporting personalized and efficient CRM strategies. Global (A), Sales (B), and Service (D) List Views are also used within Salesforce but are tailored for broader or different contexts than CRM collections.

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.

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 safely authorize a payment gateway, an Administrator needs toB. Create a Named Credentialin Salesforce Setup. Named Credentials provide a secure way of storing authentication details, including endpoint URLs, usernames, passwords, and token endpoints, which are essential for securely connecting to external payment gateway APIs.

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.

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.