Contoso acquired a partner that already runs a warranty specialist agent. Your orchestrator is on Microsoft Foundry. You must integrate the external agent without sharing long-lived secrets in prompts and without reimplementing warranty logic. Which approach is best?
Select an answer to reveal the explanation.
Short Explanation
Reuse the specialist through standard interoperability — A2A and/or MCP — with real auth and least privilege, not by stealing prompts or databases. Option D. Prompt cloning (A) forks logic and loses partner updates. Sharing DB creds (B) bypasses the agent boundary. UI scraping (C) is fragile and often non-compliant.
Full Explanation
Exam skills explicitly include integrating existing agents using A2A and/or MCP securely. Option D preserves the partner agent as a capability endpoint with discovery and auth.
Option A creates drift and maintenance debt.
Option B violates secure integration and encapsulation.
Option C is brittle automation, not a supported agent protocol strategy.
Establish mutual authentication, scoped tokens, timeouts, and tool/result validation on the boundary.
Exam tip: Prefer protocol integration of existing agents over reimplementation or UI scraping.