DATABRICKS-DEP Question 106

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  - Correct answer : A — Create the materialized view with `TRIGGER ON UPDATE` so a refresh is automatically scheduled only when the underlying source tables actually change, avoiding unnecessary compute when `fact_sales` is idle. A . The `TRIGGER ON UPDATE` refresh mode watches the source tables and schedules a refresh only when they actually change, which delivers near-real-time freshness without running compute on a fixed cadence while the source is idle. This matches both the freshness and the cost-avoidance requirement. B . An ad-hoc materialized view only refreshes when someone explicitly runs the refresh command, so freshness depends entirely on an analyst remembering to trigger it. That does not reliably deliver updates within a few minutes of new data landing. C . A per-minute cron schedule does refresh quickly, but it runs on a fixed timer even when `fact_sales` has not changed, which is exactly the wasted-compute pattern the team wants to avoid. Trigger-based refresh reacts to actual changes instead. D . A materialized view always physically stores its results and only updates them on refresh; it does not recompute live at query time the way a standard view does. Querying it without ever refreshing would just return stale, previously materialized data.