You need a repeatable way for domain experts to score multi-agent runs in Microsoft Foundry before promoting a new orchestrator version. Automated metrics exist but miss subtle policy tone issues. What should you design?
Select an answer to reveal the explanation.
Short Explanation
D is the evaluation strategy you want. Foundry-oriented multi-agent ops pair automated evals with human review for qualities models miss—tone, policy nuance, harmful helpfulness. Sample representative traces, show reviewers the full agent path (prompts, tools, outputs), score with rubrics, and require human + auto gates before promotion. Token dashboards alone are not quality. Customer complaints as sole signal is too late. Turning off tracing blinds both humans and machines. Design human review as a first-class evaluation loop.
Full Explanation
Correct Answer — D
Evaluation strategies for multi-agent solutions include designing and implementing a human review process in Foundry. Structured sampling of traces, rubric-based scoring of multi-agent behavior, and release gates combining human and automated results catch tone and policy issues metrics miss.
Why A is wrong: Token usage is an efficiency metric, not a substitute for quality or policy evaluation.
Why B is wrong: Production-only feedback is slow, customer-harming, and uncontrolled.
Why C is wrong: Tracing is essential for both human review and automated diagnosis; disabling it undermines evaluation.
Exam tip: Human review + rubrics + automated checks = promotion gate in Foundry.