1z0-1157-26 Agentic AI Foundations Associate Questions and Answers

OCI Enterprise AI Agents supports a defined set of OpenAI-compatible agent tools through the OCI Responses API. Oracle's current documentation identifies File Search, Code Interpreter, Function Calling, and MCP Calling as supported tool categories.

File Search allows an agent to retrieve relevant information from indexed content and vector stores. Code Interpreter provides a controlled environment for computational or programmatic analysis. Function Calling lets the model request execution of application-defined functions with structured parameters. MCP Calling enables the agent to discover and invoke capabilities made available by remote Model Context Protocol servers. Together, these mechanisms allow an LLM to move beyond text generation and perform retrieval, computation, application actions, and standardized external-system integration.

Oracle additionally provides supporting agent resources such as Files, Vector Stores, Containers, Conversations, Projects, and memory capabilities, while SQL Search/NL2SQL is available as an OCI-native agent capability.

SSH, FTP, RDP, VCN routing, load balancing, SMS, and fax are not the four built-in tool categories identified in the OCI Enterprise AI Agents curriculum. Consequently, A is correct and agrees with the uploaded question set.

Study Guide reference/topic: OCI Enterprise AI Agents — File Search, Code Interpreter, Function Calling, MCP Calling, Vector Stores, and agent tools.

===============

MCP initialization establishes compatibility between the MCP client and server before normal protocol operations begin. During initialization, the parties establish a mutually supported protocol version and exchange their supported capabilities and implementation information. The client initiates the process with an initialize request containing its protocol version, capabilities, and client information. The server responds with its supported protocol version, capabilities, and server information, after which the client signals that initialization has completed. Authentication is handled at the transport or deployment security layer rather than being the defining initialization exchange. MCP initialization also does not fine-tune the LLM or execute every registered tool. This capability-negotiation process enables OCI agent applications using MCP Calling to understand which remote capabilities can safely be used. Model Context Protocol

===============

MCP uses JSON-RPC 2.0 as the underlying message protocol for communication between MCP clients and MCP servers. JSON-RPC provides a structured representation for requests, responses, errors, and one-way notifications while remaining independent of the underlying transport. This separation is important because the same protocol semantics can operate over STDIO or Streamable HTTP.

The MCP architecture documentation states that the data layer implements a JSON-RPC 2.0-based exchange protocol defining message structures and semantics. It also explains that the transport layer abstracts communication details, allowing the same JSON-RPC message format to operate across supported transports. The MCP specification similarly requires messages between clients and servers to follow JSON-RPC structures, including methods, parameters, IDs for requests, and result/error structures for responses.

SOAP/XML is a different web-service protocol family; GraphQL is primarily a query language and API runtime; Protocol Buffers is a binary serialization technology. None is the MCP-defined wire-message format. Therefore, option B is correct and agrees with the uploaded answer key.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — JSON-RPC 2.0, requests, responses, notifications, and transport independence.

===============

Streamable HTTP is the standard MCP transport intended for remote or network-accessible client-server communication. Current MCP architecture documentation distinguishes it from STDIO by explaining that Streamable HTTP uses HTTP POST for client-to-server communication and can optionally use Server-Sent Events for streaming. It enables communication with remote MCP servers and can support standard HTTP authentication mechanisms.

The MCP transport specification further establishes two standard transport mechanisms: stdio and Streamable HTTP . With STDIO, the client launches an MCP server as a local subprocess and exchanges JSON-RPC messages through standard input and standard output. That pattern is therefore most appropriate for local process integration. By comparison, a Streamable HTTP server operates as an independent service and can handle multiple client connections, making it suitable for centralized or cloud-hosted MCP deployments.

Raw TCP sockets and local Unix pipes are not the standard remote MCP transport defined by the protocol. Therefore, C is correct and matches the supplied source material.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — STDIO versus Streamable HTTP transport and remote MCP deployment.

===============

The OCI Responses API is explicitly designed as an OpenAI-compatible API for interacting with supported models and constructing agentic workflows. Oracle documents it as both OpenAI-compatible and Open Responses-compliant, allowing applications to use familiar Responses API request structures and the OpenAI SDK while routing execution to OCI Generative AI. The uploaded examination source likewise marks B as correct.

Compatibility is important because developers can use established client patterns rather than adopting a proprietary OCI-only programming interface. Oracle specifically recommends the OpenAI SDK for calling the OCI Responses API. The OCI endpoint differs in its base URL, authentication model, available OCI-hosted models, and platform governance, but the request structure follows the compatible Responses API model.

The interface is also not restricted to a single model provider. OCI supports multiple supported hosted models. Nor is the API read-only: agent workflows can use Function Calling and MCP Calling, allowing applications to execute external actions through controlled tool implementations. It also supports File Search and Code Interpreter.

Therefore, the defining statement among the choices is B.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — OCI Responses API, OpenAI compatibility, supported models, tools, and SDK interoperability.

===============

Embedding models accept inputs only up to their supported input-size or token limits. Large documents can exceed those limits and therefore must be divided into smaller segments before embedding generation. The course source explicitly identifies overcoming token limits as the reason for chunking.

Oracle AI Vector Search includes native chunking functionality that can split text according to characters, words, or model vocabulary tokens. Oracle's Vector Search guidance specifically states that input length must remain within the token limits of the embedding model and provides configurable maximum chunk sizes.

Chunking also provides an important retrieval benefit. Instead of representing an entire long document with one coarse embedding, the system creates embeddings for semantically meaningful sections. A similarity query can then retrieve only the chunks most relevant to the user's question, reducing irrelevant context and improving retrieval-augmented generation precision.

Chunking does not intentionally remove semantic meaning; well-designed chunking attempts to preserve it. It does not automatically provide encryption, and SQL storage format is not its underlying purpose.

Therefore, A is correct.

Study Guide reference/topic: Agentic AI for Oracle AI Database — document chunking, embedding token limits, vector generation, semantic retrieval, and RAG.

===============

The MCP Host is the top-level AI application in the Model Context Protocol architecture. Its responsibility is to coordinate the broader application experience and manage the MCP clients used to connect with one or more MCP servers. The official MCP architecture specifies that an MCP host creates a separate MCP client for each server connection and describes the host as the AI application that coordinates and manages one or multiple MCP clients.

The distinction between host, client, and server is essential. An MCP client maintains the protocol connection to a corresponding MCP server. An MCP server exposes capabilities such as tools, resources, and prompts. The host integrates these connections with the AI application's model and user interaction flow. Therefore, it is incorrect to define the host as the protocol specification itself, an external REST service, or the component that necessarily implements each individual tool.

Option D most accurately represents this orchestration role: the host coordinates the LLM-facing application and MCP client connections to the servers providing capabilities. The source question identifies D accordingly.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — MCP Host, MCP Client, MCP Server, and client-server architecture.

===============

A standalone LLM request typically consists of supplying input and receiving model-generated output. An AI agent adds an orchestration layer that enables the model to participate in a broader execution loop. Oracle's Enterprise AI Agents architecture explicitly combines model interaction with tools, memory, conversation state, reasoning, and multi-step orchestration . Tools allow an agent to retrieve information or perform actions through File Search, Function Calling, Code Interpreter, or MCP Calling. Memory preserves relevant state within or across conversations, while iterative execution enables the agent to evaluate intermediate results and determine subsequent actions until the task is complete. These capabilities do not require changing the transformer's architecture, increasing its training speed, or providing native graphical-interface rendering. Therefore, tool access, memory handling, and iterative execution are the defining additions described by option A. Oracle Docs

===============

OCI Responses API requests are associated with an OCI Generative AI Project through the project's OCID — Oracle Cloud Identifier . Oracle requires an OCI Generative AI project for agent-related OpenAI-compatible API calls and uses the project identifier to determine the project context under which responses, conversations, files, containers, retention settings, and related resources operate.

Oracle's OCI Responses API documentation shows the OpenAI client configured with a project parameter containing a Generative AI Project OCID. Oracle explicitly states that this value identifies the OCI Generative AI project for the request. Oracle's project documentation further explains that projects organize agent-specific artifacts, provide isolation boundaries, and that the project OCID must be referenced in API and SDK calls to apply project settings during runtime.

An Object Storage bucket could contain data used by another workflow but does not identify the Generative AI project. The tenancy display name identifies a tenancy conceptually but not the target project. A VCN OCID refers to network infrastructure.

Therefore, D is correct and matches the uploaded answer key.

Study Guide reference/topic: OCI Enterprise AI Agents — Generative AI Projects, Project OCID, OCI Responses API configuration, and project isolation.

===============

Oracle Autonomous AI Database includes a managed MCP Server that is natively integrated with the database rather than requiring customers to deploy and operate a separate MCP infrastructure tier. Oracle states that the service eliminates the need to manage customer-side MCP server infrastructure, directly reducing deployment and operational overhead. It also integrates with database identity, authorization, governance, auditing, network controls, database roles, Virtual Private Database policies, ACLs, and private endpoints.

Architecturally, this is significant because MCP-exposed Select AI Agent tools remain close to the database security boundary. The managed multi-tenant MCP layer can expose approved tools while relying on established database governance controls. Oracle's architecture describes a Unified Security Layer, managed MCP Server, and Select AI Agent Framework working together as an integrated stack.

The capability does not remove SQL, move database execution outside the database, or require a universal MCP host. Instead, its primary advantage is minimizing additional infrastructure while preserving strong database-native control over access and operations. Thus C is technically correct and matches the uploaded source.

Study Guide reference/topic: Agentic AI for Oracle AI Database — Autonomous AI Database MCP Server, native security integration, governance, and managed MCP infrastructure.

OCI Generative AI provides both On-Demand and Dedicated serving modes. The fundamental architectural distinction is resource isolation. On-Demand model inference uses Oracle-managed shared infrastructure, making it suitable for straightforward consumption of supported pretrained models without reserving dedicated hardware. Dedicated mode assigns dedicated GPU resources to the customer's workload and provides predictable, isolated serving capacity.

Oracle states that Dedicated AI Clusters are compute resources dedicated to a customer's models and are not shared with other tenancies. They are used for hosting supported pretrained models and, critically, for fine-tuning and hosting custom or imported models. The course question correspondingly identifies B as correct.

Option A ignores the infrastructure-isolation difference. Option C is technically impossible because all model inference requires compute resources; On-Demand simply abstracts shared infrastructure. Option D is also incorrect because On-Demand is not limited to embedding models—OCI provides multiple supported model categories through managed inference.

Therefore, B accurately captures both shared-versus-dedicated serving and the importance of Dedicated AI Clusters for custom-model workloads.

Study Guide reference/topic: OCI Enterprise AI Agents — Enterprise AI Models, On-Demand serving, Dedicated AI Clusters, custom models, and GPU isolation.

===============

Memory poisoning is an agent-security attack in which malicious, misleading, or attacker-controlled information is introduced into memory that the agent may reuse in future reasoning or actions. The uploaded course source defines it as malicious content inserted into persistent memory stores and identifies C as correct.

Oracle's current AI Agent Memory security guidance explains why persistent memory must be treated as a security-sensitive surface. Model-derived memories, summaries, context cards, metadata, and retrieved records can become persistent state and later be inserted into prompts. Oracle therefore advises treating memory-derived content as untrusted and emphasizes that write-capable memory paths can influence future prompts and retrieval results.

The broader agent-security definition is also explicit in OWASP's Agentic AI guidance: memory poisoning involves malicious data being persisted in agent memory so that it can influence future sessions or behaviors.

This differs from temporary context-window pressure, SQL injection, or physical RAM corruption. The essential security property is persistence : compromised memory can affect later reasoning long after the original malicious interaction.

Therefore, C is correct.

Study Guide reference/topic: Introduction to AI Agents — agent memory, persistent state, memory poisoning, prompt injection persistence, and agent security.

Zero-shot Chain-of-Thought prompting encourages a language model to decompose a problem into intermediate reasoning steps without supplying worked examples in the prompt. The classic prompting addition associated with this technique is “Let's think step by step.” The technique is “zero-shot” because the user does not provide demonstrations showing how comparable problems should be solved; instead, a short natural-language instruction encourages stepwise decomposition.

OpenAI's published prompting guidance historically illustrates this exact technique, explaining that instructing a model to reason through a sequence of steps can improve performance on tasks requiring decomposition. The OpenAI Cookbook specifically gives “Let's think step by step” as an example of an instruction used to elicit a series of reasoning steps.

Setting temperature to zero affects sampling variability rather than creating Chain-of-Thought prompting. Uploading structured data is unrelated to the reasoning technique, and disabling retrieval tools changes the model's information-access environment rather than prompting its problem-solving structure.

Accordingly, C is the intended and technically correct answer. The uploaded source also marks this exact phrase as correct.

Study Guide reference/topic: Introduction to AI Agents — prompting strategies, reasoning decomposition, zero-shot Chain-of-Thought, and agent reasoning patterns.

===============

In MCP architecture, executable capabilities are exposed by an MCP server . The server advertises available tools through the protocol, including each tool's name, description, and input schema. An MCP client discovers those capabilities using tools/list and invokes a selected tool through tools/call . The uploaded course material therefore correctly identifies the separate MCP server as the location associated with production MCP tool implementations.

The official MCP architecture defines an MCP server as the program that provides context and capabilities to MCP clients. It also defines tools as executable functions exposed by servers for actions such as API calls, database queries, or file operations. During execution, the AI application routes the model-generated tool call through the corresponding MCP client to the appropriate MCP server.

Tools are not encoded into an LLM's trained weights. Locally defined function tools can indeed be declared in agent code, but that is distinct from an MCP-served tool. Likewise, the MCP client handles communication and protocol coordination; it is not conceptually the server-side implementation host.

Therefore, A is architecturally correct.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — MCP Servers, tool hosting, tools/list, tools/call, and client-server separation.

===============