Kuiz berkaitan panduan · Sederhana Tahap

Backfilling Features and Training Data Quiz

Tests understanding of why backfills matter, point-in-time correctness during recomputation, and raw data retention requirements.

Laluan panduan yang berkaitanBackfilling Features And Training Data
soalan 1 daripada 8

Bilakah pengisian semula boleh membantu selepas takrifan ciri berubah?

Pratonton setiap soalan8 soalan

Jawapan dan penjelasan muncul semasa anda mengambil kuiz.

  1. Bilakah pengisian semula boleh membantu selepas takrifan ciri berubah?
    • When historical training examples need a consistent, intentionally updated feature definition
    • Whenever any code changes, regardless of model use
    • Only after deleting all raw data
    • To make every feature timestamp equal to the current time
  2. Apakah yang berlaku jika model dilatih pada data di mana sesetengah rekod menggunakan takrifan ciri lama dan yang lain menggunakan takrifan baharu, tanpa pengisian semula?
    • The model performs identically regardless
    • The model learns from an unlabeled shift in what the feature means, behaving like noise or bias tied to record age
    • The training pipeline automatically detects and fixes the inconsistency
    • Nothing changes since feature definitions never affect training
  3. Apakah data yang diperlukan untuk mengira semula ciri sejarah dari awal selepas logiknya berubah?
    • A GPU cluster
    • A feature that has never changed
    • Retained source events or other input data with enough detail for the recomputation
    • Only the most recent feature values, without any raw event history
  4. Mengapa pengisian semula (backfill) mesti mengekalkan semantik masa peristiwa (event-time) yang sama seperti pengiraan asal?
    • Because otherwise the file format would be incompatible
    • So Kafka can process the data faster
    • Event-time semantics don't need to be preserved
    • So the backfilled value doesn't use future data unavailable at that historical timestamp, preserving point-in-time correctness
  5. Adakah setiap perubahan definisi ciri patut mencetuskan pengisian semula sejarah penuh secara automatik?
    • No; choose the affected history based on the new definition, training window, and serving needs
    • Yes, even when the model never uses the feature
    • Yes, and overwrite all prior versions immediately
    • No, historical features should never be recomputed
  6. How can a team make a feature backfill auditable and traceable to a specific definition?
    • By deleting all previous feature definitions
    • Record the feature-code/config version and write the result to a versioned output or partition
    • By preventing any changes to feature logic
    • By requiring manual re-entry of all historical data
  7. Why can rebuilding a streaming feature from historical data require careful validation?
    • Streaming features cannot be backfilled under any circumstances
    • Streaming and batch features always use the same code automatically
    • Replay and batch paths can differ in ordering, late-event handling, or implementation, so compare them against intended historical semantics
    • Kafka does not support historical data of any kind
  8. What should teams balance when setting raw-data retention for future backfills?
    • Deleting raw events immediately after aggregation to save space
    • Ignoring retention policies entirely
    • Storing only aggregated values and discarding all raw events by default
    • The history needed for planned recomputations against privacy, deletion, security, and contractual limits