Diagnostic Answers 001–014
DCM9-001 — A
Why: Chapter 9’s core definition is control of capture, storage, access and use of information predominantly outside relational DBs.
B: Data Modeling. C: too narrow—paper only. D: Data Integration.
Source: pp. 287–288. Confusion: DCM vs relational/integration work.
DCM9-002 — B
Why: effective retrieval/use of unstructured information is a stated goal.
A: no relational-conversion mandate. C: Metadata remains essential. D: indefinite retention raises cost/discovery risk.
Source: pp. 288–289. Confusion: goals vs overreach.
DCM9-003 — C
Why: compliance, litigation/e-discovery and continuity are primary business drivers.
A: infrastructure. B: interface growth is not the driver. D: governance is not replaced.
Source: p. 289.
DCM9-004 — D
Why: records responsibility is organization-wide; people create/use/retrieve/dispose according to policy.
A: specialists matter but not exclusively. B: Protection can restrict access. C: XML is not a governing principle.
Source: pp. 289–290. Confusion: specialist-only vs enterprise responsibility.
DCM9-005 — A
Why: in the bucket analogy, content is the information inside the container.
B: medium/container. C: lifecycle artifact. D: index structure, not content.
Source: pp. 290–291. Confusion: Content vs Document.
DCM9-006 — B
Why: ECM applies content management across enterprise scope.
A: CMS is narrower. C: legal hold is one records/e-discovery concern. D: backup is only one lifecycle function.
Source: p. 291. Confusion: ECM vs CMS.
DCM9-007 — C
Why: unstructured information still requires governance, security, Metadata and quality.
A/B: lack of relational schema does not make it unmanaged/unmodellable. D: it can support analytics/integration.
Source: pp. 305–306. Confusion: unstructured vs unmanaged.
DCM9-008 — D — Accountability
Why: responsibility, policy/process and auditability are Accountability.
A: authenticity/reliability. B: retrieval. C: safeguarding.
Source: p. 290.
DCM9-009 — A — Integrity
Why: genuine/trustworthy/reliable record = Integrity.
B: keep duration. C: documented governance. D: retrieval.
Source: p. 290. Confusion: Integrity vs Availability.
DCM9-010 — B — Availability
Why: record was retained but cannot be retrieved on time.
A: end-of-life. C: keeping worked. D: no exposure clue.
Source: p. 290. Confusion: Availability vs Retention.
DCM9-011 — C
Why: Disposition is secure/appropriate authorized end-of-life treatment.
A: retention is requirement-driven, not storage-price driven. B: Transparency requires understandable documentation. D: Protection may restrict access.
Source: p. 290.
DCM9-012 — D — Profitability
Why: not one of the five record characteristics. Content, Context and Timeliness are; so are Permanency and Structure.
Source: pp. 299–300.
DCM9-013 — A — Context
Why: creator/date/relationship information is context Metadata.
B: later alteration. C: arrangement/legibility. D: prompt creation.
Source: pp. 299–300. Confusion: Context vs Structure.
DCM9-014 — B — Permanency
Why: after designation, permanency most directly limits alteration during legal life.
A: accuracy matters but is not the no-change clue. C: surrounding Metadata. D: arrangement/legibility.
Source: pp. 299–300. Confusion: Permanency vs Content accuracy.