গাইড লিঙ্ক ক্যুইজ · কঠিন স্তর
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.
প্রশ্ন 1 এর 8
একটি স্ট্রিমিং বৈশিষ্ট্য পাইপলাইনে Apache Kafka কি ভূমিকা পালন করে?
প্রতিটি প্রশ্নের পূর্বরূপ দেখুন8 প্রশ্ন
আপনি কুইজ নেওয়ার সাথে সাথে উত্তর এবং ব্যাখ্যাগুলি উপস্থিত হয়।
- একটি স্ট্রিমিং বৈশিষ্ট্য পাইপলাইনে Apache Kafka কি ভূমিকা পালন করে?
- 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
- কিভাবে tumbling এবং স্লাইডিং জানালা পৃথক?
- 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
- কেন একটি জালিয়াতি মডেল জিজ্ঞাসা করবে যে 10 মিনিটের মধ্যে কতগুলি লেনদেন হয়েছে?
- 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
- ফ্লিঙ্কের ওয়াটারমার্কগুলি কী সমস্যা সমাধান করে?
- 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
- একটি ইভেন্ট-টাইম উইন্ডো রেকর্ডের কী ঘটতে পারে যা কনফিগার করা অনুমোদিত-লেটনেস পিরিয়ডের পরে আসে?
- 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
- 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
- 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
- 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