1. Stream Processing Frameworks advanced

    A Flink job checkpoints every 60 seconds. State has grown so that one checkpoint now takes 90 seconds to complete. No configuration changes. What happens over the next hour, and which metric will not show it?

    3 min answer flinkcheckpointingbackpressurestate
  2. Stream Processing Frameworks advanced Multiple choice

    A keyed aggregation holds about 2 TB of state across 48 task slots on a heap state backend with 64 GB of heap per task manager. Checkpoints take 11 minutes and the job dies with multi-second garbage-collection pauses about once a day. Throughput is within target. Which change addresses the actual constraint?

    3 min answer flinkstate-backendrocksdbcheckpointing
  3. Stream Processing Frameworks intermediate Multiple choice

    A team must join an order stream keyed by order id to a payment stream that carries order id but is keyed by payment id, with 12 partitions on one topic and 48 on the other, matching within seven days and with a standing requirement to reprocess the last 30 days after a logic fix. Which runtime fits and what is the deciding property?

    3 min answer flinkkafka streamscopartitioningstate
  4. Stream Processing Frameworks beginner

    A team runs 400 events per second through a pipeline with Kafka Streams for routing, Flink for windowed aggregation and a Spark job for a nightly correction pass, maintained by four engineers. Two of the three have had production incidents this quarter. What would you remove, what would you keep, and what would you leave alone even though it looks odd?

    3 min answer simplificationoperational costframework choiceright-sizing
  5. Stream Processing Frameworks advanced

    What justifies a stream processing framework over a simple consumer loop?

    2 min answer streamingstatewatermarkscheckpointing
  6. Stream Processing Frameworks advanced

    What should drive the choice of stream processing framework for a high-volume recommendation platform?

    2 min answer frameworksstateexactly-onceoperability