During a design review, an architect asks which choice best matches the IBM guidance. For IBM Certified watsonx Governance Lifecycle Advisor, the topic is change management. What should the team do?

Here's the deal: this is where a demo turns into an operation. The design has to survive real users, real failures, and real audits. In this scenario, answer D 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 D. Reassess models when data, purpose, version, or risk conditions materially change. 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 A is incorrect because it sounds related, but it does not solve the change management requirement described in the scenario. - Option B is incorrect because it skips the control or validation that makes change management reliable in production. - Option C is incorrect because it narrows the solution to one artifact or metric and misses the broader change management requirement. 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 'Treat approval as permanent' and 'Ignore prompt changes in generative AI systems' — 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.