Útmutatóhoz kapcsolódó kvíz · Közepes Szint
Adatminőség-figyelés a termelésben kvíz
A séma, frissesség, hiányosság és vonatkiszolgálási problémák észlelése a következtetések levonása előtt, miközben megkülönbözteti a bemeneti minőséget a modell teljesítményétől.
kérdés 1 -ból 8
What does a schema check detect in a live inference feed?
Tekintse meg az összes kérdést8 kérdéseket
A válaszok és magyarázatok megjelennek a kvíz kitöltésekor.
- What does a schema check detect in a live inference feed?
- Unexpected field names, types or structures
- A guaranteed drop in model accuracy
- A causal change in user behavior
- The model's calibration error
- What does a freshness monitor detect?
- A change in model weights
- Data that have not been updated within the expected time
- A label mismatch in a training batch
- An unexpected prediction class
- How should an unseen categorical value be handled?
- Drop the model silently
- Map it randomly to a known category
- Apply an explicit unknown-category policy and monitor its rate
- Assume the value is always invalid
- Which mismatch is an example of train-serving skew?
- A difference between two model architectures
- A change in GPU memory usage
- A delayed ground-truth label
- A difference between how features are computed in training and inference
- Why can an overly strict distribution threshold cause production issues?
- It guarantees detection of every defect
- Legitimate seasonal changes may trigger false alarms or blocks
- It prevents all schema changes
- It improves model calibration automatically
- What does passing data-quality checks establish?
- The feature relationships are unchanged
- The model is fair across all groups
- Inputs met the configured checks, not that predictions are accurate
- The data are causally valid
- Where might latency-sensitive data checks run?
- In a dashboard without storing results
- All validation only after labels arrive
- Only in the model-training notebook
- Critical schema checks inline, with heavier analysis asynchronously or in batches
- What should a team do when a production data alert fires?
- Trace the source and determine whether the change is expected before updating rules
- Change the schema immediately to silence the alert
- Retrain automatically without checking data
- Delete the alert history