Guide-linked quiz · Hard Level

Streaming Features with Kafka and Flink Quiz

Understand Kafka’s role, event time and watermarks, late-data handling, Flink checkpoints, and the limits of exactly-once guarantees.

Question 1 of 8

What role does Apache Kafka play in a streaming feature pipeline?

Preview every question8 questions

Answers and explanations appear as you take the quiz.

  1. What role does Apache Kafka play in a streaming feature pipeline?
    • It acts as a durable event log, with record ordering guaranteed within each partition
    • It trains the machine learning model directly
    • It stores the final trained feature store snapshot
    • It replaces the need for any stream-processing engine
  2. How do tumbling and sliding windows differ?
    • Sliding windows only work with Kafka, tumbling windows only work with Flink
    • Tumbling windows divide time into fixed, non-overlapping intervals; sliding windows compute a continuously updating rolling aggregation
    • Tumbling windows never expire; sliding windows expire every second
    • There is no meaningful difference between them
  3. Why would a fraud model asking how many transactions occurred in the trailing 10 minutes typically use a sliding window rather than tumbling?
    • Sliding windows are always faster to compute
    • Tumbling windows cannot count transactions
    • Because it needs a continuously updating rolling count rather than a fixed periodic bucket
    • Sliding windows use less memory in every case
  4. What problem do Flink's watermarks address?
    • Compressing event data to save storage
    • Encrypting events in transit between Kafka and Flink
    • Choosing which Kafka topic to read from
    • Estimating how far behind in event time the stream has progressed, to handle late-arriving events
  5. What can happen to an event-time window record that arrives after the configured allowed-lateness period?
    • It is dropped from that window or routed to a configured late-data side output
    • Memory usage increases without bound
    • Kafka stops accepting new events
    • Windows never finalize their results
  6. Which resource tradeoff can result from a long allowed-lateness period for an event-time window?
    • Late events are dropped immediately
    • Window state is retained longer so late records can revise results, using more state
    • Kafka partitions are automatically rebalanced
    • The feature store stops updating entirely
  7. According to the guide, what is required for end-to-end exactly-once stream output?
    • Only a Flink checkpoint, regardless of the sink
    • A high watermark setting by itself
    • A checkpointed/replayable source and a sink that participates in compatible exactly-once or idempotent handling
    • Disabling event timestamps
  8. What does the guide identify as a common misconception about streaming features?
    • That streaming features are always less accurate than batch features
    • That Kafka cannot be used for feature engineering
    • That Flink requires a relational database to function
    • That they are simply batch, but faster, when streaming introduces distinct correctness concerns like out-of-order handling

Keep testing yourself

More quizzes picked for your level.

View all quizzes