Home / DE Associate practice test / Governance and Security / Question

Databricks Data Engineer Associate · free practice question

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…

Exam-style question on Governance and Security from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Governance and Security

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?

  1. ADropping either table deletes its underlying data files, because Unity Catalog always owns the full storage lifecycle for every table type it governs, whether the table is managed or instead points at an external location.
  2. BDropping the managed table deletes its data files since Unity Catalog owns that storage lifecycle, while dropping the external table removes only the metastore metadata record and leaves the underlying cloud files intact.
  3. CDropping either table leaves its underlying data files intact, because Unity Catalog only ever unregisters metadata on DROP TABLE and never physically deletes data from cloud storage for any type of table it tracks.
  4. DDropping the managed table leaves its data files intact and removes only metadata, while dropping the external table deletes the files at the external cloud location that the table definition had originally referenced.
  5. ENeither a managed nor an external table can be dropped while it still contains data unless you first run VACUUM RETAIN 0 HOURS to clear the files, otherwise DROP TABLE returns an error and the drop is blocked.
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.

Take the full DE Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Engineer Associate practice test. Take it and get a section-by-section score.

Start the free test →