A customer wants a scalable way to track dozens of AI initiatives. Why is registering only the model file name insufficient?
Select an answer to reveal the explanation.
Short Explanation
File names tell you which artifact you're looking at, not why it exists or who's accountable for it. You need ownership, business purpose, data touched, and risk to govern AI initiatives.
Full Explanation
A file name identifies an artifact but says nothing about who owns it, what business problem it solves, what data it touches, or how risky its use is. Governance decisions—approving a use case, assessing risk, deciding who signs off—depend on context a file name does not carry. The idea that file names are too long to store reliably in a governance database is wrong because storage length is a non-issue for modern inventory systems. The idea that model artifacts change their file names automatically on every retraining run is wrong because retraining does not typically rename an artifact, and even if it did, that is unrelated to why a name alone is insufficient. The idea that file-name registration is only supported for open-source models, not proprietary ones, is wrong because the limitation applies equally regardless of licensing model. For the exam, remember that an inventory entry needs business context, not just a technical pointer.