Flow-DG

Create a comprehensive Unity Catalog governance flow diagram with the following layers and elements (diagram only, no explanation):

LAYERS (top to bottom):

  1. RBAC layer – showing role-based access control foundation
  2. Azure AD – users, groups, and service principals
  3. Access Control – RBAC grants, ABAC policies, credential vending
  4. Data Classification & Tagging – auto-discovery, MDM tags, lineage & audit
  5. Query Engine – ABAC filters, column masks, MDM status checks
  6. Managed Storage – raw (PII, 30-day TTL), silver (masked), gold (conformed dimensions, 10-year retention)
  7. External Storage – secured MDM hub, partner shares, public data products
  8. Governed Sharing – masked customer 360 extracts, anonymized metrics
  9. Retention & Archival – by domain (transactions 7yr, aggregates indefinite)
  10. End-to-end lifecycle management

ELEMENTS TO INCLUDE IN EACH BOX:

Azure AD:

  • Users: alice@contoso.com, bob@contoso.com
  • Groups: Analysts, Data Engineers, Service Principals

Access Control:

  • RBAC grants: Analysts SELECT, Engineers ALL
  • ABAC policies: PII column mask, GDPR deletion rules
  • Credential vending: zone-scoped tokens (raw/bronze/silver/gold)

Data Classification:

  • Auto-discovery: PII column tagging, GDPR audit scan, data domain classification
  • MDM tags: Customer, Product, Location entities
  • Lineage & audit: column-level lineage, job run logs, user query audit

Query Engine:

  • ABAC filters and column masks
  • email → * (masking example)
  • MDM status checks

Managed Storage:

  • raw: full PII, 30-day TTL
  • silver: masked PII for analysts
  • gold: conformed MDM dimensions, 10-year retention

External Storage:

  • Secured MDM hub for internal master data
  • Partner data shares (aggregate metrics)
  • Public data products

Governed Sharing:

  • Masked customer 360 extracts
  • Anonymized usage statistics

Retention:

  • Transactions: 7 years
  • Aggregates: Indefinite

DIAGRAM STYLE:

  • Color-coded layers (blue=RBAC, purple=identity, amber=classification, gray=compute, coral=storage, teal=lifecycle)
  • Flow arrows showing data and decision paths
  • Each box should have specific examples
  • Dashed lines for audit/lineage capture
  • No explanatory text, only the diagram and box labels with examples

Leave a Reply

Your email address will not be published. Required fields are marked *