Home / DE Professional practice test / Data Governance / Question

Databricks Data Engineer Professional · free practice question

A Unity Catalog administrator wants to allow a service principal to create tables in any schema that currently exists OR will be created in the future within…

Exam-style question on Data Governance from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Data Governance Hard

A Unity Catalog administrator wants to allow a service principal to create tables in any schema that currently exists OR will be created in the future within the catalog prod. Which privilege grant achieves this with the FEWEST, MOST targeted privileges?

  1. AGRANT CREATE SCHEMA ON CATALOG prod TO etl_sp; GRANT USE CATALOG ON CATALOG prod TO etl_sp;
  2. BGRANT ALL PRIVILEGES ON CATALOG prod TO etl_sp;
  3. CGRANT CREATE TABLE ON SCHEMA prod.bronze TO etl_sp; GRANT CREATE TABLE ON SCHEMA prod.silver TO etl_sp; (repeat for each schema)
  4. DGRANT USE CATALOG ON CATALOG prod TO etl_sp; GRANT USE SCHEMA ON CATALOG prod TO etl_sp; GRANT CREATE TABLE ON CATALOG prod TO etl_sp;
Answer & explanation

Correct answer: D

WHY D is correct: Unity Catalog's privilege inheritance model allows certain privileges granted at the catalog level to automatically apply to all current AND future schemas within that catalog. The CREATE TABLE documentation states: 'Since privileges are inherited, CREATE TABLE can also be granted on a catalog, which allows a user to create a table or view in any existing or future schema in the catalog. The user must also have the USE CATALOG privilege on its parent catalog.' Because USE SCHEMA is also required on the parent schema of any table being created, the grant set must include USE SCHEMA — granted once at catalog level it inherits to every current and future schema. Granting both USE CATALOG and CREATE TABLE at the catalog level satisfies all requirements in two statements and covers any schema created now or in the future — no per-schema re-grants are ever needed.

WHY NOT C: Granting CREATE TABLE per schema is operationally fragile and does NOT scale to future schemas. Every time a new schema is added, the administrator must remember to re-grant CREATE TABLE to the service principal. This approach does not leverage privilege inheritance and does not satisfy the 'future schemas' requirement.

WHY NOT B: ALL PRIVILEGES on a catalog is far too broad. It grants all applicable privileges (SELECT, MODIFY, CREATE TABLE, CREATE SCHEMA, APPLY TAG, etc.) on every existing and future object in the catalog. This violates the principle of least privilege — the SP only needs to create tables, not read, modify, or manage all data.

WHY NOT A: GRANT CREATE SCHEMA on a catalog allows the service principal to create new schemas, which is not the requirement. CREATE TABLE and CREATE SCHEMA are completely separate, unrelated privileges. This option would not grant the ability to create tables in any schema.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →