Free Practice Questions for Salesforce Process-Automation Exam

In Process Builder, a trigger determines when the process will run. When creating a new process, the first step involves selecting the object and deciding when the process should run—only when a record is created, or when a record is created or edited. This is known as the trigger for the process.

Option A (Criteria): Defines the specific conditions under which the process actions should fire but does not determine when the process itself is evaluated.

Option B (Trigger): ✅ Correct. It defines the entry point—when the process should evaluate.

Option C (Action): Determines what the process does once the conditions are met.

Option D (Screen): Not used in Process Builder; it belongs to Flow Builder and is used for user interaction.

Reference Extracts from Salesforce Process Automation Documents / Study Guide:

“The trigger determines when the process should run—either on record creation or when a record is created or edited.”

“The criteria define when to execute actions, but the trigger defines when to evaluate criteria.”

Salesforce enforces CPU time limits on synchronous automation processes like Flows and Apex. To decrease CPU time usage in Flows:

A. Reduce the number of formulas — Complex or repeated formula calculations consume CPU resources. Simplifying them improves performance.

C. Reduce the number of cross-object references — These create expensive queries and operations during flow execution.

E. Reduce the number of elements — Each element adds to execution complexity. Minimizing unnecessary elements decreases CPU time.

Incorrect Options:

B. “Decision Bypass” is not a standard Salesforce term. Adding more decision elements does not reduce CPU usage.

D. Flow Interview timeout refers to user interaction time, not CPU limit.

Reference Extracts from Salesforce Process Automation Study Guide:

“CPU time can be reduced by simplifying formulas, minimizing the number of elements, and avoiding cross-object references that increase query load.”

“The more elements and calculations a flow has, the more CPU time it consumes.”

=========================================================

Salesforce provides specific configuration options in Setup under Process Automation Settings to control flow runtime behavior. These include:

A. ✅ Let Administrators resume flows with pending actions: Grants admins the ability to resume paused or waiting flow interviews.

C. ✅ Let users pause flows: Enables flow designers to configure flows to be paused by users mid-execution (e.g., long workflows requiring additional input).

D. ✅ Let users resume shared flow interviews: Allows users to resume flow interviews that are shared with them based on permissions.

Incorrect Options:

B. Letting users “run as another user” is not a configurable setting in Flow.

E. Flow debugging as another user requires user impersonation techniques (like login-as) but is not part of the Process Automation Settings.

Reference Extract from Salesforce Setup Documentation on Process Automation Settings:

“From Setup, enter Process Automation Settings in Quick Find. You can allow users to pause/resume flows, and allow admins to manage paused flow interviews.”

===========

The Decision element in Flow Builder allows the configuration of multiple outcomes (paths) based on logical conditions. If no conditions match, and a default outcome is configured, the flow takes that default path.

D. Correct — If conditions in all defined outcomes evaluate to false, the flow follows the default outcome if it exists.

Incorrect Options:

A. The flow does not fail automatically; it just follows the default path or ends.

B. A Screen element must be explicitly added; it is not invoked by default.

C. If there is no default outcome, the flow may stop, but this is not always ideal or recommended.

Reference Extracts from Salesforce Process Automation Study Guide:

“The default outcome defines the path the flow takes if no other condition is met in the Decision element.”

“Always define a default outcome to prevent the flow from ending unexpectedly.”

=========================================================

In Flow Builder, the Manager tab is where all resources—including variables, constants, formulas, and choices—are displayed. It provides access to both system-generated and manually created resources.

C. Manager tab — ✅ Correct. It is the dedicated area for managing flow resources.

Incorrect Options:

A. Canvas — Used to place flow elements, not to manage resources.

B. Elements tab — Allows selection of flow elements (e.g., Assignment, Screen), not resources.

D. Button Bar — Refers to Run, Debug, Save, etc., not resource management.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Manager tab in Flow Builder to create and manage resources such as variables, formulas, and constants.”

“The Manager tab lists every resource available in your flow, whether created manually or auto-generated.”

=========================================================

In the Spring '21 Release, Salesforce introduced a key enhancement that allows Admins and Developers to see the exact CPU time consumed by Flows and Processes. This was added to help identify automation performance bottlenecks and determine which automations are consuming excessive CPU time, which could lead to governor limit violations.

Correct Option:

B. Accurate measure of the CPU time consumption of Flows and Processes — ✅ This enhancement added a more granular breakdown in debug logs for better monitoring.

Incorrect Options:

A. No such official feature as “Stagger and Throttle plug-ins” exists.

C. "Black run-as access" is not a documented or supported Salesforce feature.

D. Optimizer evaluates usage patterns but does not measure CPU time.

Reference Extracts from Salesforce Release Notes Spring ’21 - Performance Enhancements:

“In Spring ’21, debug logs now show more accurate CPU time usage of Flows and Processes.”

===========

An approval process consists of a sequence of steps and rules that determine whether a record should be approved or rejected. The three essential components are:

A. Actions — Define what happens when the record is submitted, approved, or rejected.

B. Criteria — Determine when the record is eligible for the approval process.

C. Approvers — Specify who needs to approve the record.

Incorrect Options:

D. Fields are updated but not a core component of the approval process structure.

E. Steps are part of the process, but the fundamental components are Actions, Criteria, and Approvers.

Reference Extracts from Salesforce Process Automation Study Guide:

“Approval Processes are composed of criteria, approvers, and actions that define the submission, approval, or rejection path.”

“Each approval step contains one or more approvers and actions to execute.”

=========================================================

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

=========================================================

Process Builder uses a model where you define:

C. Trigger — Defines when the process starts (e.g., when a record is created or updated).

B. Criteria Node — Defines the conditions that must be met for the action to run.

F. Action — What happens when the criteria are met (e.g., update a record, send an email, launch a flow).

Incorrect Options:

A. “Node” is a generic term and not used officially in Process Builder documentation.

D and E. “Scheduler” and “Timer” are more closely related to flows or scheduled flows than Process Builder.

Reference Extracts from Salesforce Process Automation Study Guide:

“Each process includes a trigger, criteria nodes, and actions.”

“Criteria nodes determine whether to execute specific actions based on record values.”

=========================================================