A senior engineer reviewing a lifecycle governance plan notices that only the first deployed version of a model is being monitored. What is the risk with this approach?

Monitoring only the first version means later versions can drift in behavior or risk without triggering any reassessment. Governance needs to track behavior and risk across every version actually in production, because a later version can diverge from what was originally approved. The claim that monitoring the first version is sufficient because later versions inherit the same approval automatically is incorrect because approval does not automatically transfer to a changed version without reassessment. The claim that there is no risk, since version numbers are purely administrative labels, is incorrect because version changes typically reflect real changes to the model, not just administrative labeling. The claim that the risk is purely about infrastructure cost, not about behavior or governance, is incorrect because the risk is about ungoverned behavioral drift, not infrastructure spend. For the exam, monitor and reassess each production version, not just the one that first went live.