DP-750 Certification Practice Question #16

Question

You are scripting the creation of a new governed data area in a Unity Catalog metastore that already has a metastore-level managed storage location. The end state must be a managed Delta table named `finance.reporting.gl_balances`. The four DDL statements below are shown out of order. Arrange them into the sequence in which they must execute so that each object's parent already exists when it is created, and so that the table is a Unity Catalog **managed** table.

```mermaid
flowchart LR
    subgraph Tiles[DDL statements to order]
        T1["CREATE SCHEMA IF NOT EXISTS finance.reporting;"]
        T2["CREATE TABLE finance.reporting.gl_balances (account STRING, balance DECIMAL(18,2));"]
        T3["CREATE CATALOG IF NOT EXISTS finance;"]
        T4["GRANT USE CATALOG ON CATALOG finance TO `reporting_team`;"]
    end
    S1[Step 1] --> S2[Step 2] --> S3[Step 3] --> S4[Step 4]
```

Accepted Answer

Unity Catalog's three-level namespace is strictly hierarchical, so each object can only be created after its parent exists: the catalog `finance` first, then the schema `finance.reporting`, then the table `finance.reporting.gl_balances`. Because the `CREATE TABLE` statement specifies no `LOCATION`/`MANAGED LOCATION` and the metastore already has a default managed storage location, the table is created as a Unity Catalog managed table — Unity Catalog chooses the storage path. The `GRANT USE CATALOG` is sequenced last because it references the catalog and only makes sense once the catalog (and the objects users will query) exist; `USE CATALOG` is the prerequisite usage privilege that lets the reporting team interact with objects inside `finance`.

More DP-750 practice questions