In which context does a checkout flow need to run?

In which context does a checkout flow need to run?
A . System Context Without Sharing- Enforces record Level Access
B . System Context With Sharing- Enforces RecordLevel Access
C . System Context Without Sharing- Access All Data
D . User or System Context- Depends on How Flow is Launched

Answer: 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