Finance requires each business unit to pay for its multi-agent Foundry consumption. Today all agents share one deployment with no attribution, so chargebacks are impossible. What monitoring and management strategy should you design?
Select an answer to reveal the explanation.
Short Explanation
Answer D. Cost strategy for multi-agent solutions covers usage, quotas, allocations, and chargebacks. Tag or otherwise attribute tokens and tool calls to business units, enforce allocations, and report. Shared untagged keys, deleting cost data, and unconstrained usage prevent fair chargeback and FinOps control.
Full Explanation
Correct answer: D. Design cost monitoring and management: usage visibility, quotas, allocations, and chargebacks. Propagate business-unit identifiers into traces and Azure cost tags; optionally isolate deployments or use Azure OpenAI/Foundry quota constructs per unit; alert on anomalies.
A is incorrect: untagged shared keys make accurate chargeback impossible.
B is incorrect: retaining cost telemetry is required for finance reconciliation.
C is incorrect: quotas protect budget and noisy-neighbor effects across multi-agent workloads.
Align chargeback grain with how agents and tools are owned operationally.