A consultant is advising a customer that wants a scalable implementation. The team is focused on use case intake. Which recommendation is most appropriate?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Registering only a model file name during intake is like booking a hotel room and leaving the guest name blank — the room exists, but no one is accountable for what happens in it. Option A fills out the full registration: purpose, owner, business context, data, model type, risk, and intended users captured at intake. File-name-only registration leaves everything that matters unrecorded. Late-ownership discovery creates governance gaps. Reusability does not eliminate the need to know intended use. Complete intake metadata from the start — option A!
Full explanation below image
Full Explanation
The correct answer is A. Capture purpose, owner, business context, data, model type, risk, and intended users during intake. aligns directly with the 5.0 Define and Govern AI Use Case Inventory exam objective and reflects how IBM watsonx.governance operationalizes this practice in enterprise environments. IBM watsonx.governance is designed to provide the tooling, workflows, and evidence collection mechanisms that make AI trustworthy and auditable from intake through retirement. Choosing this option ensures the implementation is both defensible to regulators and maintainable by governance teams across the full AI lifecycle. Option B is incorrect because it narrows the scope to a single artifact or metric and misses the full governance requirement. Option C is incorrect because it does not address the core governance requirement described in the scenario and would leave an important control gap in production. Option D is incorrect because it eliminates a required control and leaves the governance program without a critical safeguard. On scenario-based exam questions, the correct answer is consistently the one that operationalizes the IBM governance practice with structured controls rather than approximating it with shortcuts, manual workarounds, or oversimplified rules.