Section 7 · 5%Data Governance
Data governance
Tags, comments and the permission inheritance model.
This section tests how Unity Catalog describes data so people can find it, and how permissions flow down the object tree. The biggest way people lose marks is forgetting that a grant on a catalog or schema reaches every child object, including ones created later.
Walk the guide, line by line
Each row is one line of the official guide, in its own words on the left. Read across: plain words, what a question looks like, the answer, and the trap.
| Guide line | In plain words | A question looks like | The answer | The trap |
|---|---|---|---|---|
| 7.1 Demonstrate understanding of Unity Catalog tags and comments as mechanisms for adding metadata to securable objects to improve data discoverability. | Tags are key and value labels you attach to objects such as catalogs, schemas, tables, columns and volumes. Comments are free-text descriptions. Both are metadata, meaning data about data, and both help people search for and understand what exists. | A data team wants analysts to search for all tables that hold finance data and to read what each column means, without opening the data. | Add a tag such as a domain key to the tables and a COMMENT to the tables and columns, then search in Catalog Explorer or query the information schema tag views such as TABLE_TAGS and COLUMN_TAGS. Tags can be set with ALTER ... SET TAGS or SET TAG, and you need to be the owner or hold APPLY TAG plus USE SCHEMA and USE CATALOG. A governed tag also needs ASSIGN permission on the tag. | Putting sensitive values in tags is wrong because tag data is stored as plain text and may be replicated globally. Also, a tag does not by itself block access; it only labels, unless an ABAC policy uses it. Runner-up wins when: A governed tag wins over a plain tag when only approved keys and values should be allowed and only certain people may assign them. |
| 7.2 Demonstrate understanding of the Unity Catalog permission inheritance model as a mechanism for managing access control across catalogs, schemas, and objects. | Permission inheritance means a privilege granted on a container applies to the objects inside it. The tree runs from metastore to catalog to schema to tables, views, volumes and functions. | A team lead is granted SELECT on a schema. Later someone adds a new table to that schema, and the question asks what the lead can read. | The lead can read the new table too, because privileges granted on a catalog or schema apply to current and future child objects. Reading still needs USE CATALOG and USE SCHEMA, which can also be inherited from a higher level. MANAGE granted on a container also gives MANAGE on its children, and it is not included in ALL PRIVILEGES. | Assuming a schema grant covers only tables that existed at grant time is wrong. The reverse mistake is believing a table-level SELECT alone is enough, since the usage privileges on the parents are still required. Runner-up wins when: Granting on individual tables wins when the schema also holds tables the person must not see. |
Mind map: Where a grant lands
A grant is not tied to the object you were looking at; it is tied to the level you granted at, and it flows downward.
| What you observe | What it points to | What to do (and when the runner-up wins) |
|---|---|---|
| SELECT granted on a schema | All current and future tables and views in it | Use for whole-schema readers; grant on single tables when the schema is mixed |
| Table SELECT but no usage rights on parents | Access still fails | Add USE CATALOG and USE SCHEMA, directly or inherited |
| User needs to find tables but not read them | BROWSE on the catalog | Grant BROWSE; SELECT is not needed to see metadata |
| Need to find tables by business area | Tags and comments | Tag and comment the objects; a tag labels but does not restrict unless a policy uses it |