In Salesforce Flow, variables are dynamic resources used to store values that can change during the execution of the flow. You can assign and reassign values to variables using Assignment elements.
A). Text Template: Static content used for emails, messages, or display - it cannot change mid-flow.
B). Formula: Computed value based on current context - recalculated, but not " changed " directly.
C). Stage: Not a resource type in Flow; possibly referring to flow screen stage or Opportunity stage.
D). Variable: # Correct. The only flow resource that you can update during flow execution.
Reference Extracts from Salesforce Help Documentation on Flow Resources:
"A variable is a resource that stores values that can change as the flow runs."
"Other resources like text templates and formulas are static or calculated at runtime."

Process Builder allows the following key process actions:
A). Submit the record for approval: This is a supported action that can be configured declaratively.
B). Send email and/or Post to Chatter: Process Builder can send email alerts and post Chatter messages as part of its action options.
D). Create and update records: Process Builder allows you to modify the record that triggered the process or related records (parent/child/sibling).
Incorrect Options:
C). Merging fields from different records is not directly supported via Process Builder actions.
E). Exporting resources is not a feature supported within Process Builder.
Reference Extracts from Salesforce Help Documentation on Process Actions:
"Use actions to update records, send emails, submit for approval, or post to Chatter."
"Process Builder supports creating new records and updating related records."Reference: Salesforce Help Documentation on Process Builder Actions.

User-interactive flows (Screen Flows) can be distributed in the following ways:
B). # Flow Actions - Flows can be exposed as Quick Actions or Global Actions and launched from buttons.
C). # Custom Lightning Web Components - Developers can embed flows within LWCs using the lightning- flow base component.
E). # Lightning Pages - Admins can add flows directly to record, home, or app pages using the Flow standard component in Lightning App Builder.
Incorrect Options:
A). "Microservice Frame" is not a Salesforce feature.
D). "Field Portal Mobile App" is not a native Salesforce product and is not related to Flow distribution.
Reference Extract from Salesforce Help - Flow Distribution:
"You can distribute flows using Flow Actions, embed them in Lightning Pages, or include them in Custom Components."Reference:Salesforce Help - Distribute Flows

"Lightning Flow" is the umbrella term used by Salesforce to refer to two core declarative automation tools:
Flow Builder: The primary visual interface for creating flows of all types, such as screen flows and autolaunched flows.
Process Builder: Although being phased out, it has historically been part of the Lightning Flow suite as a tool for declarative automation based on field changes and conditions.
Incorrect Options:
A). Lightning Experience is the UI, not part of the automation toolset.
B). Approvals are not part of the Lightning Flow product family. They are a separate automation feature in Salesforce.
D). Lightning App Builder is a UI layout tool, not related to process automation.
Reference Extracts from Salesforce Process Automation Documents / Study Guide:
"Lightning Flow includes Flow Builder and Process Builder for creating automated processes." Reference:Salesforce Help - Lightning Flow

Approval Processes are used to handle structured approval requests in business workflows. They are best suited for scenarios where a user must approve a record before changes or further processing can occur.
B). Correct - Selecting a candidate and generating an interview record as part of a formal approval process is a valid use case.
D). Correct - Approval processes are often used for time tracking where a manager must approve a timecard before status is updated.
Incorrect Options:
A). This is best handled with Flow or Formula logic.
C). Use a Flow or Process Builder to update child records based on changes in a parent.
Reference Extracts from Salesforce Process Automation Study Guide:
"Approval Processes are ideal for structured, multi-step workflows requiring user sign-off before data changes."
"Use approval steps to define criteria and resulting actions such as field updates, record creation, or notifications."