A team creates a Unity Catalog managed table and later runs DROP TABLE. A separate external table points at an existing cloud storage location. What is the correct description of what happens to the underlying data files in each case?
Answer & explanation
Correct answer: B
WHY B: For a managed table Unity Catalog owns the storage lifecycle, so DROP TABLE removes metadata and the underlying data files (after the recovery window). For an external table Databricks manages only the metastore metadata; the files at the external location remain and must be deleted manually. WHY NOT A: Behavior is not identical — external-table files are never deleted by DROP TABLE. WHY NOT C: Managed-table files ARE deleted, so it is wrong to claim UC never removes data. WHY NOT D: This reverses reality — managed files are deleted, external files are kept. WHY NOT E: VACUUM is unrelated to whether a table can be dropped; drops are not blocked by data or retention.