Pass the Oracle Cloud Infrastructure 1z0-1157-26 Questions and answers with Dumpstech

An LLM-based AI agent is not simply a foundation model or chatbot user interface. It is a system in which an LLM acts as a reasoning and decision-making component while an orchestration layer gives it access to instructions, tools, state, external information, and potentially other agents. This architecture enables the system to decide which actions to perform and in what sequence to pursue a defined objective.

OpenAI describes an agent as an LLM equipped with instructions, tools, and handoffs, allowing it to plan, use tools to gather information or take actions, and delegate tasks when appropriate. Oracle similarly explains that AI agents use tools to communicate with external systems and dynamically determine which tools or integrations to use and in which order to achieve a goal.

An agent therefore does not require training an entirely new model architecture. The underlying LLM may be an existing pretrained model. What makes the system agentic is the combination of model reasoning with orchestration, tool execution, observations, state, and iterative decision-making.

Accordingly, D provides the correct architectural definition and matches the answer supplied in the uploaded source.

Study Guide reference/topic: Introduction to AI Agents — LLM-based agents, reasoning, tools, orchestration, actions, observations, and agent loops.

Tool selection in the OpenAI Agents SDK is model-driven. Each function tool exposes structured metadata that gives the model enough information to determine whether the tool is appropriate and how it should be invoked. The SDK represents a function tool using a name , description , and JSON parameter schema . OpenAI's SDK reference explicitly defines these properties as information shown to the LLM, while function-tool helpers automatically generate the parameter schema from the Python function signature and derive descriptions from documentation when available.

During an agent run, the model evaluates the user's request together with the available tool definitions. It can then select an appropriate tool and generate arguments conforming to that tool's schema. This mechanism is fundamentally semantic and contextual: meaningful names and descriptions tell the model what a tool does, while schemas describe the arguments required to execute it.

There is no rule requiring the first registered tool to be selected, every tool to be invoked, or random selection. Such behavior would undermine agentic reasoning and dynamic orchestration. Consequently, B is the technically correct answer and is explicitly identified as correct in the uploaded question set.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — Function Tools, tool metadata, JSON schemas, tool selection, and model-driven invocation.

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

The OpenAI Agents SDK uses an iterative agent loop for multi-step tool execution. In this scenario, the model first determines that it needs the multiply tool and generates a call with the arguments 15 and 8 . The application executes that tool and returns 120 as a tool result. The model receives the updated conversation state, recognizes that another operation remains, and subsequently requests divide(120, 3) . The resulting value is then available for the final response. The uploaded course source explicitly specifies this sequence.

OpenAI's Agents SDK documentation confirms that the Runner repeatedly calls the LLM, executes requested tools, appends their results, and runs the model again until final output is produced.

The Runner does not independently decide to calculate the arithmetic itself. Nor does the SDK automatically merge unrelated function calls into one synthetic operation. Likewise, an agent does not invoke every registered tool indiscriminately; the model selects the tools required by the current task.

Therefore, D accurately describes the sequential model/tool interaction.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — agent loop, sequential tool calls, tool results, Runner orchestration, and multi-step execution.

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

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.

The Vector Stores API provides infrastructure for ingesting content and retrieving the portions that are semantically relevant to a query. Files associated with a vector store can be chunked and prepared for vector-based retrieval, allowing applications and agents to locate content based on semantic similarity rather than only exact lexical matches .

OpenAI's official Vector Stores API supports searching a vector store with a natural-language query and returns relevant content chunks together with similarity scores. The API also supports attaching files to vector stores and configuring the chunking strategy used during ingestion. This architecture is foundational to retrieval-augmented generation and File Search workflows: source material is indexed, a user query retrieves semantically related chunks, and those chunks can then provide grounded context to a model.

Language translation is a generative-model task. Object Storage encryption is a cloud-storage security function, while video streaming is unrelated to the purpose of a vector store.

Accordingly, “Indexing and retrieving data by meaning” is the technically correct description and is also the answer specified by the uploaded question source.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — Vector Stores, semantic retrieval, chunking, File Search, similarity ranking, and RAG.

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

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.

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

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.

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

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 distinction concerns ownership of the conversation and orchestration flow , not synchronous versus asynchronous execution. In the OpenAI Agents SDK's Manager pattern—also called agents-as-tools—a central manager remains the active user-facing agent. It invokes specialist agents as tools, receives their outputs, synthesizes them, and retains responsibility for the final response. The specialist supports the manager without taking ownership of the conversation.

A Handoff works differently. When the current agent hands the task to another agent, the selected specialist becomes the active agent and takes over the conversation for the remainder of that portion of the run. OpenAI's official Agents SDK documentation explicitly describes the Manager pattern as retaining control and Handoffs as transferring control to a specialized agent.

This distinction allows architects to select centralized orchestration when a single agent must aggregate results or apply common controls, and decentralized handoffs when specialists should directly own particular interactions. Therefore, D states the relationship correctly and matches the uploaded question's answer key.

Study Guide reference/topic: OpenAI Responses API and Agents SDK — multi-agent orchestration, Agents as Tools/Manager pattern, and Handoffs.

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

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

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