Two business units already run separate agents: one on Microsoft Agent Framework and another exposed as an MCP tool server. You must compose them into one multi-agent solution without rewriting both from scratch. What is the most appropriate integration approach?
Select an answer to reveal the explanation.
Short Explanation
D matches the blueprint literally: integrate existing agents into a multi-agent solution securely using Agent2Agent (A2A) and/or MCP. That preserves investment and enforces protocol boundaries for auth and contracts. A monolith rewrite throws away boundaries. B dual UI is not integration. C spreadsheets are not agents. When the stem says “already run separate agents,” think A2A/MCP composition, not greenfield rewrite.
Full Explanation
Correct Answer — D
Secure integration of existing agents uses Agent2Agent (A2A) and/or MCP so heterogeneous agents participate in one solution without full rewrites, preserving runtime boundaries and contracts.
Why A is wrong: Monolith merges discard protocol boundaries and increase risk.
Why B is wrong: Manual dual-UI composition is not a multi-agent solution.
Why C is wrong: Prompt spreadsheets are not executable agent integration.
Exam tip: A2A and MCP are the named interoperability paths on AI-500.