During a design review, an architect asks which choice best matches the IBM guidance. What is the best way to handle approval workflow while staying aligned with the certification objectives?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Think of an AI approval workflow like a building permit process: informal conversations with a city planner do not authorize you to break ground. Option B is the formal permit: structured workflows covering risk review, controls, and sign-offs at key lifecycle checkpoints. Informal email approvals are verbal agreements that evaporate. Developer self-approval is the contractor pulling their own permits. Skipping review for high-accuracy models is assuming a fast car needs no safety inspection. Formal, stage-gated approval workflows — option B!
Full explanation below image
Full Explanation
The correct answer is B. Use structured workflows to review risk, controls, and sign-offs at key lifecycle stages. 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 A is incorrect because it relies on an informal, non-auditable mechanism that cannot support enterprise governance at scale. 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 eliminates a required control and leaves the governance program without a critical safeguard. 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.