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

In Flow Builder, administrators can use a fault path (fault connector) from a flow element (such as Create or Update Records) to a Screen element. This screen can include a Display Text component with an error message for the user.

D. Correct — This is the standard approach to handle errors gracefully in Screen Flows.

Incorrect Options:

A. Conditional highlighting is not a supported feature in Flow Screens.

B. "Uncategorized under Actions" does not exist in Flow Builder.

C. AppExchange apps are unnecessary for basic error handling.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use a fault connector to direct the flow to a screen that explains the error to the user.”

“Fault paths allow for graceful handling of errors, including user-friendly messages.”

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

Salesforce Flows can be invoked from several external or internal mechanisms:

B. LWC (Lightning Web Component) — Flows can be embedded into LWCs or invoked via the lightning-flow base component.

C. REST API — You can call autolaunched flows using the REST API via Flow Interview endpoints.

E. Apex — Flows can be called using the Flow.Interview class in Apex.

Incorrect Options:

A. Apex WSDL — Refers to legacy SOAP-based integrations with Apex classes, not Flows.

D. SOAP API — While Salesforce does offer SOAP API for many objects, flows are best invoked through REST or Apex for automation scenarios.

Reference Extracts from Salesforce Process Automation Study Guide:

“You can invoke flows from Apex, REST API, Process Builder, and Lightning components.”

“The lightning-flow component in LWC allows screen flows to be embedded and executed declaratively.”

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

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

===========

Flows that involve user interaction (Screen Flows) can be made available to users using several distribution methods:

B. Lightning Pages: You can embed a flow in a Lightning App page, Record page, or Home page using the Flow standard component.

C. Flow Actions: You can launch flows as Quick Actions from the UI.

D. Custom Lightning Web Components: Flows can be embedded and invoked inside custom LWCs, giving developers flexibility in UI design.

Incorrect Options:

A. Field Portal Mobile App: Not a Salesforce distribution method.

E. Microservice Frame: Not a Salesforce-recognized term or method for distributing flows.

Reference Extracts from Salesforce Help Documentation on Flow Distribution Methods:

“You can distribute screen flows via Lightning pages, flow actions, and embed them in Lightning components.”

“Custom Lightning web components can call flows using the lightning-flow component.”

===========

An approval process consists of a sequence of steps and rules that determine whether a record should be approved or rejected. The three essential components are:

A. Actions — Define what happens when the record is submitted, approved, or rejected.

B. Criteria — Determine when the record is eligible for the approval process.

C. Approvers — Specify who needs to approve the record.

Incorrect Options:

D. Fields are updated but not a core component of the approval process structure.

E. Steps are part of the process, but the fundamental components are Actions, Criteria, and Approvers.

Reference Extracts from Salesforce Process Automation Study Guide:

“Approval Processes are composed of criteria, approvers, and actions that define the submission, approval, or rejection path.”

“Each approval step contains one or more approvers and actions to execute.”

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

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

===========

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

In Salesforce Flow, variables are dynamic resources used to store values that can change during the execution of the flow. You can assign and reassign values to variables using Assignment elements.

A. Text Template: Static content used for emails, messages, or display — it cannot change mid-flow.

B. Formula: Computed value based on current context — recalculated, but not "changed" directly.

C. Stage: Not a resource type in Flow; possibly referring to flow screen stage or Opportunity stage.

D. Variable: ✅ Correct. The only flow resource that you can update during flow execution.

Reference Extracts from Salesforce Help Documentation on Flow Resources:

“A variable is a resource that stores values that can change as the flow runs.”

“Other resources like text templates and formulas are static or calculated at runtime.”

===========

Salesforce allows up to 50 versions of a flow to be stored, but only one version can be marked as active at a time. The active version is the one that runs when the flow is triggered or launched.

C. Correct — only one active version per flow is allowed.

A, B, D — These refer to version count, not how many can be active.

Reference Extracts from Salesforce Process Automation Study Guide:

“You can save up to 50 versions of a flow, but only one version can be active at a time.”

“Activate the specific version you want users or systems to run.”

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