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

A record variable in Flow holds field values for a specific record. When "Allow multiple values" is unchecked, the variable is a single record variable — meaning it stores field data for just one record.

D. Correct — The variable stores values for one record (e.g., one Contact, one Account, etc.).

Incorrect Options:

A. There’s no “Global record” term in Flow.

B and C refer to collection variables, which require “Allow multiple values” to be checked.

Reference Extracts from Salesforce Process Automation Study Guide:

“If 'Allow multiple values' is not selected, the record variable stores a single record.”

“Use record variables to store and reference record field values within the flow.”

In Flow Orchestration, Work Items are assigned to users or groups for action. To support assignment to a team where any user can act on it, the appropriate feature is Work Groups.

C. Correct — Work Groups allow multiple users to share responsibility for completing a task in Flow Orchestration.

Incorrect Options:

A. Work Stages define the phases of the orchestration, not user access.

B. Work Queues are not a Salesforce concept in Flow Orchestration.

D. Work Items are the tasks created but don’t define group access or roles.

Reference Extracts from Salesforce Process Automation Study Guide:

“Work Groups allow work items to be assigned to multiple users, where any member can take ownership.”

“Use Work Groups to delegate responsibility across teams in Flow Orchestration.”

Salesforce allows administrators to create object-specific quick actions that launch flows directly from record pages. This is ideal for collecting feedback, such as when a sales rep closes an Opportunity.

D. Use Salesforce Flow with object-specific action — ✅ A Screen Flow can be launched from an Opportunity record using an object-specific Quick Action. The flow can include fields to gather feedback, and the record context (Opportunity ID) is passed automatically.

Incorrect Options:

A. Process Builder cannot be used to launch a flow via object-specific actions.

B. While Salesforce Surveys are valid tools, they are not integrated with object-specific actions in this way.

C. Using Apex is unnecessary for this use case when standard Flow and Quick Actions provide a declarative solution.

Reference Extracts from Salesforce Help – Object-Specific Quick Actions:

“You can launch Screen Flows from object-specific quick actions to collect user input related to the current record.”

===========

Executing DML actions like Create, Update, or Delete Records inside a loop should be avoided due to governor limits (e.g., DML limit of 150 per transaction). Instead, store records in a collection and perform bulk operations after the loop.

B. Correct — Executing DML inside loops risks hitting limits and should be avoided.

Incorrect Options:

A. Assigning values is acceptable and common in loops.

C. Screen elements are not used inside loops — but displaying data is not an execution problem itself.

D. While nesting loops is discouraged for performance, the greater risk comes from DML actions inside loops.

Reference Extracts from Salesforce Process Automation Study Guide:

“Avoid performing DML operations inside a loop. Instead, collect records and update them outside the loop.”

“Bulkification of actions is a Flow best practice to prevent hitting governor limits.”

To pass a record’s ID into a flow placed on a record page (e.g., an Account record page), the variable inside the flow must be configured with the setting:

“Available for input” — ✅ This tells the flow to accept external values when invoked, such as from a Lightning App Page or Quick Action.

Salesforce automatically passes the recordId variable to a flow placed on a record page if the flow includes a Text variable marked “Available for input” with the API name recordId.

Incorrect Options:

B. “Available for output” is used when passing data out of the flow.

C. “Get Record” retrieves records inside the flow, not for passing input from the page.

D. “Allow multiple values” is used for collections, not input variables.

Reference Extracts from Salesforce Help Documentation on Flow Variables and Record-Triggered Flows:

“To pass a record ID to a flow from a Lightning record page, create a Text variable named recordId and mark it as Available for input.”

===========

In Flow Orchestration, Go To connectors are used to connect flow elements in non-sequential ways, especially when steps need to jump to another part of the orchestration, bypassing the default auto-layout flow.

B. Correct — Go To connectors are used when flow elements need to skip the default path or jump conditionally.

Incorrect Options:

A. Auto-Layout connectors are automatically generated and are not used for conditional jumps.

C. Series connectors are not a defined term in orchestration.

D. Parallel connectors are used to execute elements simultaneously, not to redirect flow.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Go To connectors in orchestration to direct the path of execution outside the default auto-layout structure.”

“Go To connectors enable conditional branching between steps or stages.”

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

To add a Screen Flow to a Lightning Page, an Administrator or Flow Designer must use the Lightning App Builder. Inside Lightning App Builder, the “Flow” standard component can be dragged onto a page layout.

D. Setup > Lightning App Builder > Page — ✅ This is the correct navigation to modify Lightning record, home, or app pages and embed flows.

Incorrect Options:

A. There is no “Flow Canvas” section in Lightning App Builder.

B. “Edit Page” is part of the App Builder interface, not a Setup-level option.

C. Flow Builder is for building the flow itself, not placing it onto a page.

Reference Extracts from Salesforce Help – Add Flows to Lightning Pages:

“Use Lightning App Builder to add the Flow component to a Lightning record, home, or app page. Then select the Screen Flow to display.”

===========

Platform Event–Triggered Flows are ideal for asynchronous integration use cases. These flows are triggered when a platform event is received. Platform events are part of Salesforce’s event-driven architecture and are designed for integrating external systems by publishing and subscribing to event messages asynchronously.

These flows run in the background and are invoked in response to events (e.g., external system sends a payload to Salesforce).

Incorrect Options:

B. Contact Request Flow: Used for managing contact us forms, not integrations.

C. Checkout Flow: Not a Salesforce standard flow type.

D. Screen Flow: Requires user interaction and is synchronous.

Reference Extracts from Salesforce Help - Platform Events Overview:

“Use Platform Event–Triggered Flows to automate business processes that should run asynchronously in response to events.”

===========

Salesforce Flow is the name of the overall suite of flow automation tools. This includes the ability to create, run, and manage flows. Flow Builder is the point-and-click UI tool used to create the flows.

Salesforce Flow = entire automation platform (includes Flow Builder, Runtime Engine, Flow Orchestration, etc.)

Flow Builder = visual tool used to design and build the flow.

Therefore:

B. Flow Builder is a part of Salesforce Flow. ✅ Correct

A. Incorrect — reversed relationship.

C. Incorrect — speed isn’t the defining difference.

D. Incorrect — both are available in Lightning Experience.

Reference Extracts from Salesforce Process Automation Study Guide:

“Salesforce Flow is the product that includes tools like Flow Builder for creating flows and automation.”

“Flow Builder is the declarative interface for designing flows within Salesforce Flow.”

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

This is a classic use case for a Scheduled Flow. The Administrator can build a Scheduled Flow that:

Queries all open Opportunities related to Accounts where the Credit Status is Red.

Loops through the records.

Updates the Stage field to Freeze.

A. Correct — This is achievable declaratively using a Scheduled Flow, which provides scalability and avoids the need for custom code.

Incorrect Options:

B. A formula field cannot change field values; it's read-only.

C. Batch Apex is valid but not preferred when the use case is achievable declaratively.

D. An Apex trigger would require coding and is unnecessary for this logic.

Reference Extracts from Salesforce Process Automation Study Guide:

“Scheduled Flows can run on a recurring basis to find and update records meeting defined criteria.”

“Use flow to perform mass updates based on related object conditions without writing code.”

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