Governance for Databrickss
Databricks governance is the control of who can see and change data, using Unity Catalog. It organises assets as catalog, schema and table, grants privileges to users and groups, records lineage and audit logs, and applies row filters and column masks. It is the final stage because it secures everything built earlier.
Stage: Operations and Governance · Part of the Databricks roadmap · Last reviewed 19 November 2026
What to learn in Governance
- Explain the Unity Catalog three-level namespace of catalog, schema and table
- Grant SELECT on a table to a group using GRANT statements
- Apply a column mask and a row filter to protect sensitive fields
- Use external locations and storage credentials to govern cloud storage access
- Trace upstream and downstream dependencies using lineage views
Governance interview questions
What is the difference between a managed table and an external table in Unity Catalog?
A managed table stores its data in Unity Catalog managed storage, and dropping it removes the data. An external table points at files in a location you control, and dropping it removes only the metadata, leaving the files in place.
How does Unity Catalog help restrict access to sensitive columns?
You attach a column mask function to a column, and it returns masked values unless the user belongs to an allowed group. Combined with row filters and GRANT privileges, this enforces rules centrally instead of in each query or dashboard.
Where Governance fits in the Databricks roadmap
Governance belongs to the Operations and Governance stage (advanced level). Run safely.
Other units in this stage
Back to the full Databricks roadmap