Practice — Case Study: Churn Model, End-to-End MLOps (5 questions)
Advanced
Open
Free
Distinguish Genuine Drift From a Pipeline Bug Before Retraining Permalink →
The churn model's prediction-distribution panel shows mean score
drifting from 0.041 to 0.058 over two weeks. No deploys occurred in
that window. Per-feature PSI shows one feature, days_since_last_login,
at 0.42 — far above every other feature.
- Walk through the specific checks you'd run, in order, to determine whether this is genuine population drift or a pipeline bug.
- Your checks reveal that a new mobile app version stopped reporting
last_loginevents for a specific device OS, defaulting the feature to 0 for those users. Which case is this, and what should happen next? - Explain concretely why retraining immediately, before completing this diagnosis, would have been the wrong move.
Share this question
Advanced
Open
Pro
Design a Model-Quality Gate That Would Have Caught a Slice Regression
Unlock this question →
Advanced
Open
Pro
Size a Canary Rollout for a Weekly-Cadence, Financially-Impactful Model
Unlock this question →
Advanced
Open
Pro