A consultant is advising a customer that wants a scalable implementation. For IBM Certified watsonx Governance Lifecycle Advisor, the topic is model lifecycle tracking. What should the team do?

Here's the deal: think of model lifecycle tracking like labeling the cables before you close the rack door. If you skip that discipline, troubleshooting gets ugly fast. In this scenario, answer A is the practical move because it keeps the implementation tied to the real IBM capability instead of chasing a shortcut. The other choices sound tempting, but they either skip governance, ignore operational reality, or solve the wrong problem.

The correct answer is A. Track models and generative AI assets from intake through development, validation, deployment, monitoring, and retirement. That aligns with the 2.0 AI Lifecycle Governance objective because it applies the feature or practice in the context where IBM expects a practitioner to use it. It also keeps the design reviewable, supportable, and realistic for a production environment.

Let's examine why the other options are incorrect: - Option B is incorrect because it narrows the solution to one artifact or metric and misses the broader model lifecycle tracking requirement. - Option C is incorrect because it sounds related, but it does not solve the model lifecycle tracking requirement described in the scenario. - Option D is incorrect because it removes visibility or governance at the exact point where the team needs it most. For the exam, connect the feature to the operational outcome: the right answer is the one that preserves control, accuracy, and maintainability instead of relying on a brittle shortcut. The incorrect options — such as 'Start tracking only after production release' and 'Track code repositories but not use cases' — describe either out-of-sequence steps or unrelated configuration tasks. This concept falls under the 2.0 AI Lifecycle Governance domain of the IBM watsonx.governance certification.