CERTIFIED-DATA-ENGINEER-PROFESSIONAL Question #112: Real Exam Question with Answer & Explanation

Question

A junior data engineer is migrating a workload from a relational database system to the Databricks Lakehouse. The source system uses a star schema, leveraging foreign key constrains and multi-table inserts to validate records on write. Which consideration will impact the decisions made by the engineer while migrating this workload?

Options

• AAll Delta Lake transactions are ACID compliance against a single table, and Databricks does not
• BDatabricks only allows foreign key constraints on hashed identifiers, which avoid collisions in
• CForeign keys must reference a primary key field; multi-table inserts must leverage Delta Lake's
• DCommitting to multiple tables simultaneously requires taking out multiple table locks and can lead
• EDatabricks supports Spark SQL and JDBC; all logic can be directly migrated from the source

Explanation

In Databricks and Delta Lake, transactions are indeed ACID-compliant, but this compliance is limited to single table transactions. Delta Lake does not inherently enforce foreign key constraints, which are a staple in relational database systems for maintaining referential integrity between tables. This means that when migrating workloads from a relational database system to Databricks Lakehouse, engineers need to reconsider how to maintain data integrity and relationships that were previously enforced by foreign key constraints. Unlike traditional relational databases where foreign key constraints help in maintaining the consistency across tables, in Databricks Lakehouse, the data engineer has to manage data consistency and integrity at the application level or through careful design of ETL processes.

No community discussion yet for this question.