Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Why Unity Catalog**: Centralized governance—access control, lineage, audit, discovery. Replaces table-level ACLs with a consistent model across workspaces. **Architecture**: Three-level hierarchy: Metastore → Catalog → Schema → Table. Metastore is account-level; catalogs group...
This hard-level Cloud/Tools question appears frequently in data engineering interviews at companies like Nihilent. While less common, it tests deeper understanding that distinguishes strong candidates.
This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.
Why Unity Catalog: Centralized governance—access control, lineage, audit, discovery. Replaces table-level ACLs with a consistent model across workspaces. Architecture: Three-level hierarchy: Metastore → Catalog → Schema → Table. Metastore is account-level; catalogs group schemas; schemas contain tables. RBAC via grants (SELECT, MODIFY, etc.) on tables, views, schemas. Lineage: Tracks data flow from source to consumption; critical for impact analysis and compliance. Audit: All access logged to cloud storage; queryable for compliance. Scalability: Single metastore can span many workspaces; federate for multi-cloud. Cost: Included in Unity Catalog tier; audit logs have storage cost. Best practice: Organize by domain (e.g., catalog per product); use managed tables for durability; enable Delta Sharing for cross-org. Apply row filters and column masks for PII.
Pro-Move: 'We use Unity Catalog row filters for PII—analysts see masked data by default; we grant unmask to compliance-only group.' Red Flag: Treating Unity Catalog as 'just another metastore'—it's a governance platform; articulate RBAC and audit use cases.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.