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

In Salesforce Flow, a record variable holds the values for a single record of a specific object type (e.g., one Account or one Contact).

A. ✅ A record variable stores a structured set of field values for one record and is used for input, manipulation, and output within a flow.

Incorrect Options:

B. The concept of "Global" is unrelated to what record variables store.

C. This describes a Record Collection Variable, not a single record variable.

D. Multiple object types would require separate variables per object type.

Reference Extracts from Salesforce Help – Work with Record Variables in Flow:

“A record variable stores the field values for one record.”

“If you need to store multiple records, use a record collection variable instead.”

===========

Salesforce allows administrators to monitor all scheduled automation, including time-based workflow actions and scheduled flows, through Setup.

To monitor pending scheduled actions:

Navigate to Setup.

Search for “Paused and Waiting Interviews” or “Time-Based Workflow.”

The Scheduled Flows and Time-Based Workflow Queues provide visibility into all upcoming automation.

Correct Option:

C. By going to Setup — This is the official and supported method to view and manage pending scheduled actions.

Incorrect Options:

A. Monitor Script — Not a Salesforce feature.

B. Checking the Inbox — Email inboxes are not a monitoring mechanism.

D. Keep-alive events — This concept does not apply to Salesforce automation.

Reference Extracts from Salesforce Process Automation Study Guide:

“Monitor paused flow interviews and scheduled actions by going to Setup and accessing relevant monitoring pages.”

“From Setup, use Paused Flow Interviews and Scheduled Jobs to track automation activities.”

Since the data volume is stable and updated frequently in an external system, and there's no need to store it in Salesforce, Salesforce Connect is the best choice. It allows real-time access to external data using External Objects. This can be used alongside Flows for automation.

C. Correct — Salesforce Connect provides real-time access, and Flows can automate interaction with that data.

Incorrect Options:

A. ETL tools are for batch data movement, not real-time access.

B. External Services is more suitable for actions (not data listing or queries).

D. Local Actions are used in Screen Flows, not ideal for real-time data integration.

Reference Extracts from Salesforce Process Automation Study Guide:

“Salesforce Connect allows integration with external data sources using External Objects for real-time data access.”

“Use Flow to automate interactions with external objects when data doesn’t need to be stored.”

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

In Flow Builder, the correct way to introduce branching logic (i.e., to take different paths based on conditions) is by using the Decision element.

The Decision element evaluates Boolean conditions or expressions and routes the flow down different paths depending on the outcome (True/False or other defined outcomes).

Incorrect Options:

A. “Branching Element” is not a valid Salesforce term.

C and D. If/Else logic is found in Apex or other programming languages but not represented this way in declarative Flow Builder.

Reference Extracts from Salesforce Help Documentation on Flow Builder:

“Use a Decision element to add conditional logic to your flows, allowing different outcomes based on evaluated conditions.”

===========

When preparing test cases for flows, admins should consider the following:

A. Negative scenarios — Test cases should validate what happens when conditions are not met and actions should not fire.

C. Formulas — Test inputs should include cases that help evaluate formula behavior for correctness and edge cases.

E. Expected outcomes — Confirm that intended automation paths execute under certain conditions.

Incorrect options:

B. Number of users affects scalability but not functional test cases.

D. Flow execution time is not typically part of a functional test plan unless performance is in scope.

Reference Extracts from Salesforce Process Automation Study Guide:

“Test flows for both successful and unsuccessful execution paths.”

“Validate formula logic using test values to ensure correct evaluation.”

“Include cases where no action should occur to ensure criteria are evaluated properly.”

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

There are 3 main “building blocks” of any Flow:

1. Elements are the individual building blocks of the Flow. These perform logical actions such as assignments, decisions, or loops. There are also data elements that will query the database or commit record changes.

2. Connectors determine which element leads to which. Winter ‘21 enables Auto-Layout, and connects the Elements together automatically.

3. Resources are the individual variables of data that are to be used in a Flow – these can be strings of text, numbers, records, formulae, or collections.

Salesforce provides a specific area in Setup where admins can monitor flows that are paused or have pending interviews (e.g., scheduled or waiting for user input):

C. ✅ In Setup → Process Automation → Paused Flow Interviews, admins can view flows that are currently in a paused state and take actions such as resume or delete.

Incorrect Options:

A. “Queue” refers to queue-based record ownership, not flows.

B. List views show flow definitions, not paused interviews.

D. Automation Home is a central dashboard but does not list paused interviews directly.

Reference Extracts from Salesforce Help – Manage Paused and Waiting Flow Interviews:

“Use the Paused Flow Interviews page to monitor flows waiting for user input or scheduled to resume at a later time.”

===========

Salesforce recommends using declarative tools like Flow to automate updates to related records. In this use case, a Record-Triggered Flow can be created on the Account object. When the billing address of the HQ account is updated, the flow can identify and update all related branch accounts (using a defined relationship such as a lookup or parent-child).

B. Correct — Create a Record-Triggered Flow on Account that checks for changes to the billing address and updates child records accordingly.

Incorrect Options:

A. Dataloader is a manual tool, not a real-time automation solution.

C. Apex can solve this but is not required for such declarative use cases.

D. A formula field only displays data; it does not trigger updates.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Record-Triggered Flows to update related records based on changes to a parent record.”

“Flows can be configured to loop through child records and apply updates when specific field values change.”

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

In a Screen Flow, when presenting a dropdown list, radio button set, or checkbox group for user selection, the Choice resource is used. It allows you to define static or dynamic lists of options for selection inputs.

A. Correct — Choice is the correct resource for configuring input controls on screen elements.

Incorrect Options:

B. Dependent picklist is a type of screen component, not a resource.

C. Decision Outcome is a branch of a Decision element, not used for screen selections.

D. Variable stores user inputs but does not define selectable options.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Choice resource to create values that appear in radio buttons, picklists, or checkbox groups in screen components.”

“Choices can be manually defined or pulled dynamically from records.”

In Process Builder, a process is made up of three core building blocks:

Trigger: Specifies when the process should start, such as when a record is created or edited.

Criteria Node: Defines the condition(s) that must be true for actions to be executed.

Actions: Define what happens when the criteria are met — examples include creating records, updating fields, and sending emails.

Incorrect Options:

B. Scheduler: Not a component of Process Builder. Scheduling is handled differently, typically in Flow.

C. Timer: Not a term used within Process Builder.

Reference Extracts from Salesforce Help Documentation on Process Builder:

“A process consists of a trigger, criteria, and actions.”

“Each criteria node defines conditions and the actions to execute when those conditions are met.”

===========