A data engineering team implements GDPR compliance in a medallion architecture. After deleting user PII from the bronze layer tables, they need to propagate those deletions to the gold layer materialized views. What action must the team take to ensure the materialized views reflect the deletions?
Show answer & explanation
Correct answer: D
WHY D is correct: Per Databricks documentation, materialized views automatically handle deletions from their source tables. A materialized view always returns a correct result — it uses incremental computation unless full recomputation is required for correctness (e.g., after a deletion that changes aggregations). You do NOT need to manually delete records from materialized views. The team only needs to refresh the materialized view and run maintenance to ensure deletions are completely processed and the underlying data files are cleaned up.
WHY NOT A: Materialized views are derived objects; you cannot run DML (DELETE) statements directly on a materialized view in Databricks. Materalized views are refreshed from their source definitions, not modified directly.
WHY NOT B: Dropping and recreating materialized views is unnecessary and expensive. Materialized views are designed to handle source deletions via refresh — recreation would also lose any additional configuration or metadata associated with the view.
WHY NOT C: skipChangeCommits is a streaming table option, not a materialized view option. Materialized views do not use this concept — they handle corrections automatically through full or incremental recomputation.
WHY NOT E: Enabling change data feed on bronze tables helps with streaming CDC pipelines but it is not a requirement for materialized view refresh after deletions. Materialized views compute correctness independently of whether CDF is enabled on source tables.