Databricks Certified Data Engineer - Professional
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
A junior data engineer is transitioning a workload from a relational database to the Databricks Lakehouse. The source system employs a star schema with foreign key constraints and multi-table inserts to enforce data validation during writes.
What factor should the engineer prioritize when making decisions during this migration in Databricks Runtime 15.2 or later?
A
Databricks enforces primary and foreign key constraints at runtime, so no additional referential integrity checks are required.
B
Databricks supports defining primary and foreign key constraints in Unity Catalog tables, but they are not enforced by the engine; ACID guarantees apply only to single-table transactions.
C
Multi-table inserts in Databricks are atomic, so referential integrity is always preserved without extra logic.
D
Foreign keys in Databricks can only reference hashed identifiers to avoid collisions in parallel writes.