Databricks Certified Generative AI Engineer Associate Exam - Topic 2 Question 38 Discussion

The task is to set up a Databricks Vector Search index for news articles, supporting queries like ''monster truck news around January 5th, 1992,'' with minimal effort. The index must filter by topic and a 10-day date range. Let's evaluate the options.

Option A: Split articles by 10-day blocks and return the block closest to the query

Pre-splitting articles into 10-day blocks requires significant preprocessing and index management (e.g., one index per block). It's effort-intensive and inflexible for dynamic date ranges.

Databricks Reference: 'Static partitioning increases setup complexity; metadata filtering is preferred' ('Databricks Vector Search Documentation').

Option B: Include metadata columns for article date and topic to support metadata filtering

Adding date and topic as metadata in the Vector Search index allows dynamic filtering (e.g., date 5 days, topic = ''monster truck'') at query time. This leverages Databricks' built-in metadata filtering, minimizing setup effort.

Databricks Reference: 'Vector Search supports metadata filtering on columns like date or category for precise retrieval with minimal preprocessing' ('Vector Search Guide,' 2023).

Option C: Pass the query directly to the vector search index and return the best articles

Passing the full query (e.g., ''Tell me about monster truck news around January 5th, 1992'') to Vector Search relies solely on embeddings, ignoring structured filtering for date and topic. This risks inaccurate results without explicit range logic.

Databricks Reference: 'Pure vector similarity may not handle temporal or categorical constraints effectively' ('Building LLM Applications with Databricks').

Option D: Create separate indexes by topic and add a classifier model to appropriately pick the best index

Separate indexes per topic plus a classifier model adds significant complexity (index creation, model training, maintenance), far exceeding ''least effort.'' It's overkill for this use case.

Databricks Reference: 'Multiple indexes increase overhead; single-index with metadata is simpler' ('Databricks Vector Search Documentation').

Conclusion: Option B is the simplest and most effective solution, using metadata filtering in a single Vector Search index to handle date ranges and topics, aligning with Databricks' emphasis on efficient, low-effort setups.