A developer needs to create a Mosaic AI Vector Search index that: (1) uses a Databricks-hosted embedding model to compute vectors, (2) stays automatically synchronized as new rows are added to the source Delta table, and (3) allows metadata filtering on a 'category' column. Which index type should be used?
Show answer & explanation
Correct answer: B
WHY B is correct: A Delta Sync Index with Databricks-managed embeddings satisfies all three requirements: (1) Databricks calls the specified embedding model endpoint to compute vectors from the source text column, (2) the index continuously or incrementally syncs with the source Delta table as rows are added (Change Data Feed must be enabled), and (3) metadata filters on any Delta table column (including 'category') are supported at query time. WHY NOT A: The Direct Vector Access Index requires manual REST API calls to upsert or delete vectors. It does not automatically sync with a Delta table when new rows are added. WHY NOT C: Delta Sync Index with self-managed embeddings requires the developer to pre-compute embeddings and store them in the Delta table before syncing. The requirement specifies using a Databricks-hosted embedding model, which is Databricks-managed embeddings (Option 1). WHY NOT D: Storage-optimized endpoints are a hardware tier optimized for large-scale indexes (1B+ vectors). They are not an index type — and this selection incorrectly mixes endpoint type with index type. Direct Vector Access Indexes on storage-optimized endpoints still lack auto-sync capability.