A model approval process requires that any model with an inherent risk score above 80 must receive sign-off from the Chief Risk Officer before advancing to deployment. How does watsonx.governance enforce this routing requirement?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Think of it this way: in real-world AI governance, role-based approval gates in governance workflows that direct high-risk models to designated approvers based on configured risk threshold criteria is exactly what teams reach for when they need to handle this scenario. Role-based approval gates are a core governance workflow component in watsonx. On the exam, remember that this falls squarely under the 2.0 AI Lifecycle Governance domain.
Full explanation below image
Full Explanation
Role-based approval gates are a core governance workflow component in watsonx.governance that enforce mandatory review and sign-off by specific organizational roles before a use case can advance to the next lifecycle stage. Gates can be configured with conditions based on risk scores, model type, or use case characteristics so that only models meeting defined criteria are routed to particular approvers. When a model exceeds the configured risk threshold, the workflow automatically requires CRO approval and prevents advancement to deployment until that approval is explicitly recorded. The correct answer, "Role-based approval gates in governance workflows that direct high-risk models to designated approvers based on configured risk threshold criteria", directly addresses the scenario described because it aligns with the specific governance requirement in question. The incorrect options ("The platform automatically deploys models below the threshold and sends models above it to a manual hold queue without a formal approval step", "An advisory notification is sent to the CRO but the model owner can override and proceed to deployment", "A compliance accelerator override rule suspends the standard workflow and activates a separate high-risk review track") may seem plausible but do not satisfy the core requirement. Understanding the distinction between these concepts is critical for IBM watsonx.governance implementations and is frequently tested in the 2.0 AI Lifecycle Governance section of the certification exam.