Maps 01–05
Map 1 — Chapter 14 operating spine
Recall: BUSINESS NEED → SOURCES → INGEST + METADATA → DQ/ALIGN → HYPOTHESIS/MODEL → TRAIN/EVALUATE → COMMUNICATE → DEPLOY/MONITOR → NEW QUESTIONS.
Meaning: technology sits inside a managed learning loop.
Rebuild: draw nine stages and circle Metadata, DQ, Governance, Security as spanning controls.
Answer check: algorithm is not first; deployment is not last.
Source: pp. 471–476, 484–491.
Map 2 — Analytics horizon
Recall: DESCRIPTIVE → PREDICTIVE → PRESCRIPTIVE.
Meaning: what/why happened → what likely happens → what action should influence outcome.
Rebuild: three columns: question, time orientation, example output.
Answer check: churn probability ≠ retention recommendation.
Source: pp. 474–475, 481–482.
Map 3 — Six-V diagnostic wheel
Recall: VOLUME | VELOCITY | VARIETY | VISCOSITY | VOLATILITY | VERACITY → MANAGEMENT RESPONSE.
Rebuild: Big Data in center; one spoke per V plus its operational implication.
Answer check: scale, speed, forms, integration difficulty, useful life, trust.
Source: pp. 476–477.
Map 4 — ETL vs ELT
Recall: DW: EXTRACT → TRANSFORM/INTEGRATE → LOAD | BIG DATA: EXTRACT → LOAD/INGEST → TRANSFORM/INTEGRATE FOR USE.
Meaning: the distinction is timing of integration.
Answer check: ELT moves transformation later; it does not erase it.
Source: pp. 471–472, 476–478.
Map 5 — Lake control loop
Recall: SOURCE → INGEST → CATALOG/METADATA → PROFILE/DQ → RELATE/KEY → ACCESS/ANALYZE → RETAIN/REVIEW; remove controls → SWAMP.
Meaning: flexible storage remains usable only with context/control.
Answer check: Metadata/provenance and DQ must appear.
Source: pp. 478–480, 499–500.