A company uses a model driven app. The company needs to automatically update the Status column in real time. You need to configure this feature…

The solution meets the goal because classic Dataverse workflows can be configured to run in real-time (synchronously). When a workflow is set to run in real-time, it executes immediately as part of the same database transaction that triggered it, providing an instant update to the user. The workflow designer includes a specific "Change Status" step, which is the designated method for programmatically updating the special status and statuscode (Status Reason) columns of a record. This combination directly fulfills the requirement for an automatic, real-time update of the Status column.

B. No: This is incorrect. A classic workflow is a valid and standard feature within the Power Platform for this exact purpose, as it can be configured for real-time execution and has the necessary action to modify a record's status.

1. Microsoft Learn. (2023). Use workflow processes. In Power Apps documentation. "You can configure a workflow to run in the background or in real time... Real-time workflows execute immediately". This document also lists "Change Status" as an available step.

2. Microsoft Learn. (2023). Configure workflow stages and steps. In Power Apps documentation. Under the "Actions" section

the "Change Status" step is described: "Changes the status of the record." This confirms it is the correct tool for the task.

3. Microsoft Learn. (2023). Synchronous and asynchronous workflows. In Power Apps documentation. "Real-time workflows are synchronous... When you trigger a synchronous workflow

it runs immediately and doesn't queue a System Job." This directly supports the "real-time" aspect of the requirement.