Your team must expose an internal order-status API to several Foundry agents as standardized tools that multiple orchestrations can reuse. Agents should discover tools consistently, and platform engineers want centralized auth, throttling, and versioning at the edge. Which design best fits Microsoft multi-agent tool ecosystems?
Select an answer to reveal the explanation.
Short Explanation
D is the right design. Model Context Protocol (MCP) is how modern multi-agent stacks standardize tool/server exposure. Azure Functions is a natural host for MCP server logic; Azure API Management sits in front for identity, throttling, and versioning. Agents then use MCP clients rather than bespoke one-off HTTP glue in every prompt. Stuffing keys into prompts is a secrets and rotation nightmare. HTML scraping is brittle. Direct DB access from agents violates least privilege and couples agents to schema. MCP + Functions + APIM is the exam-aligned Azure tool ecosystem pattern.
Full Explanation
Correct Answer — D
Building tool ecosystems for multi-agent solutions includes MCP servers and clients, often implemented with Azure Functions, Logic Apps, and Azure API Management. Publishing an MCP server behind APIM gives reusable discovery and invocation for many agents while centralizing authentication, quotas, and versioning—exactly what platform teams need.
Why A is wrong: Secrets in prompts are insecure, hard to rotate, and not a discoverable tool interface.
Why B is wrong: Portal scraping is fragile and inappropriate when a stable API exists.
Why C is wrong: Direct database credentials expand blast radius and bypass API governance.
Exam tip: MCP for tool standards; APIM for edge auth/throttle/version; Functions (or Logic Apps) for server implementation.