CERTIFIED-DATA-ANALYST-ASSOCIATE Question #79: Real Exam Question with Answer & Explanation

Question

A managed table and an unmanaged (external) table were both created in Databricks SQL, and data were ingested into each table. Later, both tables were dropped. What is the status of data for each of those tables?

Options

• AThe data in both tables were deleted.
• BThe data in the managed table were deleted, and the data in the unmanaged (external) table
• CThe data in the unmanaged (external) table were deleted and the data in the managed table were
• DThe data in both tables were left untouched.

Explanation

Option B is correct because in Databricks (and Delta Lake / Hive metastore generally), dropping a managed table removes both the metadata and the underlying data files, since Databricks owns the data lifecycle. Dropping an external (unmanaged) table removes only the metadata registration from the metastore - the data files at the external location (e.g., ADLS, S3, GCS) remain completely intact.

Why the distractors fail:

• A is wrong because external tables do not have their data deleted on drop - only their catalog entry is removed.
• C reverses the behavior - it's the managed table whose data gets deleted, not the external one.
• D is wrong because managed table data is absolutely deleted when the table is dropped.

Memory tip: Think of it as ownership - a managed table means Databricks manages everything (including cleanup), while an external table means you own the data externally, so Databricks only manages the pointer. Drop the pointer, the data stays; drop ownership, the data goes.

No community discussion yet for this question.