Create and manage logic and process automation
Pick the lightest tool that meets the need
Automation is a family of tools and the exam wants the cheapest one that works.
Business rules are no-code, run in the app UI, set, clear or recommend field values, show errors, and lock fields. They do not fire for API or integration writes, so they are not a data-integrity guarantee - use a required column or a plug-in/flow for that.
Business process flows guide users through stages spanning one or more tables. Stages contain steps bound to columns, conditions can branch, and a BPF can be scoped to security roles. A BPF guides; it does not automate.
Classic Dataverse workflows run on the server, can be asynchronous or real-time (real-time blocks the transaction), trigger on create/update/delete, and can be called as actions. They run in the context of the owner or the calling user.
Power Automate cloud flows are automated (triggered by a Dataverse row created, modified or deleted), instant (button or from an app via the Power Apps trigger), scheduled, or approval-based. Cloud flows run under the connection owner's identity - a common trap where a flow reads records the triggering user cannot see.
Other traps: a flow that updates the table that triggers it loops, so add a trigger condition or a flag column; concurrency control prevents duplicate creation; and solution-aware flows must be added to the solution to move between environments.
Rule of thumb: a reminder three days before a due date is a scheduled cloud flow with a recurrence and filter, not a workflow timeout. Blocking a save on any write path needs a platform requirement, not a form-level business rule.