Explanation:
The table test.store_wise_sales is a managed table because it was created without a LOCATION clause.
For managed Delta tables, the DROP TABLE command performs two actions:
Why other options are incorrect:
COMMIT required for dropping tables.LOCATION had been specified, only the catalog entry would be removed._delta_log) is deleted. Therefore, the data cannot be queried via Time Travel because the transaction log no longer exists. Note: In Unity Catalog, an UNDROP command might be available within a short retention window, but the standard Delta Lake behavior is full deletion.Ultimate access to all questions.
No comments yet.
A Delta Lake table named store_wise_sales was created in the test schema using the following SQL statement:
CREATE TABLE test.store_wise_sales AS (
SELECT *
FROM test.sales a
INNER JOIN test.store b
ON a.store_id = b.store_id
);
CREATE TABLE test.store_wise_sales AS (
SELECT *
FROM test.sales a
INNER JOIN test.store b
ON a.store_id = b.store_id
);
If a workspace administrator executes the command DROP TABLE test.store_wise_sales, what will be the outcome?
A
No action will take place until a COMMIT command is explicitly executed.
B
The table will be removed from the catalog, but the underlying data files will persist in storage.
C
The table will be deleted from the catalog, and the associated data files will be permanently removed from storage.
D
An error will occur because Delta Lake prevents the deletion of tables containing production data.
E
The data will be marked as deleted in the transaction log but will still be retrievable using Delta Lake Time Travel.