Immutable Snapshots and Physical Isolation.

Regulatory compliance often mandates "Immutable Snapshots." In database theory, a snapshot is a consistent view of data at a specific point in time. However, in modern Data Lakehouses (which use Copy-on-Write storage), maintaining these snapshots indefinitely within the live production system is risky. Routine maintenance operations like VACUUM (garbage collection) or DELETE might reclaim the physical files required to reconstruct that history, effectively destroying the evidence. Furthermore, auditors often require Physical Isolation—the data must exist in a separate, write-protected storage container (often configured as WORM - Write Once Read Many) to verify that no tampering could have occurred after the snapshot was taken.

Application: Databricks solves this via DEEP CLONE. Unlike a standard CTAS (which creates a new table but loses Delta-specific transaction history, partitioning efficiency, and metadata fidelity), DEEP CLONE copies the entire state: the data files and the transaction log structure. By specifying VERSION AS OF, the engineer locks the source state to the specific compliance timestamp. By specifying LOCATION, the engineer directs this frozen state to the secure "Audit Bucket." The result is a physically independent, bit-for-bit replica. Even if the production table is optimized, vacuumed, or deleted the next day, the Archive in the audit bucket remains completely untouched because Deep Clone duplicated the underlying parquet bytes at that specific version. This provides the robust chain of custody required for banking audits.

Exam: exam4