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. You keep the partner agent as a capability endpoint instead of cloning its prompts, exposing its database, or scraping its UI.
Full Explanation
Exam skills explicitly include integrating existing agents using A2A and/or MCP securely. Integrating the existing agent securely via Agent2Agent (A2A) and/or MCP with authenticated endpoints, least-privilege scopes, and explicit capability discovery rather than re-building warranty logic preserves the partner agent as a capability endpoint with discovery and auth. Copying prompts creates drift and maintenance debt. Exposing database credentials violates secure integration and encapsulation. Scraping the web chat UI 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.