Answer-first summary for fast verification
Answer: The 'orders_backup' table was created using Delta Lake’s SHALLOW CLONE functionality from the 'orders' table.
When a table is created using Delta Lake’s SHALLOW CLONE functionality, it only copies the Delta transaction logs without moving any data. This means that if a VACUUM command is run on the original table, it may remove data files that are still referenced by the clone's transaction logs, leading to errors when querying the clone. This scenario matches the described issue. Reference: [Delta Lake Cloning](https://docs.databricks.com/delta/clone.html).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A junior data engineer created a backup table named 'orders_backup' from the 'orders' table. However, queries on 'orders_backup' now fail, indicating missing data files, coinciding with a VACUUM command execution on 'orders'. How was 'orders_backup' likely created?
A
The 'orders_backup' table was created by fully copying the 'orders' table’s directory.
B
The 'orders_backup' table was created using Delta Lake’s DEEP CLONE functionality from the 'orders' table.
C
The 'orders_backup' table was created using CTAS statement from 'orders' table.
D
The 'orders_backup' table was created using Delta Lake’s SHALLOW CLONE functionality from the 'orders' table.
E
The 'orders_backup' table was created using CRAS statement from 'orders' table.
No comments yet.