Answer-first summary for fast verification
Answer: Delta Lake focuses on row-level constraints; therefore, referential integrity across multiple tables must be managed programmatically by the development team within their ETL pipelines.
While Delta Lake provides ACID transactions and supports row-level constraints (such as `CHECK` and `NOT NULL`), it does not natively enforce foreign key relationships (referential integrity) between tables. Data engineers are responsible for implementing this logic programmatically—for example, by performing validation joins or lookups to ensure related keys exist during the ingestion process.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Delta Lake does not natively enforce foreign key constraints. Which of the following best explains why this is the case and how data engineers should handle referential integrity within a Databricks environment?
A
Delta Lake relies solely on ACID transactions to automatically resolve and maintain referential integrity across all tables in a workspace.
B
Foreign key enforcement is an optional metadata feature that must be enabled via Spark SQL configuration settings before it becomes active.
C
Delta Lake's support for primary keys automatically negates the requirement for foreign key constraints, as uniqueness is guaranteed by the storage layer.
D
Delta Lake focuses on row-level constraints; therefore, referential integrity across multiple tables must be managed programmatically by the development team within their ETL pipelines.
No comments yet.