Unity Catalog is the account-level unified data governance layer provided by Databricks. It delivers centralized access control, audit logging, and data lineage across multiple workspaces for every data asset, including tables, views, functions, ML models, and files (Volumes). It unifies metadata management that used to be fragmented per workspace in the legacy Hive Metastore by introducing a three-level namespace of catalog.schema.table, and centralizes SQL-standard GRANT/REVOKE-based permission management across workspaces.
This article covers Unity Catalog end-to-end: hierarchy, permission model, External Locations, OpenSharing (formerly Delta Sharing) integration, and how it differs from Hive Metastore. It also highlights the points tested on the Data Engineer Associate (DEA) exam, focusing on the Governance and Security section (15% of the exam).
Unity Catalog uses a four-level object model topped by the metastore. Every data asset sits in this tree, and privileges granted on a catalog or schema are inherited by the objects below it (privileges granted on the metastore do not inherit, except READ METADATA).
Metastore (one per region)
├── Catalog: production
│ ├── Schema: sales
│ │ ├── Table: orders
│ │ ├── Table: customers
│ │ ├── View: daily_summary
│ │ └── Function: calc_tax()
│ ├── Schema: marketing
│ │ ├── Table: campaigns
│ │ └── Volume: raw_files
│ └── Schema: information_schema (auto-generated)
├── Catalog: development
│ └── Schema: sandbox
│ └── Table: test_orders
├── External Location: s3://data-lake/external/
└── Storage Credential: aws_s3_roleWhen you reference a data asset, always use the three-level namespace catalog.schema.object. This makes it possible to uniquely identify which environment, which domain, and which table is being referenced just from the name.
-- Access via the three-level namespace
SELECT * FROM production.sales.orders;
-- ^^^^^^^^^^ ^^^^^ ^^^^^^
-- Catalog Schema Table
-- Set a default Catalog/Schema
USE CATALOG production;
USE SCHEMA sales;
-- After the settings above, you can use short names
SELECT * FROM orders;| Level | Description | Example Design Pattern |
|---|---|---|
| Metastore | The top-level container for Unity Catalog. Create one per region and attach multiple workspaces to it | One created for ap-northeast-1 (Tokyo) |
| Catalog | Top-level logical grouping of data assets. Separated by environment, department, or project | production / development / staging, finance / marketing |
| Schema | Grouping for tables and views. Organized by domain or data layer | sales / hr / logs, bronze / silver / gold |
| Table / View / Function / Volume | The actual data assets. Tables and volumes can be managed or external | orders (Managed), external_logs (External), calc_tax() (UDF) |
To store data assets in Unity Catalog, you first create a Catalog and a Schema. Catalogs can be created by the Metastore Admin (or any user holding the CREATE CATALOG privilege), and Schemas can be created by the Catalog owner (or any user holding CREATE SCHEMA and USE CATALOG on that Catalog).
-- Create a Catalog
CREATE CATALOG IF NOT EXISTS production
COMMENT 'Production environment catalog';
-- Create a Schema
CREATE SCHEMA IF NOT EXISTS production.sales
COMMENT 'Sales domain tables';
-- Create a Managed Table (no LOCATION -> stored in Unity Catalog-managed storage)
CREATE TABLE production.sales.orders (
order_id BIGINT GENERATED ALWAYS AS IDENTITY,
customer_id BIGINT NOT NULL,
amount DECIMAL(12,2) NOT NULL,
order_date DATE NOT NULL,
status STRING DEFAULT 'pending'
)
COMMENT 'Customer order records'
TBLPROPERTIES ('quality' = 'gold');
-- Create an External Table (with LOCATION -> references data in external storage)
CREATE TABLE production.sales.external_logs (
log_id BIGINT,
message STRING,
timestamp TIMESTAMP
)
LOCATION 's3://data-lake/external/sales/logs/';Unity Catalog enforces access control with SQL-standard GRANT/REVOKE syntax. Privileges are granted on Securable Objects (Catalog, Schema, Table, View, Function, Volume, External Location, Storage Credential, and others) and attached to users, service principals, or groups (principals). Users initially have no access to data, and a privilege must be explicitly granted before a principal can perform an action. Section 7 of the DEA exam guide lists applying GRANT, REVOKE, and DENY, but the DENY statement applies only to hive_metastore and is not supported in Unity Catalog. The mechanism for explicit denial in Unity Catalog is ABAC DENY policies (Beta), which can deny only MANAGE ACCESS CONTROL (access-management operations such as granting and revoking privileges and transferring ownership). Data privileges such as SELECT cannot be denied this way.
| Privilege | Applies To | Effect |
|---|---|---|
USE CATALOG | Catalog | Required to interact with any object in the Catalog (does not grant access to data by itself) |
USE SCHEMA | Schema, Catalog | Required to interact with any object in the Schema. Granting it on a Catalog applies it to every Schema in that Catalog |
SELECT | Table, View | Read data (run SELECT statements) |
MODIFY | Table | Run INSERT / UPDATE / DELETE / MERGE |
CREATE TABLE | Schema | Create new tables in the Schema |
CREATE SCHEMA | Catalog | Create new Schemas in the Catalog |
CREATE CATALOG | Metastore | Create new Catalogs in the metastore |
ALL PRIVILEGES | All | Grants every applicable privilege on the object and its children at once (a few, such as MANAGE and READ METADATA, are not included) |
CREATE EXTERNAL LOCATION | Metastore, Storage Credential | Create an External Location using a Storage Credential (required on both the metastore and the Storage Credential) |
-- Step 1: Allow use of the Catalog (open the hallway)
GRANT USE CATALOG ON CATALOG production TO analysts;
-- Step 2: Allow use of the Schema
GRANT USE SCHEMA ON SCHEMA production.sales TO analysts;
-- Step 3: Grant SELECT on tables (let them into the room)
GRANT SELECT ON SCHEMA production.sales TO analysts;
-- ^ SELECT applies to every current and future table under the Schema
-- Restrict to a specific table
GRANT SELECT ON TABLE production.sales.orders TO analysts;
-- Grant data modification privilege
GRANT MODIFY ON TABLE production.sales.orders TO etl_service;
-- Privilege to create tables in a Schema
GRANT CREATE TABLE ON SCHEMA production.sales TO data_engineers;
-- Inspect privileges
SHOW GRANTS ON SCHEMA production.sales;
SHOW GRANTS analysts ON SCHEMA production.sales; -- only the analysts group
-- Revoke a privilege
REVOKE SELECT ON SCHEMA production.sales FROM analysts;Unity Catalog privileges flow from parent objects down to children. For example, granting SELECT on a Catalog applies SELECT to every current and future table under that Catalog. However, SELECT alone is not enough to read the data. The grantee also needs USE CATALOG on the Catalog and USE SCHEMA on the Schema. USE SCHEMA is inherited too, so granting it on the Catalog covers every Schema in it, while USE CATALOG is granted on the Catalog itself.
Privilege inheritance:
GRANT SELECT ON CATALOG production TO analysts;
-> SELECT inherited by every current and future table under production
But usage privileges are still required:
Catalog: production -> USE CATALOG required ✓
Schema: sales -> USE SCHEMA required ✓ (can also be granted on the Catalog)
Table: orders -> readable with SELECT ✓
When USE CATALOG is missing:
Catalog: production -> no USE CATALOG ✗
Schema: sales -> USE SCHEMA granted
Table: orders -> SELECT granted -> but inaccessible ✗Tables registered in Unity Catalog are mainly categorized as Managed Tables or External Tables based on where the data is stored (there are also foreign tables that reference external systems through Lakehouse Federation). The DROP behavior is fundamentally different, so the choice matters at design time.
| Comparison | Managed Table | External Table |
|---|---|---|
| Data location | Unity Catalog managed storage (the storage root of the metastore/catalog/schema) | An external path you specify (S3, ADLS, GCS) |
| How to create | CREATE TABLE ... (no LOCATION) | CREATE TABLE ... LOCATION 's3://...' |
| Data on DROP | The table is dropped, and its data files are deleted automatically after the recovery period (7 days by default); within that period you can restore it with UNDROP TABLE | Only metadata is deleted; data files remain in external storage |
| Lifecycle management | Fully managed by Unity Catalog | You manage the lifecycle of the data files |
| Recommended use cases | Most cases (the default table type that Databricks recommends) | Registering existing data that managed tables do not support (such as JSON or Avro); direct access from non-Databricks clients |
Exam guide point: Section 7 lists distinguishing managed and external tables and creating, modifying, deleting, and converting between them. With DROP TABLE, a Managed Table loses its data files too (after the recovery period), while an External Table loses only its metadata. To convert an external table to a managed table, use ALTER TABLE ... SET MANAGED.
To create an External Table, you must register the credentials Unity Catalog uses to access external storage. The mechanism has two layers: Storage Credential and External Location.
[Storage Credential] Register cloud credentials
| (IAM role / Service Principal / Service Account)
v
[External Location] Bind a credential to an allowed path
url: s3://bucket/path/ "With these credentials, access to this path is OK"
|
v
[External Table] Create a table with LOCATION pointing at the external path
production.sales.ext_logs
LOCATION 's3://bucket/path/logs/'-- 1. Create a Storage Credential
-- Not with SQL: use Catalog Explorer (Connect > Credentials),
-- the Databricks CLI, or Terraform.
-- Requires the CREATE STORAGE CREDENTIAL privilege
-- (metastore admins and account admins have it).
-- Here, aws_s3_credential holds the IAM role
-- arn:aws:iam::123456789012:role/unity-catalog-role.
-- 2. Create an External Location
-- (requires CREATE EXTERNAL LOCATION on the metastore and on the credential)
CREATE EXTERNAL LOCATION s3_data_lake
URL 's3://my-data-lake/production/'
WITH (STORAGE CREDENTIAL aws_s3_credential)
COMMENT 'Production data lake on S3';
-- 3. Grant privileges on the External Location
GRANT CREATE EXTERNAL TABLE ON EXTERNAL LOCATION s3_data_lake
TO data_engineers;
-- 4. Create the External Table
CREATE TABLE production.sales.external_events (
event_id BIGINT,
event_type STRING,
payload STRING,
created_at TIMESTAMP
)
LOCATION 's3://my-data-lake/production/events/';A Storage Credential can be reused across multiple External Locations. For example, a single IAM role can back two External Locations — s3://bucket/sales/ and s3://bucket/marketing/ — so different teams get distinct, well-bounded access ranges.
Unity Catalog was designed to solve the governance pain points of the legacy Hive Metastore. If you are planning a migration, you need to understand the following differences.
| Comparison | Hive Metastore | Unity Catalog |
|---|---|---|
| Management scope | Per-workspace (each workspace has its own isolated metastore) | Per-account (shared across multiple workspaces) |
| Namespace | Two-level (schema.table / database.table) | Three-level (catalog.schema.table) |
| Permission model | Table access control (legacy): GRANT, DENY, and REVOKE on CATALOG, SCHEMA, TABLE, VIEW, FUNCTION, and more, managed per workspace | GRANT/REVOKE with hierarchical inheritance; workspace-local groups cannot be granted privileges; no DENY statement (explicit denial only through ABAC DENY policies, in Beta) |
| Audit logs | Not covered by Unity Catalog's built-in auditing | Unified audit logs via System Tables |
| Data lineage | Not covered by Unity Catalog lineage | Automatic table- and column-level lineage |
| Table formats | Delta / Parquet / CSV / JSON / ORC / Avro | Managed Tables use Delta or Iceberg; External Tables support Delta, CSV, JSON, Avro, Parquet, ORC, and text |
| File management | DBFS (the DBFS root is accessible to every workspace user; DBFS root and mounts are now deprecated) | Volumes (with permission management and auditing) |
| Cross-workspace sharing | Not possible (metadata fragmented across workspaces) | Automatically shared across workspaces attached to the same metastore |
OpenSharing (formerly Delta Sharing) is an open protocol for securely sharing data across organizational boundaries. Unity Catalog acts as an OpenSharing provider and can share data with other organizations' Databricks environments as well as non-Databricks environments (Apache Spark, pandas, Power BI, and more).
-- Create a Share
CREATE SHARE customer_analytics;
-- Add a table to the Share
ALTER SHARE customer_analytics
ADD TABLE production.sales.orders;
-- Create a Recipient
CREATE RECIPIENT partner_company
USING ID 'partner-sharing-identifier';
-- Grant the Recipient access to the Share
GRANT SELECT ON SHARE customer_analytics TO RECIPIENT partner_company;Volumes let you govern non-table files (CSV, JSON, images, model artifacts, configuration files, and so on) under the Unity Catalog permission model. In the legacy DBFS (Databricks File System), the DBFS root is accessible to every user in the workspace, and DBFS audit events cover only calls made through the DBFS REST API and the creation and removal of mounts (the DBFS root and mounts are now deprecated). Because Volumes are created under a Catalog/Schema, you can control privileges with GRANT/REVOKE and access is recorded in the audit logs.
-- Create a Managed Volume (stored in Unity Catalog-managed storage)
CREATE VOLUME production.raw.landing_files;
-- Create an External Volume (references an external path)
CREATE EXTERNAL VOLUME production.raw.s3_landing
LOCATION 's3://my-bucket/landing/';
-- List files
LIST '/Volumes/production/raw/landing_files/';
-- Read files from SQL
SELECT * FROM csv.`/Volumes/production/raw/landing_files/2026-03/data.csv`;
-- Read files in a Volume from Python
-- df = spark.read.csv("/Volumes/production/raw/landing_files/2026-03/data.csv")Unity Catalog automatically parses the Spark queries run in notebooks and jobs, and records the data flow (lineage) between tables and between columns. No manual setup or activation is required — it works automatically wherever Unity Catalog is enabled.
Audit logs are written to the system.access.audit table (System Tables). You can query who did what to which object and when directly in SQL.
-- Unity Catalog audit events in the last 24 hours
-- (GRANT / REVOKE are logged as updatePermissions)
SELECT
event_time,
user_identity.email AS user_email,
action_name,
COALESCE(request_params.full_name_arg,
request_params.securable_full_name) AS object_name
FROM system.access.audit
WHERE service_name = 'unityCatalog'
AND event_time > current_timestamp() - INTERVAL 24 HOURS
AND action_name IN ('getTable', 'deleteTable', 'updatePermissions')
ORDER BY event_time DESC;On the current Data Engineer Associate (DEA) exam (the version effective May 4, 2026), the Governance and Security section accounts for 15% of the questions. Unity Catalog is the core topic in that section. Make sure you nail the items below.
| Topic | What to Remember |
|---|---|
| Three-level namespace | catalog.schema.table structure. The metastore is not part of the namespace |
| USE CATALOG / USE SCHEMA | SELECT does not work without USE CATALOG on the Catalog and USE SCHEMA on the Schema (USAGE is the legacy Hive Metastore privilege name). Parent is the hallway, child is the room |
| GRANT / REVOKE / DENY | Section 7 of the guide lists applying GRANT, REVOKE, and DENY. The DENY statement applies only to hive_metastore and is not supported in Unity Catalog. Explicit denial in Unity Catalog uses ABAC DENY policies (Beta), which can deny only MANAGE ACCESS CONTROL |
| Managed vs External | DROP behavior: Managed -> data files are also deleted after the recovery period (7 days by default), and UNDROP TABLE can restore the table within it; External -> only metadata is deleted. Distinguished by the presence of a LOCATION clause. Convert an external table to a managed table with ALTER TABLE ... SET MANAGED |
| Row filters and column masks | A row filter is a SQL UDF evaluated for each row; rows for which it returns FALSE are excluded (ALTER TABLE ... SET ROW FILTER). A column mask is a SQL UDF that takes the column value and returns either the original or a masked value (ALTER TABLE ... ALTER COLUMN ... SET MASK) |
| ABAC policies | Policies conditioned on governed tags are attached to a catalog, schema, or table and apply row filters and column masks consistently across many tables. They require serverless compute or another supported configuration, such as standard compute on Databricks Runtime 16.4 or above |
| Storage Credential → External Location | Two-layer authentication. Credential = cloud credentials, Location = allowed path range |
| Volumes | The recommended place for non-tabular files instead of the deprecated DBFS root and mounts. Privileges such as READ VOLUME and WRITE VOLUME are managed with GRANT/REVOKE, and access is recorded in the audit logs |
| Data lineage | No activation needed (recorded automatically). Two flavors: table-level and column-level |
| OpenSharing (formerly Delta Sharing) | Not listed in the exam guide effective May 4, 2026 (it was in scope as Delta Sharing in the previous version). Open protocol. No data copy required. Recipients do not have to be Databricks users |
| Privilege inheritance | Privileges granted on a Catalog are inherited by every current and future Schema and object below it. Reading data still requires USE CATALOG and USE SCHEMA |
Governance and Security / Unity Catalog
Question 1
The analyst team (group name: analysts) tried to SELECT from production.sales.orders but got a 'PERMISSION DENIED' error. The administrator has already run GRANT USE SCHEMA ON SCHEMA production.sales TO analysts and GRANT SELECT ON SCHEMA production.sales TO analysts. Which additional SQL statement is required to resolve the issue?
Correct answer: A
To read data from a table in Unity Catalog, you need SELECT on the table (or on its parent Schema or Catalog) plus USE CATALOG on the parent Catalog and USE SCHEMA on the parent Schema. USE SCHEMA and SELECT have already been granted, so the missing piece is USE CATALOG on the production catalog. Option B grants every applicable privilege on the table, but the data still cannot be read without USE CATALOG, and it violates least privilege. Option C (READ) is not a Unity Catalog privilege name. Option D (BROWSE) is a real privilege, but it only lets users discover objects, view their metadata, and request access; it does not let them read data. Note that USAGE is the privilege name in the legacy Hive Metastore; Unity Catalog uses USE CATALOG and USE SCHEMA.
Governance and Security / External Location
Question 2
A data engineer wants to create an External Table that references existing data on S3. What is the correct order of steps in Unity Catalog?
Correct answer: C
Creating an External Table requires a Storage Credential and an External Location to exist first. The correct order is (1) Storage Credential (register cloud credentials), (2) External Location (define the allowed path range using that credential), (3) External Table (use a LOCATION clause to create the table). The External Location references the Storage Credential, so the Credential must exist first. The External Table's LOCATION must fall inside the External Location's URL range, so the Location must exist before the Table.
Governance and Security / Table Types
Question 3
You run DROP TABLE production.sales.orders on a Unity Catalog Managed Table. With the recovery period left at its default, what happens to the data files?
Correct answer: B
When you drop a Unity Catalog Managed Table, its data files are not deleted immediately. Within the recovery period (7 days by default) you can restore the table with UNDROP TABLE; after the period expires, Databricks deletes the data files from cloud storage automatically. Option A is wrong on both counts: the files are not deleted immediately, and the table can be restored. Option C describes an External Table, where only the metadata is deleted and the data files remain in external storage. As for option D, you cannot SELECT a dropped table by its original name. On the exam, make sure you can instantly answer the Managed vs. External difference in terms of whether the data files get deleted, and remember that a Managed Table has a recovery window.
Try More Unity Catalog Questions
Test your level with 16,000+ questions, including Governance and Security items
Try free questions →What is the difference between Unity Catalog and Hive Metastore?
The Hive metastore is a legacy, per-workspace metastore: both its metadata and its permissions (table access control) are managed per workspace. Unity Catalog operates at the account level and provides unified access control, audit logs, and data lineage across multiple workspaces. The permission models also differ: Hive metastore table access control supports the DENY statement in addition to GRANT and REVOKE, but DENY applies only to hive_metastore and is not supported in Unity Catalog. In Unity Catalog, users initially have no access to data, and a privilege must be explicitly granted before a principal can perform an action. Explicit denial is available only through ABAC DENY policies (Beta), which can deny only MANAGE ACCESS CONTROL. Unity Catalog privileges are granted to users, service principals, and account groups (workspace-local groups cannot be granted Unity Catalog privileges) and apply consistently across the Catalog/Schema/Table/View/Function/Volume hierarchy.
Is Unity Catalog free to use?
Unity Catalog requires the Premium plan or above; it is not available on the Standard tier (on Azure, new workspaces must be created on Premium from April 1, 2026, and the Azure Databricks documentation says that Standard tier workspaces remaining on October 1, 2026 are upgraded to Premium automatically). For learning, you can try it in the free Free Edition, which allows one workspace and one metastore per account. Some features have extra requirements: for example, ABAC (attribute-based access control) policies need serverless compute or another supported configuration, such as standard compute on Databricks Runtime 16.4 or above. Check the official Databricks documentation for the latest requirements.
What is the difference between USE CATALOG / USE SCHEMA and SELECT in Unity Catalog?
USE CATALOG and USE SCHEMA are usage privileges: they are required to interact with objects inside a catalog or schema, but they do not grant access to data by themselves. USE CATALOG is granted on a Catalog and USE SCHEMA on a Schema. SELECT is the right to read data from a table or view. For example, to SELECT from production.sales.orders, you need SELECT on the table plus USE CATALOG on the production catalog and USE SCHEMA on the sales schema. Think of USE CATALOG / USE SCHEMA as the keys to the hallway and SELECT as the key to the room. You cannot access the data with just one of them. Note that USAGE is the privilege name from the legacy Hive metastore.
Related Unity Catalog Articles
Data Engineer Associate: Complete Guide
Unity Catalog is tested in the Governance and Security section (15%)
Delta Lake Complete Guide
Unity Catalog Managed Tables use the Delta or Iceberg format
Delta Sharing Explained
Securely share data from Unity Catalog
Databricks SQL Complete Guide
GRANT/REVOKE syntax and the query execution environment
Practice with certification-focused question sets
Try free questionsNicheeLab Editorial Team
NicheeLab editorial team focused on data engineering and cloud certification learning. Content is structured around practical study needs and official exam domains.
Databricks Certifications: All 8 Exams, Difficulty & Study Plan (2026)
Complete guide to all 8 Databricks certifications — Data Eng...
Databricks Exam Difficulty Ranking: 7 Certs Compared (2026)
Seven Databricks certifications ranked by difficulty, with s...
Databricks Study Guide: Fastest Pass Route & Time Estimates (2026)
How to pass Databricks certifications efficiently. Official ...
Databricks Data Engineer Associate: Complete Guide (2026)
Domain-by-domain breakdown of the Databricks Certified Data ...
Databricks Data Engineer Professional: Complete Guide (2026)
Tactics for the Databricks Certified Data Engineer Professio...