In the Spring ' 21 Release, Salesforce introduced a key enhancement that allows Admins and Developers to see the exact CPU time consumed by Flows and Processes. This was added to help identify automation performance bottlenecks and determine which automations are consuming excessive CPU time, which could lead to governor limit violations.

Correct Option:

B. Accurate measure of the CPU time consumption of Flows and Processes — ✅ This enhancement added a more granular breakdown in debug logs for better monitoring.

Incorrect Options:

A. No such official feature as “Stagger and Throttle plug-ins” exists.

C. " Black run-as access " is not a documented or supported Salesforce feature.

D. Optimizer evaluates usage patterns but does not measure CPU time.

Reference Extracts from Salesforce Release Notes Spring ’21 - Performance Enhancements:

“In Spring ’21, debug logs now show more accurate CPU time usage of Flows and Processes.”

===========

The Debug button in Flow Builder is designed to help administrators test their flows in real-time. When using Debug, admins can:

Enter custom values for input variables.

Observe the flow’s path of execution.

Monitor how decisions and assignments behave.

See outputs, errors, and element-by-element outcomes.

This helps identify logic issues before activating the flow.

A. Correct — The Debug tool is intended for entering input values and viewing detailed flow execution results.

Incorrect Options:

B. Auto-save settings are unrelated to the Debug tool.

C. Flow versioning is handled manually and not linked to debugging.

D. Flows do not support rollbacks of committed database changes during debugging.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Debug to test a flow’s logic step-by-step, passing values into input variables and monitoring outcomes.”

“Debugging helps trace decision paths, assignments, and screen navigation.”

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

Local Actions are custom Lightning components (Aura-based) that can be used in Screen Flows to interact with external systems or perform client-side logic.

A. Correct — Lightning components used in Flow are only supported in Lightning Runtime.

B. Correct — Local Actions are only supported in Screen Flows (not autolaunched or background flows).

Incorrect Options:

C. Local Actions can be tested in Developer Edition orgs and standard sandboxes; there is no such restriction to Partial or Full.

D. Autolaunched Flows do not support Local Actions; therefore, the system context does not apply.

Reference Extracts from Salesforce Process Automation Study Guide:

“Local Actions are available only in Screen Flows and must run in Lightning Runtime.”

“Use Local Actions in flows to perform custom logic or integrate with client-side systems via Lightning components.”

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

===========

Flow Builder provides a Loop element under the Logic category that allows flow designers to iterate over a collection (list) of records one at a time. This is useful for applying changes to each record, evaluating conditions, or accumulating results.

B. Correct — The Loop element under Logic is designed specifically for iterating through collections.

Incorrect Options:

A. Integration elements are used for calling external services.

C. Screen is for user input, not iteration.

D. Action elements execute tasks, not control flow iteration.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Loop element to iterate over items in a collection. It’s a type of Logic element in Flow Builder.”

“Each loop cycle processes one item from the collection.”

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

You can create Object-Specific Actions that launch a Flow directly from a record page (e.g., Opportunity). This allows users to launch feedback flows with record context automatically passed into the flow.

D. Correct — Object-Specific Actions can launch flows tied to specific record types like Opportunity.

Incorrect Options:

A. While buttons can launch flows, object-specific actions are more user-friendly and are shown in quick actions.

B, C. Surveys are valid for feedback collection but not integrated as Object-Specific Actions directly in this context.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use Object-Specific Actions to launch Screen Flows from record pages.”

“Flows can automatically receive the recordId from the object when triggered by a quick action.”

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

Salesforce Flow for Service leverages Flows built in Flow Builder and deploys them using the Actions and Recommendations component. Admins use Actions and Recommendations deployments to define which flows and when they should be shown to agents in the Lightning Service Console.

A. Correct — Create flows using Flow Builder, then configure them within an Actions and Recommendations deployment or reference them in a process.

Incorrect Options:

B and C — Actions and Recommendations is not configured from Process Builder or Flow directly but through deployment setup in Setup.

D. Process Builder is deprecated for future use and not the recommended tool for this function.

Reference Extracts from Salesforce Process Automation Study Guide:

“Actions and Recommendations surface guided workflows built with Flow Builder. These are deployed via Actions and Recommendations deployments.”

“Use Flow Builder to build Screen Flows, then configure them for use in the console using the component.”

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

The Flow Debug Details in Salesforce provide an accurate measure of CPU time consumption for each flow execution. This insight allows administrators to identify which elements or actions in a flow are consuming excessive resources and are potential performance bottlenecks.

E. Correct — Salesforce provides CPU time consumption data in debug logs and Flow Debug details, which helps admins fine-tune flows and avoid hitting governor limits.

Incorrect Options:

A. “Stagger and Throttle plug-ins” is not a standard Salesforce feature.

B. “Blacktab run-as access” is not a recognized Salesforce product or feature.

C. Optimizer helps identify unused components and metadata, not runtime performance issues.

D. Raising a case may help in extreme cases but is not a proactive or scalable way to detect bottlenecks.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use flow debug logs to monitor CPU time and identify inefficient elements in your flow.”

“Monitor execution details such as memory usage, loop iterations, and DML limits to optimize automation performance.”

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

External Objects in Salesforce connect to data that resides in external systems. When used in Flows:

A. Correct — You can read and update External Object records in Flows, but you cannot create new External Object records via Flow due to their read-only nature in terms of creation.

Incorrect Options:

B. Incorrect — External Objects are accessed via OData connectors, not exclusively through SOAP.

C. Incorrect — External Objects have certain limitations and are not treated exactly the same as standard objects.

D. Incorrect — You typically do not update Display URLs or External IDs via flow; they are managed via the external source.

Reference Extracts from Salesforce Process Automation Study Guide:

“Flows support read and update operations on external objects but not create operations.”

“External Objects rely on external systems to manage their lifecycle and do not support DML operations such as create.”

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

When building flows for external users (such as customers or partners), they should be distributed using Sites or Experience Cloud Portals. These flows are typically used for collecting data from people who are not Salesforce internal users.

Valid use cases include:

A. Survey forms — Screen flows can collect external user feedback.

C. Interest forms — Data collection before events, campaigns, or inquiries.

E. Product registration — Collecting details on newly purchased products from customers.

Incorrect use cases:

B. Service rep script — This is intended for internal users and belongs in a Service Console.

D. Lead conversion wizard — This task is internal and should be handled within the authenticated Salesforce org.

Reference Extracts from Salesforce Process Automation Study Guide:

“Flows distributed through Sites or Portals are ideal for data collection from unauthenticated users.”

“Use Screen Flows to build custom forms that external users can access through Experience Cloud or Sites.”

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