Exam 1z0-1157-26 Topic 1 Question 29 Discussion

In MCP, STDIO is designed for local process-based communication. Under this transport, the host or client application launches the MCP server as a subprocess and exchanges protocol messages through the server's standard input ( stdin ) and standard output ( stdout ). The uploaded examination source identifies this behavior as the correct definition.
STDIO should be contrasted with Streamable HTTP , which is designed for independently running, network- accessible MCP servers and remote communication. STDIO is particularly suitable for local integrations where the MCP server executable can run on the same machine as the host application.
The transport mechanism does not change MCP's underlying message semantics. MCP communication still uses JSON-RPC structures; STDIO does not replace JSON with an unrelated plain-text protocol.
Authentication requirements such as OAuth are also not an inherent requirement of STDIO. OAuth and HTTP-oriented authentication concerns primarily arise in remote server architectures.
Therefore, the defining STDIO behavior is local subprocess execution coupled with stdin/stdout message exchange.
Answer C correctly captures the architecture described by MCP and by the uploaded course source.
Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals - STDIO transport, local MCP servers, subprocess lifecycle, JSON-RPC, and Streamable HTTP comparison.