Salesforce Process-Automation - Salesforce Process Automation Accredited Professional Exam (SP25)

Salesforce’s standard field history tracking does not support multi-select picklists. To track changes (old vs. new values) on such fields, a custom solution is needed. The best declarative approach is to use an after-save Record-Triggered Flow, which compares the previous and current values and stores the result in a custom object or field for auditing.

A. Correct — Use a Record-Triggered Flow to capture the prior value using the $Record__Prior global variable and compare it with the current value.

Incorrect Options:

B. Field history tracking does not support multi-select picklists natively.

C. Raising a case will not enable unsupported standard functionality.

D. Apex Trigger is possible but not required since Flow can handle this declaratively.

Reference Extracts from Salesforce Process Automation Study Guide:

“Multi-select picklists are not supported by standard field history tracking. Use Flow to track changes to these fields.”

“Record-Triggered Flows can access $Record__Prior to detect field changes.”

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

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

===========

Flows, particularly Screen Flows, are ideal for this use case. They allow for:

Conditional logic (via Decision elements) to show different screens or questions based on the user’s input or record values (e.g., country and language).

A guided, user-interactive experience tailored to the scenario.

Correct Option:

D. ✅ Using a Screen Flow with conditional logic allows a no-code solution to display the right questions at the right time.

Incorrect Options:

A. Apex is unnecessary for declarative logic.

B. Process Builder cannot display UI or ask questions.

C. While LWC offers flexibility, it adds development complexity not needed when Flow can handle the requirement declaratively.

Reference Extract from Salesforce Help – Flow Builder:

“Use Screen Flows to guide users through a process and use decision elements to customize based on user input or record data.”

===========

Salesforce provides a standard "File Upload" screen component within Flow Builder for user-interactive flows. This feature allows users to upload files during a Screen Flow, and the files are associated with a record or stored in the system, depending on configuration.

Option A (Custom Lightning Component): Unnecessary for this scenario because Salesforce provides a standard component.

Option B (Apex + Visualforce): Outdated approach; not recommended for Lightning Experience unless legacy functionality is required.

Option C (File Upload standard Screen Component): ✅ Correct. This is the native and recommended way to allow file uploads in Lightning Screen Flows.

Option D (Node.js): Not applicable within the Salesforce platform for declarative flow-based file uploads.

Reference Extracts from Salesforce Process Automation Documents / Study Guide:

“Use the File Upload screen component in Flow Builder to let users upload files directly in a Screen Flow.”

“This component is available in Lightning Experience and is recommended for all file upload interactions in user flows.”

Salesforce Flow is built using three primary components:

A. Element: These are the building blocks of logic in a flow. Examples include Assignment, Decision, Get Records, Screen, and Loop.

B. Resource: These are data holders such as variables, constants, formulas, and more that the flow uses to store and manipulate values.

E. Connector: Connectors determine the path the flow takes by linking elements together. They establish the direction of execution from one element to the next.

Incorrect Options:

C. Variables are a type of resource, not a separate building block.

D. Constants are also a resource type under the “Resource” umbrella.

Reference Extracts from Salesforce Help Documentation on Flow Builder:

“Every flow consists of elements, connectors, and resources. Elements define what the flow does, resources store data, and connectors determine the path.”

===========

To enable user selection in a Screen Flow — for example, in a radio button, picklist, or checkbox — the appropriate resource is a Choice.

A. Choice — ✅ A Choice resource defines selectable options in screen components such as radio buttons, picklists, or multi-select lists.

Incorrect Options:

B. Dependent Picklist is a screen component type, but it requires Choice resources to populate it.

C. Variables store data but don’t define selectable input choices.

D. Decision is used for branching logic, not for user selection.

Reference Extracts from Salesforce Help – Add Choices to Screen Elements in Flow Builder:

“Define Choice resources to let users select from a list of options in screen flow components.”

===========

In Flow Orchestration, each execution instance is referred to as a "Run." This terminology is used to monitor active or completed orchestrations in the Orchestration Runs list in Setup.

D. Correct — Each time an orchestration is executed, it is called a Run.

Incorrect Options:

A. "Session" is not used in orchestration terminology.

B. "Interview" is the term for individual Flow executions, not orchestration-level.

C. "Spool" is not a recognized Salesforce automation term.

Reference Extracts from Salesforce Process Automation Study Guide:

“Each execution of a flow orchestration is called a Run and can be monitored in the Orchestration Runs list in Setup.”

“Use the Orchestration Run view to examine errors, progress, and completion status.”

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

Schedule-Triggered Flows can be configured to run at frequent intervals (e.g., hourly) and include logic to retrieve data from external sources using External Services, HTTP Callouts (via Apex actions), or External Objects.

A. Correct — Schedule-Triggered Flows support declarative execution at scheduled intervals and can be paired with External Services for near real-time sync.

Incorrect Options:

B. Einstein Analytics is for data visualization and reporting, not near real-time data integration.

C. Apex Schedulable class is code-based and typically not the first recommendation for admins.

D. Manual data loads are not scalable and do not support near real-time updates.

Reference Extracts from Salesforce Process Automation Study Guide:

“Scheduled Flows are ideal for polling or syncing external data sources at set intervals.”

“Combine Scheduled Flows with External Services or Apex actions for external integrations.”

When a flow is launched by another flow, an Apex class, or a button, Salesforce uses input variables to pass values into the flow. To make a variable available for incoming values, the administrator must mark it as “Available for input.”

D. Available for input — ✅ Correct. This enables external sources to set the variable's value.

Incorrect Options:

A. Field is required — Controls form behavior, not data transfer into flows.

B. Available for output — Used when values should be returned after flow completion.

C. Allow Multiple Values — Only used for collection-type variables.

Reference Extracts from Salesforce Process Automation Study Guide:

“Mark a variable as ‘Available for input’ to pass values into the flow from external sources such as URL parameters, Apex, or another flow.”

“Only variables with the ‘Available for input’ checkbox selected can receive external data.”

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

When an orchestration encounters an error, Salesforce can send orchestration error email notifications to designated recipients. Additionally, the Orchestration Runs list in Setup shows all active and failed orchestration runs with error details.

B. Correct — Admins receive orchestration error email notifications if configured properly.

D. Correct — Errors are displayed in the Orchestration Runs section in Setup.

Incorrect Options:

A. Event Monitoring is for advanced analytics and not specific to orchestration debugging.

C. Flow error emails are sent for standalone flow errors, not specifically orchestration.

Reference Extracts from Salesforce Process Automation Study Guide:

“Orchestration error notifications alert admins to issues in orchestration flow runs.”

“Monitor orchestration activity and errors from the Orchestration Runs page in Setup.”

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