Diagnostic Key — DII8-015 to DII8-028
DII8-015 — C · p. 264 · CDC vs full extract/replication
CDC identifies/transmits changed rows. A: modeling, not CDC. B: governance. C: correct. D: archive purpose differs.
DII8-016 — D · p. 264 · Data-based vs log-based CDC
D correctly separates data/application indicators/change objects from DBMS logs. A/B/C: none describe the chapter’s defining distinction.
DII8-017 — A · pp. 264–265, 268–269 · Async vs Sync
Producer must continue during receiver outage → async/loose. A: correct. B/C: create shared blocking/coordination dependency. D: accounts are irrelevant.
DII8-018 — B · p. 265 · Synchronous benefit vs dependency risk
B: immediate synchronization comes with blocking/shared availability risk. A: sync is not higher latency than nightly batch. C: state/availability planning matters more, not less. D: pub-sub is a different interaction model.
DII8-019 — C · pp. 265–266 · Streaming vs Batch
C: continuous low-latency event processing. A: batch snapshot. B: streaming often minimizes physical staging. D: sharing governance.
DII8-020 — D · p. 266 · Replication vs semantic integration
D: replication fits exact synchronized copies with controlled changes. A: competing independent writes create conflict. B: unrelated structures/meanings need integration. C: replication necessarily maintains copies.
DII8-021 — A · p. 266 · Archive accessibility vs retention
A: technology/format obsolescence can make retained data unreadable. B/C: unrelated patterns. D: retention obligations may be the reason for archiving.
DII8-022 — B · p. 267 · Canonical vs pairwise formats
B: common representation reduces pairwise transformations. A: product uniformity not required. C: governance is needed to maintain the model. D: timing remains requirements-driven.
DII8-023 — C · pp. 267–268 · Point-to-point vs Hub
C: interface/support burden grows rapidly as systems increase. A/B: direct links can exchange data/files. D: no warehouse requirement.
DII8-024 — D · pp. 267–268 · Hub vs Point-to-point
D: common hub/canonical representation reduces interfaces and inconsistency. A/B/C: preserve or worsen proliferation/dependency.
DII8-025 — A · p. 268 · Pub-sub vs direct access
A: subscribers receive published output. B: direct DB access is not pub-sub. C: publisher does not necessarily wait for consumers. D: publishing does not imply archive.
DII8-026 — B · pp. 268–269 · Tight vs Loose coupling
B: queue + continue is loose/asynchronous. A/C/D: each creates tighter dependency.
DII8-027 — C · p. 269; p. 277 · Orchestration vs controls/profiling
C: orchestration coordinates execution order/dependencies. A: security. B: governance agreement. D: profiling.
DII8-028 — D · p. 269 · Orchestration vs Process controls
D: exception logs and dependency charts are evidence/controls. A: topology choice. B: canonical modeling. C: CDC technique.