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

Since the data volume is stable and updated frequently in an external system, and there's no need to store it in Salesforce, Salesforce Connect is the best choice. It allows real-time access to external data using External Objects. This can be used alongside Flows for automation.

C. Correct — Salesforce Connect provides real-time access, and Flows can automate interaction with that data.

Incorrect Options:

A. ETL tools are for batch data movement, not real-time access.

B. External Services is more suitable for actions (not data listing or queries).

D. Local Actions are used in Screen Flows, not ideal for real-time data integration.

Reference Extracts from Salesforce Process Automation Study Guide:

“Salesforce Connect allows integration with external data sources using External Objects for real-time data access.”

“Use Flow to automate interactions with external objects when data doesn’t need to be stored.”

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

In Flow Builder, the Manager tab is where all resources—including variables, constants, formulas, and choices—are displayed. It provides access to both system-generated and manually created resources.

C. Manager tab — ✅ Correct. It is the dedicated area for managing flow resources.

Incorrect Options:

A. Canvas — Used to place flow elements, not to manage resources.

B. Elements tab — Allows selection of flow elements (e.g., Assignment, Screen), not resources.

D. Button Bar — Refers to Run, Debug, Save, etc., not resource management.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Manager tab in Flow Builder to create and manage resources such as variables, formulas, and constants.”

“The Manager tab lists every resource available in your flow, whether created manually or auto-generated.”

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

The Decision element is the only element in Flow Builder that provides branching logic. It evaluates conditions and decides the direction the flow should take next based on the defined outcomes.

A. Assignment: Used to assign or change variable values; does not create logic branches.

B. Loop: Used to iterate through items in a collection.

C. Subflow: Used to invoke another flow but cannot implement branching directly.

Reference Extracts from Salesforce Help Documentation on Flow Builder Elements:

“The Decision element lets you conditionally route your flow along different paths based on logic you define.”

===========

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

===========

Salesforce recommends using declarative tools like Flow to automate updates to related records. In this use case, a Record-Triggered Flow can be created on the Account object. When the billing address of the HQ account is updated, the flow can identify and update all related branch accounts (using a defined relationship such as a lookup or parent-child).

B. Correct — Create a Record-Triggered Flow on Account that checks for changes to the billing address and updates child records accordingly.

Incorrect Options:

A. Dataloader is a manual tool, not a real-time automation solution.

C. Apex can solve this but is not required for such declarative use cases.

D. A formula field only displays data; it does not trigger updates.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Record-Triggered Flows to update related records based on changes to a parent record.”

“Flows can be configured to loop through child records and apply updates when specific field values change.”

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

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

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

In Salesforce Flow, to post to a Chatter feed and mention the record owner, the Post to Chatter action can be used with a message input. Mentions are added using the syntax:

@[{!User.Id}] or simply @[reference], where the reference points to a user ID.

This enables the Chatter post to tag the record owner by dynamically inserting their user ID into the message.

Incorrect Options:

A. There is no concept of “flow directives”; this terminology is incorrect.

B. Assignment is used to assign values to variables but not to create a Chatter mention.

C. Creating shadow records is not necessary and overly complex for this use case.

Reference Extracts from Salesforce Help - Automate Posts to Chatter Using Flow:

“Use the Post to Chatter action to send a message to a record's feed. Mention users by entering @[userId].”

===========

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

===========

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

===========

This question appears to conflate “use cases” with flow elements, but the intent is to ask what kind of conditions or logic scenarios a Decision element can evaluate. Here’s the breakdown:

A. Get Record — When used before a Decision, it provides data that can be inspected in the Decision logic.

C. Find a Matching Record — This is a use case supported by combining Get Records + Decision elements.

D. Match Record — Similar to C, this describes the scenario of checking if a record meets specific criteria.

A, C, D: Correct — These represent valid use cases where a Decision element inspects a retrieved record or value.

Incorrect Option:

B. "Find Record" is not a Salesforce term or specific action.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Decision elements to evaluate the output of Get Records and branch based on criteria.”

“Common use cases include checking if a matching record exists or evaluating a field’s value.”

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