Databricks-DE-Assoc Databricks Intelligence Platform Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  CREATE TABLE my_catalog.my_schema.my_table (id INT, name STRING) USING DELTA;

  Why this is correct

  This statement creates a managed Delta table in Unity Catalog under the specified catalog and schema. The table is fully managed by Unity Catalog, and access can be controlled via SQL GRANT statements. This is the correct syntax for creating a Unity Catalog managed table.

• ✗

  CREATE EXTERNAL TABLE my_catalog.my_schema.my_table (id INT, name STRING) USING DELTA LOCATION '/mnt/data/my_table';

  Why it's wrong here

  While this creates an external table in Unity Catalog, the LOCATION must be a path within an external location that is registered in Unity Catalog. Using '/mnt/data/my_table' directly may not be valid unless it is an external location. The question asks for a table governed by Unity Catalog, and a managed table is simpler and fully governed.

• ✗

  CREATE TABLE my_catalog.my_schema.my_table AS SELECT * FROM parquet.`/mnt/data/my_table`;

  Why it's wrong here

  This creates a table using a query, but the resulting table will be a managed Delta table in Unity Catalog if the three-part name is used. However, the syntax does not specify USING DELTA, and the source is Parquet. It could work, but it is not the most direct way to create a Delta table with a specified schema. The question implies creating a table with a defined schema, not from a query.

• ✗

  CREATE TABLE my_table (id INT, name STRING) USING DELTA LOCATION '/mnt/data/my_table';

  Why it's wrong here

  This creates an external table with a specified location, but without a catalog and schema, it defaults to the Hive metastore, not Unity Catalog. To create in Unity Catalog, the table name must be three-part and the location must be an external location registered in Unity Catalog.