A company uses Dataverse to configure derived values for sales records.

A calculated column is the correct option because it can evaluate a mathematical expression over numerical columns in the same Dataverse row without custom code. Dataverse stores the calculation definition and derives the exposed read-only value from the underlying columns rather than requiring the application to maintain an ordinary stored result. This satisfies the requirement for a dynamic, non-manually persisted value. A business rule would typically set a column value during a create or update event, resulting in stored data that can become stale if the rule does not run for every path. JavaScript operates only in supported client experiences and would not provide a consistent table-level value to all consumers. A dataflow transforms and loads data on a schedule or run; it materializes data rather than evaluating the field whenever accessed. The expression should account for blanks, numeric precision, and supported functions. The Study Guide explicitly lists “configure calculated, rollup, and formula columns.” Under the choices provided, D is the native declarative behavior that matches the calculation, access, storage, and low-code requirements.

Study Guide reference/topic: “Implement business and process logic — Configure calculated columns.” AB-410 Study Guide | Microsoft Learn technical reference