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

Every flow in Salesforce is built from core components that define its structure and behavior:

A. Connector — Connectors define the path between elements.

C. Screen — Used in Screen Flows to gather input or display data.

D. Element — Generic term for any step in the flow (e.g., Assignment, Get Records, Screen).

Incorrect Options:

B. Action Group is not a standard Flow component; it may be confused with Process Builder terminology.

E. Test Class is specific to Apex and unrelated to Flows.

Reference Extracts from Salesforce Process Automation Study Guide:

“Flows are composed of Elements (e.g., screens, assignments), Connectors (paths), and Resources.”

“Screen elements enable interaction, and connectors determine how elements are executed.”

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

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

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

In Flow Builder, the Screen element is used to collect information from users interactively. When the flow reaches a Screen element, it pauses and waits for the user to provide input before proceeding. This is ideal for login flows, form submissions, and guided workflows.

D. Correct — The Screen element is explicitly designed to capture user input and pause flow execution until a user acts.

Incorrect Options:

A. Logic elements (e.g., Decision, Loop) are used for controlling flow logic but do not collect input.

B. Integration refers to data interactions (e.g., External Services), not user input.

C. Actions perform operations such as sending emails or creating records, but they don’t involve user input.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Screen elements to display information and collect input from users in a Screen Flow.”

“Screen elements pause the flow until the user completes their interaction.”

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

The Debug button in Flow Builder is a key tool for testing. When clicked, it allows admins to:

Provide test values for input variables.

Walk through the flow step-by-step.

Monitor paths taken by the flow logic.

See data assignments, decisions, loop outcomes, and errors (if any).

Option D is correct — this describes the full purpose and capability of the Debug button.

Incorrect Options:

A. The Debug button does run the latest version, but not due to auto-save mode.

B. Salesforce flows do not support automatic rollback through debugging.

C. Flow versioning must be done manually; debugging does not create new versions.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Debug to test flow logic, provide input values, and monitor detailed element-by-element execution.”

“Debug mode provides enhanced error tracking and variable tracing to help identify issues before activation.”

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

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

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

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

In Process Builder, a trigger determines when the process will run. When creating a new process, the first step involves selecting the object and deciding when the process should run—only when a record is created, or when a record is created or edited. This is known as the trigger for the process.

Option A (Criteria): Defines the specific conditions under which the process actions should fire but does not determine when the process itself is evaluated.

Option B (Trigger): ✅ Correct. It defines the entry point—when the process should evaluate.

Option C (Action): Determines what the process does once the conditions are met.

Option D (Screen): Not used in Process Builder; it belongs to Flow Builder and is used for user interaction.

Reference Extracts from Salesforce Process Automation Documents / Study Guide:

“The trigger determines when the process should run—either on record creation or when a record is created or edited.”

“The criteria define when to execute actions, but the trigger defines when to evaluate criteria.”

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

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

To add a Screen Flow to a Lightning Page, an Administrator or Flow Designer must use the Lightning App Builder. Inside Lightning App Builder, the “Flow” standard component can be dragged onto a page layout.

D. Setup > Lightning App Builder > Page — ✅ This is the correct navigation to modify Lightning record, home, or app pages and embed flows.

Incorrect Options:

A. There is no “Flow Canvas” section in Lightning App Builder.

B. “Edit Page” is part of the App Builder interface, not a Setup-level option.

C. Flow Builder is for building the flow itself, not placing it onto a page.

Reference Extracts from Salesforce Help – Add Flows to Lightning Pages:

“Use Lightning App Builder to add the Flow component to a Lightning record, home, or app page. Then select the Screen Flow to display.”

===========

Salesforce Flow supports multiple types of flows, but the two most commonly supported and configurable types are:

B. Autolaunched Flows: These flows do not require user interaction. They can be triggered automatically via processes, record changes, Apex, or scheduled to run at specific times. They are primarily used for behind-the-scenes automation such as record updates, calculations, and decision logic.

C. Screen Flows: These flows include screens that allow user interaction. Screen flows are typically used in wizards or guided processes where user input is required, such as entering data or making selections.

Incorrect Options:

A. Remote Flows: This is not a supported flow type in Salesforce terminology.

D. Managed Flows: This is not a recognized flow type; “managed” might refer to package-managed flows, but it's not a flow type classification.

Reference Extracts from Salesforce Process Automation Documents / Study Guide:

“Autolaunched flows run in the background without user interaction.”

“Screen flows provide a UI for user interaction.”

“Salesforce Flow supports Screen Flows, Autolaunched Flows (with or without triggers), Scheduled Flows, and more.”

===========