A project lead is turning a proof of concept into a governed production workflow. The team is focused on approval workflow. Which recommendation is most appropriate?

Here's the deal: think of approval workflow like labeling the cables before you close the rack door. If you skip that discipline, troubleshooting gets ugly fast. In this scenario, answer B 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 B. Use structured workflows to review risk, controls, and sign-offs at key lifecycle stages. 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 narrows the solution to one artifact or metric and misses the broader approval workflow requirement. - Option C is incorrect because it sounds related, but it does not solve the approval workflow requirement described in the scenario. - Option D is incorrect because it skips the control or validation that makes approval workflow reliable in production. 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 'Approve through informal email threads only' and 'Let developers self-approve high-risk models' — 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.