Study Databricks DE-PRO Unity Catalog Inheritance: key concepts, common traps, and exam decision cues.
This domain is small, but it is precise. Databricks wants metadata that makes enterprise data easier to find and permission logic that is easy to reason about.
| Requirement | Better first instinct |
|---|---|
| make enterprise data easier to understand and find | add descriptions and metadata intentionally |
| reason about inherited permissions | follow the Unity Catalog object path carefully |
| avoid permission surprises | know which higher-level grants flow downward |
| Governance need | Stronger first answer |
|---|---|
| make data understandable | useful descriptions and metadata |
| make permissions predictable | object-path inheritance reasoning |
| reduce surprise access outcomes | explicit understanding of downward grant flow |
This domain is easy to underestimate because the mechanics seem simple. The exam often uses that precision against you.
| If the stem says… | Strong reading |
|---|---|
| “make data more discoverable” | enrich metadata and descriptions |
| “permission inheritance” | this is a Unity Catalog object-model question |
| “enterprise data” | governance is part of platform usability, not just restriction |
Metadata helps teams:
That makes it part of enterprise data governance, not an optional polish step.
| Trap | Better rule |
|---|---|
| treating metadata as optional decoration | DE-PRO treats it as a governance tool |
| granting permissions without reasoning through inheritance | inheritance changes effective access |
| mixing discoverability with sharing mode | they are related but distinct governance choices |
| Scenario clue | Stronger answer shape |
|---|---|
| “people cannot tell which dataset is authoritative” | metadata and descriptions |
| “effective permissions are confusing” | object-path inheritance reasoning |
| “question mentions catalog/schema/table flow” | Unity Catalog inheritance |
| “discoverability is the business pain” | governance via metadata, not performance tuning |
Governance questions usually reward choosing the control plane rather than the compute plane. If the goal is discoverability, improve metadata and descriptions. If the question is about effective permissions, reason through Unity Catalog inheritance along the object path. The weakest answers usually resize compute for what is clearly a governance or metadata problem.