Explanation:
Shallow clones (also known as zero-copy clones) only duplicate the metadata of the source table and continue to reference the original data files. This makes them extremely fast and cost-effective for development, testing, or staging tasks where data duplication is unnecessary. Conversely, deep clones copy both the metadata and the actual data files, providing a fully independent copy that is unaffected by changes or file deletions in the source.
Ultimate access to all questions.
In Delta Lake, under which scenario is it most appropriate to use a shallow clone instead of a deep clone?
A
When you need to ensure the target table is completely decoupled from the source and protected from data file deletion in the source.
B
When you need to create a full backup of a table for long-term archiving and regulatory compliance.
C
When you need to perform rapid testing or experimentation on a table without the storage overhead or time required to duplicate underlying data files.
D
When a full replica of both the data and the transaction log is required for a disaster recovery site.
No comments yet.