A company uses Microsoft Dataverse to store customer records on the Account table.

The Microsoft Dataverse trigger “When a row is added, modified or deleted” is the correct trigger because the flow must run automatically whenever the Account Number field changes. The trigger can be configured for the Modified change type, the Account table, and an appropriate scope. Its Select columns or filtering-attributes setting should identify the account-number column so unrelated row updates do not start the validation flow. A trigger condition can further prevent work when the value is blank or already normalized. “When a row is selected” is an instant, user-initiated trigger and does not run automatically. A business-process-flow step only runs when that step is explicitly invoked. “When an action is performed” responds to a defined Dataverse action rather than a standard column modification. The correction logic should also avoid recursively retriggering itself when it updates the formatted value, for example by comparing the existing and normalized values before writing. The Study Guide explicitly lists “recommend cloud flow triggers.” Option D is the only event trigger that directly observes Dataverse row modification and can be narrowed to the required field.

Study Guide reference/topic: “Create cloud flows — Recommend cloud flow triggers.” AB-410 Study Guide | Microsoft Learn technical reference