Explanation:
Shallow clones are ideal for use cases like testing, debugging, or creating staging environments because they only copy the transaction log (metadata) and reference the original data files. This allows for near-instantaneous creation and significant storage savings, as the actual data is not duplicated. In contrast, a deep clone creates a complete, independent copy of both the data and metadata.
Ultimate access to all questions.
In Delta Lake, under which specific scenario is a shallow clone preferred over a deep clone?
A
When preparing a table for long-term archival to ensure data durability even if the source is removed.
B
When you need a fully independent copy of both the metadata and the physical data files for disaster recovery.
C
When the source table contains highly sensitive data that must be physically isolated in a new storage location.
D
When you require a rapid copy for short-term testing or development while maintaining minimal storage overhead.
No comments yet.