A financial services firm needs to apply a proprietary internal risk classification system (Low/Medium/High/Critical) alongside standard watsonx.governance risk levels. Which feature supports this requirement?
Select an answer to reveal the explanation.
Short Explanation and Infographic
It's like a compliance officer reviewing contracts — they check every clause against the rulebook. watsonx.governance supports custom risk taxonomies enabling organizations to define proprietary risk classification systems that reflect their internal governance frameworks, industry-specific regulations, or board-mandated risk tiers. This custom taxonomy can be applied at the use case level alongside or in place of standard built-in risk categories and is stored as part of the governance record available for audit review.
Full explanation below image
Full Explanation
watsonx.governance supports custom risk taxonomies enabling organizations to define proprietary risk classification systems that reflect their internal governance frameworks, industry-specific regulations, or board-mandated risk tiers. This custom taxonomy can be applied at the use case level alongside or in place of standard built-in risk categories and is stored as part of the governance record available for audit review. The incorrect options — such as 'Overriding the platform's risk framework via a configuration YAML file uploaded to COS' and 'Creating a separate external risk register and linking it via URL in the Factsheet' — describe either out-of-sequence steps or unrelated configuration tasks. This concept falls under the 5.0 Define and Govern AI Use Case Inventory domain of the IBM watsonx.governance certification.