Skip to content

Explaining what Mosaic AI Vector Search is made of and how it works

Mosaic AI Vector Search is Databricks' managed vector database that lets you create searchable indexes over embeddings and retrieve semantically similar records for use in RAG and other GenAI applications. It integrates natively with Delta tables and Unity Catalog, so indexes can stay synchronized with source data and inherit the same governance model.

1 · Learn the must-know

  • A Vector Search Endpoint is the compute resource that must exist before you can create or query any index, and multiple indexes can share one endpoint.
  • A Delta Sync Index is linked to a source Delta table and automatically keeps embeddings up to date as the table changes, using either Continuous or Triggered (scheduled/manual) sync modes.
  • A Direct Vector Access Index lets you read and write vectors directly via API without a backing Delta table, useful when embeddings are computed or managed externally.
  • You can either let Databricks compute embeddings automatically using a specified embedding model endpoint (Compute Embeddings) or supply pre-computed embedding vectors yourself.
  • Indexes and endpoints are registered in Unity Catalog under a catalog.schema.index_name namespace, so standard Unity Catalog permissions govern access to them.
  • Similarity search returns approximate nearest neighbors ranked by a distance metric (e.g., cosine or L2), and queries can combine vector similarity with metadata filters on other Delta table columns.

2 · Check your understanding

Check this objectiveFree · always available

A Generative AI Engineer is building a Delta Sync Index in Mosaic AI Vector Search backed by a Unity Catalog Delta table that receives new product review rows every few minutes. The application must reflect new reviews in search results within seconds, and the team wants to avoid manually triggering syncs after every batch load. Which pipeline type should the engineer configure for the index?

Your objective map0 tried · 0 answered correctly · 56 untouched

What you have tried across Databricks GenAI Engineer's objectives, not a readiness score.

Design Applications10.71% of the exam*0 of 6 tried
Data Preparation14.29% of the exam*0 of 8 tried
Application Development23.21% of the exam*0 of 13 tried
Assembling and Deploying Applications26.79% of the exam*0 of 15 tried
Governance7.14% of the exam*0 of 4 tried
Evaluation and Monitoring17.86% of the exam*0 of 10 tried

* Our estimate. Databricks publishes no section weights.

3 · Keep going