Diagnostics — DQ13-018–034
DQ13-018 — B
Why B wins: orphan CUSTOMER_ID is a broken parent-child relationship, the classic Integrity clue.
Why A/C/D lose: short phone = likely Validity; late feed = Timeliness; duplicate customer = Uniqueness.
Source: pp. 430–431.
Confusion pair: Integrity vs Validity/Uniqueness.
DQ13-019 — C
Why C wins: Timeliness measures whether data becomes available within the time needed by the consumer/process.
Why A/B/D lose: currentness = Currency; duplicate resolution = Uniqueness; allowed domain = Validity.
Source: pp. 431–432.
Confusion pair: Timeliness vs Currency.
DQ13-020 — D
Why D wins: Currency is up-to-dateness relative to fact volatility and consumer need.
Why A/B/C lose: deadline = Timeliness; mandatory presence = Completeness; record relationships = Integrity.
Source: pp. 431–432.
Confusion pair: Currency vs Timeliness.
DQ13-021 — A
Why A wins: Reasonableness asks whether a value/aggregate is plausible against expectations/benchmarks.
Why B/C/D lose: matching parent = Integrity; required null = Completeness; duplicate entity = Uniqueness.
Source: pp. 431–432.
Confusion pair: Reasonableness vs Validity.
DQ13-022 — B
Why B wins: multiple records representing one real entity is the Uniqueness/Deduplication test.
Why A/C/D lose: real address = Accuracy; approved domain = Validity; SLA cutoff = Timeliness.
Source: pp. 431–432.
Confusion pair: Uniqueness vs Consistency.
DQ13-023 — C
Why C wins: Accuracy is correct representation of the real-life entity/event.
Why A/B/D lose: format = Validity; mandatory population = Completeness; elapsed time = Timeliness.
Source: p. 432.
Confusion pair: Accuracy vs Validity.
DQ13-024 — D
Why D wins: passing syntax proves format validity, not ownership/truth; the value is inaccurate for that customer.
Why A/B/C lose: validity cannot prove Accuracy; no presence issue exists; ownership mismatch is not a delivery-time issue.
Source: pp. 429–432.
Confusion pair: Validity vs Accuracy.
DQ13-025 — A
Why A wins: values are current/correct, but they miss the required availability cutoff.
Why B/C/D lose: Currency and Accuracy pass by the facts; duplicate identity is irrelevant.
Source: pp. 431–432.
Confusion pair: Timeliness vs Currency.
DQ13-026 — B
Why B wins: delivery is on schedule but the facts are too stale for use.
Why A/C/D lose: Timeliness passes; relationships/presence are not the issue.
Source: pp. 431–432.
Confusion pair: Currency vs Timeliness.
DQ13-027 — C
Why C wins: CUSTOMER_ID is present, so simple completeness passes; the parent relationship fails Integrity.
Why A/B/D lose: presence is not the problem; currency and plausibility are not described.
Source: pp. 430–431.
Confusion pair: Completeness vs Integrity.
DQ13-028 — D
Why D wins: two records represent one real customer, the defining Uniqueness clue.
Why A/B/C lose: inconsistent attributes may coexist but are not decisive; timing/domain conformance are unrelated.
Source: pp. 431–432.
Confusion pair: Uniqueness vs Consistency.
DQ13-029 — A
Why A wins: Business Rules express desired business/data behavior; DQ Rules operationalize applicable expectations into measurable dimension-aligned tests.
Why B/C/D lose: the rule types are related; DQ Rules are not tool-generated by definition; Business Rules can be measurable.
Source: pp. 432–434.
Confusion pair: Business Rule vs DQ Rule.
DQ13-030 — B
Why B wins: approved reference-table membership is a Validity domain rule.
Why A/C/D lose: no presence, reality-verification, or elapsed-time test is described.
Source: pp. 432–433.
Confusion pair: Validity domain vs Accuracy.
DQ13-031 — C
Why C wins: completeness can be conditional; population is required only when business status demands it.
Why A/B/D lose: entity duplication, time, and real-world truth are not the test.
Source: pp. 430, 433.
Confusion pair: Conditional completeness vs simple null check.
DQ13-032 — D
Why D wins: the integer is syntactically valid; the problem is implausible volume relative to a benchmark.
Why A/B/C lose: format/domain, relationship, and presence are not the deciding evidence.
Source: pp. 431–434.
Confusion pair: Reasonableness vs Validity.
DQ13-033 — A
Why A wins: Accuracy requires comparison with reality or a sufficiently trusted verified source.
Why B/C/D lose: length/domain/presence are Validity/Completeness checks, not truth verification.
Source: pp. 432–434.
Confusion pair: Accuracy verification vs validation.
DQ13-034 — B
Why B wins: Plan defines scope, impact, causes, and improvement options before implementation.
Why A/C/D lose: recurring scorecards = Check/operations; implementation = Do; routine response = Act/operations.
Source: pp. 434–436.
Confusion pair: PDCA Plan vs Do/Check/Act.