A data engineer creates a managed Delta table named analytics.sales.transactions in Unity Catalog by running CREATE TABLE analytics.sales.transactions AS SELECT * FROM raw.events. A second engineer independently creates an external table named finance.reporting.invoices using CREATE EXTERNAL TABLE finance.reporting.invoices LOCATION 's3://company-data/invoices/'. Both engineers later run DROP TABLE on their respective tables. Which statement CORRECTLY describes the outcome of both DROP operations?
Answer & explanation
Correct answer: B
WHY B is correct: Unity Catalog distinguishes clearly between managed and external tables in terms of lifecycle management. For managed tables, Unity Catalog controls both the governance (metadata, access policies) AND the physical data storage. Therefore, when a managed table is dropped, Unity Catalog removes it from the metastore and deletes the underlying data files from the Unity Catalog-managed storage location after a recovery period (7 days by default), during which UNDROP TABLE can restore it. For external tables, Unity Catalog manages only the governance — access control and metadata — but does NOT own the data files, which reside in a user-specified cloud storage path. Dropping an external table removes only the metadata registration (the 'pointer') from the metastore; the data files at the specified external location remain unchanged. This is a critical distinction for data lifecycle management and disaster recovery planning.
WHY NOT A: It is incorrect that Unity Catalog treats both table types identically for deletion. The managed/external distinction exists precisely to handle different lifecycle ownership models. External tables exist because organizations need to retain data file control outside of Databricks (for other tools, compliance, or cross-platform access), so Unity Catalog intentionally never deletes external data files on DROP.
WHY NOT C: It is incorrect that dropping a managed table leaves the data files untouched. Managed tables are 'fully managed by Unity Catalog, which means Unity Catalog manages both the governance and the underlying data files.' Dropping a managed table is a complete deletion operation — both metadata and data files are removed.
WHY NOT D: The description reverses the behavior. It is the managed table (not the external table) whose data files are deleted on DROP. External tables do NOT transfer ownership to Unity Catalog — that is the definition of an external table. Additionally, while VACUUM handles old Delta file cleanup, a DROP TABLE on a managed table removes the data files as part of the drop operation itself, not through a deferred VACUUM cycle.
WHY NOT E: Unity Catalog does not provide a built-in 30-day recycle bin or quarantine storage tier for dropped tables as of the current platform version. While Delta Lake's time travel allows querying historical table versions before they are vacuumed, a DROP TABLE removes the table registration and (for managed tables) the data. There is no automatic recycle bin restore mechanism, and no PURGE TABLE command exists in this context.