Meridian Applied Laboratory Integration

← Control Center

The hands-on companion to 00A is 00B — CDMP Applied Data Management Laboratory — Meridian Commerce Group.

Drive root: https://drive.google.com/drive/folders/1pzkI4XHcc7xblPqUZyQVn-fU7ZhQ5vaf
GitHub section: 00B Meridian Lab

Relationship between 00A and 00B

• The chapter theory package remains the primary source-grounded CDMP learning/exam-prep system.
• Applied labs make the DMBOK observable but do not replace reading, retrieval, comparison, scenarios, or question practice.

Source gate

Do not finalize a chapter-specific applied lab until the full controlling DMBOK chapter has been read. Meridian situations can be original, but DAMA concepts, terminology, roles, processes, sequences, metrics, and conclusions must be source-checked.

Technology gate

Use Main 00B’s Technology Competency Roadmap to decide:

• what technology is actually required;
• why it matters;
• target depth;
• readiness test;
• stopping boundary.

Outside courses, books, videos, tutorials, and official documentation may teach the technology itself. Supplied scripts are scaffolding; the learner must eventually read, explain, modify, and rebuild important logic independently.

Fit-to-chapter rule

Not every chapter becomes coding. Choose the medium that makes the DMBOK concept concrete:

• technical build;
• break/diagnose/repair lab;
• management artifact;
• ethical/decision dilemma;
• trace/observation exercise;
• role simulation;
• cross-domain incident.

Meridian continuity

Reuse the same company, stable IDs, synthetic data, systems, roles, defects, and prior decisions across chapters so later work builds on earlier evidence.

Evidence rule

A lab is not complete because a command ran successfully. Capture inspectable evidence, interpret it, explain what would fail without the discipline/control, and complete a DMBOK Debrief reconnecting the observed work to the chapter.

Independence rule

Important labs include reduced-scaffolding or blank-editor reconstruction. Completion means the learner can reproduce and explain the core reasoning rather than replaying a tutorial line by line.

Scope boundary

Technology exists to make Data Management visible. Do not drift into production DBA administration, advanced software engineering, cloud-platform administration, distributed data engineering, or data-science modeling unless a later explicit learning goal requires it.

Software-source rule

Current official software documentation may control software behavior and syntax, but it never replaces the DMBOK as the authority for DAMA meaning.

Source: 00A-01, Section 21.