OCI Generative AI defines two principal approaches for developing enterprise-grade agentic applications. The first is to build agents using the OCI Responses API , an API-first model that allows developers to control agent interactions through an OpenAI-compatible interface. The second is to deploy hosted agentic applications using OCI Generative AI Applications and Deployments, where OCI manages substantial portions of the application runtime infrastructure. Oracle explicitly documents these as the two main Enterprise AI Agent approaches and notes that they can also be combined in hybrid architectures.

The Responses API approach is appropriate when developers want direct programmatic control over models, tools, context, and agent behavior without independently managing inference infrastructure. Hosted agent applications are appropriate when custom agent runtimes need managed container deployment, networking, identity, storage integration, scaling, and production lifecycle support. OCI's broader Generative AI architecture positions these mechanisms within its Enterprise AI Agents layer.

The supported architecture is therefore not divided according to Python versus Java, pricing categories, or frontend versus backend classification. Option A reproduces Oracle's documented deployment choices precisely and matches the supplied examination source.

Study Guide reference/topic: OCI Enterprise AI Agents — OCI Responses API, Applications, Deployments, hosted agentic applications, and hybrid architectures.

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

Oracle AI Vector Search defines VECTOR_DISTANCE as the primary SQL function for calculating the distance between two vectors. When the function is called without explicitly specifying a distance metric, Oracle specifies COSINE as the default metric for ordinary, non-BINARY vectors. Cosine distance measures the angular relationship between vector representations and is widely used for semantic similarity because embeddings with similar meaning tend to point in similar directions in vector space. Oracle treats BINARY vectors differently: their default metric is HAMMING. Euclidean, or L2, distance is supported but must be selected when required; it is not the general default. Levenshtein distance applies to string-edit comparisons, while bitwise XOR is not the default Oracle vector-distance metric. Therefore, for the scenario stated in the question, option C is the verified answer. Oracle Docs

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

OCI Enterprise AI Governance provides the control framework required to operate generative and agentic AI workloads securely in enterprise environments. Oracle defines governance as a combination of infrastructure protection, access control, network security, and runtime safety mechanisms. Key capabilities include OCI IAM policies , which determine who can access and manage Generative AI resources; Private Endpoints , which prevent model traffic from requiring public network exposure; Zero Trust Packet Routing , which introduces identity-aware network enforcement; and Guardrails , which apply safety and compliance controls to model inputs and outputs.

Oracle Guardrails specifically support mechanisms including content moderation, prompt-injection detection, and personally identifiable information detection. These controls address AI-specific operational and security risks rather than model lifecycle rollback or performance optimization.

Therefore, option D accurately expresses the purpose of Enterprise AI Governance. Model version management, runtime implementation, and latency monitoring may be operational concerns in an AI platform, but they are not the principal governance function described by OCI. The uploaded examination source also identifies D as the correct answer.

Study Guide reference/topic: OCI Enterprise AI Agents — Enterprise AI Governance, IAM, Private Endpoints, Zero Trust Packet Routing, and Guardrails.

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

Oracle AI Database provides a native VECTOR data type specifically for storing vector embeddings. The uploaded course source identifies VECTOR as the correct native column type.

Oracle's official AI Vector Search documentation states that the built-in VECTOR data type provides the foundation for storing embeddings directly alongside relational business data. A table can therefore define a vector column in the same way it defines conventional Oracle columns, for example doc_vector VECTOR .

This native representation is important because Oracle AI Database can apply vector-specific SQL operations and vector indexes directly to stored embeddings. Applications can combine similarity search with relational predicates, JSON processing, graph operations, spatial queries, and standard SQL without moving embeddings into a separate specialized vector database.

Although Oracle may internally use storage mechanisms such as SecureFiles for vector representation, BLOB is not the logical SQL column type developers use for AI Vector Search embeddings . JSON and VARCHAR2 are likewise general-purpose data types and do not provide native vector semantics.

Therefore, A is correct.

Study Guide reference/topic: Agentic AI for Oracle AI Database — VECTOR data type, vector columns, embedding storage, vector indexes, and AI Vector Search.

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

In MCP, STDIO is designed for local process-based communication. Under this transport, the host or client application launches the MCP server as a subprocess and exchanges protocol messages through the server's standard input ( stdin ) and standard output ( stdout ). The uploaded examination source identifies this behavior as the correct definition.

STDIO should be contrasted with Streamable HTTP , which is designed for independently running, network-accessible MCP servers and remote communication. STDIO is particularly suitable for local integrations where the MCP server executable can run on the same machine as the host application.

The transport mechanism does not change MCP's underlying message semantics. MCP communication still uses JSON-RPC structures; STDIO does not replace JSON with an unrelated plain-text protocol. Authentication requirements such as OAuth are also not an inherent requirement of STDIO. OAuth and HTTP-oriented authentication concerns primarily arise in remote server architectures.

Therefore, the defining STDIO behavior is local subprocess execution coupled with stdin/stdout message exchange.

Answer C correctly captures the architecture described by MCP and by the uploaded course source.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — STDIO transport, local MCP servers, subprocess lifecycle, JSON-RPC, and Streamable HTTP comparison.

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

MCP delivers its greatest architectural value when an AI application must interact with capabilities that exist outside the application's own process , particularly external services, databases, SaaS platforms, APIs, or cloud-hosted tools. Instead of implementing a proprietary integration contract for every agent/tool combination, an MCP server exposes those capabilities using a standardized protocol.

The MCP specification describes the protocol as a standardized mechanism for integrating LLM applications with external data sources and tools . Its tools specification further states that MCP servers can expose capabilities that query databases, call APIs, perform computations, or otherwise interact with external systems.

For trivial local functions such as add() or multiply() , a normal in-process function-tool definition is usually simpler because no separate server protocol is needed. Similarly, an application that has no external dependencies gains relatively little from introducing MCP solely for prompts or local output parsers.

Thus the decisive use case is integration across system or deployment boundaries, especially where capabilities should be reusable by multiple MCP-compatible clients.

Therefore, D is the correct answer and is also explicitly marked correct in the uploaded source.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — external tools, MCP servers, interoperability, reusable integrations, and remote services.

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

In MCP, Tools are the primitive explicitly designed to be model-controlled. They represent executable functions that an MCP server exposes so that a language model can take actions, retrieve information, query databases, invoke APIs, modify files, or perform computations. The uploaded question set identifies Tools as the correct answer.

The official MCP specification defines three principal server primitives with different control models: Prompts are user-controlled , Resources are application-controlled , and Tools are model-controlled . Tools can be discovered by the model-facing application and invoked automatically according to the model's contextual interpretation of the user's request.

Resources differ because they primarily provide contextual data such as file contents or database schemas. Prompts provide reusable templates or instructions normally selected through user interaction. “Schemas” are not one of the three MCP primitives in this control hierarchy; schemas describe structures such as tool parameters rather than constituting a standalone primitive.

Therefore, A is correct.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — MCP primitives, Tools, Resources, Prompts, control hierarchy, and tool invocation.

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