In Process Builder, a process is made up of three core building blocks:
Trigger: Specifies when the process should start, such as when a record is created or edited.
Criteria Node: Defines the condition(s) that must be true for actions to be executed.
Actions: Define what happens when the criteria are met - examples include creating records, updating fields, and sending emails.
Incorrect Options:
B). Scheduler: Not a component of Process Builder. Scheduling is handled differently, typically in Flow.
C). Timer: Not a term used within Process Builder.
Reference Extracts from Salesforce Help Documentation on Process Builder:
"A process consists of a trigger, criteria, and actions."
"Each criteria node defines conditions and the actions to execute when those conditions are met."

To execute flows (both screen and autolaunched flows), a user must have the Run Flows user permission.
This permission ensures users can initiate and interact with flows provided in the UI or behind the scenes.
C). Correct - Run Flows allows users to start and complete flows.
Incorrect Options:
A). Manage Flows allows creation and modification of flows, not execution.
B). Flow User is a legacy license label, not a permission.
D). View Screen Flows is not an official Salesforce permission.
Reference Extracts from Salesforce Process Automation Study Guide:
"Users must have the 'Run Flows' permission to execute screen flows or autolaunched flows."
"Ensure appropriate profiles or permission sets grant this permission."

When an orchestration encounters an error, Salesforce can send orchestration error email notifications to designated recipients. Additionally, the Orchestration Runs list in Setup shows all active and failed orchestration runs with error details.
B). Correct - Admins receive orchestration error email notifications if configured properly.
D). Correct - Errors are displayed in the Orchestration Runs section in Setup.
Incorrect Options:
A). Event Monitoring is for advanced analytics and not specific to orchestration debugging.
C). Flow error emails are sent for standalone flow errors, not specifically orchestration.
Reference Extracts from Salesforce Process Automation Study Guide:
"Orchestration error notifications alert admins to issues in orchestration flow runs."
"Monitor orchestration activity and errors from the Orchestration Runs page in Setup."

Salesforce allows administrators to create object-specific quick actions that launch flows directly from record pages. This is ideal for collecting feedback, such as when a sales rep closes an Opportunity.
D). Use Salesforce Flow with object-specific action - # A Screen Flow can be launched from an Opportunity record using an object-specific Quick Action. The flow can include fields to gather feedback, and the record context (Opportunity ID) is passed automatically.
Incorrect Options:
A). Process Builder cannot be used to launch a flow via object-specific actions.
B). While Salesforce Surveys are valid tools, they are not integrated with object-specific actions in this way.
C). Using Apex is unnecessary for this use case when standard Flow and Quick Actions provide a declarative solution.
Reference Extracts from Salesforce Help - Object-Specific Quick Actions:
"You can launch Screen Flows from object-specific quick actions to collect user input related to the current record."

To execute a flow, the user must:
D). # Have the "Run Flows" permission, which allows them to execute flows that are not auto-launched (e.g., Screen Flows).
C). # Have the "Flow User" checkbox selected on their User detail page to ensure proper permission execution context.
Incorrect Options:
A and B. While object and field permissions apply, they are not specific flow execution requirements. Flow errors will occur only if access is restricted at runtime.
Reference Extract from Salesforce Help - Flow Execution and User Permissions:
"Users must have the Run Flows user permission and the Flow User checkbox enabled to execute flows."