Sample question 1 — Design AI-powered business solutions
A solutions architect wants a Copilot Studio agent to read live pricing from a partner's hosted service through an open interoperability standard, without writing a custom connector for every endpoint. Which design choice best fits?
- A. Expose the partner's data through a Model Context Protocol server and connect the agent to it as an extension.
- B. Hard-code the partner's current prices inside the agent's topic so the agent never needs a network call.
- C. Export the partner's prices to a spreadsheet and attach the file to the agent as static knowledge.
- D. Require each endpoint to expose a bespoke REST contract that a developer must wrap in a custom connector.
Answer: A. Option A is correct. The Model Context Protocol (MCP) provides an open interoperability standard for connecting agents to tools and data sources, so a single MCP server exposes the partner's endpoints without a custom connector per endpoint. Option B is incorrect because hard-coded prices go stale the moment the partner changes them. Option C is incorrect because a static spreadsheet does not reflect live pricing. Option D is incorrect because writing a bespoke REST wrapper for every endpoint is exactly the custom-connector burden MCP removes.
