A bank has deployed a credit-scoring model that passed validation at launch. Six months later the operations team notices approval rates have shifted, though no code or configuration has changed. Using the NIST AI Risk Management Framework, which function's activities are the team primarily carrying out when they set quantitative thresholds, instrument the live system, and track scoring performance over time to detect this degradation?
- AMAP, because the team is establishing the deployment context and cataloguing the categories of risk that the credit-scoring system could plausibly create in operation.
- BMEASURE, because the team is defining metrics and continuously assessing the deployed model's performance to identify drift and other emergent risks over time. Correct
- CMANAGE, because the team is allocating resources to treat the identified drift and is deciding which mitigation or rollback response to apply first.
- DGOVERN, because the team is enforcing the organisational policies and accountability structures that require credit models to be supervised after launch.
Why A is wrong: MAP is tempting because contextual framing precedes measurement, but MAP establishes context and identifies risks up front rather than continuously quantifying and tracking live performance, which is the activity described.
Why B is correct: MEASURE covers selecting metrics and using quantitative and qualitative methods to assess, analyse and track identified risks of a deployed system, which is exactly the instrumentation and monitoring of scoring performance described.
Why C is wrong: MANAGE is tempting since acting on drift eventually falls here, but it concerns prioritising and responding to risks already measured, not the measurement and tracking step that surfaces the drift.
Why D is wrong: GOVERN is tempting because a monitoring mandate originates in governance, but GOVERN sets the culture, policies and roles that cut across functions rather than performing the live quantitative tracking itself.