A customer wants a scalable AI use case inventory across dozens of projects. What role structure should the consultant recommend to keep the inventory trustworthy?
Select an answer to reveal the explanation.
Short Explanation
When you scale an AI inventory, don’t blur accountability. You need a named owner and reviewer for each entry so updates, decisions, and remediation stay current for that specific use case.
Full Explanation
Named owners and reviewers per entry keep accountability specific and traceable even as the number of use cases grows. The single central team that owns every entry across all projects is incorrect because a distant central team lacks the context to make timely updates and decisions for use cases it did not build. Treating the inventory as a passive report with no formal ownership is incorrect because it removes the accountability that makes it useful. Rotating ownership assigned at random each quarter to spread the workload is incorrect because random rotation breaks continuity and means no one develops real familiarity with a given use case. For the exam, scale the number of accountable pairs with the number of use cases, not the other way around.