A logistics company already runs a mature “shipment tracker” agent in another business unit’s Microsoft Foundry project. A new customer-experience multi-agent solution must securely invoke that existing agent as a collaborator rather than reimplementing tracking logic, using an agent-to-agent interoperability approach. Which integration approach best matches the requirement?
Select an answer to reveal the explanation.
Short Explanation
Reusing an existing agent safely means a real interoperability path—A2A and/or MCP—with secure identity, not prompt copy-paste, leaked keys, or UI scraping. A2A/MCP are the exam-aligned ways to integrate existing agents into a multi-agent solution. D is correct.
Full Explanation
Correct answer: D. Multi-agent development includes integrating existing agents securely using Agent2Agent (A2A) and/or MCP. That preserves a governed interface, authentication, and tool/agent contracts without reimplementation.
A is incorrect because prompt copying does not provide live agent capabilities, version alignment, or secure invocation of the real agent.
B is incorrect because embedding private API keys in client-side code is a severe secret exposure and bypasses proper server-side identity.
C is incorrect because UI scraping is brittle, unsupported, and unsuitable for production agent collaboration.
Exam focus: prefer A2A/MCP for secure agent reuse over informal coupling.