Free Practice Questions for Salesforce Process-Automation Exam

The Debug feature in Flow Builder allows administrators to run the flow in a testing environment, supply test values for input variables, and view detailed logs of flow execution including path taken, values assigned, and where errors occurred.

Correct Option:

A. ✅ Debug lets admins provide test inputs and view real-time flow behavior for troubleshooting.

Incorrect Options:

B. Debug does not roll back database changes unless "rollback mode" is explicitly selected.

C. Auto-save mode is unrelated to debugging.

D. You cannot create new flow versions from the Debug panel; versioning is done separately.

Reference Extract from Salesforce Help – Debug a Flow:

“The Debug button allows you to test your flow with custom inputs and see detailed information about how it runs, including any errors encountered.”

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

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

Platform Events are part of Salesforce's event-driven architecture. When using Flows to subscribe to Platform Events, it’s important to understand how event listeners are tracked and how Flows interact with those events.

B. Correct — The Subscriptions related list on a Platform Event's detail page lists flows, Apex triggers, and processes subscribed to the event.

Incorrect Options:

A. Salesforce does not automatically prevent infinite loops; developers must design safeguards.

C. If a package with active event subscriptions is uninstalled, it can break functionality unless cleaned up.

D. You cannot query Platform Event messages using SOQL; events are ephemeral and processed in real-time.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Subscriptions related list to view flows, triggers, and other automation tools listening to a Platform Event.”

“Platform Event messages are not stored in the database and cannot be queried via SOQL.”

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

Salesforce provides several standard components for use in Screen Flows, including:

A. Phone Number — A standard input field that formats and validates phone numbers.

B. File Upload — Allows users to upload one or more files to a record.

C. URL — Used to capture or display a website address.

Incorrect Options:

D. Animations are not a standard component in Flow Builder.

E. “MIME Image” is not a provided screen component.

Reference Extracts from Salesforce Process Automation Study Guide:

“Screen Flow elements include standard components like text, phone, URL, date, file upload, and more.”

“Use File Upload component to let users attach files directly to records.”

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

Outbound Message Actions are part of the declarative automation toolkit in Salesforce (used within Workflow Rules and Flow Builder). They allow Salesforce to send data (in the form of a SOAP message) to an external web service endpoint automatically when specific criteria are met.

D. Correct — Outbound Message Action is a declarative method to push data updates to external systems when a record change occurs (e.g., employee offboarding).

Incorrect Options:

A. Salesforce Handler is not a native automation tool or term in Salesforce.

B. JSON Auto Connector is not an official Salesforce feature.

C. “API Connect” refers to third-party integration platforms, not a native Salesforce feature.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use an Outbound Message to send information to an external web service in response to data changes in Salesforce.”

“Outbound Messages allow real-time integration without writing code, using SOAP-based communication.”

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

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

===========

When a flow interview fails and no fault path is configured, Salesforce sends a default error email to the flow owner or designated error recipients. However, if the flow includes a fault path (configured using a Fault Connector), Salesforce follows that path and sends an email or performs alternate logic, such as logging the error or showing a friendly message.

B. Correct — Fault paths allow graceful error handling and can include email alerts.

Incorrect Options:

A. System Admins are not notified by default unless they are explicitly configured as recipients.

C. Email localization is not guaranteed by default for flow errors.

D. The user is shown an error; they are not redirected to the beginning of the flow automatically.

Reference Extracts from Salesforce Process Automation Study Guide:

“Flows can use Fault paths to handle errors gracefully. These paths allow for sending error messages, email alerts, or redirecting logic.”

“If no Fault path is set, a default error message is displayed, and an error email is sent.”

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

In Salesforce Flow Builder, flow elements are broadly categorized into three functional types:

Screen elements — Capture user input (e.g., screens, display text, choice inputs)

Logic elements — Direct the flow (e.g., Decision, Assignment, Loop)

Action elements — Interact with Salesforce or external systems (e.g., Create Record, Send Email, Subflow)

Correct Option:

B. ✅ Screen, logic, and actions

Incorrect Options:

A. Not official categories of Flow elements.

C. “Connectors” are how elements are linked, but not a category of elements.

D. Variables and choices are resources, not flow elements.

Reference Extracts from Salesforce Help – Flow Element Reference:

“Flow elements fall into categories such as Screen (UI), Logic (routing), and Actions (system interaction).”

===========

The Flow Debug Details in Salesforce provide an accurate measure of CPU time consumption for each flow execution. This insight allows administrators to identify which elements or actions in a flow are consuming excessive resources and are potential performance bottlenecks.

E. Correct — Salesforce provides CPU time consumption data in debug logs and Flow Debug details, which helps admins fine-tune flows and avoid hitting governor limits.

Incorrect Options:

A. “Stagger and Throttle plug-ins” is not a standard Salesforce feature.

B. “Blacktab run-as access” is not a recognized Salesforce product or feature.

C. Optimizer helps identify unused components and metadata, not runtime performance issues.

D. Raising a case may help in extreme cases but is not a proactive or scalable way to detect bottlenecks.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use flow debug logs to monitor CPU time and identify inefficient elements in your flow.”

“Monitor execution details such as memory usage, loop iterations, and DML limits to optimize automation performance.”

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

Lightning Flows can be configured to selectively display, assign, or restrict access to records based on conditions such as user role, profile, or custom metadata. In combination with Flow and record-level access logic (e.g., ownership, sharing settings), the system can enforce visibility rules.

D. Correct — Flows can enforce business logic to hide or prevent access based on context, especially when tied with conditions about the user or record type.

Incorrect Options:

A. Process Builder does not manage UI visibility.

B. Apex Triggers execute at the database level, not in the UI.

C. Dynamic Forms are used to conditionally show/hide fields, not entire records.

Reference Extracts from Salesforce Process Automation Study Guide:

“Flows can be used to enforce access control by checking user roles or profiles before displaying or updating records.”

“Combine Flow logic with conditional checks to enforce business rules for different user groups.”

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