By default, flows execute in user context, which respects the running user’s permissions and sharing rules. However, in certain scenarios, such as when creating or updating records that users may not have access to, flows can be configured to run in system context.
System context means:
The flow bypasses the user’s field-level security, object permissions, and sharing rules.
This is useful when automation must enforce business logic regardless of user access.
Correct Option:
D. System context — This is the only option that refers to Salesforce’s official execution context override for flows.
Incorrect Options:
A. RunAs context — Refers to Apex unit testing, not flow execution.
B. User context — Is the default behavior; not used to override security.
C. Debug context — Not a real execution mode in flows.
Reference Extracts from Salesforce Process Automation Study Guide:
“You can configure certain flows to run in system context so that they ignore object-level and field-level security.”
“Flows that run in system context operate with elevated privileges.”
=========================================================
