Process-Automation Salesforce Process Automation Accredited Professional Exam (SP25) Free Practice Exam Questions (2025 Updated)

You can count records in Flow by:

Using the Get Records element to retrieve all Contact records with MailingCity = "Sydney".

Using a number variable with an Assignment element to increment the count.

Alternatively, you can use a Collection Variable and use {!CollectionVariable.size} to get the total count.

C. Correct — This method allows counting records using declarative tools only (Flow), without any code.

Incorrect Options:

A. Process Builder does not support direct counting or looping logic.

B. Apex is not required; the use case can be handled declaratively.

D. "for()" loops are part of Apex and not available in Flow Builder.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Flow’s Get Records element to retrieve data and store it in a collection variable. Use the collection’s .size property to get the count.”

“Loops and assignment logic can be used to increment counters if needed.”

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

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

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

Scheduled actions in flows (via scheduled paths) can be triggered relative to:

A. Specific date/time fields on the triggering record (e.g., 3 days before CreatedDate or a custom field).

C. Specific days of the week (supported in Scheduled Flows that run daily/weekly and evaluate record criteria).

A. Correct — You can configure scheduled paths based on a date/time field on the triggering record.

C. Correct — In Scheduled Flows, you can define execution by specific days of the week.

Incorrect Options:

B. Scheduling based on when a process "ran last time" is not a supported scheduling condition.

D. Salesforce scheduling does not support relative dates to rare calendar events like leap year days.

Reference Extracts from Salesforce Process Automation Study Guide:

“Scheduled paths in record-triggered flows can be based on date/time fields or offsets (e.g., 5 days before Due Date).”

“Scheduled Flows can be configured to run on specific days of the week or month.”

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

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

Flow Builder, specifically Screen Flows, is ideal for building guided, step-by-step user experiences. Admins can use screens, choice inputs, navigation buttons, and conditional logic to create an interactive product catalog walkthrough.

A. Correct — Flow Builder’s Screen Flows are designed for guided UI processes.

Incorrect Options:

B. Process Builder does not support UI interaction.

C. Apex Triggers are code-based and not used for UI walkthroughs.

D. Approvals are used for record sign-off, not guided processes.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Screen Flows to guide users through complex business processes with input forms, navigation, and branching logic.”

“Ideal for data collection, wizards, or step-by-step processes.”

When automating communication between Salesforce and an external system, an Outbound Message action is one of the easiest declarative tools available. It sends SOAP messages to external systems when a specific condition is met, such as when an employee is offboarded.

C. Outbound Message Action — ✅ This tool allows Salesforce to send field data to a designated external endpoint in real time.

Incorrect Options:

A. SalesforceHandler is not a valid or recognized term/tool.

B. API Connect is not a Salesforce feature (used in IBM).

D. JSON Auto Connector is not a standard Salesforce feature.

Reference Extracts from Salesforce Help – Outbound Messaging:

“Outbound messages allow you to specify the endpoint and data to send when certain events occur, automating integrations with external systems.”

===========

In Record-Triggered Flows, the global variable $Record__Prior is used to reference the values of the record as they existed immediately before the flow was triggered. This is extremely useful for comparing field values before and after changes.

Correct Option:

D. $Record__Prior — ✅ This variable allows conditional logic based on field changes (e.g., IF Stage changes from Prospect to Closed).

Incorrect Options:

A. $Flow contains system variables about the current flow execution.

B. $Record contains the current values (post-change).

C. PRIORVALUE is used in formulas, but not as a standalone global variable in Flow.

Reference Extracts from Salesforce Help – Use PriorValue in Record-Triggered Flows:

“Use $Record__Prior in flows to access the record’s values before the triggering update.”

===========

To make an Apex method callable from Flow, the method must be annotated with @InvocableMethod. This annotation tells Salesforce that the method can be called from declarative tools such as Flow.

D. Correct — The @InvocableMethod annotation is required for Apex methods to be used in Flow.

Incorrect Options:

A. The Process.Plugin interface is used for Process Builder plugins, not Flow.

B. Only Apex classes with @InvocableMethod are available in Flow, not all.

C. Maps and Sets are not supported as Flow input/output types. Only primitives, Apex-defined types, or sObjects (in collections or singly) are allowed.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the @InvocableMethod annotation to expose Apex methods to Flow and Process Builder.”

“Flows support Apex classes with Invocable methods and simple parameter types such as primitives, sObjects, and Lists.”

In Salesforce Flow, a connector is the arrow between elements that determines the order of execution. After an element completes, the connector tells the flow engine which element to execute next. Each element can have one or more connectors leading to other elements.

Correct Option:

B. ✅ A connector tells the flow which element to execute next, allowing admins to control the flow's logic path.

Incorrect Options:

A. External database connections are handled through integrations, not connectors.

C. Connectors do not create resources.

D. To start another flow, you use a Subflow element—not a connector.

Reference Extract from Salesforce Help – Understand Flow Connectors:

“Connectors determine the direction a flow takes after each element runs. Use connectors to define the flow’s execution path.”

===========

Outbound messages are a declarative way to send SOAP-based messages to external systems in Salesforce. However, they do not guarantee message ordering. While messages are retried if the endpoint fails (up to 24 hours with exponential backoff), Salesforce does not ensure the order in which those messages are delivered if multiple are queued.

Correct Option:

B. Outbound messages could potentially be delivered out of order — ✅ This is a known limitation noted in Salesforce documentation.

Incorrect Options:

A. Salesforce retries for up to 24 hours, not limited to 3 retries.

C. Outbound messaging does support basic monitoring in setup but does not provide detailed audit trails.

D. There’s no such hard limit of “5 outbound message types for guaranteed delivery.”

Reference Extracts from Salesforce Developer Documentation – Outbound Messaging:

“Delivery order is not guaranteed. If multiple messages are queued, they may be delivered in any order.”

“Salesforce retries failed messages for up to 24 hours using exponential backoff.”

===========

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

===========

Salesforce officially ended support for Microsoft Internet Explorer 11 in Lightning Experience. Many features — including Flow Builder and other automation tools — either degrade or fail in IE11.

Correct Option:

B. Salesforce automation tools are currently not supported in Microsoft Internet Explorer — ✅ Admins should use modern browsers such as Chrome, Edge, or Firefox.

Incorrect Options:

A. Automation tools are fully supported in Salesforce Lightning.

C. Salesforce Developer Edition provides access to all core automation features.

D. Record access is not restricted by OWD being Public; rather, OWD affects sharing logic.

Reference Extracts from Salesforce Help Documentation:

“Salesforce no longer supports IE11 in Lightning Experience as of Winter ’21. Use a modern browser for building and managing flows.”

The Debug button in Flow Builder is designed to help administrators test their flows in real-time. When using Debug, admins can:

Enter custom values for input variables.

Observe the flow’s path of execution.

Monitor how decisions and assignments behave.

See outputs, errors, and element-by-element outcomes.

This helps identify logic issues before activating the flow.

A. Correct — The Debug tool is intended for entering input values and viewing detailed flow execution results.

Incorrect Options:

B. Auto-save settings are unrelated to the Debug tool.

C. Flow versioning is handled manually and not linked to debugging.

D. Flows do not support rollbacks of committed database changes during debugging.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Debug to test a flow’s logic step-by-step, passing values into input variables and monitoring outcomes.”

“Debugging helps trace decision paths, assignments, and screen navigation.”

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

Outbound Messages are part of declarative integrations in Salesforce and are triggered from Workflow Rules or Approval Processes. However, they come with limitations.

A. Correct — Outbound Messages do not provide a native audit trail. Admins must monitor via outbound messaging logs or Setup > Outbound Messages.

C. Correct — Because delivery is asynchronous and Salesforce retries messages independently, the order of delivery cannot be guaranteed.

Incorrect Options:

B. There is no documented limit of "five outbound message types for guaranteed delivery."

D. Salesforce retries failed outbound messages for up to 24 hours, not just three attempts, and messages are not "lost" until that retry window is exceeded.

Reference Extracts from Salesforce Process Automation Study Guide:

“Salesforce doesn’t guarantee delivery order of outbound messages.”

“Outbound messages are retried for up to 24 hours if the endpoint is unavailable.”

“Admins can monitor outbound messages via Setup, but audit trails are not automatic.”

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

Roll-up summary fields only work for master-detail relationships. Since the standard relationship between Account and Case is lookup (not master-detail), a roll-up summary field cannot be used directly. Instead, the correct solution is to use Flow to count the number of open related cases and update the custom field on the Account.

C. Correct — A scheduled or record-triggered Flow can count related Cases and update the custom field accordingly.

Incorrect Options:

A. Not supported because Account → Case is not master-detail.

B. Process Builder does not support looping or counting related records.

D. Scheduled Apex would work but is not declarative and requires code.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Flow to roll up data in lookup relationships by counting or summarizing related child records.”

“Roll-up summary fields are only available for master-detail relationships.”

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

In Screen Flows, when a user navigates backward (using the Back button), data entered on the current screen is not automatically preserved unless it has been stored in a variable or explicitly captured.

Correct Option:

D. ✅ Navigating back will clear values on the current screen unless stored in flow variables. Users will need to re-enter that data.

Incorrect Options:

A. “Allow navigation” is not a standard property; back navigation is enabled through screen flow settings and screen components.

B. There is no special “Navigate Flows” permission.

C. Navigating backward does not result in duplicates unless the flow is poorly structured.

Reference Extract from Salesforce Help – Configure Screen Flow Navigation:

“When users navigate backward, unsaved input on the current screen is lost unless captured in variables.”

===========

Login Flows in Salesforce are typically built using Screen Flows, allowing administrators to present users with prompts, forms, and additional steps during the login process. When more complex logic is needed post-login (e.g., validating conditions or updating data), it is best practice to call an autolaunched flow.

Correct Design:

D. ✅ Use Screen Flow for user interaction and trigger an autolaunched flow in the background to handle logic such as validation, record updates, or redirection.

Incorrect Options:

A. Apex Triggers do not run in login flow context.

B. Handling all logic inside a Screen Flow can result in poor performance or limited modularity.

C. Process Builder and Workflow Rules cannot be used in Login Flows.

Reference Extracts from Salesforce Help – Screen Flows and Login Flows:

“Use Screen Flows for login flows to display forms and route logic through autolaunched flows for complex decisions.”

===========

Following best practices when building flows ensures performance, reliability, and scalability.

A. Correct — Flows should always be built and tested in a sandbox or test environment before deployment to production.

C. Correct — Performing database updates in bulk (after the flow collects all records) minimizes CPU time and DML limit issues.

D. Correct — Accessing external objects after DML operations within the same transaction can cause unexpected behavior due to external system limitations.

Incorrect Options:

B. Allowing end users to change flow structure is not a supported or recommended design pattern.

E. Although saving often is helpful, it is not documented as a core flow design best practice.

Reference Extracts from Salesforce Process Automation Study Guide:

“Avoid

When a Flow encounters an unhandled error, Salesforce sends an error email to the flow owner or the last user who modified the flow. This email includes important debugging information such as:

Flow name and version

The flow element where the error occurred

The error message

The user who was running the flow, including their full name and user ID

Correct Option:

C. View the full name of the run-as user in the email — ✅ This helps identify who encountered the error and what triggered it.

Incorrect Options:

A. You cannot schedule queries from within the email.

B. You cannot directly launch a debugger from an email.

D. The email pertains only to a specific flow instance that failed.

Reference Extracts from Salesforce Help – Debug Flows:

“Error emails contain the user’s name, the element that failed, and details on the error to assist in resolution.”

===========