Bài kiểm tra có liên kết hướng dẫn · Trung bình Cấp độ
Tính năng chèn lấp và bài kiểm tra dữ liệu đào tạo
Kiểm tra sự hiểu biết về lý do tại sao việc chèn lấp lại quan trọng, tính chính xác tại từng thời điểm trong quá trình tính toán lại và các yêu cầu lưu giữ dữ liệu thô.
Câu hỏi 1 của 8
When can a backfill help after a feature definition changes?
Xem trước mọi câu hỏi8 câu hỏi
Câu trả lời và giải thích xuất hiện khi bạn làm bài kiểm tra.
- When can a backfill help after a feature definition changes?
- 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
- What happens if a model trains on data where some records use an old feature definition and others use a new one, without backfilling?
- 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
- What data is needed to recompute a historical feature from scratch after its logic changes?
- 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
- Why must a backfill preserve the same event-time semantics as the original computation?
- 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
- Should every feature-definition change automatically trigger a full-history backfill?
- 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
- 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
- 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
- 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