A record-triggered flow must create a related task and send an email whenever an Opportunity is closed. Why should this run after save rather than before save?
- ABefore-save flows cannot create related records or send emails, which only after-save flows support Correct
- BBefore-save flows run too slowly to complete the additional work within the save window
- CBefore-save flows always require a screen element, which cannot be shown during a save
- DBefore-save flows run only on record creation and would miss the Opportunity being edited to closed
Why A is correct: Before-save flows are limited to updating the triggering record and cannot perform actions such as creating related records, sending email, or calling other automation, all of which require the after-save context.
Why B is wrong: Before-save flows are actually the faster path; the reason they are unsuitable here is functional rather than a matter of speed, so this misstates the constraint.
Why C is wrong: No record-triggered flow, before or after save, can contain a screen element, so requiring a screen is not the distinction; this misdescribes both flow behaviour.
Why D is wrong: Before-save flows can be configured to run on create, on update, or both, so the trigger event is not the limitation; the true limitation is the actions they may perform.