When configuring Email Alerts in Salesforce (used in Workflow, Process Builder, and Flow), the system allows selecting specific recipient types. Among the valid options:
B). Case Owner - Valid recipient type in Email Alerts.
D). Account Owner - Supported recipient type.
E). Account Team - Supported as long as Account Team members are defined.
Incorrect Options:
A). Campaign Owner is not a supported email alert recipient out-of-the-box.
C). Portal Role is not an available option in Email Alert configuration.
Reference Extracts from Salesforce Process Automation Study Guide:
"Email Alerts can be sent to users, roles, public groups, and related record owners like Case Owner or Account Owner."
"Account Team members can be selected as recipients in Email Alert configuration."

In Salesforce Flow, a record variable holds the values for a single record of a specific object type (e.g., one Account or one Contact).
A). # A record variable stores a structured set of field values for one record and is used for input, manipulation, and output within a flow.
Incorrect Options:
B). The concept of " Global " is unrelated to what record variables store.
C). This describes a Record Collection Variable, not a single record variable.
D). Multiple object types would require separate variables per object type.
Reference Extracts from Salesforce Help - Work with Record Variables in Flow:
"A record variable stores the field values for one record."
"If you need to store multiple records, use a record collection variable instead."

Salesforce Flow supports multiple versions of a flow, but only one version can be active at any time. The active version is the one that will be executed when the flow is invoked.
C). # A single active version ensures consistency and control over which logic is running.
Incorrect Options:
A, B, D: You can create up to 50 versions of a flow, but only one can be active.
Reference Extracts from Salesforce Help - Version a Flow:
"You can have up to 50 versions of a flow, but only one version can be active at a time."Reference:Salesforce Help - Activate or Deactivate a Flow

Lightning Flows can be configured to selectively display, assign, or restrict access to records based on conditions such as user role, profile, or custom metadata. In combination with Flow and record-level access logic (e.g., ownership, sharing settings), the system can enforce visibility rules.
D). Correct - Flows can enforce business logic to hide or prevent access based on context, especially when tied with conditions about the user or record type.
Incorrect Options:
A). Process Builder does not manage UI visibility.
B). Apex Triggers execute at the database level, not in the UI.
C). Dynamic Forms are used to conditionally show/hide fields, not entire records.
Reference Extracts from Salesforce Process Automation Study Guide:
"Flows can be used to enforce access control by checking user roles or profiles before displaying or updating records."
"Combine Flow logic with conditional checks to enforce business rules for different user groups."

Process Builder supports multiple criteria nodes with independent action groups. If a record meets multiple criteria nodes in a single process, the system evaluates each node and executes the associated actions as applicable.
Correct Option:
C). # One Process with multiple criteria nodes is optimal. Each condition can trigger its own actions independently.
Incorrect Options:
A and B. Workflow Rules cannot easily handle multiple branching conditions with independent actions.
D). Creating two processes is unnecessary overhead and adds complexity.
Reference Extract from Salesforce Help - Process Builder:
"Each process can include multiple criteria nodes and associated actions. A record can trigger multiple actions if it meets multiple criteria."