lock_openFree sampleFundamentals of AI and MLmedium
A logistics company trains a demand forecasting model and then deploys it as a REST API endpoint behind a load balancer. Six months later, a newly hired engineer rewrites the data pre-processing pipeline, causing feature values to be computed differently from how they were computed during training. The model begins producing erratic forecasts. This situation exemplifies which ML lifecycle challenge?
- ATraining-serving skew, where the features supplied to the model during inference differ from those seen during training due to inconsistent pre-processing.check_circle Correct
- BConcept drift, where the relationship between demand signals and actual order volumes has changed in the market since the model was trained.
- CModel decay, where the statistical patterns learned during training become less relevant as new products and routes are introduced over time.
- DOverfitting, where the model memorised noise in the original training data and now fails to generalise to slightly different feature values.
Identify training-serving skew as the lifecycle challenge arising when inference-time feature computation differs from training-time feature computation. Training-serving skew is a deployment and monitoring concern in the ML lifecycle. It arises when the code path used to compute features at inference time diverges from the code path used during training, even when the raw input data is comparable. The model was optimised for a specific feature representation; any discrepancy causes the model to operate outside its training distribution. Preventing training-serving skew requires shared, versioned feature transformation code used in both training pipelines and serving systems.
Why A is correct: Correct. Training-serving skew occurs when the transformation applied to raw inputs at inference time diverges from the transformation applied during training. Even though the underlying raw data is similar, the model receives feature values outside its training distribution, producing unreliable outputs. This is a recurring operational challenge in the deployment and monitoring phase of the ML lifecycle.
Why B is wrong: Tempting because concept drift also causes previously accurate models to produce erratic forecasts, and it is a legitimate post-deployment risk. However, concept drift is a gradual market or environmental change, whereas the described problem began immediately after a specific code change. The direct causal link to the pipeline rewrite points to training-serving skew rather than an external distribution shift.
Why C is wrong: Tempting because model decay describes a temporal degradation that is common in logistics forecasting as the product catalogue and route network evolves. However, model decay is a slow process driven by real-world changes, not an immediate effect triggered by a code change in the pre-processing pipeline.
Why D is wrong: Tempting because overfitting does cause sensitivity to input variation, but overfitting is a training-phase problem that would have been visible in validation metrics before deployment. The scenario describes a model that performed well for six months before a specific pipeline change, which rules out pre-existing overfitting as the explanation.