The data architect has mandated that all tables in the Lakehouse should be configured as external (also known as "unmanaged") Delta Lake tables. Which approach will ensure that this requirement is…

Question

Options

• AWhen 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
• CWhen data is saved to a table, make sure that a full file path is specified alongside the Delta
• 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

• B
  2% (1)
• D
  94% (47)
• E
  4% (2)

Explanation

To create an external or unmanaged Delta Lake table, you need to use the EXTERNAL keyword in the CREATE TABLE statement. This indicates that the table is not managed by the catalog and the data files are not deleted when the table is dropped. You also need to provide a LOCATION clause to specify the path where the data files are stored. CREATE EXTERNAL TABLE events ( date DATE, eventId STRING, eventType STRING, data STRING) USING DELTA LOCATION /mnt/delta/events'; This creates an external Delta Lake table named events that references the data files in the /mnt/delta/events' path. If you drop this table, the data files will remain intact and you can recreate the table with the same statement.

No community discussion yet for this question.