Skip to content

Diagnostics C16-029–042

C16-029 — Correct: A

Correct rationale: Chapter 16 lists establishing an organizational data strategy among common CDO mandates.

Option logic - A: Chapter 16 lists establishing an organizational data strategy among common CDO mandates. - B: Database administration is an IT operational role. - C: Compensation is an HR matter. - D: The CDO may establish governance standards and often oversees related capabilities, but does not make governance unnecessary.

Source: Chapter 16, p. 534
Confusion pair: CDO vs operational roles
Mistake Autopsy Tag: Confused executive mandate with execution role


C16-030 — Correct: B

Correct rationale: Chapter 16 says that in a decentralized model the CDO can be responsible for data strategy while distributed resources execute it.

Option logic - A: Direct reporting of all resources would be centralized, not the decentralized arrangement described. - B: Chapter 16 says that in a decentralized model the CDO can be responsible for data strategy while distributed resources execute it. - C: Decentralized execution can still have enterprise strategy and executive accountability. - D: The ARB is an architecture-governance body, not the CDO role.

Source: Chapter 16, p. 534
Confusion pair: Strategy ownership vs execution placement
Mistake Autopsy Tag: Confused strategic accountability with reporting structure


C16-031 — Correct: C

Correct rationale: Chapter 16 uses this distinction to show governance providing strategy, standards, policies, and accountability while management implements and operates within that guidance.

Option logic - A: This reverses policy/implementation responsibilities. - B: Both functions can span business and technology and require partnership. - C: Chapter 16 uses this distinction to show governance providing strategy, standards, policies, and accountability while management implements and operates within that guidance. - D: The chapter emphasizes synergy and agreement on roles/accountabilities, not separation.

Source: Chapter 16, pp. 534–535
Confusion pair: Governance vs management
Mistake Autopsy Tag: Confused guidance with execution


C16-032 — Correct: D

Correct rationale: Chapter 16 says governance may act as the lead in highly regulated environments where policy and accountability dominate, with the DMO reporting or matrixed to it.

Option logic - A: The chapter describes a close partnership, not elimination of governance. - B: Reporting to the CIO is not required and may be avoided to retain business perspective. - C: Stewards participate in governance but do not replace enterprise governance structures. - D: Chapter 16 says governance may act as the lead in highly regulated environments where policy and accountability dominate, with the DMO reporting or matrixed to it.

Source: Chapter 16, pp. 534–535
Confusion pair: Governance lead vs DMO lead
Mistake Autopsy Tag: Applied fixed reporting rule


C16-033 — Correct: A

Correct rationale: The source explicitly says DMO capability commonly develops organically from successful Data Quality work as value and cross-enterprise needs expand into related disciplines.

Option logic - A: The source explicitly says DMO capability commonly develops organically from successful Data Quality work as value and cross-enterprise needs expand into related disciplines. - B: The source describes the opposite possible evolution: DQ can be an entry point. - C: The chapter says maturing DQ benefits from a unified approach and often expands to MDM/Reference/Metadata. - D: Operating-model type depends on accountability/structure; discipline expansion alone does not prove network.

Source: Chapter 16, p. 535
Confusion pair: Data Quality initiative vs DMO evolution
Mistake Autopsy Tag: Missed capability expansion pattern


C16-034 — Correct: B

Correct rationale: Chapter 16 says Data Architects in the DMO can interface with architecture peers through ARBs, which review standards and may approve or disapprove projects/systems.

Option logic - A: The stakeholder map prioritizes engagement, not architecture standards. - B: Chapter 16 says Data Architects in the DMO can interface with architecture peers through ARBs, which review standards and may approve or disapprove projects/systems. - C: Compensation review is unrelated to architecture decisions. - D: A DQ issue log is not the architecture approval mechanism described.

Source: Chapter 16, pp. 535–536
Confusion pair: ARB vs Data Governance/other mechanisms
Mistake Autopsy Tag: Missed architecture governance mechanism


C16-035 — Correct: C

Correct rationale: Chapter 16 describes ad hoc leader meetings as a workable coordination method when formal mechanisms are absent, but says difficulty managing it will likely drive creation of a formal role or committee.

Option logic - A: The chapter emphasizes coordination because both functions affect one another. - B: No automatic reporting-line change is prescribed. - C: Chapter 16 describes ad hoc leader meetings as a workable coordination method when formal mechanisms are absent, but says difficulty managing it will likely drive creation of a formal role or committee. - D: Governance can actually be one of the coordination platforms; it need not be suspended.

Source: Chapter 16, p. 536
Confusion pair: Ad hoc coordination vs formalization
Mistake Autopsy Tag: Ignored evolution of governance mechanism


C16-036 — Correct: D

Correct rationale: The chapter highlights regulation/privacy/security variation plus global operating challenges such as distributed people, systems, time zones, and languages.

Option logic - A: The source says global firms should pay special attention to adhering to standards, not abandon them. - B: No such DBA reporting requirement exists. - C: Global structures explicitly need regional/business participation. - D: The chapter highlights regulation/privacy/security variation plus global operating challenges such as distributed people, systems, time zones, and languages.

Source: Chapter 16, pp. 536–537
Confusion pair: Global complexity vs local-only design
Mistake Autopsy Tag: Ignored cross-border operating constraints


C16-037 — Correct: A

Correct rationale: These seven attention areas are explicitly listed for global Data Management organizations.

Option logic - A: These seven attention areas are explicitly listed for global Data Management organizations. - B: The chapter seeks a balance of alignment and regional variation, not unbounded autonomy. - C: Synchronization and standards are explicit goals. - D: The chapter does not prescribe universal full centralization.

Source: Chapter 16, pp. 536–537
Confusion pair: Global alignment vs local autonomy
Mistake Autopsy Tag: Missed global management checklist


C16-038 — Correct: B

Correct rationale: The chapter explicitly says these models become more attractive globally because accountability and standards can align while regional differences remain possible.

Option logic - A: Federation retains enterprise strategy; it does not remove it. - B: The chapter explicitly says these models become more attractive globally because accountability and standards can align while regional differences remain possible. - C: Global complexity usually requires more explicit governance/accountability, not none. - D: Regional variation is one reason these models are attractive.

Source: Chapter 16, p. 537
Confusion pair: Federation/network vs full centralization
Mistake Autopsy Tag: Missed balance of alignment and regional variation


C16-039 — Correct: C

Correct rationale: The global section stresses standards and accountability while noting the need to accommodate country-specific laws and regional variations.

Option logic - A: Uncoordinated local standards undermine the enterprise alignment the chapter seeks. - B: Local legal requirements are a primary reason global Data Management is complex and cannot be ignored. - C: The global section stresses standards and accountability while noting the need to accommodate country-specific laws and regional variations. - D: Central authority alone cannot replace local knowledge or legal compliance.

Source: Chapter 16, pp. 536–537
Confusion pair: Enterprise standard vs regional requirement
Mistake Autopsy Tag: Chose consistency over legal/local fit


C16-040 — Correct: D

Correct rationale: Chapter 16 explicitly calls out training and communication as a global-management priority because distributed teams must understand and execute common expectations.

Option logic - A: Model version control is a specific IT role responsibility, not the leading organizational issue here. - B: Performance tuning does not solve inconsistent interpretation. - C: Compensation may matter in role design but does not address the cross-language/time-zone understanding problem. - D: Chapter 16 explicitly calls out training and communication as a global-management priority because distributed teams must understand and execute common expectations.

Source: Chapter 16, pp. 536–537
Confusion pair: Global communication vs technical controls
Mistake Autopsy Tag: Misdiagnosed adoption issue as technology


C16-041 — Correct: A

Correct rationale: The global section specifically names economies of scale and reducing duplication as objectives.

Option logic - A: The global section specifically names economies of scale and reducing duplication as objectives. - B: Stakeholder influence is not the core issue in duplicated tools/processes. - C: Additional independent layers can worsen duplication rather than solve it. - D: Governance and architecture are complementary bodies, not substitutes in this way.

Source: Chapter 16, pp. 536–537
Confusion pair: Economies of scale vs regional duplication
Mistake Autopsy Tag: Failed to consolidate shared capability


C16-042 — Correct: B

Correct rationale: Federation explicitly provides centralized strategy with decentralized execution and is presented as particularly useful for large/global enterprises with regional needs.

Option logic - A: Pure decentralization lacks the strong enterprise strategy/accountability layer described. - B: Federation explicitly provides centralized strategy with decentralized execution and is presented as particularly useful for large/global enterprises with regional needs. - C: Pure centralization may not accommodate the necessary regional autonomy/variation as effectively. - D: Committee-only informality lacks the layered formal accountability required for the scenario.

Source: Chapter 16, pp. 526–527, 536–537
Confusion pair: Federated vs centralized/decentralized
Mistake Autopsy Tag: Global operating-model selection

← Answers 015–028 · Answers 043–056 →