Definition of derived data: Assess the statement. “Derived data are detailed, current data intended to be the single, authoritative source for all decision support applications.”

Introduction / Context: Derived data are created by transforming base (atomic) data: aggregations, calculations, rollups, and other summaries that support analytics. This statement incorrectly equates derived data with the “single authoritative source” of detailed, current data—roles more typically associated with an operational data store (ODS) or mastered operational layer.

Given Data / Assumptions:

• Base/atomic data: detailed, low-level, often near real-time.
• Derived data: calculated or aggregated from base data.
• Authoritative sources are governed systems of record or curated ODS layers.

Concept / Approach: Decision support relies on both detailed and derived layers. The authoritative source of truth for operational attributes is usually mastered atomic data; derived layers accelerate analytics by precomputing metrics like daily revenue, 30-day rolling averages, or cohort retention. Conflating these layers leads to confusion and may degrade traceability.

Step-by-Step Solution:

Verification / Alternative check: Data catalogs typically distinguish “golden” atomic datasets from “certified” derived datasets, with lineage diagrams confirming dependency.

Why Other Options Are Wrong:

• Calling the statement “Correct” misrepresents standard definitions.
• “ODS” and “CDC” are about integration/latency, not the meaning of “derived.”
• Lineage helps trust but does not change definitions.

Common Pitfalls: Treating derived metrics as interchangeable with base facts; losing lineage; double-deriving metrics leading to reconciliation issues.

Final Answer: Incorrect