Study Databricks DE-ASSOC Unity Catalog: key concepts, common traps, and exam decision cues.
This lesson covers the governance object model that DE-ASSOC tests repeatedly. The exam wants you to separate who manages the table storage, how Unity Catalog organizes objects, and which role or ownership boundary controls the object.
Managed table: Table where Databricks manages the underlying data and lifecycle more directly under its governed model.
External table: Table whose data lives in an external storage location while Databricks governs access to the table metadata.
Unity Catalog hierarchy: The governed object path that starts with catalog, then schema, then table or other data object.
| If the problem is mainly about… | Strong lane |
|---|---|
| platform-managed storage responsibility and tighter lifecycle control | managed table |
| reusing externally controlled storage with governed access | external table |
| object hierarchy and where a table lives logically | catalog -> schema -> table thinking |
| who owns or administers governance boundaries | Unity Catalog role and ownership lane |
| Question type | Better instinct |
|---|---|
| Who manages the storage lifecycle more directly? | managed vs external table |
| Where does this governed object live logically? | catalog -> schema -> table |
| Which role or owner should control the object boundary? | Unity Catalog roles and ownership |
| How do I keep governance even when data lives outside Databricks-managed storage? | external table with UC governance |
Many stems sound like table syntax questions but are actually about responsibility boundaries:
If you classify that boundary correctly, the managed-versus-external answer usually becomes straightforward.
A team must keep the data files in an externally controlled location, but they still want Databricks-governed table access and permissions. Which direction is strongest first?
Correct answer: B. The storage stays external, but governance still lives through the Databricks table object.