Diagnostic Key — DII8-043 to DII8-056
DII8-043 — C · pp. 276–277 · Reuse vs duplicate services
C: reuse/modify an existing enterprise service where feasible. A: creates proliferation. B: direct DB access increases coupling. D: small changes still require appropriate governance.
DII8-044 — D · p. 277 · Persistent vs transient modeling
D: both data at rest and data in motion—hubs, interfaces, messages, streams, canonical structures—need modeling. A/B/C: each is incomplete.
DII8-045 — A · pp. 277–278 · Mapping vs Orchestration
A: orchestration handles frequency/dependencies/order. B: discovery finds sources. C: sharing governance. D: archive media unrelated.
DII8-046 — B · pp. 278–279 · Migration vs simple copy
B: migration is repeatedly tested/executed and requires full integration analysis/design. A: testing is essential. C: timing need not always be synchronous. D: transformation is often required.
DII8-047 — C · p. 279 · Publication vs Migration
C: publication makes new/changed critical data available to consumers/hubs/buses on schedules/events. A: disposition. B: profiling. D: does not replace sources.
DII8-048 — D · p. 279 · CEP flow vs ordinary routing
D: context/history → real-time stream → meaningful event → triggered action. A/B/C: do not represent CEP.
DII8-049 — A · pp. 279–280 · DII service tier vs dependent consumer
A: integration must meet the most demanding dependent consumer’s service requirement. B: would under-service critical dependency. C: monitoring continues after project testing. D: proactive monitoring is required.
DII8-050 — B · p. 280 · Project documentation vs operational Metadata
B: mappings, meanings, rules, history and service catalogs must remain reliable after go-live. A: not temporary. C: monitoring remains necessary. D: Metadata does not replace sources.
DII8-051 — C · pp. 280–281 · Virtualization server vs warehouse
C: virtual integration can span heterogeneous sources but does not automatically eliminate warehouses. A: not necessarily a physical staging DB. B: chapter explicitly rejects automatic replacement. D: not a governance agreement.
DII8-052 — D · p. 281 · ESB vs batch/archive
D: ESB commonly supports near-real-time heterogeneous messaging, asynchronous/loose. A/B: unrelated. C: ESB is not limited to synchronous commits.
DII8-053 — A · pp. 282–283 · Enterprise standardization vs value-driven adoption
A: replacing every working local integration solely for uniformity is a mistake. B/C/D: business participation, sponsorship and reuse are recommended when appropriate.
DII8-054 — B · pp. 284–285 · Sharing Agreement vs technical specification
B: agreement/MOU defines responsibilities, use, restrictions and service expectations. A/C/D: technical artifacts may still be needed but do not govern the relationship.
DII8-055 — C · p. 285 · Forward vs Backward lineage
C: backward/forward paths support origin and downstream impact analysis. A/B: unrelated metrics/security. D: lineage complements rather than replaces mapping.
DII8-056 — D · p. 285 · Output count vs DII value metrics
D: availability + volumes/speed/latency + cost/complexity/reuse better show program value. A/B/C: isolated counts are too narrow.