The data architect has mandated that all tables in the Lakehouse should be configured as external Delta Lake tables. Which approach will ensure that this requirement is met?

Question

Options

• AWhenever a database is being created, make sure that the location keyword is used
• BWhen configuring an external data warehouse for all table storage. leverage Databricks for all
• CWhenever a table is being created, make sure that the location keyword is used.
• DWhen tables are created, make sure that the external keyword is used in the create table
• EWhen the workspace is being configured, make sure that external cloud object storage has been

• C
  89% (25)
• D
  7% (2)
• E
  4% (1)

Explanation

In Databricks and Delta Lake, a table is classified as external when its data lives at a storage path that Databricks does not manage. The mechanism to declare this at creation time is the LOCATION keyword in the CREATE TABLE statement. When LOCATION is specified, Databricks treats the table as external: dropping the table removes only the metadata from the metastore, not the underlying files. Without LOCATION, a table is a managed table and Databricks controls both metadata and data lifecycle. Using the EXTERNAL keyword alone (D) is not sufficient in all Databricks SQL contexts; the authoritative approach is providing LOCATION. Creating the database with a location (A) sets a default storage path for the database but does not guarantee each individual table is external.

No community discussion yet for this question.