Your team will publish a read-only inventory lookup tool to many agents. Security wants centralized auth, throttling, and versioning. Which implementation aligns with MCP server design on Azure?
Select an answer to reveal the explanation.
Short Explanation
A matches the skill: design and build MCP servers and clients using Azure Functions, Logic Apps, and Azure API Management. Functions (or similar compute) implement the tool logic; APIM fronts auth, throttling, and versioning; agents connect as MCP clients. B shared unsigned scripts are not a governed tool plane. C anonymous blob dumps lack auth and query semantics. D SQL strings in images skip protocol benefits and leak secrets. For AI-500 develop items, MCP + Azure integration services is the expected pattern for enterprise tool publishing.
Full Explanation
Correct Answer — A
MCP server design commonly uses Azure Functions (or comparable hosts) with Azure API Management for authentication, throttling, and versioning, enabling many agent clients to consume a governed tool.
Why B is wrong: Shared scripts lack centralized control, auth, and protocol structure.
Why C is wrong: Anonymous blobs do not provide secured tool invocation or throttling.
Why D is wrong: Connection strings in images and no MCP undermines security and reuse.
Exam tip: APIM + Functions is a frequent exam-friendly MCP hosting shape.