A team is preparing a production rollout and needs to avoid a design mistake. Which approach best demonstrates model lifecycle tracking in a IBM Certified watsonx Governance Lifecycle Advisor environment?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Tracking a model only after production is like buying a car and skipping the inspection history — you own the vehicle but have no idea what happened before you got the keys. Option A is the full history: track models and generative AI assets from intake through development, validation, deployment, monitoring, and retirement. Post-production-only tracking misses every early-stage decision. Code-repo-only tracking misses use-case context. Deleting records after approval eliminates traceability exactly when you need it most. Full lifecycle tracking from day one — option A!
Full explanation below image
Full Explanation
The correct answer is A. Track models and generative AI assets from intake through development, validation, deployment, monitoring, and retirement. aligns directly with the 2.0 AI Lifecycle Governance 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 does not address the core governance requirement described in the scenario and would leave an important control gap in production. 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.