A shared multi-agent Foundry platform serves three business units. Finance demands showback of model and tool spend per unit; one unit is exhausting the shared quota and starving others. What cost-management strategy should you design?
Select an answer to reveal the explanation.
Short Explanation
You need usage metering by business-unit tags or projects, enforced per-unit quotas or allocations, and chargeback or showback reports. That way you can attribute tokens and tool calls, stop the noisy neighbor from consuming the shared pool, and keep other units running.
Full Explanation
The metering, quota, and chargeback/showback strategy is correct. Cost management includes usage tracking, quotas, allocations, and chargebacks. Shared multi-agent platforms need per-business-unit metering, such as tags or projects, enforced allocations, and showback or chargeback reports so one unit cannot starve others. This attributes tokens and tool calls, stops one unit from consuming the shared pool, and constrains noisy neighbors without blocking other units.
Why the single unallocated invoice approach is wrong: unallocated invoices prevent accountability and noisy-neighbor diagnosis.
Why the unlimited deployments approach is wrong: unlimited shared use without quotas creates starvation and bill shock.
Why the disable cost monitoring approach is wrong: production multi-agent platforms require active cost governance; experimental status is not an excuse in shared production.
Exam tip: Meter + quota + chargeback/showback for shared agent platforms.