During a design review, an architect asks which choice best matches the IBM guidance. What is the best way to handle risk classification while staying aligned with the certification objectives?

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 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. Classify use cases by impact, regulation, data sensitivity, automation level, and user population. That aligns with the 5.0 Define and Govern AI Use Case Inventory 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 risk classification requirement. - Option C is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option D is incorrect because it sounds related, but it does not solve the risk classification requirement described in the scenario. 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 'Classify by team size only' and 'Call every internal tool low risk' — 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.