গাইড লিঙ্ক ক্যুইজ · মাঝারি স্তর
মডেল প্রসঙ্গ প্রোটোকল কুইজ
হোস্ট/ক্লায়েন্ট/সার্ভারের ভূমিকা, সরঞ্জাম এবং সংস্থান, অনুমতি, সক্ষমতা আবিষ্কার, প্রোটোকল সংস্করণ এবং বিশ্বাসের সীমানা পরীক্ষা করে।
প্রশ্ন 1 এর 8
In MCP architecture, what coordinates the user experience and security decisions?
প্রতিটি প্রশ্নের পূর্বরূপ দেখুন8 প্রশ্ন
আপনি কুইজ নেওয়ার সাথে সাথে উত্তর এবং ব্যাখ্যাগুলি উপস্থিত হয়।
- In MCP architecture, what coordinates the user experience and security decisions?
- A resource item
- The server’s prompt template
- The model weights alone
- The host application
- Which MCP capability supplies contextual content rather than performing an operation?
- A resource
- A tool
- A permission grant
- A transport retry
- What does a successful MCP connection establish?
- That the server is certified trustworthy
- That communication works, not that every tool is safe or correct
- That every capability has been authorized for every user
- That the user’s task is complete
- Why inspect a server’s tool descriptions and behavior before allowing write operations?
- Tool names are guaranteed to describe all side effects
- The protocol forbids write operations
- Tools can change external state and require an appropriate permission boundary
- Descriptions automatically enforce user authorization
- What should an application do with instructions embedded in server-returned content?
- Allow them to override authorization
- Convert them into permanent host policy
- Follow them without showing the user
- Treat them as input to evaluate, not authority to expand the user’s request
- Why inspect negotiated capabilities after connecting?
- Hosts and servers may implement different subsets of the specification
- Every host supports every feature identically
- Capability discovery is only cosmetic
- It proves the tool outputs are factually correct
- Which lifecycle checks are relevant to an MCP integration?
- Only whether the server has a logo
- Argument validation, errors, reconnection, and revoked access
- Only the first successful connection
- The color of the host interface
- Why record server and protocol versions?
- Versions guarantee semantic equivalence
- The protocol version stores user secrets
- A version change can affect compatibility and behavior during later investigation
- Version records replace authorization