CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. B2B-COMMERCE-ADMINISTRATOR

Free B2B-COMMERCE-ADMINISTRATOR Exam Braindumps (page: 16)

Page 16 of 65
PDF with 256 Questions

Which two places can the administrator go to set up variation products using the B2B commerce apps navigation menu?

  1. Products
  2. Commerce setup
  3. Entitlement Policies
  4. Product Workspace
  5. Catalogs.

Answer(s): A,D

Explanation:

According to the Product Variations and Attributes page, product variations and attributes are features that allow you to create and manage products that have different versions or options, such as size, color, style, etc. Product variations and attributes can be set up using the B2B Commerce app navigation menu in two places: Products and Product Workspace. Products option allows you to access the product list view, where you can create, edit, delete, clone, or import/export products. Product Workspace option allows you to access the product workspace, where you can view and edit product details, such as name, description, status, visibility, category, image, etc. You can also add product variations and attributes in the product workspace by using the Variation Grouping tab or the Guided Setup tab. Therefore, options A and D are correct. Options B, C, and E are false because Commerce Setup, Entitlement Policies, and Catalogs are not places where you can set up product variations and attributes using the B2B Commerce app navigation menu. Commerce Setup option allows you to install components for your B2B Commerce site, such as reports, dashboards, sample data, etc. Entitlement Policies option allows you to manage entitlement policies for your B2B Commerce site, such as minimum order quantity, maximum order quantity, reorder frequency, etc. Catalogs option allows you to manage catalogs and catalog assignments for your B2B Commerce site. Catalogs are collections of products that are available for a store or a reorder portal.


Reference:

Product Variations and Attributes, Product Variations and Attributes Overview



In which context does a checkout flow need to run?

  1. System Context Without Sharing- Enforces record Level Access
  2. System Context With Sharing- Enforces RecordLevel Access
  3. System Context Without Sharing- Access All Data
  4. User or System Context- Depends on How Flow is Launched

Answer(s): B

Explanation:

According to the Checkout Flow page, 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



What needs to be done after cloning and saving the out-of-box checkout flow template before it can be used?

  1. Change the permission on the existing checkout flow.
  2. Rename the existing Checkout Flow in place
  3. Activate the flow.
  4. Add a version letter.

Answer(s): C

Explanation:

According to the Checkout Flow page, 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 can be created or modified using Flow Builder in Salesforce Setup. To create a checkout flow from scratch or from an existing template, you need to do the following steps:

Navigate to Flow Builder in Salesforce Setup.

Click New Flow or Open a Template.

Select Checkout Flow as the flow type.

Add or edit elements for each step of your checkout process.

Save your flow with a unique name and description.

Activate your flow so that it can be used on your B2B Commerce site. Therefore, option C is correct.

Option A is false because changing the permission on the existing checkout flow is not a step that needs to be done after cloning and saving the out-of-box checkout flow template before it can be used. The permission on the existing checkout flow template is already set to system context with sharing-enforces record level access by default and does not need to be changed.

Option B is false because renaming the existing checkout flow in place is not a step that needs to be done after cloning and saving the out-of-box checkout flow template before it can be used. Renaming the existing checkout flow template would overwrite the original template and prevent you from using it again. You should clone the existing checkout flow template and save it with a new name instead.

Option D is false because adding a version letter is not a step that needs to be done after cloning and saving the out-of-box checkout flow template before it can be used. Adding a version letter is an optional step that can help you keep track of the changes you make to your checkout flow over time, but it is not required for using your checkout flow on your B2B Commerce site.


Reference:

Checkout Flow, Checkout Flow Overview



Why is the System context with Sharing-Enforces Record Level Accessimportant to B2B Commerce?

  1. It is required to check out.
  2. It is required for guest browsing.
  3. It is required to synchronize content.
  4. It is required to view products in the storefront.

Answer(s): A

Explanation:

According to the Checkout Flow page, 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. One of the reasons why system context with sharing-enforces record level access is important to B2B Commerce is that it is required to check out. Checking out is the final step of the checkout process where the user confirms their order details, payment method, shipping address, and shipping method. To check out, the flow needs to run in system context with sharing- enforces record level access so that it can create an order record, update the cart status, send an order confirmation email, and perform any other actions that are configured for checkout. Therefore, option A is correct. Options B, C, and D are false because system context with sharing-enforces record level access is not required for guest browsing, synchronizing content, or viewing products in the storefront. Guest browsing is a feature that allows anonymous users to browse your site without logging in or creating an account. Synchronizing content is a feature that allows you to sync content assets between Salesforce CMS and B2B Commerce. Viewing products in the storefront is a feature that allows users to see the products that are available for purchase on your site.


Reference:

Checkout Flow, Checkout Flow Overview



Page 16 of 65



Post your Comments and Discuss Salesforce B2B-COMMERCE-ADMINISTRATOR exam with other Community members:

Praj commented on December 16, 2023
The Page offered 256 questions - After buying the PDF format file only has 136 Question - Why such a scam
Anonymous
upvote