05 — Scenario Lab
← Battle Cards · Chapter 1 Home · Next: Question Bank →
For every scenario, answer the complete decision grid before reading the rationale:
- Primary problem
- Leading DMBOK Knowledge Area
- Supporting Knowledge Areas
- Relevant roles
- Best activity/control/process/model/artifact
- Tempting weaker response and why it is weaker
- A changed fact that would change the answer
Scenario 1 — The Tool-First Integration Project
A company buys a new integration platform because executives liked a vendor demo. Six months later, teams realize they never agreed on which customer data should be shared, acceptable latency, Data Quality, security rules or lineage needs.
Best answer: Technology choice led before business-aligned data requirements were understood. Chapter 1 says Data Management requirements should drive IT decisions.
Leading KA: Data Architecture.
Supporting: Integration & Interoperability, Data Quality, Data Security, Metadata.
Roles: sponsor/CDO, business stakeholders, Data Architect, integration lead, Stewards.
Weaker response: replace the tool immediately. That does not repair the missing requirements/planning process.
Changed fact: if requirements were already defined and the platform failed them, the issue shifts toward technology fit/execution.
Source: Sections 2.4, 2.5.4, 2.5.12; pp. 25, 28–29, 33.
Scenario 2 — Which Customer Is the Customer?
Sales, Billing and Support use different definitions of “customer,” then leadership combines the systems and gets contradictory totals.
Best answer: Data is representation; different groups made different representational choices for the same concept. This is an enterprise-perspective problem, not merely a reporting problem.
Leading KA: Data Governance.
Supporting: Modeling & Design, Metadata, Reference & Master Data, Data Quality.
Roles: Data Owners, Stewards/SMEs, modelers/architects, reporting consumers.
Weaker response: average the counts or pick the largest number. That hides the semantic disagreement.
Changed fact: if definitions were identical but duplicate records caused the mismatch, Data Quality or Master Data resolution would become more central.
Source: Sections 2.1, 2.5.7; pp. 20–22, 29–30.
Scenario 3 — Perfectly Available, Unusable Dataset
A warehouse has 99.99% uptime, strong encryption and fast queries, but analysts refuse to use a dataset because product codes are inconsistent and historical values cannot be trusted.
Best answer: Managing data means managing Data Quality, and quality is measured against business/stakeholder needs.
Leading KA: Data Quality.
Supporting: Data Governance, Metadata, Storage & Operations.
Roles: Data Owner, Steward, data consumers, DQ analysts, platform/operations staff.
Weaker response: buy faster hardware. Performance is not the cause of distrust.
Changed fact: if the data were accurate but users did not understand the fields, Metadata would lead.
Source: Sections 2.4, 2.5.3; pp. 23, 27–29.
Scenario 4 — Where Did Revenue Come From?
An executive challenges a revenue KPI. The analyst can show the value but not the source transactions, transformations or systems it passed through.
Best answer: The missing concept is data lineage. Metadata makes the trace understandable.
Leading KA: Metadata Management.
Supporting: Integration & Interoperability, DW/BI, Data Architecture.
Roles: Metadata/lineage specialists, integration engineers, architects, analysts/BI owners.
Weaker response: extend retention. That does not answer where the KPI came from.
Changed fact: if the question were how long source transactions should be kept and when destroyed, lifecycle management would lead.
Source: Sections 2.5.5, 2.5.9; pp. 29–32.
Scenario 5 — Manage Everything Equally
A Data Management office declares that every file, table, log, email and intermediate dataset will receive identical stewardship, documentation, quality monitoring and review.
Best answer: Organizations cannot manage every piece of data equally. Prioritize critical data and minimize ROT — Redundant, Obsolete, Trivial data.
Leading KA: Data Governance.
Supporting: Metadata, Data Quality, Document & Content Management where lifecycle/retention applies.
Roles: Data Owners, Stewards, Governance Council, records/content/lifecycle stakeholders.
Weaker response: automate the same controls faster. Automation does not fix the prioritization problem.
Changed fact: a small, bounded regulated dataset defined as uniformly critical could reasonably receive consistent controls.
Source: Sections 2.5.9–2.5.10; pp. 31–32.
Scenario 6 — The Missing Program Artifact
The CDO already has vision, business case, principles and success measures. The team now needs a sequenced list of programs/projects with assignments and milestones.
Best answer: Data Management Implementation Roadmap.
Leading KA: Data Governance.
Supporting: Data Architecture and affected Data Management functions.
Roles: CDO/program sponsor, governance leadership, PMO/program manager, accountable functional leaders.
Weaker response: rewrite the Charter. The mandate already exists; implementation sequencing is missing.
Changed fact: if leaders instead need three-year goals and accountable functions/leaders, the Scope Statement is the better artifact.
Source: Section 2.6; pp. 34–35.
Scenario 7 — Choose the Framework
A steering committee wants to see how Business Strategy, IT Strategy, organizational infrastructure/processes and IT infrastructure/processes fit together around data and information.
Best answer: Strategic Alignment Model (SAM).
Leading KA: Data Architecture.
Supporting: Data Governance.
Roles: enterprise/data/IT architects, business and IT executives, steering committee.
Weaker response: DAMA Wheel. It maps Knowledge Areas, not four-domain business/IT alignment.
Changed fact: if an explicit Information layer and Strategy/Tactics/Operations grid were needed, AIM would fit better.
Source: Sections 3.1–3.3; pp. 36–38.
Scenario 8 — Build a Knowledge Area Context
A Data Quality team wants a reusable diagram of inputs, suppliers, activities, participants, deliverables, consumers, tools, techniques and metrics.
Best answer: Knowledge Area Context Diagram.
Leading KA: Data Governance for the generic operating-pattern context.
Supporting: the Knowledge Area being described plus Metadata for documented context.
Roles: KA lead, suppliers, participants, consumers, governance/assurance stakeholders.
Key classifications: person performing/managing/approving = Participant; measurable result = Metric.
Weaker response: DAMA Wheel; it only shows the overall KA taxonomy.
Changed fact: if only recurring factors around Goals & Principles are needed, use the Environmental Factors Hexagon.
Source: Section 3.3; pp. 38–41.
Scenario 9 — Phase Classification
A Metadata team (1) defines multi-year direction/standards, (2) monitors approved ownership, (3) builds/tests a lineage integration and (4) supports it after launch.
Best answer: (1) Plan, (2) Control, (3) Develop, (4) Operate.
Leading KA: Metadata Management.
Supporting: Data Governance, Integration & Interoperability.
Roles: Metadata lead, lineage developers, assurance staff, service owners.
Deciding clue: Control assures ongoing conditions; Operate runs/supports after deployment.
Source: Section 3.3, p. 40.
Scenario 10 — Advanced Analytics Without Foundations
Executives want predictive analytics immediately while Data Quality, Metadata, architecture, source integration and Governance are weak.
Best answer: dependency/evolved views show analytics depends on upstream foundations; the Aiken Pyramid also illustrates progression toward advanced use.
Leading KA: DW/BI.
Supporting: Data Quality, Metadata, Architecture, Reference & Master Data, Integration & Interoperability, Governance.
Roles: BI/analytics leaders, Data Owners/Stewards, architects, DQ/Metadata/integration teams.
Weaker response: buy a stronger analytics product. The missing capability is upstream management, not compute.
Changed fact: if foundations were reliable and only analytic tools/skills were absent, analytics capability itself would lead.
Source: Sections 3.4–3.5; pp. 41–45.
Scenario 11 — Data Has Value and Risk
A health organization finds a dataset useful for care recommendations and revenue, but it contains sensitive information, stale fields and possible unexpected reuse.
Best answer: Data represents both value and risk. Lifecycle management must include quality, protection, ethics, privacy and appropriate use.
Leading KA: Data Security.
Supporting: Data Quality, Governance, Metadata.
Roles: Data Owner, security/privacy/ethics stakeholders, Stewards, consumers, risk/compliance participants.
Weaker response: monetize first and address risk if regulators object. That violates lifecycle/risk principles.
Changed fact: anonymization, currency and approved use reduce specific risks but do not eliminate all risk.
Source: Sections 2.4, 2.5.8, 2.5.11; pp. 25, 30, 32–33.
Scenario 12 — Governance Is Not the Whole Program
A company establishes a Governance Council, stewardship roles and policies, then declares Data Management complete while integration, models, storage, quality, Metadata and reporting remain weak.
Best answer: Executives confused Data Governance with the entire Data Management discipline.
Leading KA: Data Governance.
Supporting: all other Knowledge Areas represented by the DAMA Wheel.
Roles: Governance Council, Data Owners/Stewards, CDO/Data Management leaders, KA practitioners.
Weaker response: abolish Governance because it did not solve everything. Governance is necessary; the error was treating it as sufficient.
Changed fact: if other KAs were mature but enterprise decisions were inconsistent and no one had decision rights, Governance would be the primary missing capability.
Source: Sections 3.3 and 4; pp. 37–49.
Cross-scenario pattern key
| Scenario | Primary reasoning pattern |
|---|---|
| S1 | Principle / Strategy — requirements before technology |
| S2 | Representation / Context / Enterprise Perspective |
| S3 | Data Quality — fitness for use |
| S4 | Lineage / Metadata |
| S5 | Lifecycle / Prioritization / ROT |
| S6 | Strategy / Artifact selection |
| S7 | Framework selection |
| S8 | Context Diagram |
| S9 | P-C-D-O |
| S10 | Dependency / Foundation |
| S11 | Risk |
| S12 | Governance vs Management |
Repair rule after a miss
Tag the miss before retesting: knowledge gap; vocabulary confusion; confusion pair; role/responsibility confusion; sequence/process error; missed qualifier; misread stem; poor elimination; overthinking; changed correct answer; time pressure; or source-lookup failure.
Then revisit only the relevant Guided Learning section/Battle Card and retest with a changed scenario.