Question Bank Coverage & Diagnostic Map
Verified count and difficulty
| Metric |
Count |
| Total questions |
56 |
| Foundational |
10 |
| Standard |
32 |
| Difficult |
13 |
| Expert-discrimination |
1 |
Correct-answer balance
| Position |
Count |
| A |
14 |
| B |
14 |
| C |
14 |
| D |
14 |
Topic coverage
| Topic |
Questions |
| Introduction |
8 |
| ETL & Latency |
10 |
| Interaction & Architecture |
12 |
| Plan & Analyze |
8 |
| Design & Develop |
8 |
| Tools & Implementation |
6 |
| Governance & Metrics |
4 |
Cognitive coverage
| Cognitive type |
Questions |
| Recall |
10 |
| Understand |
13 |
| Distinguish |
13 |
| Apply |
20 |
Use the Drive bank taxonomy after a real miss:
- knowledge gap;
- vocabulary confusion;
- confusion pair;
- role/responsibility;
- sequence/process;
- missed qualifier;
- misread stem;
- poor elimination;
- overthinking;
- changed answer;
- time pressure;
- source-lookup failure.
High-value confusion pairs represented in the bank
- Integration vs Interoperability
- enterprise integration vs point-to-point sprawl
- ETL vs ELT
- Mapping vs Orchestration
- Snapshot/Delta/CDC vs Replication
- Data-based vs Log-based CDC
- Batch vs low-latency
- Async vs Sync
- Streaming vs Batch
- Replication vs semantic integration
- Canonical model vs pairwise formats
- Point-to-point vs Hub
- Publish-subscribe vs direct access
- Tight vs Loose coupling
- Orchestration vs Process Controls
- EAI vs direct DB access
- ESB vs SOA/CEP
- SOA vs API
- CEP vs message routing
- Virtualization vs physical integration / warehouse
- DaaS vs Database-as-a-Service
- iPaaS vs on-prem middleware
- Discovery vs Profiling
- Lineage vs Mapping
- Profiling vs documentation assumptions
- Architecture vs tool selection
- Reuse vs duplicate services
- Migration vs simple copy
- Publication vs Migration
- Sharing Agreement vs technical spec
- Forward vs Backward lineage
- output count vs DII value metrics
Artifact 08 remains empty until these tags are backed by real performance patterns.
← Answers 043–056 · Teach-Back →