Documenting Sales Dashboard Guidelines and Transformations

Why the Answer Is Correct

A data dictionary is the standard governance document that records the definitions, data types, formats, allowed values, and—critically—the transformation rules applied to the data feeding a set of deliverables such as the sales dashboards described in the scenario. Because the analyst owns a suite of dashboards and needs a single reference that codifies the guidelines (naming, definitions, standards) and the transformations (calculated fields, aggregations, filters) applied to that data, the data dictionary is the artifact that satisfies both halves of the requirement. Objective 5.1 data management practices explicitly treat the data dictionary as the tool for documenting data assets consistently across deliverables.

Why the Other Options Are Wrong

D, data versioning, is a change-management practice that stores and tracks successive snapshots of dashboards or datasets so users can roll back; it records what changed and when, but it does not publish the standing guidelines or explain transformation logic as a readable reference document. B, data lineage, maps where data originates and how it flows and changes between systems, which covers transformation flow but not the definitional guidelines and standards that govern a dashboard suite. A, data flow diagram, is a visual model of movement of data through a process or system, so it illustrates movement rather than documenting the rules and transformation specifications an analyst maintains for delivery.

Community Comment Notes

The only posted comment, from Amelia233, argues for D, reasoning that 'Data versioning documents the guidelines, changes, and transformations made to a set of dashboards over time.' That reasoning conflates version history with a governing reference document: versioning tracks revisions rather than defining the guidelines and transformation rules the analyst must publish for the dashboard suite.