Govern the design and build of an AI system by defining the business context, performing impact assessments, applying ethical considerations, and documenting the process for compliance and risk management.

A retailer is starting to build an agentic AI system that will plan and execute multi-step refund workflows, calling internal tools to issue payments and update records with limited human review. The product owner is eager to begin model selection and prompt engineering. Before any of that, the governance lead insists the team first nail down the business context for the use case. Which task most directly establishes that business context at the design stage?

• AArticulate the business problem the system must solve, the value it is expected to deliver, the decisions and actions it will take, and the constraints and affected parties that bound it.check_circle Correct
• BBenchmark several candidate foundation models on a held-out refund-reasoning dataset so the team can pick the most accurate one before scoping the workflow.
• CDraft the post-deployment monitoring metrics and alert thresholds the operations team will watch once the refund agent is running live in production.
• DWrite the user-facing transparency notice telling customers that an automated system, rather than a human agent, is handling their refund request end to end.

Why A is correct: Defining the problem, expected value, the actions the agentic system will take autonomously, and the constraints and affected parties is exactly what framing the business context means; it sets the purpose and boundaries that every later design and risk decision depends on.

Why B is wrong: Comparative benchmarking is a real and useful activity, but it is model selection, which presupposes the business context is already defined; choosing a model before the problem, value and constraints are framed risks optimising for the wrong objective.

Why C is wrong: Monitoring metrics matter, but they belong to operations once the system is live and cannot be set sensibly until the use case and its objectives are defined; this skips the framing the governance lead is asking for.

Why D is wrong: A transparency notice is a legitimate downstream obligation, but it is a disclosure control that follows from design decisions; it does not establish the business problem, value, or constraints that frame the use case.