何よりもまず、国際市場のさまざまな国の人々のさまざまなニーズに応えるために、このWebサイトで1z0-1157-26学習質問の3種類のバージョンを用意しました。第二に、1z0-1157-26実践教材の支払い後、年間を通じて当社から最新のトレーニング教材を無料で入手できることを保証できます。最後になりましたが、私たちは週7日、1日24時間でお客様に最も思いやりのあるアフターサービスを提供します。
| Section | Objectives |
|---|---|
| Topic 1: LangChain for AI Agents | - LangChain fundamentals
|
| Topic 2: Agentic AI for Oracle AI Database | - Oracle AI Database agentic AI capabilities
|
| Topic 3: OCI Enterprise AI Agents | - OCI Enterprise AI platform
|
| Topic 4: Introduction to AI Agents | - AI agent fundamentals and architecture
|
| Topic 5: OpenAI Responses API and Agents SDK | - OpenAI agent development
|
| Topic 6: Introduction to MCP | - Model Context Protocol fundamentals
|
ShikenPASSはOracle試験問題集を提供するウエブダイトで、ここによく分かります。最もよくて最新で資料を提供いたします。こうして、君は安心で1z0-1157-26試験の準備を行ってください。弊社の資料を使って、１００％に合格を保証いたします。もし合格しないと、われは全額で返金いたします。
質問 # 27
From the LLM's perspective, what is consistent between MCP-served tools and locally defined tools?
正解：B
解説：
MCP standardizes how external systems expose capabilities to an AI application, but the model does not need to reason about the transport or deployment location of each capability. Once an MCP server's tools are discovered and incorporated into an agent's available tool set, they are represented to the model as callable tools with names, descriptions, and input schemas. Locally implemented function tools are presented through essentially the same model-facing tool abstraction. OpenAI's Agents SDK documentation explicitly states that tools obtained from configured MCP servers are added to the agent's list of available tools, alongside ordinary tools. Therefore, from the LLM's perspective, both are selected and invoked through the tool-calling mechanism rather than through separate network-specific interfaces.
Authentication, network connectivity, server lifecycle, authorization, and actual execution remain responsibilities of the application/MCP infrastructure. They are deliberately abstracted away from the model.
Therefore, option B precisely captures the architectural consistency described in the course question.
Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals - MCP tools, tool discovery, agent tool abstraction, and client-server integration.
質問 # 28
Which three model categories are available through OCI Enterprise AI Models?
正解：D
解説：
OCI Enterprise AI Models provides managed foundation-model capabilities oriented around three principal inference tasks: Chat, Embeddings, and Rerank . Chat models generate conversational or instructional responses and form the reasoning/generation foundation for many agentic applications. Embed models transform text or other supported content into numerical vector representations, enabling semantic search, recommendations, clustering, classification, and retrieval-augmented generation. Rerank models take an initial collection of retrieved candidates and reorder them according to relevance to a query, improving retrieval quality before selected context is passed to a generative model.
Oracle's current OCI Generative AI documentation explicitly identifies Chat, Embeddings, and Rerank as core Enterprise AI Model tasks. Robotics is not one of the defined Enterprise AI model categories, while clustering and classification are applications of embeddings rather than independent model categories. SQL, NoSQL, and Graph describe database technologies rather than generative-model classes.
The uploaded question source also identifies the Chat/Embed/Rerank combination as the correct selection.
Study Guide reference/topic: OCI Enterprise AI Agents - Enterprise AI Models, chat inference, embeddings, reranking, and model-supported agent workflows.
質問 # 29
What is short-term memory compaction in OCI Enterprise AI Agents?
正解：A
解説：
Short-term memory compaction is a mechanism for reducing an expanding conversation history into a smaller retained representation while preserving the important information needed for subsequent turns. The uploaded source characterizes this as a summarization process for long conversations , making B the intended answer.
Oracle's current OCI Generative AI documentation states that when conversation compaction is enabled, earlier chat history is automatically condensed as a conversation grows. The purpose is to retain relevant context while lowering token usage and reducing latency. The application can continue using the same conversation ID without manually rebuilding the condensed history.
Conceptually, compaction prevents long-running conversations from continually accumulating every earlier turn verbatim. Instead, previous material is compressed into a more concise memory representation that can still inform future model calls. This is a context-management feature rather than a security masking mechanism.
It also has nothing to do with optimizing Python tool execution or improving network routing. Those belong to separate runtime and infrastructure concerns.
Therefore, B is correct.
Study Guide reference/topic: OCI Enterprise AI Agents - Conversations API, short-term memory, conversation compaction, context retention, token optimization, and latency management.
質問 # 30
According to the MCP architecture model, which statement describes the client-server relationship?
正解：D
解説：
MCP follows a host-client-server architecture in which the host creates an MCP client for each MCP server it connects to. The official architecture specifies that each MCP client maintains a dedicated connection with its corresponding MCP server . A host connecting to several servers therefore normally manages several MCP client instances rather than multiplexing all servers through one shared client connection. MCP also does not require clients and servers to reside on different machines. STDIO-based servers commonly execute locally, while Streamable HTTP supports remotely deployed servers. Likewise, a remote MCP server can serve many MCP clients, so a server is not permanently restricted to one client. This client-server separation is particularly relevant to OCI Enterprise AI Agents because MCP Calling enables OCI agent workflows to consume capabilities exposed by remote MCP servers through a standardized integration model.
質問 # 31
In JSON-RPC 2.0, what is the difference between a request and a notification?
正解：D
解説：
The defining distinction is the presence of a request identifier and the expectation of a corresponding response. In JSON-RPC 2.0, a normal request contains an id value so that the sender can correlate the response with the request. A notification deliberately omits the ID because no response is expected. The supplied course material identifies exactly this distinction.
MCP uses JSON-RPC 2.0 as its underlying messaging protocol. Its architecture documentation explicitly states that clients and servers exchange requests and responses, while notifications are used where no response is required. MCP's notification examples contain no id field, and the documentation explains that this follows JSON-RPC notification semantics.
The difference has nothing to do with whether data is structured, whether encryption is enabled, or which transport is used. Both requests and notifications can carry structured JSON parameters. Security belongs to the transport/authentication layer, while MCP can transmit JSON-RPC messages over supported transports such as STDIO or Streamable HTTP.
Therefore, B is the precise protocol-level distinction.
Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals - JSON-RPC 2.0 requests, responses, IDs, and notifications.
質問 # 32
......
Oracle人が職場や学校で高い生産性を備えている場合、最終的に1z0-1157-26試験で成功することは避けられません。あなたもそう。 1z0-1157-26の実際の試験を購入するお客様との永続的かつ持続可能な協力関係があります。学習プロセス中の知識のギャップを埋めるために1z0-1157-26学習教材を改修および更新し、1z0-1157-26試験の自信と成功率を高めるように最善を尽くします。
1z0-1157-26日本語版参考書: https://www.shikenpass.com/1z0-1157-26-shiken.html