An administrator is troubleshooting a pilot deployment and wants the most appropriate next step. For IBM Certified watsonx Governance Lifecycle Advisor, the topic is use case intake. What should the team do?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Intake is where governance begins—it's like a doctor asking thorough questions during a first visit instead of jumping straight to treatment. You need to understand the purpose, who's accountable, what business problem you're solving, what data you're using, what kind of model it is, how risky it is, and who will use it. Just filing away a model name is like logging a patient by their first name only. Good intake sets you up for smart governance decisions down the road!
Full explanation below image
Full Explanation
The correct answer is a. Effective use case intake requires capturing comprehensive context: purpose (what business problem), owner (accountability), business context (strategic alignment), data (sources and characteristics), model type (classification, regression, generative AI, etc.), risk assessment (potential harms), and intended users (who will rely on this). This information forms the foundation for all downstream governance decisions. Option b is inadequate because a model file name alone provides zero governance context; you need business and technical information to assess risk and design appropriate controls. Option c is wrong because waiting until launch means governance decisions are made without full understanding of the use case; intake must happen early when decisions can still be shaped. Option d is incorrect because intended use is critical for risk assessment and control design; a model may be technically reusable but in different contexts requires different governance approaches and monitoring.