KStream & KTable — Concept Check
Questions on KStream & KTable. KStream represents an unbounded event log; KTable represents a changelog-backed materialised view (latest value per key); GlobalKTable replicates fully to every instance.
Questions in this quiz
8 questions on KStream & KTable — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.You have a KStream of order events and a KTable of user profiles. What happens when you join them?
- AOnly the first order event is enriched.
- BEach order event is enriched with the current user profile.
- CThe join creates a new KTable with combined data.
- DOrder events are stored as the latest user profile.
2.A developer uses a GlobalKTable for product data. What is a key advantage of this approach?
- ALower memory usage per instance.
- BFaster write operations.
- CAutomatic scaling with data size.
- DNo need for co-partitioning with the stream.
3.What transformation would you use to log each order event without modifying it?
- Abranch
- Bfilter
- CmapValues
- Dpeek
4.In a KStream-KStream join, what is required to correlate the events?
- AA changelog topic for fault tolerance.
- BCo-partitioning of streams.
- CA time window for matching events.
- DA GlobalKTable for reference data.
5.A KTable is backed by which type of store for fault tolerance?
- AKafka topic directly
- BIn-memory cache
- CRocksDB state store
- DGlobalKTable
6.Why might you choose a GlobalKTable over a KTable for small reference data?
- AAutomatic data sharding.
- BFaster data updates.
- CLower memory requirements.
- DNo co-partitioning needed for joins.
7.Which operation would you use to route valid orders to different topics based on shipping type?
- AmapValues
- Bfilter
- Cbranch
- Dpeek
8.What is a key characteristic of a KStream?
- AProcesses each record independently.
- BBacked by a changelog for fault tolerance.
- CStores the latest value per key.
- DReplicates to every instance.