Answer Key DG3-001–DG3-016
DG3-001 — A: Data Governance
Why: exercise of authority/control over management of data assets; planning, implementation, monitoring, enforcement. Data Management is execution; IT Governance governs technology portfolios; operating framework is one DG design artifact.
Source: p. 69. Confusion: DG vs DM / ITG.
DG3-002 — B: Data Management
Why: the stem asks who executes work. Governance supplies authority/oversight; DGC is a governance body; ITG governs technology.
Source: pp. 74–75. Confusion: oversight vs execution.
DG3-003 — C: Business-driven
Why: Chapter 3 makes DG a business function tied to business interaction with data and business value. Framework-based concerns structure; multi-layered concerns levels; measured concerns evidence.
Source: pp. 72–74.
DG3-004 — D: Sustainable
Why: disappearing after project funding shows lack of durable sponsorship/funding/operation. Embedded concerns integration into workflows; Measured concerns baselines/evidence.
Source: p. 73.
DG3-005 — A: Embedded
Why: governance is inserted into normal SDLC/analytics/MDM work. Sustainable means durable; Measured means quantified; Multi-layered means levels.
Source: p. 73.
DG3-006 — B: Measured
Why: baseline + measurable improvement is the decisive clue.
Source: p. 73.
DG3-007 — C: Leadership and strategy
Why: committed leadership + data strategy driven by business strategy is the exact principle. Business-driven is broader business ownership; Shared responsibility concerns business/technical participation; Principle-based concerns policy foundations.
Source: p. 74.
DG3-008 — D: Business-driven
Why: directly rejects IT-only governance by framing DG as a business function.
Source: p. 74.
DG3-009 — A: Shared responsibility
Why: explicitly business stewards + technical Data Management professionals.
Source: p. 74.
DG3-010 — B: Multi-layered
Why: enterprise, local and intermediate governance levels.
Source: p. 74.
DG3-011 — C: Framework-based
Why: operating framework defines accountabilities/interactions. Principle-based concerns guiding principles, not organizational interaction design.
Source: p. 74.
DG3-012 — D: Principle-based
Why: guiding principles form foundation for policy/governance work.
Source: p. 74.
DG3-013 — A: Steering Committee
Why: highest authority + executive oversight/support/funding. DGC handles initiatives/escalations; DGO coordinates; Stewardship works domain/project issues.
Source: pp. 76–77; Table 4.
DG3-014 — B: DGC
Why: governance initiatives, policies/metrics, issues/escalations. Steering is top funding authority; DGO coordinates; Stewardship works locally.
Source: pp. 76–77.
DG3-015 — C: DGO
Why: ongoing enterprise definitions/standards/owner-steward coordination.
Source: pp. 76–77.
DG3-016 — D: Data Stewardship Team
Why: subject-area/project working community of business/technical stewards/analysts. Local Governance Committee is a governance layer, not the specific working-community clue.
Source: pp. 76–78.