Home / Data Analyst practice test / Executing queries using Databricks SQL and Databricks SQL Warehouses / Question

Databricks Data Analyst Associate · free practice question

A data team designs a Databricks SQL pipeline with two use cases: (1) near-real-time ingestion of continuously arriving IoT sensor records from a streaming…

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

Updated November 10, 2026

Executing queries using Databricks SQL and Databricks SQL Warehouses

A data team designs a Databricks SQL pipeline with two use cases: (1) near-real-time ingestion of continuously arriving IoT sensor records from a streaming Delta source, and (2) periodic refresh of pre-aggregated sales summaries queried heavily by a BI dashboard. Which combination of Databricks table types is correct?

  1. AA Materialized View for IoT ingestion and a Streaming Table for the sales summaries: Materialized Views read streaming sources natively, and Streaming Tables batch-aggregate data on a schedule
  2. BA Streaming Table for both use cases: Streaming Tables handle live streaming ingestion and periodic pre-aggregated summaries for BI dashboards under one unified pipeline execution model
  3. CA Materialized View for both use cases: Materialized Views use TRIGGER ON UPDATE for near-real-time ingestion and also serve pre-aggregated batch workloads for heavily queried BI dashboards
  4. DA standard view for IoT ingestion and a Streaming Table for the sales summaries: views recompute on each query and remove ingestion latency, and Streaming Tables run scheduled batch loads
  5. EA Streaming Table for the IoT records and a Materialized View for the sales summaries: Streaming Tables ingest incremental streaming data, and Materialized Views pre-compute aggregations on refresh
Answer & explanation

Correct answer: E

WHY E: Streaming Tables are built for continuously appending incremental data from streaming sources. Materialized Views pre-compute and cache aggregations with flexible refresh options (scheduled or TRIGGER ON UPDATE), which makes them ideal for heavily queried BI dashboards.

WHY NOT A: The assignment is reversed: Streaming Tables handle continuous ingestion, not Materialized Views.

WHY NOT B: Streaming Tables are designed for append-only ingestion, not for declarative pre-aggregated transformations intended for BI queries.

WHY NOT C: Materialized Views can be refreshed in near real time, but Streaming Tables are the architecturally correct choice for pipelines that ingest continuously arriving data.

WHY NOT D: Standard (dynamic) views recompute on every query with no caching, which adds latency and ingests nothing; Streaming Tables are insert-focused and not designed for aggregation summaries.

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 →