A customer asks a consultant which single practice would most undermine a scalable lifecycle-tracking programme. Which practice is it?
Select an answer to reveal the explanation.
Short Explanation
Code without the use case is half a record—you can see what was built but not what it was for or who is accountable. If you track only repositories, you miss the business owner, purpose, and risk classification.
Full Explanation
Tracking source-code repositories for each model while leaving the business use cases they support untracked is the most undermining practice. The use case carries the business owner, purpose and risk classification; tracking only the repository leaves governance blind to those, even though the code itself is fully versioned. Assigning a named owner to each model at the point of intake is incorrect because it is a governance strength, not a weakness. Recording validation results before a model is approved for deployment is incorrect because it is exactly what the lifecycle is meant to capture. Logging monitoring alerts against the model that triggered them is incorrect because it is good practice, not a gap. For the exam, remember that code and use-case metadata must both be tracked; neither substitutes for the other.