Oracle 1Z0-184-25 Practice Exam Questions & Answers

In Oracle 23ai, EFCONSTRUCTION (A) controls the number of closest vector candidates (edges) considered during HNSW index construction, affecting the graph's connectivity and search quality. Higher values improve accuracy but increase build time. VECTOR_MEMORY_SIZE (B) sets memory allocation, not candidate count. NEIGHBOURS (C) isn't a parameter; it might confuse with NEIGHBOR_PARTITIONS (IVF). TARGET_ACCURACY (D) adjusts query-time accuracy, not index creation. Oracle's HNSW documentation specifies EFCONSTRUCTION for this purpose.

In Oracle Database 23ai, a VECTOR column can be defined with a specific size (e.g., VECTOR(512, FLOAT32)) or left unspecified (e.g., VECTOR). Not defining a size (D) provides flexibility during development because different embedding models (e.g., BERT, SentenceTransformer) generate vectors with varying dimensions (e.g., 768, 384) and data types (e.g., FLOAT32, INT8). This avoids locking the schema into one model, allowing experimentation. Accuracy (A) isn't directly impacted by size definition; it depends on the model and metric. A fixed size doesn't restrict the database to one model (B) but requires matching dimensions. Text length (C) affects tokenization, not vector dimensions. Oracle's documentation supports undefined VECTOR columns for flexibility in AI workflows.

AI Smart Scan in Exadata System Software 24ai (B) accelerates AI workloads, including vector search, by offloading processing to storage servers using Exadata's RDMA Memory (XRMEM), Smart Cache, and on-storage capabilities. This enhances performance for large-scale vector operations. Real-time monitoring (A) isn't its focus; that's for management tools. Queryoptimization (C) is a general Exadata feature (Smart Scan), but AI Smart Scan specifically targets AI tasks. Oracle's 24ai documentation emphasizes its role in speeding up AI computations.

For speed over accuracy with billions of vectors, approximate similarity search (ANN) with a low target accuracy setting (B) (e.g., 70%) uses indexes like HNSW or IVF, probing fewer vectors to return top-10 matches quickly. Exact flat search (A) scans all vectors, too slow for billions. Relational filtering with exact search (C) adds overhead without speed gains. Exact search with high accuracy (D) maximizes precision but sacrifices speed. Oracle's documentation recommends ANN for large-scale, speed-focused queries.

In Oracle Database 23ai, vector distance calculations are primarily handled by the VECTOR_DISTANCE function, which supports multiple metrics (e.g., COSINE, EUCLIDEAN) specified as parameters (e.g., VECTOR_DISTANCE(v1, v2, EUCLIDEAN)). However, the question implies distinct functions, a common convention in some databases or libraries, and Oracle's documentation aligns L2_DISTANCE (B) with the Euclidean metric. L2 (Euclidean) distance is the straight-line distance between two points in vector space, computed as (xi - yi), where xi and yi are vector components. For example, for vectors [1, 2] and [4, 6], L2 distance is ((1-4) + (2-6)) = (9 + 16) = 5.

Option A, L1_DISTANCE, represents Manhattan distance (|xi - yi|), summing absolute differences---not Euclidean. Option C, HAMMING_DISTANCE, counts differing bits, suited for binary vectors (e.g., INT8), not continuous Euclidean spaces typically used with FLOAT32 embeddings. Option D, COSINE_DISTANCE (1 - cosine similarity), measures angular separation, distinct from Euclidean's magnitude-inclusive approach. While VECTOR_DISTANCE is the general function in 23ai, L2_DISTANCE may be an alias or a contextual shorthand in some Oracle AI examples, reflecting Euclidean's prominence in geometric similarity tasks. Misinterpreting this could lead to choosing COSINE for spatial tasks where magnitude matters, skewing results. Oracle's vector search framework supports Euclidean via VECTOR_DISTANCE, but B aligns with the question's phrasing.