Salesforce recommends using declarative tools like Flow to automate updates to related records. In this use case, a Record-Triggered Flow can be created on the Account object. When the billing address of the HQ account is updated, the flow can identify and update all related branch accounts (using a defined relationship such as a lookup or parent-child).
B). Correct - Create a Record-Triggered Flow on Account that checks for changes to the billing address and updates child records accordingly.
Incorrect Options:
A). Dataloader is a manual tool, not a real-time automation solution.
C). Apex can solve this but is not required for such declarative use cases.
D). A formula field only displays data; it does not trigger updates.
Reference Extracts from Salesforce Process Automation Study Guide:
"Use Record-Triggered Flows to update related records based on changes to a parent record."
"Flows can be configured to loop through child records and apply updates when specific field values change."

Flows execute in the context of the running user, unless explicitly set to System Context. If the user does not have access to certain objects or fields, the flow will throw a permission error during execution.
A). Correct - Missing object or field-level permissions for the flow user is a common cause of runtime errors.
Incorrect Options:
B). Person accounts are unrelated to flow execution.
C). There ' s no such requirement that Screen Flows need role-based access.
D). API access is not required to run a flow via the UI.
Reference Extracts from Salesforce Process Automation Study Guide:
"Flows run in user context by default, respecting all object and field-level permissions."
"Ensure that the running user has access to all referenced objects and fields."

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

To conditionally restrict deletion of records based on field values (like Opportunity Stage), you must intercept the delete action and stop it when certain criteria are met. This is not achievable through Validation Rules or profile-level permissions (which are all-or-nothing at the object level). The best way to achieve this in Flow is through a Before Delete Record-Triggered Flow that invokes an Apex action to throw a custom error when the condition is met.
D). Correct - A Record-Triggered Flow on delete, combined with invocable Apex, can block deletion based on specific record field values.
Incorrect Options:
A). Profile object permissions cannot apply field-level logic to deletions.
B). Platform Events are not related to deletion restrictions.
C). Validation Rules do not trigger on deletions.
Reference Extracts from Salesforce Process Automation Study Guide:
"To restrict deletion conditionally, use a Before Delete flow with an Apex action that throws an error if conditions are met."
"Validation Rules are not evaluated during delete operations."

Schedule-Triggered Flows can be configured to run at frequent intervals (e.g., hourly) and include logic to retrieve data from external sources using External Services, HTTP Callouts (via Apex actions), or External Objects.
A). Correct - Schedule-Triggered Flows support declarative execution at scheduled intervals and can be paired with External Services for near real-time sync.
Incorrect Options:
B). Einstein Analytics is for data visualization and reporting, not near real-time data integration.
C). Apex Schedulable class is code-based and typically not the first recommendation for admins.
D). Manual data loads are not scalable and do not support near real-time updates.
Reference Extracts from Salesforce Process Automation Study Guide:
"Scheduled Flows are ideal for polling or syncing external data sources at set intervals."
"Combine Scheduled Flows with External Services or Apex actions for external integrations."