What should an AI use-case intake process capture when a new model or system is first registered?
Select an answer to reveal the explanation.
Short Explanation
Intake is the one moment you're guaranteed everyone's attention. You need the whole picture at registration, not bits and pieces later.
Full Explanation
The correct answer is the option that captures purpose, owner, business context, data used, model type, risk level, and intended users together at registration. A use-case inventory only supports governance decisions if each entry answers who owns it, why it exists, what data and model it involves, how risky it is, and who it is for, all captured at the same point in time. The option that records only the model file name and version number is incorrect because a file name identifies an artifact, not a use case; it tells a reviewer nothing about purpose, risk, or accountability. The option that captures business context and data sources but assigns ownership only once the model reaches production is incorrect because deferring ownership leaves the entry unaccountable for the period before launch, which is exactly when early design decisions get made. The option that captures model type and risk level but defers intended use until the system is live is incorrect because intended use shapes the risk assessment itself; skipping it at intake means the risk level recorded is a guess. For the exam, treat intake as a single, complete capture, not a rolling set of fields filled in as convenient.