Databricks Generative AI Engineer Associate Practice Question 5: Hybrid Search Part Numbers
Databricks Certified Generative AI Engineer Associate · Test 1 · question 5 of 10
A support agent for an industrial parts distributor retrieves from a Databricks AI Search (formerly Vector Search) index of product descriptions. Customer queries mix natural language with exact identifiers, for example "replacement seal kit for pump HX-4471-B". Retrieval handles the descriptive part well but often returns seal kits for similar-sounding pumps instead of HX-4471-B.
Which change to the retrieval call best addresses this with the least effort?
Show answer and explanation
Answer:
Dense embeddings capture meaning well but handle rare exact tokens like part numbers poorly: "HX-4471-B" and "HX-4417-B" end up close together in vector space. Hybrid search runs approximate nearest-neighbor search and full-text (keyword) search together and merges the two ranked lists with Reciprocal Rank Fusion. The exact identifier gets keyword precision and the descriptive text keeps its semantic match, which suits these mixed queries. It is a single parameter on the query, with no re-indexing.
Option A is wrong. More results mostly means more wrong seal kits in the prompt. The exact match still has no ranking advantage.
Option C is wrong. A bigger embedding does not make similarity search reliable at matching arbitrary alphanumeric codes, and re-embedding the whole catalog is a lot of work.
Option D is wrong. Direct Vector Access describes how the index is *updated* (manually, via the API) rather than how it is queried. It adds no keyword matching.
Reference: Query an AI Search index