Pass the Salesforce Accredited Professional Certification Process-Automation Questions and answers with ExamsMirror

Flow Interviews are individual executions of flows and each has its own runtime context and data.

A. Correct — Every flow execution creates a distinct flow interview.

C. Correct — Salesforce allows up to 50 active versions of a flow. While only one can be set as active, others can exist.

E. Correct — Deleting unused interviews reduces clutter and keeps the user experience clean.

Incorrect Options:

B. Incorrect — Browser back/forward navigation does not control flow screen navigation. Navigation is governed within the flow’s logic and element structure.

D. Incorrect — All flow interviews, whether paused or not, can be deleted administratively; deactivation applies to flows, not interviews.

Reference Extracts from Salesforce Process Automation Study Guide:

“Each time a flow runs, it creates a unique interview.”

“Salesforce supports up to 50 versions of a flow.”

“Deleting paused or unused interviews can help users focus only on relevant, actionable flows.”

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

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

===========

To evaluate whether the Opportunity Stage is changed to Closed-Won or Closed-Lost, a Decision element in Flow is used. It allows branching logic to determine if the stage matches those values, and then trigger appropriate actions such as notifying sales leaders.

C. Correct — The Decision element allows branching based on criteria (e.g., Stage equals Closed-Won or Closed-Lost).

Incorrect Options:

A. Workflow field update cannot send notifications and is limited in scope.

B. Quick Actions are user-triggered, not automated.

D. Update Record is used to change data, not evaluate conditions.

Reference Extracts from Salesforce Process Automation Study Guide:

“Decision elements evaluate field values or formulas and determine the path a flow should take.”

“Use Decision elements to branch automation logic based on conditions like Stage = Closed-Won.”

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

In Salesforce Flow Builder, flow elements are broadly categorized into three functional types:

Screen elements — Capture user input (e.g., screens, display text, choice inputs)

Logic elements — Direct the flow (e.g., Decision, Assignment, Loop)

Action elements — Interact with Salesforce or external systems (e.g., Create Record, Send Email, Subflow)

Correct Option:

B. ✅ Screen, logic, and actions

Incorrect Options:

A. Not official categories of Flow elements.

C. “Connectors” are how elements are linked, but not a category of elements.

D. Variables and choices are resources, not flow elements.

Reference Extracts from Salesforce Help – Flow Element Reference:

“Flow elements fall into categories such as Screen (UI), Logic (routing), and Actions (system interaction).”

===========

When invoking external services (like an API callout) from a Flow, it is critical to add proper fault paths to handle unexpected failures, especially since such callouts can fail due to service unavailability, timeouts, or validation issues. Using the “Add Fault Path” option in Flow allows developers to gracefully handle the error (e.g., show a user-friendly message, log the error, or retry).

Correct Option:

A. ✅ Adding an error handler ensures the user experience is preserved even if the external call fails.

Incorrect Options:

B. While running in a separate transaction might help, this is not configurable directly in Flow.

C. Apex is more flexible but not necessary unless the requirement exceeds Flow’s capabilities.

D. Process Builder cannot make external callouts.

Reference Extract from Salesforce Help – Add Fault Handling to Your Flow:

“Add a fault path to any element that may fail, such as external services or DML operations, to ensure the flow doesn’t fail silently.”

===========

In Salesforce Flow Builder, branching logic is achieved using the Decision element. This element evaluates conditions and determines the path the flow should take.

B. Correct — The Decision element is the official way to create branches in Flow logic.

Incorrect Options:

A and C are programming terms not applicable in declarative Flow design.

D. “Branching Element” is not an official Salesforce component.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Decision element to control the flow path based on logical criteria.”

“Decision elements act as conditional routers for flow execution.”

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

DML operations in Flow include creating, updating, deleting, or getting records from the Salesforce database.

A. Update Records — Issues an UPDATE DML operation.

D. Create Records — Issues an INSERT DML operation.

These elements modify the Salesforce database and are subject to governor limits like the 150 DML per transaction limit.

Incorrect Options:

B. Sort Records is not an element in Salesforce Flow.

C. Share Records is not a standard Flow element; record sharing is typically handled through manual sharing or Apex.

Reference Extracts from Salesforce Process Automation Study Guide:

“Create Records and Update Records are flow elements that trigger DML operations.”

“DML elements are subject to governor limits and should be bulkified when inside loops.”

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

Some complex automation scenarios are not supported entirely by Process Builder and require invoking a flow for advanced logic. For example:

A. Clone a record and its children — This requires loops and complex logic, which is best handled in a flow. Process Builder can launch a flow to do this.

C. Delete a related record — Process Builder cannot delete records directly, but it can invoke a flow to handle the deletion.

These use cases show how combining a process with a flow (using invocable flows) enables more robust automation.

Incorrect options:

B. Posting to Chatter can be done directly in Process Builder.

D. Modifying visibility of Chatter feed items is not typically accomplished through Process + Flow.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use invocable flows when process logic requires looping, record deletion, or multiple updates.”

“Process Builder can call flows when advanced logic is needed beyond its native actions.”

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

In Flow Builder, a variable is a type of resource that stores temporary data used during the flow’s execution. Variables can be modified as the flow progresses, making them ideal for dynamic logic, calculations, and user input storage.

Correct Option:

C. ✅ Variable — Designed to hold and change data during a flow’s runtime.

Incorrect Options:

A. Error Message is not a data-holding resource.

B. Text Template is static and cannot be changed mid-flow.

D. Formula resources are read-only and recalculated but not updated directly.

Reference Extract from Salesforce Help – Flow Variables:

“Use variables to temporarily store values. Variables can hold strings, numbers, records, and more. They can change throughout the flow.”

===========

User-interactive flows (Screen Flows) can be distributed in the following ways:

B. ✅ Flow Actions — Flows can be exposed as Quick Actions or Global Actions and launched from buttons.

C. ✅ Custom Lightning Web Components — Developers can embed flows within LWCs using the lightning-flow base component.

E. ✅ Lightning Pages — Admins can add flows directly to record, home, or app pages using the Flow standard component in Lightning App Builder.

Incorrect Options:

A. “Microservice Frame” is not a Salesforce feature.

D. “Field Portal Mobile App” is not a native Salesforce product and is not related to Flow distribution.

Reference Extract from Salesforce Help – Flow Distribution:

“You can distribute flows using Flow Actions, embed them in Lightning Pages, or include them in Custom Components.”Reference:Salesforce Help - Distribute Flows