An enterprise is building a search system for its product catalog, which holds 50 million product descriptions in a Delta table, to be embedded as 768-dimension vectors. The product catalog experiences frequent updates, with items regularly being added or removed. The system requires query responses to be delivered within 100 milliseconds. What is the most appropriate Vector Search configuration given these requirements?
Answer & explanation
Correct answer: A
WHY A is correct: 50M vectors at 768 dimensions is well within the standard endpoint's ~320M capacity. Delta Sync with Databricks-managed embeddings handles automatic embedding computation. Continuous sync mode keeps the index current as the source Delta table changes — ideal for a live product catalog. Standard endpoint query latency is lower than storage-optimized (storage-optimized adds ~250ms overhead).
WHY NOT B: Storage-optimized endpoints add roughly 250 ms of query latency, so a 100 ms target is out of reach. They are designed for very large datasets (1B+) where standard endpoints are insufficient, which 50M vectors is not. A Direct Vector Access index would also need every add and remove pushed through the API by the team's own code.
WHY NOT C: Query latency depends on the endpoint type, not on how vectors are written, so skipping the sync pipeline does not make queries faster. A Direct Vector Access index also has to be updated by the team's own upsert and delete calls and needs the embeddings computed outside Databricks, which risks a stale index for a continuously changing catalog. Delta Sync follows the source table automatically.
WHY NOT D: As noted, storage-optimized endpoints add ~250ms query latency and don't support continuous sync. Both properties disqualify this option for a real-time, sub-100ms catalog search system.