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

===========

To expose the value of a flow variable back to the component, process, or Apex that invoked the flow, the variable must be marked as Available for output.

C. Available for output: ✅ This allows the variable’s value to be accessed after the flow finishes executing.

Incorrect Options:

A. " Field is required " makes the variable mandatory but has no effect on input/output.

B. " Allow Multiple Values " enables collection variables, not output access.

D. " Available for input " allows the flow to receive a value into the variable, not output it.

Reference Extracts from Salesforce Help Documentation on Flow Variables:

“Mark a variable as Available for output to allow flows, Apex, and other callers to retrieve its value.”

“Use ‘Available for input’ to pass data into the flow; use ‘Available for output’ to return data.”

===========

During Lead conversion in Salesforce:

A. ✅ An Account is created if no matching Account exists.

D. ✅ Custom Lead fields can be mapped to standard or custom fields on the resulting Account, Contact, or Opportunity via field mapping settings.

Incorrect Options:

B. A Contact is always created, regardless of whether a match is found.

C. Creating an Opportunity is optional during Lead conversion.

Reference Extract from Salesforce Help – Customize How Leads Get Converted:

“Admins can map custom lead fields to account, contact, or opportunity fields.”

“Opportunity creation is optional during lead conversion.”

===========

In Flow Orchestration, each execution instance is referred to as a " Run. " This terminology is used to monitor active or completed orchestrations in the Orchestration Runs list in Setup.

D. Correct — Each time an orchestration is executed, it is called a Run.

Incorrect Options:

A. " Session " is not used in orchestration terminology.

B. " Interview " is the term for individual Flow executions, not orchestration-level.

C. " Spool " is not a recognized Salesforce automation term.

Reference Extracts from Salesforce Process Automation Study Guide:

“Each execution of a flow orchestration is called a Run and can be monitored in the Orchestration Runs list in Setup.”

“Use the Orchestration Run view to examine errors, progress, and completion status.”

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

To post to Chatter after a time delay (7 days after a Case is opened), a Scheduled Action should be used within a declarative automation tool.

D. Scheduled Process Builder — ✅ Process Builder allows for scheduled actions (e.g., “7 days after CreatedDate”) that can post to Chatter or take other actions.

Incorrect Options:

A. Apex Trigger could work but is not necessary when a declarative tool like Process Builder is sufficient.

B. LWC is a front-end UI framework, not used for backend time-based automation.

C. Scheduled Workflow Rules are legacy and do not support Chatter Post actions natively.

Reference Extracts from Salesforce Help Documentation:

“Scheduled actions in Process Builder can be used to wait for a set time and then perform actions such as posting to Chatter.”Explanation:

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

===========

Salesforce Screen Flows support embedding custom Lightning Web Components. To allow users to select an asset during onboarding, the LWC should be embedded directly into the flow via the Screen element.

C. Correct — The LWC must implement the lightningFlowScreen interface to be used within a flow screen.

Incorrect Options:

A. iframe embedding is not supported in Screen Flows.

B. Workflow Rules are deprecated and do not support interaction with LWCs.

D. Lightning Out is used to run Salesforce components in external applications—not relevant for internal Screen Flows.

Reference Extracts from Salesforce Process Automation Study Guide:

“To use a custom LWC in a Screen Flow, implement the lightningFlowScreen interface.”

“Screen Flows allow you to incorporate custom LWCs to extend UI functionality.”

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

In Flow Builder, a variable is a type of resource that stores temporary data used during the flow’s execution. Variables can be modified as the flow progresses, making them ideal for dynamic logic, calculations, and user input storage.

Correct Option:

C. ✅ Variable — Designed to hold and change data during a flow’s runtime.

Incorrect Options:

A. Error Message is not a data-holding resource.

B. Text Template is static and cannot be changed mid-flow.

D. Formula resources are read-only and recalculated but not updated directly.

Reference Extract from Salesforce Help – Flow Variables:

“Use variables to temporarily store values. Variables can hold strings, numbers, records, and more. They can change throughout the flow.”

===========

In Flow Orchestration, Work Items are assigned to users or groups for action. To support assignment to a team where any user can act on it, the appropriate feature is Work Groups.

C. Correct — Work Groups allow multiple users to share responsibility for completing a task in Flow Orchestration.

Incorrect Options:

A. Work Stages define the phases of the orchestration, not user access.

B. Work Queues are not a Salesforce concept in Flow Orchestration.

D. Work Items are the tasks created but don’t define group access or roles.

Reference Extracts from Salesforce Process Automation Study Guide:

“Work Groups allow work items to be assigned to multiple users, where any member can take ownership.”

“Use Work Groups to delegate responsibility across teams in Flow Orchestration.”

When building and using custom screen components in Salesforce Flow, there are several key considerations:

A. Correct — Custom Lightning components used in Flow run only in Lightning Runtime (not Classic).

B. Correct — Custom components can be created by developers or installed from AppExchange.

D. Correct — Screen components are only supported in Screen Flows, not Auto-Launched Flows.

Incorrect Options:

C. The " Use Lightning Components " checkbox was deprecated; it is no longer required in newer versions of Flow.

E. Visualforce is a legacy technology and not used to distribute Lightning-based Screen Flows.

Reference Extracts from Salesforce Process Automation Study Guide:

“Custom screen components are supported only in Screen Flows and run in Lightning Runtime.”

“You can install screen components from AppExchange or build your own using Lightning Web Components.”

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