Free Practice Questions for Salesforce Process-Automation Exam

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

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

Based on Salesforce's official documentation, the best approach to initiate an approval request based on a field value change is by using Process Builder. The admin can configure a process on the Account object that listens for changes to the Type field. When the value changes from "Prospect" to "Customer," the process can then execute an action to automatically submit the record for approval.

Process Builder supports the "Submit for Approval" action, which is the only declarative (point-and-click) tool in Salesforce that allows direct submission of records into an approval process without writing code. This makes it ideal for the described scenario.

Option A: Involves Apex, but there is no need to write custom code for this standard use case.

Option B: While Flows can update field values and send emails, Flows cannot directly submit a record into an approval process without additional custom logic or invocable actions.

Option C: While it suggests using a Flow, standard Flows do not have a built-in “Submit for Approval” action like Process Builder does.

Option D: Correctly uses a Process to monitor the change and submit the record for approval, aligning with recommended best practices from Salesforce.

Reference Extracts from Salesforce Process Automation Documents / Study Guide:

“Use Process Builder to automatically submit a record for approval when it meets specific criteria.”

“Flows do not directly support submission for approval without using Apex or invocable methods.”

“Approval processes are best triggered using declarative tools such as Process Builder for field change monitoring.”

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

===========

Einstein Next Best Action (NBA) provides contextual and intelligent recommendations using three main components:

Recommendations: The content or actions being suggested to users.

Strategies: Define logic and conditions for surfacing those recommendations.

Flows: Allow users to act on recommendations by launching guided automation.

A. Correct — Flows, Recommendations, and Strategies are the core components of Next Best Action.

Incorrect Options:

B, C, D: These options include either Guided Layouts or Local Actions, which are not required or standard components of Einstein NBA. Local Actions are useful but optional in Screen Flows and not specific to NBA.

Reference Extracts from Salesforce Process Automation Study Guide:

“Einstein Next Best Action uses Recommendations, Flows, and Strategies to present personalized suggestions.”

“Strategies determine which recommendations to show based on business rules and real-time data.”

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

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

===========

When building flows for external users (such as customers or partners), they should be distributed using Sites or Experience Cloud Portals. These flows are typically used for collecting data from people who are not Salesforce internal users.

Valid use cases include:

A. Survey forms — Screen flows can collect external user feedback.

C. Interest forms — Data collection before events, campaigns, or inquiries.

E. Product registration — Collecting details on newly purchased products from customers.

Incorrect use cases:

B. Service rep script — This is intended for internal users and belongs in a Service Console.

D. Lead conversion wizard — This task is internal and should be handled within the authenticated Salesforce org.

Reference Extracts from Salesforce Process Automation Study Guide:

“Flows distributed through Sites or Portals are ideal for data collection from unauthenticated users.”

“Use Screen Flows to build custom forms that external users can access through Experience Cloud or Sites.”

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

Salesforce has announced that Workflow Rules and Process Builder will be deprecated, and Flow is the future of automation. Salesforce provides two official options:

A. Migrate to Flow tool — Salesforce has introduced a built-in migration tool to convert existing Workflow Rules into Flows.

B. Manual conversion — Complex workflows or unsupported configurations may require manually rebuilding them in Flow.

Incorrect Options:

C. API versioning is not a tool for migration.

D. There is no official Salesforce AppExchange app named “Flow Conversion.”

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Migrate to Flow tool in Setup to convert eligible Workflow Rules to Flows.”

“For unsupported actions, manually recreate the logic using Flow Builder.”QUESTION NO: 132

Universal Containers (UC) is automating its approval process for partner submissions. UC wants to designate certain partner users as approvers. How can UC accomplish this?

A. Add partner users using the Delegated Approver lookup field.

B. Upgrade partner users to internal users and give them approver permissions.

C. Use Data Loader to add partner users as Delegated Approvers.

D. Give partner users "super user access" and update their role to Approver.

Answer: A

To restrict visibility of customer assist records between business units (sales users), the best approach involves configuring:

Record-level security (via sharing rules or Apex-managed sharing)

Apex Triggers if complex, dynamic visibility rules are needed

Dynamic Forms (Option D) control page layout behavior (UI visibility), but not record-level access. Therefore, the correct answer is:

A. Use Apex Trigger — ✅ With Apex, complex logic can be written to dynamically adjust record access, such as removing sharing based on business group or role hierarchy.

Incorrect Options:

B. Lightning Flow and C. Process Builder are for automation, not security enforcement.

D. Dynamic Form only manages field visibility, not record access.

Reference Extracts from Salesforce Help Documentation:

“To implement custom sharing logic based on business criteria, use Apex-managed sharing in a trigger or class.”

===========