Home / Data Analyst practice test / Data Modeling with Databricks SQL / Question

Databricks Data Analyst Associate · free practice question

An enterprise data team needs a schema that tracks the full change history of business entities over time, handles data from multiple source systems with…

Exam-style question on Data Modeling with Databricks SQL from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Data Modeling with Databricks SQL

An enterprise data team needs a schema that tracks the full change history of business entities over time, handles data from multiple source systems with different keys for the same real-world entity, and supports auditable lineage. Which schema best meets these requirements?

  1. AA layered warehouse with staging tables that buffer raw source extracts, core dimensional tables keyed by surrogate keys, and data mart tables aggregated and shaped for individual consumer teams
  2. BA star schema with slowly changing dimension (SCD) Type 2 on each dimension table, adding start and end date columns to keep earlier attribute states alongside the current version of each row
  3. CA flat denormalized wide table that stores the attributes of each business object in a single record, giving the simplest analytical queries with no joins while tolerating high column sparsity
  4. DA data vault schema with Hubs that store business keys, Links that capture relationships between Hubs, and Satellites that hold descriptive attributes and their historical changes with load timestamps
  5. EA snowflake schema with dimensions normalized into a third-normal-form hierarchy, foreign keys enforcing referential integrity, and updates applied in place over the prior attribute values
Answer & explanation

Correct answer: D

WHY D: The data vault schema is purpose-built for enterprise environments with multiple source systems. Hubs hold business keys (one per real-world entity regardless of source), Links model relationships between hubs, and Satellites store the descriptive attributes plus full change history with load timestamps. This directly satisfies auditable lineage, multi-source key integration, and historical tracking.

WHY NOT A: A staging-plus-mart architecture describes an ETL pipeline pattern, not a schema design that natively addresses multi-source key integration or change history tracking at the entity level.

WHY NOT B: SCD Type 2 on a star schema does preserve history, but it does not address multi-source key integration across systems or provide the structured auditability and decoupled loading that data vault offers.

WHY NOT C: A flat wide denormalized table collapses the attributes into a single record and does not preserve historical changes or support multi-source business key reconciliation.

WHY NOT E: A third-normal-form snowflake schema with in-place updates destroys history. It also requires complex JOINs and lacks the built-in multi-source business key isolation that data vault hubs provide.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →