Question 360
After an input schema migration, the monitor fails because it compares old and new features with different types. What should be updated?
Explanation
Correct Answer
A monitor needs comparable feature definitions; type changes can invalidate distribution calculations independently of model quality.
Incorrect Answers
Choose a seasonally appropriate reference baseline and comparison window. It addresses another case: A monitoring job compares today's holiday shopping traffic against last month's regular weekday transactions and reports large drift. For that case, the distinguishing justification or acceptance check is: Reference selection affects drift meaning; normal seasonal patterns can appear anomalous against an unrepresentative comparison period. The present case instead states: After an input schema migration, the monitor fails because it compares old and new features with different types. It calls for Version the monitoring input schema and rebuild compatible feature mappings. Showing success for the other case would not establish: A monitor needs comparable feature definitions; type changes can invalidate distribution calculations independently of model quality.
The alternative, Prioritize important model features or an approved subset in drift analysis, belongs to a different technical condition: A drift alert fires on a low-value free-text field, but operators care about the top predictive features. There the source-specific mechanism or proof is: Feature-focused monitoring directs attention toward changes with greater potential influence on model behavior. The condition asked about here is: After an input schema migration, the monitor fails because it compares old and new features with different types. A suitable correction is Version the monitoring input schema and rebuild compatible feature mappings; the targeted justification or result is: A monitor needs comparable feature definitions; type changes can invalidate distribution calculations independently of model quality.
Configure alert notifications and an escalation owner for threshold breaches. That operation would be relevant if: A drift monitor detects a large shift but the platform team has not configured any alert recipient. Its corresponding reason or verification is: Monitoring results must reach accountable operators before they can trigger investigation or approved retraining. However the problem in this question is: After an input schema migration, the monitor fails because it compares old and new features with different types. The requirement instead calls for Version the monitoring input schema and rebuild compatible feature mappings; the question-specific check is: A monitor needs comparable feature definitions; type changes can invalidate distribution calculations independently of model quality.