Skip to content

← Technology Roadmap

Career Data Governance Platforms

This layer is career-facing rather than the foundation of the CDMP curriculum.

Core rule

Learn Data Governance first. Learn the platform second.

The target professional identity is:

“I understand ownership, stewardship, business definitions, metadata, lineage, Data Quality, policy, lifecycle controls, accountability and evidence—and I can operationalize those decisions in enterprise governance platforms.”

Not:

“I know a governance product, therefore I know Data Governance.”

T12 — Microsoft Purview Data Governance — Primary Career Specialization

Timing: begin serious work after Chapter 12 Metadata Management; extend into Data Quality after Chapter 13.

Governance scope to learn

Focus on the Data Governance side of Microsoft Purview rather than treating the entire Purview product family as one required curriculum:

  • Data Map concepts and metadata/source scanning awareness;
  • Unified Catalog;
  • governance domains;
  • data products;
  • business concepts / glossary;
  • owners and stewards;
  • critical data and discoverability;
  • lineage;
  • Data Quality/health concepts when Chapter 13 foundation is complete;
  • governed access/workflow concepts at governance-practitioner depth.

Learning target

Be able to translate a DAMA/Meridian governance requirement into the corresponding kind of Purview governance object/workflow and explain why the object exists.

Stop boundary

Do not become an Azure/Fabric engineer. Source-registration/scanning behavior should be understood enough to govern metadata onboarding and troubleshoot common governance gaps, but production ingestion/platform engineering remains outside the target.

Certification guidance recorded in the roadmap

  • DP-900 Azure Data Fundamentals may be useful as an optional Microsoft data/cloud vocabulary foundation.
  • DP-600 is intentionally not part of this governance path because it is an analytics-engineering credential.
  • The retired SC-400 should not be pursued.
  • Current SC-401 is information-security focused rather than a direct Unified Catalog/Data Map governance credential; consider only if the career path deliberately expands toward information protection/security governance.

T13 — Collibra Governance & Stewardship — Secondary Portability

Why: Collibra provides a strong governance-specialist vocabulary and stewardship/workflow perspective independent of Microsoft’s ecosystem.

Learn at concept-transfer depth

  • community/domain/asset-style governance organization at the level needed to understand employer terminology;
  • glossary/business terms;
  • ownership/stewardship;
  • policies and governance workflows;
  • metadata/catalog and lineage concepts;
  • Data Quality relationships;
  • issue/approval workflows;
  • evidence and accountability.

Career goal

Translate concepts rather than memorize screens. Example:

“In Purview I represented this through a governance domain, business concept/data product, ownership and lineage. In Collibra the object model/workflow differs, but the governance decision is the same.”

Certification value

Collibra’s governance/stewardship training can provide more governance-pure vendor credentialing than a broader cloud/analytics certification. Pursue when it supports target job postings or access is economically reasonable.

T14 — Employer-Specific Platforms: Informatica, Alation & Atlan

Do not try to become expert in every catalog/governance product.

Use these platforms when repeated target-job evidence creates a reason:

  • Informatica Cloud Data Governance and Catalog: important when employers use Informatica for governance/catalog/quality and may have vendor credentials aligned to that ecosystem.
  • Alation: learn employer terminology and governance/catalog concepts when it appears repeatedly in target roles.
  • Atlan: learn when target employers/jobs show meaningful demand.

The transferable concepts remain metadata, glossary, ownership, stewardship, lineage, Data Quality, policy, workflow, discovery and evidence.

OpenMetadata — Meridian Sandbox, Not Primary Career Bet

OpenMetadata remains useful in the lab because it allows hands-on catalog/metadata/lineage practice without making the curriculum depend on paid enterprise licenses. It is a practice environment, not the claim that employers use it more than Purview/Collibra.

Platform-learning proof

For any governance platform, create a small portfolio/evidence package that shows:

  1. Business governance problem.
  2. DMBOK concept/decision.
  3. Platform object/workflow used to operationalize it.
  4. Screenshot/export/config evidence.
  5. Explanation of ownership/stewardship/metadata/lineage/quality behavior.
  6. Changed-fact scenario showing you understand the governance logic beyond the UI.

Sources: Technology Competency Roadmap; Detailed Technology Competency Reference; Data Governance Platform Career Evaluation incorporated into the program.