Home / Data Analyst practice test / Understanding of Databricks Data Intelligence Platform / Question

Databricks Data Analyst Associate · free practice question

A data engineer creates a managed Delta table named `analytics.sales.transactions` in Unity Catalog by running `CREATE TABLE analytics.sales.transactions AS…

Exam-style question on Understanding of Databricks Data Intelligence Platform from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Understanding of Databricks Data Intelligence Platform

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?

  1. ABoth the managed and external table DROP operations delete the table's metadata entries from the Unity Catalog metastore AND permanently delete the underlying data files from cloud storage, because registering any table in Unity Catalog — whether managed or external — transfers full data lifecycle ownership to Unity Catalog, which then controls deletion behavior identically for both table types.
  2. BDropping the managed table analytics.sales.transactions removes its metadata AND, after a recovery period (7 days by default), deletes its data files. Dropping the external table finance.reporting.invoices removes only the metadata pointer; the files at s3://company-data/invoices/ stay intact.
  3. CBoth DROP operations remove only the metadata entry from the Unity Catalog metastore; neither operation ever deletes the underlying data files, because Unity Catalog operates exclusively at the governance layer and delegates all data file lifecycle management to the cloud provider's storage service, which requires a separate storage API call to permanently remove files.
  4. DDropping the managed table analytics.sales.transactions removes only the metadata entry and leaves the data files in place until an engineer manually runs VACUUM on the storage path. Dropping the external table finance.reporting.invoices immediately and permanently deletes both the metadata and all underlying data files in S3, because external tables transfer complete storage ownership to Unity Catalog upon initial table registration.
  5. EDropping either type of table in Unity Catalog automatically places the table in a 30-day recycle bin from which it can be fully restored, including all historical data versions. The underlying data files for both managed and external tables are preserved during this recycle period in a quarantine storage tier, and administrators must explicitly call PURGE TABLE with a FORCE flag to permanently remove them from storage.
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.

Take the full Data Analyst practice test free →

Would you pass today?

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

Start the free test →