Your team must expose internal order-status and inventory operations to several Foundry agents through a standard tool protocol. Operations should run as scalable Azure compute with existing API backends. Which approach best builds the tool ecosystem?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: B. Building tool ecosystems with MCP servers/clients—including Azure Functions, Logic Apps, and API Management—is a core develop skill. HTML scraping (A), human email tools (C), and SQL-in-prompt (D) are insecure and non-standard. MCP gives schema’d tools, auth boundaries, and reusable integration.
Full Explanation
AI-500 expects candidates to design and build MCP servers and clients, including Azure Functions, Logic Apps, and Azure API Management. MCP standardizes tool discovery and invocation for multi-agent hosts. Implement authenticated, least-privilege backends; validate inputs; return structured results. Option A is brittle and unsafe. Option C reintroduces manual latency. Option D exposes data planes and invites injection. Front existing order APIs with MCP tool definitions, apply APIM policies where appropriate, and document tool scopes for each agent’s allowlist.