In a Lakeflow Spark Declarative Pipeline, a bronze streaming table ingests append-only clickstream events. A downstream Gold object must present hourly revenue totals that always reflect the full, current state of the upstream data, including late-arriving corrections. Which object type is the most appropriate for the Gold aggregation, and why?
Answer & explanation
Correct answer: A
WHY A: A materialized view recomputes from the current state of its sources on each update, so aggregations reflect late-arriving and corrected data — the right fit for a Gold summary table. WHY NOT B: Streaming tables process each input row exactly once via a checkpoint; they are for append-style ingestion, and the claim that they rebuild all history every run is false. WHY NOT C: A standard view stores no data — it is evaluated at query time and does not persist results physically. WHY NOT D: Materialized views are first-class objects inside declarative pipelines. WHY NOT E: A temporary view materializes no data and is pipeline-scoped, so it does not persist across runs.