Certified B2B Commerce Administrator: Salesforce Certified B2B Commerce Administrator Exam

Product and Content Management are two navigation options on the store main page in the B2B Commerce app. The store main page is the landing page for a store or reorder portal in the B2B Commerce app. The navigation options allow admins to access different features and settings for their B2B commerce sites. Product allows admins to manage products, categories, price books, and product variations for their stores. Content Management allows admins to manage content assets, collections, channels, and workspaces for their stores.Reference:[Store Main Page]; [Product]; [Content Management]

Drop ins and AppExchange connectors are two options for investigating additional functionality for Salesforce B2B commerce in the areas of international taxation and credit card payments. Drop ins are prebuilt components that you can use to extend the functionality of your B2B commerce site without coding. AppExchange connectors are third-party applications that integrate with Salesforce and provide additional features and services. For example, you can use Avalara AvaTax Drop-in or Vertex Tax Connector for international taxation, and Stripe Payment Gateway or CyberSource Payment Gateway for credit card payments.Reference:Drop-Ins Overview; [AppExchange]

According to theCheckout Flowpage, checkout flow is a feature that allows you to customize the steps and actions that occur when a user places an order on your B2B Commerce site. Checkout flow is a type of flow that runs in the system context with sharing-enforces record level access. System context with sharing-enforces record level access means that the flow runs with the permissions of the Salesforce system user but respects the sharing rules of your org. This ensures that the flow can access all the necessary data and functionality for checkout but also respects the security and visibility settings of your org. Therefore, option B is correct. Options A, C, and D are false because they are not the context in which a checkout flow needs to run. System context without sharing-enforces record level access means that the flow runs with the permissions of the Salesforce system user but ignores the sharing rules of your org. This could result in data leakage or unauthorized access during checkout. System context without sharing-access all data means that the flow runs with the permissions of the Salesforce system user and has access to all data in your org regardless of sharing rules or field-level security. This could result in data leakage or unauthorized access during checkout. User or system context-depends on how flow is launched means that the flow runs with either the permissions of the user who launched it or the permissions of the Salesforce system user depending on how it was triggered. This could result in inconsistent or unpredictable behavior during checkout.Reference:Checkout Flow, Checkout Flow Overview