Documenting Sales Dashboard Guidelines and Transformations
Short answer
C The analyst is creating a data dictionary that records the guidelines and transformation rules for the suite of sales dashboards.
Question
Key Takeaways
The question tests whether you can match a documentation need—codifying guidelines and transformations for dashboards—to the right artifact, with the trap being to pick data versioning because it sounds like it tracks change over time.
This DA0-002 question asks which documentation artifact captures the guidelines and transformation rules for a suite of sales dashboards. The page establishes that a data dictionary is the artifact that records definitions, standards, and transformation rules, making it the correct choice over lineage, versioning, or a data flow diagram.
Common mistake: Many learners choose D, data versioning, because the single community comment argues it documents 'guidelines, changes, and transformations' over time; however, versioning is a change-control practice that stores snapshots, not a reference document defining dashboard data rules and transformations.
Expert Analysis
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.
Official Reference
https://www.comptia.org/certifications/data
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question says a document 'covers the guidelines and transformation' of data assets, look for the artifact that defines data—data dictionary—rather than artifacts that only track flow (lineage), movement (flow diagram), or history (versioning).
Frequently Asked Questions
Why isn't data versioning the right answer for documenting dashboard guidelines?
How does a data dictionary differ from data lineage for dashboards?
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
6b7911d 👍 1 Answered BB. Data lineage The key word is transformation. Data lineage documents where the data behind the dashboards comes from, how it moves, and every transformation applied before it reaches the final visuals. A lineage document for a suite of sales dashboards traces each metric back to its source system and records the rules and logic used along the way, such as filters, joins, calculations and aggregations. Those rules are the guidelines the question mentions. This document is how anyone can trust or troubleshoot a number on the dashboard. Data versioning tracks changes to a dataset or report over time so earlier states can be compared or restored. It answers which version is current and what changed between releases. It does not describe how the data is transformed or what guidelines govern it. Nothing in the question mentions releases, revisions or change history, so versioning does not fit. The other two options are close but still miss. A data flow diagram is a visual showing data moving between systems, while the question describes a written document that covers guidelines and rules. A data dictionary defines fields, data types and allowed values, but it does not cover how the data is transformed.
-
Amelia233 👍 1 Answered DData versioning documents the guidelines, changes, and transformations made to a set of dashboards over time. It helps track different versions and understand how the dashboards have evolved. 👉 Final Answer: D. Data versioning ✅
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DA0-002 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DA0-002 Practice Test →