A team is preparing a production rollout and needs to avoid a design mistake. What is the best way to handle use case intake while staying aligned with the certification objectives?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Use case intake is like onboarding a new employee: if you collect only their name and skip department, manager, and access needs, the first day is chaos. Option A is the complete onboarding checklist: purpose, owner, context, data, model type, risk, and intended users — all at intake. Name-only registration is a badge with no role. Waiting to discover ownership at launch is hiring someone with no manager. Skipping intended use because the model is reusable is handing out all-access badges to a shared identity. Complete, upfront intake — 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.