Oracle Agentic AI Foundations Associate 1z0-1157-26 Exam Dumps: Updated Questions & Answers (September 2026)

The OpenAI Agents SDK implements an iterative agent loop in which the model determines which available capability should be invoked, receives the resulting observation, and can then make another tool call based on that updated context. Consequently, the model first requests multiply(15, 8) . The function executes and returns 120 ; that tool output is supplied back to the model. The model then determines that the remaining operation requires divide(120, 3) and requests the second tool.

OpenAI describes Agents as LLMs equipped with tools and explains that the SDK runtime manages repeated model/tool interactions until the workflow produces final output. Function tools expose schemas and executable implementations to this orchestration process.

The Runner is responsible for coordinating the loop; it does not independently substitute its own arithmetic logic for the model's tool decisions. Similarly, the SDK does not synthesize a new combined function when two distinct tools are required, nor does it invoke every available tool without reason.

The uploaded question source explicitly marks the sequential multiply-then-divide behavior as correct.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — agent loop, sequential function calling, tool observations, and Runner orchestration.

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

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.

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

The Runner is responsible for executing the OpenAI Agents SDK agent loop. The uploaded course source identifies this directly as the Runner's role.

When Runner.run() , Runner.run_sync() , or Runner.run_streamed() is invoked, the Runner starts with an agent and user input, calls the configured model, evaluates the model output, and decides what happens next. If the output is final, execution terminates. If the model requests a tool call, the Runner executes the tool, appends the result, and calls the model again. If the model produces a handoff, the Runner updates the active agent and continues the loop. OpenAI's official documentation describes precisely this lifecycle.

The Runner is therefore an orchestration/runtime component rather than an agent-hosting deployment service. Authentication configuration exists separately, and function-tool JSON schemas are generated by the tool-definition mechanisms rather than being the Runner's primary responsibility.

This distinction is central to the SDK architecture: the Agent defines behavior and capabilities , while the Runner executes the iterative workflow .

Therefore, C is correct.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — Runner, agent loop, tool execution, handoffs, final output, and runtime orchestration.

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

When a LangChain agent is invoked through agent.invoke() , the agent runtime abstracts the core mechanics required for model-mediated tool execution. LangChain tools expose structured inputs and outputs, and tool definitions provide the model with schemas derived from Python type information or explicitly supplied schemas. The framework then coordinates model responses containing tool calls, dispatches the corresponding tools, passes observations back to the model, and repeats the process until the agent reaches a termination condition.

This is a major distinction between directly binding tools to a standalone chat model and using a LangChain agent. LangChain documentation states that, with a model alone, the developer must execute returned tool calls and feed results back manually; when an agent is used, the agent loop handles that tool-execution loop .

Thus, the course's intended abstraction is captured by B: building/exposing tool schemas, processing model tool calls, and orchestrating iterative execution. GPU memory distribution and model training are infrastructure/model-development responsibilities, not functions of agent.invoke() .

The supplied question source explicitly marks B as the expected answer.

Study Guide reference/topic: LangChain for AI Agents — agent.invoke(), tool schemas, tool-call parsing, ToolNode execution, and iterative agent loops.

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

The @function_tool decorator converts an ordinary Python function into a FunctionTool that can be exposed to an agent for model-directed invocation. The Agents SDK automatically derives important tool metadata: by default, the Python function name becomes the tool name, its docstring supplies the tool description, and the function signature is converted into a JSON schema describing the expected arguments. This structured representation allows the language model to determine when the function is relevant and generate valid arguments for it. The decorator does not inherently expose the function as a REST endpoint, persist return values to disk, or guarantee automatic retries whenever execution fails. This mechanism corresponds closely to OCI Enterprise AI Agents' Function Calling model, where application-controlled functions extend an agent beyond pure model generation and enable controlled interaction with external business logic. OpenAI GitHub

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

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.

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

OCI Generative AI uses Dedicated AI Clusters to provide the isolated compute infrastructure required for fine-tuning and hosting custom model workloads. Oracle defines Dedicated AI Clusters as compute resources dedicated to a customer's models rather than shared with other tenancies. They can be created specifically for fine-tuning or for hosting model endpoints.

Oracle's current model onboarding workflow confirms the requirement. For imported models, the process includes importing the model, creating a hosting Dedicated AI Cluster , creating an endpoint, and then invoking the model. Fine-tuned models similarly require dedicated clusters for fine-tuning and subsequent hosting.

Shared On-Demand inference is appropriate for supported Oracle-hosted pretrained models, but it does not provide the dedicated isolated serving environment required by these custom model workflows. Object Storage can be an input location for model artifacts or training data, but it is storage rather than model-serving infrastructure. General-purpose Free Tier compute is likewise not the managed Generative AI capability Oracle specifies for custom-model serving.

Thus, B is correct and agrees with the uploaded course material.

Study Guide reference/topic: OCI Enterprise AI Agents — Dedicated AI Clusters, imported models, fine-tuned custom models, hosting clusters, and endpoints.

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

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.

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

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.

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

For production OCI Enterprise AI workloads, Oracle recommends OCI IAM-based authentication rather than long-lived development credentials. The uploaded source identifies OCI IAM authentication with signed requests and IAM policies as the correct production architecture.

Oracle's OCI Responses API authentication documentation distinguishes service API keys used for testing and early development from IAM authentication intended for production and OCI-managed environments. IAM-based authentication uses OCI identity principals and request-signing mechanisms and allows authorization to be controlled through centralized IAM policies. Oracle specifically recommends IAM when applications execute in services such as OCI Functions or Oracle Kubernetes Engine, when long-lived API keys should be avoided, or when fine-grained centralized access control is required.

IAM policies also implement least privilege by defining exactly which users, groups, resource principals, or workloads can access individual Generative AI resource types.

Browser cookies, anonymous tenancy access, and credentials committed into source repositories violate standard enterprise security practices and significantly increase credential-exposure risk.

Therefore, A is the only production-grade authentication approach among the choices.

Study Guide reference/topic: OCI Enterprise AI Agents — OCI IAM, signed requests, policies, principals, least privilege, and production authentication.

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