Architecture history — Lambda → Kappa → lakehouse → streamhouse

From your world. Your current batch lakehouse: where a streamhouse would and would not change it

Practice quiz with instant feedback. For a scored run that counts toward your local progress, use uv run de quiz STH-01.

1What is the defining structural feature of a Lambda architecture? AA single streaming pipeline that replays a log to reprocess history BTwo parallel pipelines (a batch recompute layer and a low-latency speed layer) merged at serving time CA single transactional lake table queried by SQL at batch latency DA stream-native storage layer that serves both streaming and batch reads

4A platform stores all curated data in Iceberg tables on S3. Athena queries the tables. Spark refreshes them every few minutes. What is this platform, and what is its latency limit? AKappa, limited by log retention BLakehouse, limited to batch/micro-batch (minutes) commit latency CStreamhouse, sub-second DLambda, limited by reconciliation

7Which statements are TRUE about how to classify a real architecture? (choose all) (select all that apply) AYou classify by storage and pipeline shape, not by the vendor's marketing label BTwo parallel pipelines merged at serving indicate Lambda CA stream-native store that serves both streaming and batch reads from one copy indicates a streamhouse DAny system that uses Kafka anywhere is Kappa