Diagnostic Key — DII8-001 to DII8-014
DII8-001 — A · pp. 257–259 · Integration vs Interoperability
Why correct: this is Chapter 8’s explicit distinction.
A: correct. B: too narrow; integration can be physical or virtual and interoperability is broader than API programming. C: describes adjacent KAs. D: backup/recovery are operations concerns, not definitions.
DII8-002 — B · pp. 257–258 · DII use cases
Why correct: migration/conversion is explicitly named.
A/C: unrelated business activities. B: correct. D: agreements can govern sharing, but creating contracts is not the basic DII use case.
DII8-003 — C · p. 258 · Metadata vs execution
Why correct: Metadata preserves inventory, meaning, rules, processing history and lineage.
A: rules themselves are Metadata; Metadata does not replace them. B: Metadata does not determine latency. C: correct. D: governance remains necessary.
DII8-004 — D · pp. 258–260 · Enterprise integration vs point-to-point sprawl
Why correct: uncontrolled interface growth raises support cost/complexity.
A: small environments may make direct links reasonable. B: identical structures reduce the problem. C: DII supports multiple timing models. D: correct.
DII8-005 — A · pp. 259–260 · DII goals vs technology mandates
Why correct: required data should be available in required form/timeframe.
A: correct. B: DII does not require replacing all sources. C: virtualization is one pattern. D: latency is requirements-driven.
DII8-006 — B · p. 260 · Enterprise perspective vs local-only design
Why correct: enterprise design perspective plus iterative/incremental delivery is a chapter principle.
A: reverses the principle. B: correct. C: business participation is required. D: tool sprawl raises support burden.
DII8-007 — C · p. 260; pp. 283–284 · Business accountability vs technical implementation
Why correct: meaning-changing transformations require business accountability.
A: latency is unrelated. B: canonical messaging is not the central failure. C: correct. D: staging is an implementation choice.
DII8-008 — D · p. 260 · Compliance reuse vs one-off controls
Why correct: shared integration capability can reuse compliance logic and simplify verification.
A: legal requirements remain. B: protected data does not become public. C: documentation remains essential. D: correct.
DII8-009 — A · pp. 260–262 · Extract vs Transform/Load
Why correct: Extract selects/acquires required source data.
A: correct. B: describes target-side transformation/ELT. C: pub-sub. D: canonical governance.
DII8-010 — B · pp. 261–262 · Transformation vs governance
Why correct: semantic conversion is a transformation.
A: project governance. B: correct. C: sharing governance. D: service-level management.
DII8-011 — C · pp. 262–263 · ETL vs ELT
Why correct: ELT loads raw first and uses target transformation capability.
A: meaningless prerequisite. B: describes ETL order. C: correct. D: staging is not the defining distinction.
DII8-012 — D · p. 263; p. 277 · Mapping vs Orchestration
Why correct: mapping specifies sources/targets, selections, updates, lookups, calculations and transformations.
A: timing/dependencies are orchestration. B: bandwidth is not mapping. C: approval is governance. D: correct.
DII8-013 — A · p. 263 · Latency vs volume/cost
Why correct: latency is source-generation-to-target-availability time.
A: correct. B: interface complexity. C: model/rule count. D: solution cost.
DII8-014 — B · pp. 263–264 · Batch vs low-latency
Why correct: high-volume scheduled processing with acceptable delay is a batch fit.
A: unnecessary synchronous coordination. B: correct. C: CEP interprets events. D: virtualization is not a timing pattern.