Answer-first summary for fast verification
Answer: When you want to rapidly test logic or schema changes without incurring the cost and time of duplicating the underlying data files.
Shallow clones create a copy of the table's metadata while continuing to reference the original data files on cloud storage. This makes them extremely fast and cost-effective for short-term experimentation, development testing, or staging, as no data migration occurs. In contrast, deep clones copy both metadata and the actual data files, making them more suitable for long-term archival or migration.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
In which of the following scenarios is a shallow clone preferred over a deep clone within a Databricks Delta Lake environment?
A
When archiving a table to meet long-term regulatory compliance and data retention requirements.
B
When you want to rapidly test logic or schema changes without incurring the cost and time of duplicating the underlying data files.
C
When you need to create a full, independent copy of both data and metadata to support a disaster recovery strategy.
D
When it is necessary to decouple the target table entirely from the source to ensure source updates never impact the clone.