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.

Oracle AI Vector Search supports both in-database embedding generation and external embedding providers , making A the correct answer. The supplied question source identifies the same combination.
For in-database processing, Oracle AI Database includes an ONNX runtime. Compatible ONNX embedding models can be imported as database objects and invoked directly through SQL using functions such as VECTOR_EMBEDDING . This allows vectorization to occur without moving source data outside the database.
Oracle also supports REST-based embedding generation. DBMS_VECTOR.UTL_TO_EMBEDDING and related APIs can call external or local providers. Officially documented providers include OCI Generative AI, Cohere, OpenAI, Google AI, Hugging Face, Vertex AI, Mistral, Ollama, and Private AI, depending on the operation and configuration.
Manual Python export/import workflows are technically possible in custom architectures, but they are not the supported approaches being tested. Option C is explicitly false because Oracle supports in-database ONNX inference.
Therefore, A correctly captures Oracle's native and external embedding-generation strategies.
Study Guide reference/topic: Agentic AI for Oracle AI Database - ONNX Runtime, VECTOR_EMBEDDING, DBMS_VECTOR, REST embedding providers, and AI Vector Search.

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.

MCP addresses the integration fragmentation created when multiple AI applications must independently connect to multiple external tools, services, and data sources. The uploaded course material characterizes this explicitly as the N × M custom-connector problem : without a common interoperability layer, every application-to-tool pairing can require a separate integration.
The official MCP architecture supports this framing by defining a standardized client-server protocol. MCP hosts establish clients that communicate with MCP servers, while servers expose reusable capabilities such as tools, resources, and prompts. A compatible AI application therefore consumes capabilities through the MCP protocol rather than requiring a completely bespoke protocol implementation for each downstream system.
MCP's tool-discovery mechanism further allows clients to obtain standardized names, descriptions, and schemas dynamically.
The problem is architectural interoperability, not GPU allocation, inference latency, or context-window limitations. Those issues require separate model, infrastructure, or prompt-management techniques. MCP instead standardizes the boundary between AI applications and external capabilities, reducing duplicated connector logic and enabling reusable integrations.
Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals - interoperability, MCP client
/server architecture, tool discovery, and the N × M integration problem.

OCI production AI architectures use the standard OCI observability and governance services to provide operational visibility and accountability. OCI Logging collects and centralizes service and application logs; OCI Generative AI hosted applications can expose deployment logs that open directly in OCI Logging and the Observability and Management service. OCI Monitoring supplies metrics and alarms for monitoring resource health and operational conditions. OCI Audit records calls made to supported OCI public API endpoints, providing an authoritative record of administrative and resource-management actions for investigation and compliance. Oracle's architecture guidance specifically recommends enabling OCI Logging, OCI Monitoring, and OCI Audit logs for critical AI-platform components. The services in the other options have legitimate OCI purposes, but they do not collectively represent the principal observability-and-auditing stack. Therefore, option A is the verified combination. Oracle Docs