Question 53 — AB-620 Practice Exam 2
For each statement below, indicate whether the answer is True or False
| Item | True | False |
|---|---|---|
| An MCP server owner can update a published tool so that connected Copilot Studio agents receive the changed definition without separate per-agent updates. | □ | □ |
| With connector or REST API actions configured separately for multiple agents, an API change can require updates to each affected agent. | □ | □ |
| A Copilot Studio maker can modify an MCP tool description locally while leaving the MCP server definition unchanged. | □ | □ |
| An MCP server is primarily suited to integrations that require every consuming agent to maintain its own independent copy of each tool definition. | □ | □ |
Correct answers
- An MCP server owner can update a published tool so that connected Copilot Studio agents receive the changed definition without separate per-agent updates. → True
- With connector or REST API actions configured separately for multiple agents, an API change can require updates to each affected agent. → True
- A Copilot Studio maker can modify an MCP tool description locally while leaving the MCP server definition unchanged. → False
- An MCP server is primarily suited to integrations that require every consuming agent to maintain its own independent copy of each tool definition. → False
Explanations
True: MCP supports centralized capability management, so server-side changes to published tools or resources can propagate to connected agents automatically.
True: Individually defined connector or REST API actions can require maintenance in each affected agent when the underlying API changes.
False: MCP tool descriptions are controlled by the server and cannot be edited by the maker inside Copilot Studio.
False: MCP is designed around centrally published capabilities that can be shared across compatible agents rather than duplicated as independent definitions in every agent.
An MCP server owner can update a published tool so that connected Copilot Studio agents receive the changed definition without separate per-agent updates.
With connector or REST API actions configured separately for multiple agents, an API change can require updates to each affected agent.
A Copilot Studio maker can modify an MCP tool description locally while leaving the MCP server definition unchanged.
An MCP server is primarily suited to integrations that require every consuming agent to maintain its own independent copy of each tool definition.