Diagnostic Key — DII8-029 to DII8-042
DII8-029 — A · pp. 269–270 · EAI vs direct database access
A: EAI uses defined application interfaces/APIs rather than direct store reach-through. B: cloud not required. C: CEP is separate. D: physical consolidation not required.
DII8-030 — B · p. 270; p. 281 · ESB vs SOA/CEP
B: ESB is message-oriented intermediary supporting heterogeneous, often loosely coupled exchange. A: warehouse schema. C: profiling. D: MOU/sharing governance.
DII8-031 — C · pp. 270–271 · SOA vs API
C: SOA is reusable-service architecture; APIs commonly expose services. A: central storage not required. B: broader than protocol. D: unrelated to replication.
DII8-032 — D · p. 271 · CEP vs message routing
D: multiple streams/context → meaningful fraud condition → triggered block. A: moving data does not infer the pattern. B: archive. C: copy synchronization.
DII8-033 — A · pp. 271–272; p. 281 · Virtualization vs physical integration
A: one logical view over distributed sources without required physical consolidation. B: physical consolidation. C: retention policy. D: service agreement.
DII8-034 — B · p. 272 · DaaS vs Database-as-a-Service
B: governed data delivered on demand via vendor or enterprise catalog/service. A: describes infrastructure DBaaS. C: virtualization may support DaaS but is not synonymous. D: ETL is movement/transformation.
DII8-035 — C · p. 272 · iPaaS vs on-prem middleware
C: cloud-delivered integration spanning data/process/SOA/app, including SaaS/on-prem. A: does not require moving all data public-cloud. B: governance remains. D: not archive media.
DII8-036 — D · pp. 272–273 · Exchange standard vs one-off interface
D: common structure/meaning reduces ambiguity and support complexity. A: mapping may still be required. B: does not guarantee latency. C: vendor uniformity not required.
DII8-037 — A · pp. 273–274 · Requirements before design/build
A: requirements/lifecycle needs come first. B/C: development follows analysis/design. D: archive is not universal first step.
DII8-038 — B · p. 274 · Discovery vs Profiling/Design
B: discovery locates candidate sources using technical search and subject expertise. A: code comes later. C: SLA approval is not discovery. D: discovery does not force cloud.
DII8-039 — C · p. 274; p. 285 · Lineage vs Mapping
C: lineage captures origin, movement, transformation and use for impact analysis. A/B/D: isolated technical facts are not lineage.
DII8-040 — D · pp. 274–275 · Profiling vs documentation assumptions
D: profiling tests actual nulls/defaults/patterns. A: sharing governance. B: event processing. C: service catalog.
DII8-041 — A · p. 275 · Business rules vs technical metrics
A: definitions are one of four business-rule categories. B/C/D: technical artifacts/metrics, not business-rule categories.
DII8-042 — B · p. 276 · Architecture vs tool selection
B: DII architecture includes persistent/transient structures, orchestration/frequency, regulatory/security and operational requirements. A/C/D: each is far too narrow.