The most accurate evaluation criteria for this use case is:

B. ✅ “When a record is created, and any time it’s edited to subsequently meet criteria”

This ensures that the rule triggers:

When the record is first created and meets the criteria

Or when it is edited later, and the condition (Stage = Closed Lost and Amount > $1,000,000) becomes true

Incorrect Options:

A. Could cause the action to trigger multiple times even when the criteria remains true.

C. Only runs once at record creation.

D. Is not a valid listed option in Workflow Rule settings.

Reference Extract from Salesforce Help – Workflow Rule Considerations:

“Use ' created, and any time it ' s edited to subsequently meet criteria ' when actions should only happen once per record per condition.”

===========

To automatically update a related field based on changes to another field (such as updating Commission when Entitlement changes), the most effective solution is to use a Record-Triggered Flow with the “Update Related Records” action, often referred to as “Update Records → Related Records.”

A. Correct — This method allows the flow to target related records and apply updates when specific field changes are detected.

Incorrect Options:

B. Master-Detail cannot be applied between individual fields; it is for objects.

C. No such setting exists for " Auto Update Related Fields. "

D. “Allowed Dependencies” is not a valid flow configuration option.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Record-Triggered Flows to perform automatic updates on related records when changes are made to key fields.”

“The ‘Update Records’ element can target records related to the triggering record using lookup relationships.”

To update a record in the future when a specific time condition is met, the correct tool is Flow Builder, specifically using a Scheduled Path in a Record-Triggered Flow or a Scheduled Flow.

Salesforce supports:

Scheduled Paths in Record-Triggered Flows: Executes actions after a specified time has passed since a triggering event.

Scheduled Flows: Autolaunched flows that are configured to run at specific intervals or times, independent of user interaction or record changes.

Incorrect Options:

A. Approvals: Used for routing records through approval steps, not for time-based updates.

B. Process Builder: While it supports scheduled actions, Salesforce is deprecating its use in favor of Flows.

C. Workflow Rules: Time-based workflow actions are legacy and being phased out in favor of Flow.

Reference Extracts from Salesforce Process Automation Documents / Study Guide:

“Scheduled flows are ideal for automating tasks that must be executed at a specific future date and time.”

“Record-triggered flows can use scheduled paths to delay automation until after a defined period.”

===========

In Salesforce Flows, performing DML operations (e.g., create, update, delete) inside a loop is a major performance and scalability risk. It can result in hitting governor limits such as CPU time or the maximum number of DML statements (150 per transaction).

B. Executing actions like creating or updating records — ✅ Correct. Avoid placing DML operations inside a loop. Instead, collect data in a collection variable and perform the operation outside the loop.

Incorrect Options:

A. Nesting loops can be complex but not inherently a limit risk if used carefully.

C. Displaying data to users is not typically done in loops, but it wouldn’t violate limits.

D. Assigning variable values is safe and normal within a loop.

Reference Extracts from Salesforce Process Automation Study Guide:

“To avoid hitting governor limits, never place Create or Update elements inside a loop. Use collection variables to store records and process them after the loop.”

“Bulkify flows by separating DML operations from loop logic.”

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

In Flow Builder, the Run and Debug buttons serve different purposes:

Run: Executes the flow without showing detailed logs or error messages — suitable for simple tests in screen flows.

Debug: ✅ Executes the flow while also displaying detailed step-by-step logs, path taken, variable values, and error messages — essential for troubleshooting.

Incorrect Options:

A. Run is not limited to active flows.

B. Both Run and Debug test the flow, but Debug is used for diagnostics.

C. Debug does not “fix” issues; it helps identify them.

Reference Extracts from Salesforce Help Documentation on Flow Debugging:

“Use Debug to run the flow and view the execution path, variable values, and errors.”

“Run simply executes the flow without displaying debug details.”

When a flow contains screen components, it must be embedded in user-facing areas of the Lightning Experience UI. Salesforce officially supports distributing Screen Flows through:

A. Lightning Pages — Using the Flow component in the Lightning App Builder, screen flows can be placed on record pages, app home pages, and more.

B. Utility Bar — Admins can configure flows to appear as pop-up panels in the utility bar, available globally in apps.

Other options:

C. Buttons: Custom buttons can launch flows, but only auto-launched flows or flows embedded via screen flows and actions. Buttons are not a direct distribution channel for screen flows.

D. LWC JavaScript: Developers can wrap flows in custom Lightning Web Components, but this is not a standard, declarative distribution method.

E. Related List: Related lists do not support embedding flows.

Reference Extracts from Salesforce Process Automation Study Guide:

“To make screen flows available to users, add them to record pages using the Flow Lightning component or add them to the utility bar in the app.”

“Utility bar flows appear in the footer of the Lightning Experience and are accessible globally.”

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

Login Flows are implemented using Screen Flows that display input fields and perform validation or post-login tasks. Salesforce allows you to attach a Screen Flow to the login process via Login Flow Setup. Within this Screen Flow, you can design both the UI and automation logic using decisions, assignments, and actions.

D. Correct — A Screen Flow can both collect user input and execute logic, eliminating the need for separate flow types.

Incorrect Options:

A. Workflow Rules and Process Builder are deprecated and not usable in Login Flows.

B. Apex Triggers cannot be used in Login Flows.

C. Autolaunched Flows are not supported in Login Flow context because they lack a UI.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Screen Flows for Login Flows to display custom screens and execute business logic during user login.”

To create and manage Flow Orchestrations, the user must have the " Manage Flow " permission. Without it, the orchestration builder will not be accessible in Flow Builder.

B. Correct — The “Manage Flow” permission is required to access and build orchestrations.

Incorrect Options:

A. “LEX for Flows” is not a real permission or feature.

C. Referencing External Objects does not block orchestration creation.

D. There is no setting called “Orchestration” in Setup to enable or disable this feature.

Reference Extracts from Salesforce Process Automation Study Guide:

“To build and manage orchestrations, users must have the Manage Flow permission.”

“Flow Orchestration is available in supported editions and does not require a special enablement setting.”

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

===========