AIF-C01 Practice Question 33: Model Context Protocol
AWS Certified AI Practitioner (AIF-C01) · Test 4 · question 3 of 10
A company has several teams building AI agents. Each team writes its own custom integration code for the same internal systems, such as the ticketing API and the customer database, so the tools are duplicated, inconsistent, and hard to govern. Every tool change also requires redeploying each agent. What should the company adopt to standardize how its agents discover and call these tools?
Show answer and explanation
Answer:
The Model Context Protocol (MCP) is a universal standard for connecting agents to external capabilities, often described as "USB-C for AI applications". Instead of registering tools directly inside each agent, MCP servers host the tools, and agents discover and invoke them in a standardized way. AWS lists the situations where MCP fits: duplicated tools, developers spending too much time on inconsistent custom integrations, and a need for centralized governance over how agents reach enterprise systems. Because MCP decouples agents from the tools they use, a tool can change without redeploying every agent (option D).
- A is wrong because RAG adds *reference information* to a prompt. Reading about the API doesn't let an agent actually call it, and it does nothing to standardize integrations. - B is wrong because tool definitions consume the context window, and cramming more of them in can degrade the model's performance. It also leaves the duplicated integration code in place. - C is wrong because fine-tuning changes a model's weights. It doesn't give agents a shared, governed way to connect to live systems, and the tools would still be rebuilt by each team.
Reference: What is MCP?