An administrator is troubleshooting a pilot deployment and wants the most appropriate next step. The team is focused on model lifecycle tracking. Which recommendation is most appropriate?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Model lifecycle tracking is like a pharmaceutical chain of custody: every step from raw ingredient to dispensed pill is logged — you cannot just start tracking at the pharmacy counter. Option A is the complete chain: intake through development, validation, deployment, monitoring, and retirement. Production-start tracking misses the whole development story. Code-only tracking ignores the governance use case. Deleting records post-approval creates a gap that will fail an audit. End-to-end lifecycle tracking — 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.