Tag: Vector Search

AI, Azure AI, Databases, DP-800, Microsoft Certification August 1, 2026

Choose between using ANN and ENN for vector search (DP-800 Exam Prep)

This post is a part of the DP-800: Developing AI-Enabled Database Solutions Exam Prep Hub.
This topic falls under these sections:
Implement AI capabilities in database solutions (25–30%)
   --> Design and implement intelligent search
      --> Choose between using ANN and ENN for vector search

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Introduction

Vector search is the foundation of modern AI-powered applications such as Retrieval-Augmented Generation (RAG), semantic search, recommendation engines, document similarity, and intelligent assistants. As vector databases grow from thousands to millions of embeddings, selecting the appropriate search algorithm becomes increasingly important.

One of the most important architectural decisions is choosing between:

Approximate Nearest Neighbor (ANN) search
Exact Nearest Neighbor (ENN) search

Although both methods retrieve vectors that are similar to a query vector, they differ significantly in performance, scalability, accuracy, resource usage, and appropriate use cases.

For the DP-800 exam, candidates should understand when to use ANN versus ENN, how vector indexes influence each approach, and the trade-offs involved in balancing search speed with search accuracy.

Understanding Nearest Neighbor Search

Once embeddings have been generated for documents, products, images, or other data, a user query is also converted into an embedding.

The search engine must identify the vectors that are “closest” to the query vector.

Closeness is typically measured using:

Cosine similarity
Euclidean distance (L2)
Dot product

The challenge becomes finding the nearest vectors efficiently.

If a database contains:

5,000 vectors
500,000 vectors
50 million vectors

the search strategy dramatically affects response time.

Exact Nearest Neighbor (ENN)

Exact Nearest Neighbor performs an exhaustive comparison.

Every stored vector is compared against the query vector.

The system computes the distance to every record before returning the closest matches.

Characteristics

Searches every vector
Produces mathematically exact results
No approximation
Highest accuracy
Computationally expensive
Slower as data grows

ENN Workflow

			
Query Vector
↓
Compare against Vector 1
↓
Compare against Vector 2
↓
Compare against Vector 3
↓
...
↓
Compare against Vector N
↓
Sort by similarity
↓
Return Top K

		

Advantages of ENN

Maximum Accuracy

Every possible vector is evaluated.

No relevant documents are skipped.

Deterministic Results

The same query always produces the same ranking.

No Index Approximation

Results represent the actual nearest neighbors.

Simpler Conceptually

The algorithm is straightforward.

No graph traversal or approximation heuristics are involved.

Disadvantages of ENN

Poor Scalability

Performance decreases linearly with dataset size.

Examples:

1,000 vectors → very fast
100,000 vectors → acceptable
10 million vectors → slow
100 million vectors → often impractical

High CPU Usage

Every query compares against every stored embedding.

Higher Latency

Search time increases as the vector collection grows.

Common ENN Use Cases

ENN is appropriate when:

Maximum precision is required
Dataset is relatively small
Scientific applications require exact matches
Benchmarking ANN algorithms
Testing search quality
Evaluation environments

Examples include:

Medical research
Financial analytics
Legal document comparison
Academic datasets
Quality assurance testing

Approximate Nearest Neighbor (ANN)

Approximate Nearest Neighbor avoids comparing every vector.

Instead, it uses specialized vector indexes that intelligently narrow the search space.

The goal is to find vectors that are almost certainly among the nearest neighbors while dramatically improving search speed.

ANN typically achieves:

95–99.9% recall
Much lower latency
Massive scalability

ANN Workflow

			
Query Vector
↓
Search Vector Index
↓
Explore Nearby Candidates
↓
Evaluate Candidate Vectors
↓
Return Top K

		

Instead of examining millions of vectors, ANN may evaluate only a few hundred or a few thousand candidate vectors.

Advantages of ANN

Extremely Fast

ANN dramatically reduces search time.

Milliseconds instead of seconds.

Highly Scalable

Suitable for:

Millions of vectors
Tens of millions
Hundreds of millions
Billions of vectors

Lower Compute Costs

Fewer distance calculations are required.

Excellent User Experience

Ideal for interactive AI applications requiring real-time responses.

Production Ready

Nearly every modern AI search engine uses ANN.

Examples include:

Azure AI Search
Azure SQL vector indexes
Azure Cosmos DB vector search
Pinecone
Milvus
Weaviate
Qdrant
FAISS
pgvector with ANN indexes

Disadvantages of ANN

Results Are Approximate

Occasionally, the true nearest neighbor may not be returned.

Instead, the algorithm returns vectors that are extremely close.

Slight Reduction in Recall

Typical recall values:

depending on index configuration.

Index Maintenance

ANN requires building and maintaining vector indexes.

Additional Memory Usage

Indexes consume additional storage.

ANN vs ENN Comparison

Feature	ENN	ANN
Accuracy	100%	Nearly 100%
Speed	Slower	Much faster
Scalability	Poor	Excellent
Uses Vector Index	No	Yes
CPU Usage	High	Lower
Memory Usage	Lower	Higher
Best for Small Data	Yes	Sometimes
Best for Large Data	No	Yes
Typical Production Choice	Rare	Very Common

Why ANN Is Usually Preferred

Most enterprise AI applications prioritize:

Fast responses
Interactive user experiences
Large knowledge bases
Millions of documents

Waiting several seconds for every search is unacceptable.

Therefore, ANN has become the industry standard for production semantic search.

For example:

A chatbot searching:

8 million support articles

cannot realistically compare every embedding.

Instead, ANN rapidly narrows the candidate set before computing exact similarity among only the most promising vectors.

Recall vs Accuracy

One of the most important concepts is recall.

Recall measures how many of the true nearest neighbors are successfully returned.

Example:

Suppose the true Top 10 neighbors are:

			
A
B
C
D
E
F
G
H
I
J

		

An ANN search returns:

			
A
B
C
D
E
F
G
H
I
K

		

Recall is:

9 / 10 = 90%

Although one neighbor is missing, the results are still highly useful for most AI applications.

Many ANN algorithms achieve recall rates above 99%.

Popular ANN Algorithms

Several indexing algorithms support ANN search.

Common examples include:

HNSW (Hierarchical Navigable Small World)

Most common modern ANN algorithm.

Advantages:

Very fast
Excellent recall
High-quality results
Widely used

IVF (Inverted File Index)

Partitions vectors into clusters.

Search examines only relevant clusters.

Good for extremely large datasets.

DiskANN

Optimized for very large vector collections stored partly on disk.

Designed for cloud-scale systems.

Product Quantization (PQ)

Compresses vectors to reduce memory usage.

Often combined with IVF.

Choosing Between ANN and ENN

Choose ENN When

Dataset is small
Exact results are mandatory
Benchmarking search quality
Scientific analysis
Compliance requires deterministic behavior
Testing vector models

Choose ANN When

Dataset contains millions of vectors
Response time matters
Building chatbots
Implementing RAG
Semantic document search
Recommendation systems
AI copilots
Enterprise knowledge bases

ANN in Azure SQL

Azure SQL’s vector search capabilities are designed to support scalable semantic search workloads.

When vector indexes are implemented, Azure SQL can perform ANN searches efficiently, making it practical to query very large embedding collections while maintaining excellent recall.

This enables AI-powered applications to combine:

Relational filtering
Vector similarity
SQL queries
AI inference

within a single database platform.

ANN and Hybrid Search

Many production applications combine ANN with traditional filtering.

Example:

A company stores:

20 million product embeddings

A customer searches:

“Wireless ergonomic keyboard”

The query first filters:

			
Category = Electronics
Brand = Microsoft
Price < $150

Then ANN searches only the filtered candidate vectors.

This combination improves:

Speed
Relevance
Scalability

DP-800 Exam Tips

Understand that ENN performs exhaustive comparisons, while ANN uses vector indexes to accelerate nearest-neighbor retrieval.
Remember that ANN trades a small amount of accuracy for significant gains in performance and scalability, making it the preferred option for production AI systems.
Be familiar with HNSW, IVF, and other ANN indexing techniques at a conceptual level.
Know that ENN is appropriate for small datasets, benchmarking, and scenarios requiring mathematically exact results.
Expect scenario-based questions asking which approach is best based on dataset size, latency requirements, scalability, and accuracy expectations.
Recognize that ANN is the default choice for RAG systems, semantic search, recommendation engines, AI assistants, and enterprise knowledge bases containing millions of embeddings.

Practice Exam Questions

Question 1

A company has built a Retrieval-Augmented Generation (RAG) solution that searches through 50 million document embeddings. Users expect responses within two seconds. Which vector search approach is the most appropriate?

A. Exact Nearest Neighbor (ENN) because it guarantees mathematically exact results for every query

B. Approximate Nearest Neighbor (ANN) because it provides low-latency searches while maintaining high recall

C. Sequential table scans because they avoid maintaining vector indexes

D. Full-text search because embeddings are not required for semantic search

Correct Answer: B

Explanation: ANN is specifically designed for large-scale vector datasets where fast response times are essential. It dramatically reduces search latency while maintaining very high recall, making it ideal for production RAG systems.

Question 2

A research laboratory is validating a new embedding model and requires every query to return the mathematically closest vectors with no approximation. Which search method should be used?

A. Hybrid search

B. Hierarchical Navigable Small World (HNSW)

C. Exact Nearest Neighbor (ENN)

D. Approximate Nearest Neighbor (ANN)

Correct Answer: C

Explanation: ENN compares the query vector against every stored vector, guaranteeing exact nearest-neighbor results. This makes it appropriate for benchmarking, scientific validation, and testing.

Question 3

What is the primary advantage of Approximate Nearest Neighbor (ANN) search over Exact Nearest Neighbor (ENN) search?

A. ANN always returns more accurate results.

B. ANN eliminates the need for vector embeddings.

C. ANN significantly improves search performance and scalability by reducing the number of vectors evaluated.

D. ANN only works with relational databases.

Correct Answer: C

Explanation: ANN achieves much faster searches by using specialized vector indexes to evaluate only the most promising candidate vectors instead of comparing every vector.

Question 4

A database contains approximately 2,500 embeddings used by a legal review application where accuracy is more important than response time. Which search strategy is most appropriate?

A. Approximate Nearest Neighbor (ANN)

B. Hybrid search

C. Semantic ranking

D. Exact Nearest Neighbor (ENN)

Correct Answer: D

Explanation: With a relatively small dataset and strict accuracy requirements, ENN is preferred because it guarantees exact nearest-neighbor results.

Question 5

Which statement best describes the concept of recall in Approximate Nearest Neighbor search?

A. It measures how quickly a query completes.

B. It measures the percentage of true nearest neighbors successfully returned.

C. It measures the amount of memory consumed by the vector index.

D. It measures the total number of vectors stored.

Correct Answer: B

Explanation: Recall measures how many of the actual nearest neighbors are retrieved by the ANN algorithm. Higher recall indicates results that more closely match those of an exact search.

Question 6

Which indexing algorithm is most commonly associated with modern ANN implementations due to its excellent balance of speed and recall?

A. HNSW (Hierarchical Navigable Small World)

B. B-tree

C. Hash index

D. Clustered columnstore index

Correct Answer: A

Explanation: HNSW is one of the most widely used ANN algorithms because it provides fast searches with excellent recall for large vector datasets.

Question 7

A development team notices that vector search performance decreases as the database grows from thousands to tens of millions of embeddings. Which architectural change is most likely to improve scalability?

A. Replace vector embeddings with keyword indexes.

B. Use ENN for every query.

C. Disable vector indexes.

D. Implement ANN with an appropriate vector index.

Correct Answer: D

Explanation: ANN combined with vector indexes is specifically designed to scale efficiently to millions or even billions of embeddings while maintaining acceptable accuracy.

Question 8

Which characteristic is typically associated with Exact Nearest Neighbor (ENN) search?

A. Uses approximation techniques to improve performance.

B. Compares only a subset of candidate vectors.

C. Performs exhaustive comparisons against every stored vector.

D. Requires HNSW indexing.

Correct Answer: C

Explanation: ENN performs a complete comparison against all stored vectors, ensuring mathematically exact results but requiring significantly more computation.

Question 9

An AI-powered product recommendation system serves millions of users each day. The recommendation engine must respond in milliseconds while maintaining highly relevant results. Which approach best meets these requirements?

A. Exact Nearest Neighbor (ENN)

B. Sequential vector scans

C. ANN using vector indexes

D. Full-table scans followed by sorting

Correct Answer: C

Explanation: ANN is optimized for production AI workloads that require low latency and high scalability while maintaining high-quality semantic search results.

Question 10

Which statement best summarizes the trade-off between ANN and ENN?

A. ENN sacrifices accuracy for better scalability.

B. ANN always returns identical results to ENN.

C. ENN requires vector indexes while ANN does not.

D. ANN slightly reduces accuracy in exchange for dramatically improved search performance and scalability.

Correct Answer: D

Explanation: The primary trade-off is that ANN accepts a small reduction in accuracy (typically maintaining 95–99%+ recall) to achieve significantly faster query performance and support very large datasets.

Go to the DP-800 Exam Prep Hub main page

AI, Azure AI, Databases, DP-800, Microsoft Certification August 1, 2026

Implement vector search (DP-800 Exam Prep)

This post is a part of the DP-800: Developing AI-Enabled Database Solutions Exam Prep Hub.
This topic falls under these sections:
Implement AI capabilities in database solutions (25–30%)
   --> Design and implement intelligent search
      --> Implement vector search

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Introduction

Implementing vector search is one of the foundational skills for building modern AI-enabled database applications. Vector search enables databases to retrieve information based on semantic meaning rather than exact keyword matches, making it essential for Retrieval-Augmented Generation (RAG), AI assistants, recommendation engines, semantic document search, knowledge management systems, and intelligent enterprise applications.

What Is Vector Search?

Traditional SQL queries search for exact values.

For example:

			
SELECT *
FROM Products
WHERE ProductName = 'Laptop';

WHERE Description LIKE '%wireless%'

These approaches rely on exact text matching.

However, AI applications often need to answer questions like:

“Find documents about reducing cloud costs.”

Relevant documents might contain:

Lower Azure spending
Optimize infrastructure expenses
Cloud cost optimization
Reduce operational costs

Although these documents contain different words, they share the same meaning.

Vector search enables databases to find these semantically related documents.

How Vector Search Works

Vector search consists of several stages.

			
User Query
↓
Embedding Model
↓
Query Vector
↓
Vector Similarity Search
↓
Nearest Neighbor Documents
↓
(Optional)
Large Language Model (LLM)

		

Instead of comparing text directly, the database compares numeric vector representations generated by an embedding model.

What Is a Vector?

A vector is a high-dimensional numerical representation of data.

Example:

			
"Azure SQL Database"
↓
[-0.134,
0.281,
0.998,
...
1536 dimensions]

		

Every document stored in the database has its own embedding vector.

When a user submits a query, the query is also converted into a vector.

The database then compares vectors mathematically to identify the most similar results.

Components of a Vector Search Solution

A complete vector search implementation includes several components.

1. Source Data

Examples include:

PDF files
Product catalogs
Emails
Knowledge articles
Web pages
Support tickets
SQL records

2. Embedding Model

The embedding model converts text into vectors.

Popular examples include:

Azure OpenAI Embeddings
OpenAI text embedding models
Sentence Transformers
Other compatible embedding models

The embedding model should remain consistent for both indexing and querying.

3. Vector Storage

Embeddings are stored inside the database.

Example table:

DocumentID	Content	Embedding
101	Product Manual	[1536 values]
102	FAQ	[1536 values]
103	Warranty Guide	[1536 values]

Modern SQL databases increasingly support dedicated vector data types.

4. Vector Index

Searching millions of vectors without an index would require comparing every vector.

Vector indexes organize embeddings for efficient similarity searches.

Common vector indexes include:

Flat (Exact Search)
HNSW
IVF
IVF + Product Quantization (PQ)

Approximate Nearest Neighbor (ANN) indexes are commonly used in production systems because they significantly reduce search latency while maintaining high recall.

5. Similarity Function

The database determines which vectors are closest.

Common similarity metrics include:

Cosine similarity
Euclidean distance
Dot product

Cosine similarity is the most common metric for semantic search.

Exact Search vs Approximate Search

Exact (Brute Force) Search

The database compares the query vector against every stored vector.

Advantages:

Perfect accuracy
Guaranteed nearest neighbors

Disadvantages:

Slow
Poor scalability

Best suited for:

Small datasets
Testing
Validation

Approximate Nearest Neighbor (ANN)

ANN indexes intelligently reduce the search space.

Advantages:

Extremely fast
Scales to millions or billions of vectors
Lower CPU utilization

Tradeoff:

Results are highly accurate but not mathematically perfect.

Most enterprise AI applications use ANN search.

Implementing Vector Search

A typical implementation follows these steps.

Step 1. Prepare Data

Collect the documents.

Examples:

Product manuals
Policies
Emails
Support articles

Clean the text by removing unnecessary formatting and duplicate content.

Step 2. Generate Embeddings

Use an embedding model to create vectors.

Example workflow:

			
Document
↓
Embedding Model
↓
1536-Dimensional Vector

		

Each document receives one or more embeddings.

Step 3. Store Embeddings

Store:

Original text
Metadata
Embedding vector

Example:

DocumentID	Category	Content	Embedding
501	HR	Vacation Policy	Vector
502	IT	VPN Setup	Vector

Metadata enables additional filtering during searches.

Step 4. Create a Vector Index

The vector index accelerates similarity searches.

Without an index:

			
Query
↓
Compare to every vector

With an ANN index:

			
Query
↓
Index
↓
Small candidate set
↓
Best matches

		

Step 5. Convert User Query

The user’s search query is embedded using the same embedding model.

Example:

			
"How do I connect remotely?"
↓
Embedding Model
↓
Query Vector

		

Consistency is critical. Using a different embedding model for queries than for indexed documents can significantly reduce search quality.

Step 6. Perform Similarity Search

The database compares the query vector with stored vectors.

Example SQL pseudocode:

			
SELECT TOP 5
    DocumentID,
    SimilarityScore
FROM Documents
ORDER BY VECTOR_DISTANCE(Embedding, @QueryVector);

		

The exact syntax varies depending on the database platform and vector search implementation.

Step 7. Return Results

The application retrieves the closest documents.

Example:

Rank	Document
1	VPN Configuration Guide
2	Remote Access FAQ
3	Employee Network Policy

Vector Search Workflow

			
Documents
↓
Generate Embeddings
↓
Store Vectors
↓
Create Vector Index
↓
User Query
↓
Generate Query Embedding
↓
Similarity Search
↓
Top Matching Documents

		

Filtering Vector Search Results

Many applications combine vector search with traditional SQL filtering.

Example:

			
Semantic Search
+
WHERE Department = 'Finance'
+
ORDER BY Similarity

		

This approach is often called hybrid filtering, allowing organizations to limit searches by structured metadata while still leveraging semantic similarity.

Examples of filters include:

Department
Date
Customer
Region
Security classification
Language

Hybrid Search

Hybrid search combines:

Keyword search
Full-text search
Vector search

Example:

			
Keyword Search
+
Vector Search
↓
Combined Ranking
↓
Final Results

		

Benefits include:

Higher relevance
Better handling of synonyms
Stronger ranking
Improved user satisfaction

Many enterprise AI search systems use hybrid search instead of vector search alone.

Using Vector Search in RAG

Retrieval-Augmented Generation relies heavily on vector search.

Workflow:

			
User Question
↓
Embedding
↓
Vector Search
↓
Relevant Documents
↓
LLM
↓
Grounded Response

		

Instead of relying solely on the LLM’s training data, the model uses retrieved documents as grounding data.

Benefits:

More accurate responses
Reduced hallucinations
Access to current organizational knowledge

Common Vector Search Scenarios

Enterprise Knowledge Search

Users ask natural language questions.

Example:

“How do I reset my VPN password?”

The database retrieves the most semantically relevant documentation.

Customer Support

Support engineers search:

“Printer won’t connect.”

Relevant troubleshooting documents are retrieved even if they use different wording.

Product Recommendation

Customers searching for:

“Comfortable running shoes”

may receive products described as:

Lightweight trainers
Cushioned athletic footwear
Marathon shoes

Legal Document Search

Law firms search by legal concepts rather than exact wording.

Healthcare Knowledge Bases

Clinicians retrieve similar cases based on symptoms rather than identical terminology.

Performance Considerations

Database developers should evaluate:

Search Latency

Users expect responses within milliseconds.

ANN indexes dramatically reduce latency.

Recall

Recall measures how many of the true nearest neighbors are returned.

Higher recall generally improves RAG quality.

Index Size

Larger indexes often improve retrieval quality but require more memory.

Memory Consumption

HNSW indexes typically consume more RAM than compressed indexes.

Index Build Time

Large vector indexes may require significant time to build.

Plan for maintenance windows when rebuilding indexes.

Update Frequency

Applications with frequent inserts and deletes should use index types that efficiently support incremental updates.

Common Implementation Mistakes

Using Different Embedding Models

Documents embedded with one model should not be searched using vectors generated by a different model.

Using the Wrong Similarity Metric

Many embedding models assume cosine similarity.

Using Euclidean distance or dot product incorrectly may reduce search accuracy.

Not Creating a Vector Index

Searching without an index performs poorly on large datasets.

Ignoring Metadata

Metadata filtering significantly improves result quality.

Returning Too Many Documents

Retrieving excessive documents increases latency and may overwhelm downstream LLMs in RAG systems.

Best Practices

Use the same embedding model for indexing and querying.
Choose a similarity metric recommended for the embedding model.
Use ANN indexes for production environments.
Combine vector search with metadata filters when appropriate.
Consider hybrid search for the highest-quality results.
Benchmark recall, latency, and throughput using realistic workloads.
Monitor index growth and rebuild or optimize indexes when necessary.
Store both embeddings and the original source content.

DP-800 Exam Tips

Remember these key points for the exam:

Vector search retrieves data based on semantic similarity rather than exact text.
Embeddings are numerical representations generated by AI models.
The same embedding model should be used for both indexing and querying.
Vector indexes improve search performance by reducing the number of vector comparisons.
Approximate Nearest Neighbor (ANN) indexes provide fast searches with high recall.
Cosine similarity is the most commonly used metric for semantic search.
Hybrid search combines keyword search with vector search to improve relevance.
Vector search is a core component of Retrieval-Augmented Generation (RAG).

Practice Exam Questions

Question 1

A company is building a chatbot that answers employee questions using internal policy documents. The solution converts both documents and user queries into embeddings before searching for relevant information.

What is the primary purpose of generating embeddings?

A. To compress documents for storage

B. To represent text numerically so semantic similarity can be measured

C. To encrypt sensitive information

D. To improve SQL transaction performance

Answer: B

Explanation:
Embeddings convert text into high-dimensional numerical vectors that capture semantic meaning. These vectors enable similarity comparisons that go beyond exact keyword matching.

Question 2

A developer plans to implement vector search against a database containing 30 million document embeddings.

Which approach provides the best balance between scalability and query performance?

A. Sequentially compare every vector

B. Use a clustered index

C. Use an Approximate Nearest Neighbor (ANN) vector index

D. Create additional foreign keys

Answer: C

Explanation:
ANN indexes are specifically designed to support efficient vector similarity searches across very large datasets while maintaining high recall and low latency.

Question 3

A user searches for:

“Affordable cloud storage”

The returned documents discuss:

Cost-effective cloud backup
Low-cost online storage
Budget-friendly data storage

Why were these documents returned?

A. SQL wildcard matching

B. Lexical keyword matching

C. Primary key lookup

D. Semantic similarity using vector search

Answer: D

Explanation:
Vector search retrieves content based on semantic meaning rather than identical words, enabling related concepts and synonyms to be found.

Question 4

Which statement best describes hybrid search?

A. It combines vector search with keyword or full-text search.

B. It stores vectors in multiple databases.

C. It replaces embeddings with SQL indexes.

D. It searches only relational columns.

Answer: A

Explanation:
Hybrid search combines traditional lexical search with semantic vector search, often producing more relevant and comprehensive search results.

Question 5

Why should the same embedding model be used for both document indexing and query generation?

A. It reduces storage costs.

B. It eliminates the need for vector indexes.

C. It ensures vectors exist in the same semantic space for meaningful comparisons.

D. It automatically creates SQL indexes.

Answer: C

Explanation:
Embeddings generated by different models may occupy different vector spaces, making similarity calculations unreliable and reducing retrieval quality.

Question 6

What is the primary function of a vector index?

A. Encrypt embedding vectors

B. Reduce the number of vector comparisons during searches

C. Compress relational tables

D. Replace SQL indexes

Answer: B

Explanation:
Vector indexes organize embeddings so the search engine evaluates only the most promising candidates instead of comparing every stored vector.

Question 7

A Retrieval-Augmented Generation (RAG) application performs vector search before sending retrieved documents to a large language model.

Why is this retrieval step important?

A. It reduces SQL storage requirements.

B. It converts SQL tables into vectors.

C. It grounds the model with relevant information, improving response accuracy.

D. It eliminates the need for embeddings.

Answer: C

Explanation:
RAG retrieves relevant documents that provide context to the LLM, helping produce accurate, current, and evidence-based responses while reducing hallucinations.

Question 8

Which SQL capability is most commonly combined with vector search to narrow search results to specific business data?

A. Metadata filtering using WHERE clauses

B. ALTER TABLE statements

C. Transaction logging

D. Foreign key constraints

Answer: A

Explanation:
Combining vector search with structured SQL filters allows applications to restrict results by attributes such as department, region, or document type while maintaining semantic relevance.

Question 9

A developer performs vector similarity searches without creating a vector index.

What is the most likely consequence?

A. Embeddings become corrupted.

B. Query performance decreases significantly as the dataset grows.

C. SQL transactions stop working.

D. Documents cannot be embedded.

Answer: B

Explanation:
Without a vector index, the system typically performs an exhaustive comparison against every stored vector, resulting in much slower query performance on large datasets.

Question 10

Which statement best summarizes the role of vector search in AI-enabled database applications?

A. It replaces relational databases.

B. It removes the need for SQL queries.

C. It automatically generates embeddings.

D. It enables retrieval of information based on semantic meaning instead of exact text matching.

Answer: D

Explanation:
Vector search is designed to retrieve semantically similar information by comparing embedding vectors, making it a foundational capability for intelligent search, recommendation systems, and RAG-based applications.

Go to the DP-800 Exam Prep Hub main page

AI, Azure AI, Databases, DP-800, Microsoft Certification August 1, 2026August 1, 2026

Implement hybrid search (DP-800 Exam Prep)

This post is a part of the DP-800: Developing AI-Enabled Database Solutions Exam Prep Hub.
This topic falls under these sections:
Implement AI capabilities in database solutions (25–30%)
   --> Design and implement intelligent search
      --> Implement hybrid search

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Introduction

Hybrid search is a core capability for modern AI-enabled database solutions because it combines the strengths of traditional keyword search and vector (semantic) search. By leveraging both lexical and semantic matching techniques, hybrid search delivers more accurate, relevant, and context-aware search results than either approach alone. Hybrid search is widely used in Retrieval-Augmented Generation (RAG) applications, enterprise knowledge bases, AI assistants, recommendation systems, and intelligent search platforms.

What Is Hybrid Search?

Hybrid search combines multiple search techniques into a single query, typically including:

Keyword search
Full-text search
Vector (semantic) search

Instead of relying on only one search method, hybrid search retrieves candidates from multiple search engines and combines the results using a ranking algorithm.

For example, consider a user searching for:

“How do I reduce Azure storage costs?”

A keyword search might find documents containing the exact terms:

Azure
Storage
Costs

A vector search might retrieve documents discussing:

Lower cloud expenses
Optimize storage spending
Reduce infrastructure costs

Hybrid search combines both result sets and ranks the most relevant documents at the top.

Why Hybrid Search Is Important

Neither keyword search nor vector search is perfect by itself.

Keyword Search Strengths

Keyword search excels at finding:

Exact product names
Error codes
File names
Database object names
Technical terminology

Example:

SQL72014

A keyword search finds documents containing that exact error code.

Keyword Search Weaknesses

Keyword search struggles with:

Synonyms
Different wording
Natural language
Conceptual relationships

Example:

Search:

“Vacation policy”

Document:

“Paid time off guidelines”

Although both describe the same concept, keyword search may not find the document.

Vector Search Strengths

Vector search understands meaning.

Example:

Search:

“Improve application speed”

Documents discussing:

Performance optimization
Query tuning
Faster database execution

can all be returned because their embeddings are semantically similar.

Vector Search Weaknesses

Vector search may struggle with:

Product IDs
Version numbers
Error codes
Exact names
Highly specialized terminology

Example:

Searching for:

SQL71561

works better with keyword search.

Hybrid Search Combines Both Approaches

			
User Query
↓
Keyword Search
+
Vector Search
↓
Combined Results
↓
Ranking
↓
Top Results

		

This allows users to benefit from both lexical precision and semantic understanding.

How Hybrid Search Works

A hybrid search implementation generally follows these steps.

Step 1. User Submits a Query

Example:

“How do I configure Azure SQL backups?”

Step 2. Keyword Search Executes

The database searches for:

Azure
SQL
Backups
Configure

using:

Full-text indexes
SQL predicates
Traditional search indexes

Step 3. Vector Search Executes

The same query is converted into an embedding.

			
Query
↓
Embedding Model
↓
Vector

		

The vector is compared against stored document embeddings.

Step 4. Merge Results

Suppose keyword search returns:

Document	Score
Backup Overview	95
SQL Backup Guide	90

Vector search returns:

Document	Score
Disaster Recovery	93
Data Protection	88

The system merges these candidate sets.

Step 5. Rank Results

The ranking engine evaluates:

Keyword relevance
Semantic similarity
Metadata
Popularity
Freshness
Business rules

The highest-ranking documents are returned.

Components of a Hybrid Search Solution

Source Documents

Examples include:

PDFs
Product documentation
Knowledge articles
Support tickets
Policies
Emails
SQL records

Full-Text Index

Supports traditional keyword searching.

Optimized for:

Exact phrases
Words
Wildcards
Boolean searches

Embedding Model

Generates vector representations for documents and queries.

Examples:

Azure OpenAI Embeddings
OpenAI embedding models
Sentence Transformers

The same embedding model should be used during indexing and querying.

Vector Index

Stores embeddings for efficient semantic search.

Examples:

HNSW
IVF
Flat index
Product Quantization (PQ)

Ranking Engine

Combines multiple signals into a single relevance score.

Search Pipeline

			
User Query
↓
Keyword Search
       \
        \
         Ranking Engine
        /
       /
Vector Search
↓
Combined Results

		

Both searches occur independently before the results are combined.

Ranking in Hybrid Search

Hybrid search is more than simply combining two result lists.

Each result receives a relevance score based on multiple factors.

Typical ranking signals include:

Keyword score
Vector similarity score
Document freshness
Popularity
User permissions
Metadata
Business importance

The ranking algorithm determines the final ordering.

Metadata Filtering

Hybrid search often includes structured SQL filters.

Example:

WHERE Department = 'Finance'

WHERE DocumentType = 'Policy'

The search becomes:

			
Keyword Search
+
Vector Search
+
Metadata Filters
↓
Ranking

		

Filtering improves both relevance and performance.

Hybrid Search in RAG

Hybrid search is commonly used in Retrieval-Augmented Generation.

Workflow:

			
User Question
↓
Hybrid Search
↓
Relevant Documents
↓
Large Language Model
↓
Grounded Response

		

Benefits include:

Higher-quality context
Reduced hallucinations
More complete retrieval
Better factual accuracy

Example Scenario

Suppose an employee asks:

“How do I access my benefits after changing jobs?”

Keyword search retrieves:

Benefits
Jobs

Vector search retrieves:

Employee transition
HR onboarding
Employment status changes

Hybrid search combines both sets, increasing the likelihood of returning the most relevant documents.

Hybrid Search vs Keyword Search

Feature	Keyword Search	Hybrid Search
Exact terms	Excellent	Excellent
Synonyms	Poor	Excellent
Natural language	Limited	Excellent
Error codes	Excellent	Excellent
Semantic understanding	None	Excellent
AI applications	Limited	Excellent

Hybrid Search vs Vector Search

Feature	Vector Search	Hybrid Search
Semantic understanding	Excellent	Excellent
Exact identifiers	Moderate	Excellent
Error codes	Moderate	Excellent
Product names	Moderate	Excellent
Natural language	Excellent	Excellent
Overall relevance	High	Very High

Benefits of Hybrid Search

Better Relevance

Combines multiple search signals.

Handles Synonyms

Users don’t need exact wording.

Supports Technical Queries

Keyword search finds:

Error codes
File names
Product names

Supports Natural Language

Vector search understands concepts.

Improved User Satisfaction

Users receive better search results.

Better RAG Responses

The LLM receives more relevant context.

Challenges

Increased Complexity

Two search systems must be maintained.

Higher Resource Usage

Both keyword and vector searches execute.

Ranking Tuning

Determining the correct weighting between keyword and semantic scores may require experimentation.

Embedding Maintenance

Embeddings should be regenerated when source content changes significantly or when migrating to a new embedding model.

Common Hybrid Search Scenarios

Enterprise Knowledge Bases

Employees search documentation using natural language.

Customer Support

Support agents retrieve troubleshooting articles using both error codes and descriptive questions.

Product Catalogs

Customers search using product names, descriptions, or intent.

Healthcare

Clinicians search using symptoms while also matching standardized medical terminology.

Legal Research

Lawyers search using statutes, case numbers, and legal concepts.

Financial Services

Analysts search reports using account identifiers and descriptive business questions.

Best Practices

Combine full-text and vector search for production AI applications.
Use the same embedding model during indexing and querying.
Create appropriate full-text and vector indexes.
Apply metadata filters whenever possible.
Tune ranking weights using representative user queries.
Evaluate both precision and recall during testing.
Continuously monitor search quality and user feedback.
Refresh embeddings when source documents change significantly.
Secure search results using role-based access controls and document permissions.

DP-800 Exam Tips

Remember these key points for the exam:

Hybrid search combines traditional keyword search with vector search.
Keyword search excels at exact terms, identifiers, and technical strings.
Vector search excels at semantic meaning and natural language.
Hybrid search generally provides better relevance than either approach alone.
Ranking combines multiple signals, including lexical relevance, semantic similarity, and metadata.
Metadata filtering improves both performance and result quality.
Hybrid search is commonly used in Retrieval-Augmented Generation (RAG) systems.
The same embedding model should be used for both indexing and querying to ensure meaningful vector comparisons.

Practice Exam Questions

Question 1

A company is building an AI-powered knowledge base that must support searches for both exact error codes and natural language questions.

Which search approach is most appropriate?

A. Hybrid search

B. Keyword search only

C. Vector search only

D. Relational indexing only

Answer: A

Explanation:
Hybrid search combines keyword and vector search, enabling both exact matching for error codes and semantic matching for natural language queries.

Question 2

A user searches for:

“Improve database response time”

The system returns documents discussing query tuning, indexing strategies, and SQL optimization, even though those exact words were not used.

Which component enabled this behavior?

A. Full-text search

B. Vector search

C. Clustered indexes

D. Foreign key constraints

Answer: B

Explanation:
Vector search compares embeddings that capture semantic meaning, allowing conceptually related documents to be retrieved even when different wording is used.

Question 3

What is the primary purpose of the ranking engine in a hybrid search solution?

A. Generate document embeddings

B. Create vector indexes

C. Combine and order results from multiple search methods

D. Encrypt search results

Answer: C

Explanation:
The ranking engine merges results from keyword and vector searches and orders them using relevance signals such as lexical score, semantic similarity, freshness, and metadata.

Question 4

Which type of query is generally handled most effectively by keyword search?

A. “How can I reduce cloud expenses?”

B. “Best practices for disaster recovery”

C. “Ways to improve SQL performance”

D. “SQL71561”

Answer: D

Explanation:
Exact identifiers such as error codes, product names, and version numbers are best handled using keyword or full-text search.

Question 5

Why is hybrid search commonly used in Retrieval-Augmented Generation (RAG) applications?

A. It eliminates the need for embeddings.

B. It improves retrieval quality by combining lexical and semantic matching.

C. It replaces large language models.

D. It removes the need for vector indexes.

Answer: B

Explanation:
Hybrid search retrieves more comprehensive and relevant information than either keyword or vector search alone, providing higher-quality context to the LLM.

Question 6

A search solution first performs keyword search, then vector similarity search, and finally combines both result sets.

Which step typically follows next?

A. Delete duplicate documents from the database.

B. Recreate all vector indexes.

C. Rank the combined results using relevance signals.

D. Generate new embeddings for every document.

Answer: C

Explanation:
After gathering candidate documents, the ranking engine evaluates multiple relevance signals to determine the final ordering presented to the user.

Question 7

Which statement best describes metadata filtering in hybrid search?

A. It replaces vector search.

B. It restricts search results using structured attributes such as department or document type.

C. It converts SQL tables into embeddings.

D. It automatically updates document embeddings.

Answer: B

Explanation:
Metadata filters narrow the search scope using structured data while still allowing semantic and keyword search within the filtered dataset.

Question 8

A developer configures hybrid search using one embedding model for indexing documents and a different embedding model for processing user queries.

What is the most likely result?

A. Improved semantic accuracy.

B. Reduced index size.

C. Faster query execution.

D. Lower-quality semantic matches because vectors occupy different embedding spaces.

Answer: D

Explanation:
Embeddings produced by different models are generally not directly comparable, leading to poorer semantic similarity calculations and less relevant search results.

Question 9

Which advantage does hybrid search have over vector search alone?

A. It supports exact matching for identifiers while preserving semantic search capabilities.

B. It eliminates the need for full-text indexes.

C. It guarantees mathematically perfect search results.

D. It removes the need for metadata.

Answer: A

Explanation:
Hybrid search enhances vector search by adding lexical matching, making it more effective for exact terms such as product names, file names, and error codes.

Question 10

Which best practice should a database developer follow when implementing hybrid search?

A. Use different embedding models for documents and queries.

B. Disable metadata filtering to improve semantic search.

C. Combine full-text search, vector search, and structured filtering to improve relevance.

D. Use exhaustive vector search for every production workload regardless of size.

Answer: C

Explanation:
A well-designed hybrid search solution combines lexical search, semantic search, and structured metadata filtering to maximize relevance, scalability, and user satisfaction in AI-enabled database applications.

Go to the DP-800 Exam Prep Hub main page

AI, Artificial Intelligence (AI), Azure AI, Databases, DP-800, Microsoft Certification August 1, 2026

Evaluate performance of vector and hybrid search (DP-800 Exam Prep)

This post is a part of the DP-800: Developing AI-Enabled Database Solutions Exam Prep Hub.
This topic falls under these sections:
Implement AI capabilities in database solutions (25–30%)
   --> Design and implement intelligent search
      --> Evaluate performance of vector and hybrid search

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Introduction

Evaluating the performance of vector and hybrid search solutions is a critical responsibility when developing AI-enabled database applications. While implementing vector search is important, ensuring that the search solution consistently returns accurate, relevant, fast, and scalable results is equally essential. Database developers must understand how to measure search quality, optimize retrieval performance, balance latency with accuracy, and monitor search systems over time.

This knowledge is especially important for applications such as:

Retrieval-Augmented Generation (RAG)
Enterprise knowledge search
AI-powered chatbots
Document retrieval
Recommendation systems
Intelligent search applications

Why Performance Evaluation Matters

Unlike traditional SQL queries that typically return deterministic results, vector and hybrid search systems retrieve documents based on statistical similarity.

This means there is always a balance between:

Search speed
Search accuracy
Resource consumption
Scalability

A search system that responds instantly but returns irrelevant documents is not useful.

Likewise, a system that returns perfect results but requires several seconds per query may not satisfy user expectations.

The goal is to optimize the entire search experience.

Key Performance Metrics

Several metrics are commonly used to evaluate vector and hybrid search.

Query Latency

Latency measures how long a search takes to return results.

Example:

			
User Query
↓
120 ms
↓
Results Returned

		

Lower latency improves user experience.

Typical enterprise AI search systems aim for response times measured in milliseconds.

Factors affecting latency include:

Index type
Dataset size
Hardware resources
Number of search algorithms executed
Network latency
Number of retrieved documents

Throughput

Throughput measures the number of search requests a system can process within a given time.

Examples:

Searches per second
Queries per minute

Higher throughput enables more concurrent users.

Throughput depends on:

CPU
Memory
Index efficiency
Parallel processing
Database architecture

Recall

Recall measures how many relevant documents are successfully retrieved.

Example:

Relevant documents:

			
A
B
C
D
E

		

Returned documents:

			
A
B
C
X
Y

		

Recall:

3 / 5 = 60%

Higher recall generally improves RAG quality because more relevant information is available to the large language model.

Precision

Precision measures how many returned documents are actually relevant.

Example:

Returned:

			
A
B
C
X
Y

		

Relevant:

			
A
B
C

Precision:

3 / 5 = 60%

High precision reduces irrelevant search results.

F1 Score

The F1 Score combines precision and recall into a single metric.

It is especially useful when both false positives and false negatives matter.

Higher F1 scores indicate a better overall balance between retrieving relevant documents and avoiding irrelevant ones.

Mean Reciprocal Rank (MRR)

MRR measures how highly the first relevant result appears in the ranked list.

Example:

Relevant document positions:

Query	First Relevant Result
Query 1	Rank 1
Query 2	Rank 2
Query 3	Rank 4

Higher MRR indicates users find relevant information more quickly.

MRR is commonly used when evaluating question-answering systems and RAG applications.

Normalized Discounted Cumulative Gain (NDCG)

NDCG measures:

Ranking quality
Position of relevant documents
Graded relevance

Unlike recall, NDCG rewards placing the most relevant documents near the top.

This is especially important because users rarely read beyond the first few search results.

Evaluating Vector Search

When evaluating vector search, developers typically measure:

Recall
Precision
Latency
Index build time
Memory usage
Storage requirements

Index Performance

Questions include:

How quickly are searches completed?
How much memory does the index require?
How long does index creation take?
How efficiently are inserts handled?

Search Quality

Evaluate:

Are similar documents retrieved?
Are unrelated documents excluded?
Are synonyms recognized?
Does semantic similarity match user expectations?

Evaluating Hybrid Search

Hybrid search combines:

Full-text search
Vector search
Metadata filtering
Ranking algorithms such as Reciprocal Rank Fusion (RRF)
Optional semantic reranking

Because more components participate, additional evaluation is necessary.

Ranking Quality

Developers evaluate whether:

Exact matches appear near the top.
Semantically relevant documents are included.
Duplicate results are minimized.
Ranking is consistent.

Hybrid Relevance

Example query:

“Reduce Azure costs”

Good hybrid results may include:

Azure cost optimization
Cloud spending reduction
Budget management
Reserved capacity guidance

Poor hybrid results may include unrelated Azure topics.

Measuring Retrieval Quality

Many organizations create benchmark datasets.

Example:

Question:

“How do I configure VPN access?”

Expected documents:

VPN Setup Guide
Remote Access Policy
Authentication Configuration

The search system is evaluated based on whether these expected documents appear in the returned results.

Human Evaluation

Automated metrics cannot evaluate every aspect of search quality.

Organizations often perform manual reviews.

Experts examine:

Relevance
Completeness
Ranking quality
Consistency

Human evaluation is particularly valuable for RAG applications.

Offline Evaluation

Offline testing uses historical datasets.

Advantages:

Repeatable
Safe
Fast
No production impact

Developers compare:

Multiple embedding models
Index types
Similarity metrics
Ranking algorithms

Online Evaluation

Online evaluation uses live users.

Common techniques include:

A/B Testing

Group A:

Current search system

Group B:

New search implementation

Metrics compared include:

Click-through rate
User satisfaction
Search success
Session completion

User Feedback

Collect feedback such as:

Helpful
Not Helpful

User feedback helps improve future search tuning.

Factors Affecting Vector Search Performance

Embedding Quality

Poor embeddings reduce retrieval quality regardless of index performance.

Always choose embedding models appropriate for the domain.

Similarity Metric

Common choices:

Cosine similarity
Dot product
Euclidean distance

Using the wrong metric can reduce search accuracy.

Vector Index Type

Different index types provide different tradeoffs.

Index	Speed	Recall	Memory
Flat	Slow	Highest	Moderate
HNSW	Very Fast	Very High	High
IVF	Fast	High	Moderate
IVF + PQ	Very Fast	Moderate-High	Low

Candidate Set Size

Returning more candidate documents often increases recall.

However:

Latency increases.
More data must be reranked.
LLM token usage increases in RAG.

Balance is important.

Metadata Filtering

Filtering improves:

Precision
Latency

Example:

WHERE Department = 'Finance'

Searching fewer documents reduces processing time while improving relevance.

Evaluating Hybrid Search Components

Keyword Search

Evaluate:

Exact matches
Phrase matching
Synonym handling
Technical terminology

Vector Search

Evaluate:

Semantic understanding
Related concepts
Context awareness

Reciprocal Rank Fusion (RRF)

Evaluate:

Ranking consistency
Combined relevance
Candidate diversity

Semantic Reranking

Evaluate:

Final ranking quality
User satisfaction
Response accuracy

Common Performance Bottlenecks

Missing Vector Index

Searching every embedding significantly increases latency.

Poor Embeddings

Weak embeddings reduce semantic quality.

Excessive Candidate Retrieval

Retrieving hundreds of documents unnecessarily increases reranking and LLM processing time.

Large Embedding Dimensions

Higher-dimensional embeddings require:

More storage
More memory
More computation

Frequent Index Rebuilds

Rebuilding indexes too frequently can consume unnecessary resources.

Use incremental updates where supported.

Optimization Techniques

Choose the Correct Index

Examples:

Small datasets → Flat
Medium datasets → HNSW
Very large datasets → IVF or IVF + PQ

Tune Candidate Count

Retrieve only the number of documents needed.

Use Metadata Filters

Reduce unnecessary searches.

Optimize Embeddings

Select high-quality embedding models.

Use Hybrid Search

Combining lexical and semantic search generally improves relevance.

Apply Semantic Reranking

Use reranking on a limited candidate set to improve final result quality.

Performance Monitoring

Production systems should monitor:

Average latency
Peak latency
Recall
Precision
Throughput
Memory usage
Index size
Search failures
User satisfaction
Search abandonment rate

Monitoring enables proactive tuning as data volumes and usage patterns evolve.

Best Practices

Benchmark search quality before deployment.
Measure both latency and retrieval quality.
Use benchmark datasets with known expected results.
Combine automated metrics with human evaluation.
Tune candidate retrieval size based on workload.
Select the appropriate vector index for dataset size.
Monitor production search metrics continuously.
Refresh embeddings when source data changes significantly.
Evaluate hybrid search using realistic business queries.
Test changes in a staging environment before production deployment.

DP-800 Exam Tips

Remember these key points for the exam:

Vector search performance should be evaluated using both speed and retrieval quality metrics.
Recall measures how many relevant documents are retrieved.
Precision measures how many returned documents are relevant.
MRR evaluates how quickly users encounter the first relevant result.
NDCG evaluates the quality of document ranking.
Hybrid search should be evaluated as a complete pipeline, including keyword search, vector search, RRF, and optional semantic reranking.
Metadata filtering improves both precision and performance.
Human evaluation remains important because automated metrics cannot fully measure search usefulness.
Production systems should continuously monitor latency, recall, throughput, and user satisfaction.

Practice Exam Questions

Question 1

A database developer is evaluating a vector search solution. Which metric measures the percentage of retrieved documents that are actually relevant?

A. Recall

B. Latency

C. Precision

D. Throughput

Answer: C

Explanation:
Precision measures the proportion of retrieved documents that are relevant. High precision indicates that the search results contain few irrelevant documents.

Question 2

A Retrieval-Augmented Generation (RAG) application consistently retrieves only three of the five relevant documents for most user queries.

Which performance metric is primarily affected?

A. Recall

B. Mean Reciprocal Rank (MRR)

C. Throughput

D. Query latency

Answer: A

Explanation:
Recall measures how many relevant documents are successfully retrieved. Missing relevant documents lowers the recall score.

Question 3

Which metric evaluates how quickly users encounter the first relevant search result?

A. F1 Score

B. Mean Reciprocal Rank (MRR)

C. Precision

D. Throughput

Answer: B

Explanation:
MRR evaluates the ranking position of the first relevant result, rewarding systems that place useful documents near the top of the results list.

Question 4

A search solution returns highly relevant documents, but users complain that responses take several seconds.

Which performance metric should the development team investigate first?

A. Index build time

B. Storage utilization

C. Embedding dimension

D. Query latency

Answer: D

Explanation:
Query latency measures the time required to return search results. High latency negatively impacts the user experience, even when retrieval quality is good.

Question 5

Which statement best describes hybrid search performance evaluation?

A. Only vector search accuracy needs to be measured.

B. Only keyword search latency matters.

C. Evaluation should include keyword search, vector search, ranking quality, and overall retrieval performance.

D. Performance is determined solely by embedding size.

Answer: C

Explanation:
Hybrid search combines multiple retrieval methods, so developers should evaluate the complete search pipeline rather than a single component.

Question 6

A developer increases the number of candidate documents retrieved before semantic reranking.

What is the most likely tradeoff?

A. Lower latency and reduced memory usage

B. Higher recall but increased latency and reranking costs

C. Reduced recall with faster indexing

D. Elimination of vector indexing requirements

Answer: B

Explanation:
Retrieving more candidate documents increases the likelihood of finding relevant information but also increases processing time, reranking effort, and LLM token usage.

Question 7

Why is human evaluation still valuable when assessing AI-powered search systems?

A. Automated metrics cannot fully measure user relevance and usefulness.

B. Human evaluation eliminates the need for benchmark datasets.

C. Human reviewers create vector indexes.

D. Human evaluation replaces latency testing.

Answer: A

Explanation:
While automated metrics quantify retrieval quality, human reviewers can assess contextual relevance, completeness, and overall usefulness from a user perspective.

Question 8

Which optimization technique can improve both search precision and query performance?

A. Increasing embedding dimensions indefinitely

B. Removing vector indexes

C. Using metadata filtering to narrow the search scope

D. Returning every matching document

Answer: C

Explanation:
Metadata filters reduce the number of candidate documents that must be searched, improving both relevance and performance.

Question 9

Which performance metric evaluates the overall quality of document ranking by giving more credit when highly relevant documents appear near the top of the results?

A. Recall

B. Precision

C. Throughput

D. Normalized Discounted Cumulative Gain (NDCG)

Answer: D

Explanation:
NDCG measures ranking quality by considering both document relevance and the position of documents in the ranked results, rewarding systems that place the most relevant items first.

Question 10

A development team wants to compare two different embedding models before deploying a new search solution.

Which evaluation approach is most appropriate?

A. Online A/B testing only

B. Disable benchmarking and rely on production feedback

C. Conduct repeatable offline testing using benchmark datasets with expected search results

D. Measure only CPU utilization

Answer: C

Explanation:
Offline benchmarking with known datasets enables developers to compare embedding models, similarity metrics, and indexing strategies safely and consistently before deploying changes to production.

Go to the DP-800 Exam Prep Hub main page

AI, AI-103, Azure AI, Microsoft Certification May 25, 2026

Configure semantic search, hybrid search, and vector search for Grounding (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement information extraction solutions (10–15%)
   --> Build retrieval and grounding pipelines
      --> Configure semantic search, hybrid search, and vector search for Grounding

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

For the AI-103: Develop AI Apps and Agents on Azure certification exam, one of the most important modern AI concepts is understanding how to configure and use:

Semantic search
Vector search
Hybrid search

These technologies are foundational to:

Retrieval-Augmented Generation (RAG)
AI agents
Enterprise copilots
Knowledge mining systems
Grounded AI applications

In modern Azure AI architectures, these search methods help Large Language Models (LLMs) retrieve relevant enterprise content so responses are accurate, current, and grounded in trusted data.

Why Grounding Matters

LLMs such as those used through Azure OpenAI Service are powerful, but they have limitations:

They may hallucinate
Their training data may be outdated
They do not automatically know private organizational data
They cannot inherently access enterprise documents

Grounding solves this problem.

What Is Grounding?

Grounding means providing an AI model with relevant external data during inference.

Example:

			
User Question:
"What is our company travel reimbursement policy?"
AI Workflow:
1. Retrieve policy document chunks
2. Provide chunks to LLM
3. Generate grounded answer

		

Without grounding, the model might invent an answer.

With grounding, the response is based on actual company documentation.

Core Azure Services Used

Several Azure services commonly appear in grounding architectures.

Service	Purpose
Azure AI Search	Search indexes, vector search, semantic ranking
Azure OpenAI Service	Embeddings generation and LLM responses
Azure Blob Storage	Store source documents
Azure AI Document Intelligence	Extract document content
Azure AI Foundry	Build AI agents and orchestration workflows

Understanding Search Types

There are three major search approaches you must understand for AI-103:

Search Type	Main Purpose
Keyword Search	Exact text matching
Semantic Search	Meaning-based ranking
Vector Search	Embedding similarity
Hybrid Search	Combines keyword + semantic + vector

Traditional Keyword Search

Traditional search relies on:

Exact matches
Tokens
Lexical analysis

Example:

			
Search Query:
"reset password"

Documents containing:

"reset password"

will rank highly.

However, keyword search struggles with:

Synonyms
Context
Natural language intent

Example:

"change account credentials"

may not match well.

Semantic Search

What Is Semantic Search?

Semantic search improves retrieval by understanding:

Context
Meaning
Intent
Relationships between words

Instead of only exact keywords, semantic search uses language understanding to improve ranking quality.

How Semantic Search Works

Semantic search:

Interprets user intent
Understands relationships between phrases
Re-ranks search results
Produces more relevant answers

Example:

			
User Query:
"How do I update my login information?"

Semantic search may retrieve:

"Instructions for changing account credentials"

even without exact keyword matches.

Semantic Ranking

In Azure AI Search, semantic ranking:

Reorders results based on relevance
Uses deep language models
Improves natural language search experiences

Important AI-103 point:

Semantic search enhances ranking, but it does not replace vector search.

Semantic Captions and Answers

Azure AI Search semantic search can generate:

Semantic captions
Semantic answers

Semantic Captions

Short highlighted summaries from documents.

Semantic Answers

Direct answers extracted from indexed content.

Example:

			
Question:
"What is the vacation accrual policy?"
Semantic answer:
"Employees accrue 10 vacation days annually."

Vector Search

What Is Vector Search?

Vector search uses embeddings to retrieve semantically similar content.

Instead of matching keywords, vector search compares numerical vectors.

What Are Embeddings?

Embeddings are numerical representations of content.

Words or concepts with similar meanings are placed near each other in vector space.

Example:

			
"car"
"automobile"
"vehicle"

These concepts become mathematically similar vectors.

Embedding Generation

Embeddings are commonly generated using models in:

Azure OpenAI Service
Azure AI Foundry models

Typical embedding workflow:

Chunk documents
Generate embeddings
Store vectors in search index
Generate embedding for user query
Retrieve nearest vectors

Vector Search Workflow

			
Document Chunk
      ↓
Embedding Model
      ↓
Vector Embedding
      ↓
Stored in Search Index

		

Query workflow:

			
User Query
     ↓
Embedding Model
     ↓
Query Vector
     ↓
Nearest Neighbor Search

		

Nearest Neighbor Search

Vector databases use similarity calculations such as:

Cosine similarity
Euclidean distance

The system retrieves content with the closest vectors.

Important exam concept:

Vector similarity measures semantic closeness.

Configuring Vector Search in Azure AI Search

To configure vector search, you typically:

Create vector-enabled fields
Generate embeddings
Store embeddings in index
Configure vector search profiles
Execute vector queries

Example Vector Index Structure

Example fields:

Field	Type
id	String
content	String
contentVector	Collection(Float)
title	String

The vector field stores embeddings.

Vector Dimensions

Embedding models produce vectors with fixed dimensions.

Example:

1536 dimensions

Important:

The vector field dimension must match the embedding model output.

Hybrid Search

What Is Hybrid Search?

Hybrid search combines:

Keyword search
Semantic ranking
Vector similarity

This is one of the most important AI-103 topics.

Why Hybrid Search Matters

Each search method has strengths and weaknesses.

Method	Strength
Keyword search	Exact matching
Semantic search	Better ranking/context
Vector search	Conceptual similarity

Hybrid search combines all three for optimal retrieval quality.

Hybrid Search Architecture

			
User Query
   ↓
Keyword Search
   +
Vector Search
   ↓
Combined Results
   ↓
Semantic Re-ranking
   ↓
Top Grounding Results

		

This architecture is extremely common in enterprise RAG systems.

Why Hybrid Search Is Recommended

Hybrid search improves:

Recall
Precision
Relevance
Context matching
Grounding quality

This reduces hallucinations and improves AI responses.

Retrieval-Augmented Generation (RAG)

What Is RAG?

RAG combines:

Retrieval systems
External knowledge
Generative AI

Workflow:

			
User Query
   ↓
Search Retrieval
   ↓
Relevant Chunks
   ↓
LLM Prompt
   ↓
Grounded Response

		

Grounding Pipeline Example

			
Documents in Blob Storage
        ↓
Azure AI Search Indexer
        ↓
Chunking
        ↓
Embedding Generation
        ↓
Vector Index
        ↓
Hybrid Search Retrieval
        ↓
Azure OpenAI Prompt
        ↓
Grounded Response

		

This pipeline appears frequently in AI-103 scenarios.

Chunking and Retrieval Quality

Chunking directly affects search quality.

Good chunks:

Preserve meaning
Fit token limits
Improve embedding relevance

Poor chunking causes:

Incomplete answers
Lost context
Lower retrieval accuracy

Semantic vs Vector Search

Semantic Search	Vector Search
Improves ranking	Retrieves by embedding similarity
Language understanding	Numerical vector comparison
Works with textual relevance	Works with semantic proximity
Re-ranking layer	Retrieval mechanism

Important:

These technologies complement each other.

Filtering in Grounding Pipelines

Metadata filtering improves retrieval quality.

Common filters:

Department
Security level
Document type
Date
Language

Example:

department = Finance

This limits retrieval scope.

Security Trimming

Enterprise grounding systems often require:

RBAC
Document-level security
Identity-aware retrieval

Important exam concept:

Users should retrieve only authorized content.

Performance Optimization

Key optimization techniques:

Proper chunk sizes
Embedding caching
Hybrid search
Metadata filtering
Incremental indexing
Semantic ranking

Hybrid search

Important AI-103 Exam Tips

Know These Core Concepts

Concept	Key Purpose
Embeddings	Vector representation
Vector search	Semantic retrieval
Semantic ranking	Better result ordering
Hybrid search	Combined retrieval
Grounding	Providing trusted context
Chunking	Breaking documents into manageable pieces

Frequently Tested Knowledge Areas

Expect questions involving:

RAG architectures
Embedding generation
Vector-enabled indexes
Hybrid retrieval
Semantic ranking
Grounding pipelines
Azure AI Search configuration
Chunking strategies

Final Thoughts

Semantic search, vector search, and hybrid search are foundational technologies for modern AI systems on Azure.

For AI-103, focus heavily on:

How embeddings work
When to use vector search
Why hybrid search is recommended
How semantic ranking improves results
How grounding reduces hallucinations
How Azure AI Search integrates with Azure OpenAI

These concepts are central to enterprise AI agents, copilots, and generative AI applications.

B. It uses language understanding to improve relevance

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Microsoft Certification May 25, 2026May 25, 2026

Choose the appropriate Foundry Services for generative tasks, Grounding, Vector Search, Agent Workflows, or Multimodal Processing (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Plan and manage an Azure AI solution (25–30%)
   --> Choose the appropriate Foundry services for generative AI and agents
      --> Choose the Appropriate Foundry Services for generative tasks, Grounding, Vector Search, Agent Workflows, or Multimodal Processing

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

One of the core responsibilities of an Azure AI developer is selecting the correct Azure AI Foundry services and supporting Azure technologies for specific AI workloads.

The AI-103 certification exam places significant emphasis on understanding how Azure AI Foundry services support:

Generative AI tasks
Grounding and Retrieval-Augmented Generation (RAG)
Vector search
AI agent workflows
Multimodal processing

Modern AI solutions are composed of multiple services working together rather than a single AI model.

For example:

A chatbot may require an LLM, vector search, embeddings, grounding, and agent orchestration.
A document assistant may require multimodal processing, OCR, embeddings, and RAG.
An AI agent may require tool calling, memory, orchestration, and workflow management.

Understanding which Foundry services to use in each scenario is critical both for the AI-103 exam and for real-world Azure AI development.

What Is Azure AI Foundry?

Azure AI Foundry is Microsoft’s unified AI development platform for:

Building AI applications
Developing AI agents
Managing models
Orchestrating workflows
Evaluating AI systems
Implementing responsible AI controls

Azure AI Foundry provides:

Model access
Prompt engineering tools
Agent frameworks
Retrieval and grounding tools
Evaluation systems
Safety controls
Deployment and monitoring capabilities

It integrates with many Azure AI services including:

Azure OpenAI
Azure AI Search
Azure AI Vision
Azure AI Language
Azure AI Document Intelligence
Azure AI Content Safety

Understanding the Core Service Categories

For the AI-103 exam, you should understand how Foundry services align to these major AI solution categories:

Generative AI services
Grounding and RAG services
Vector search services
Agent workflow services
Multimodal processing services
Evaluation and safety services

Generative AI Services

What Are Generative AI Services?

Generative AI services enable applications to:

Generate text
Summarize content
Create conversations
Produce code
Generate structured outputs
Perform reasoning tasks
Support AI copilots and assistants

The primary Foundry-related service for generative AI is:

Azure OpenAI Service

Azure OpenAI Service

Azure OpenAI provides access to advanced foundation models such as:

GPT models
GPT-4-class reasoning models
Multimodal GPT models
Embedding models
Audio-capable models

Azure OpenAI is commonly used for:

Chatbots
AI copilots
Content generation
AI agents
Coding assistants
Summarization
Question answering

When to Use Azure OpenAI

Use Azure OpenAI when the solution requires:

Natural language generation
Conversational AI
Complex reasoning
Function/tool calling
AI agents
Summarization
Code generation
Long-context processing

Example Generative AI Scenario

Scenario

A company wants to create an AI assistant that:

Answers employee questions
Summarizes internal documents
Generates emails
Uses enterprise data

Recommended Services:

Azure OpenAI
Azure AI Search
Embedding models
RAG architecture

Reason:

Azure OpenAI provides the conversational and reasoning capabilities.

Grounding and Retrieval-Augmented Generation (RAG)

What Is Grounding?

Grounding refers to providing AI models with reliable external data sources so responses are based on factual and current information.

Without grounding, LLMs may:

Hallucinate
Provide outdated information
Generate inaccurate answers

Grounding improves:

Accuracy
Relevance
Reliability
Enterprise trustworthiness

What Is Retrieval-Augmented Generation (RAG)?

RAG combines:

Retrieval systems
Embedding models
Vector search
Generative AI models

The workflow typically includes:

Convert documents into embeddings
Store vectors in a vector index
Convert user query into embeddings
Retrieve relevant content
Inject retrieved content into the LLM prompt
Generate grounded response

Azure Services Used for RAG

Common Azure services used for grounding and RAG include:

Azure AI Search
Azure OpenAI
Embedding models
Azure Storage
Azure Cosmos DB (optional)
Azure SQL Database with vector support

Azure AI Search

Azure AI Search is a core service for:

Vector search
Hybrid search
Semantic search
Enterprise retrieval
RAG pipelines

It enables applications to:

Index documents
Perform semantic retrieval
Store vector embeddings
Execute hybrid search queries

Finding conceptually similar documents even without exact keywords.

Hybrid Search

Combines:

Keyword search
Semantic ranking
Vector search

Hybrid search often produces the best retrieval quality.

When to Use Azure AI Search

Use Azure AI Search when applications require:

RAG
Semantic retrieval
Vector similarity search
Enterprise document retrieval
Knowledge-base search
Hybrid search scenarios

Example Grounding Scenario

Scenario

A healthcare chatbot must answer questions using the latest internal policy documents.

Recommended Services:

Azure OpenAI
Azure AI Search
Embedding models

Reason:

RAG enables grounded responses using current enterprise documents.

Vector Search Services

What Is Vector Search?

Vector search retrieves information based on semantic similarity rather than exact text matching.

Documents and queries are converted into numerical vectors called embeddings.

Similar meanings produce similar vectors.

Embedding Models

Embedding models transform content into vector representations.

These embeddings support:

Similarity matching
Semantic retrieval
Recommendation systems
RAG pipelines

Azure Services Supporting Vector Search

Azure AI Search

Primary enterprise vector search platform.

Azure Cosmos DB

Can support vector indexing and similarity search.

Useful for:

Globally distributed systems
High-scale AI applications

Azure SQL Database

Supports vector operations in modern AI workloads.

Useful for:

Structured enterprise systems
Integrated relational and AI workloads

Choosing the Correct Vector Search Service

Use Azure AI Search When:

Building enterprise RAG systems
Implementing hybrid search
Using semantic ranking
Creating AI copilots

Use Azure Cosmos DB When:

Global distribution is required
Massive scale is needed
NoSQL flexibility is important

Use Azure SQL Database When:

AI functionality must integrate with relational data
Existing SQL systems already exist

Agent Workflow Services

What Are AI Agents?

AI agents are AI systems capable of:

Reasoning
Planning
Tool usage
Multi-step execution
Task automation
Dynamic decision-making

Unlike basic chatbots, agents can:

Take actions
Call APIs
Use memory
Execute workflows
Interact with systems

Azure AI Foundry Agent Capabilities

Azure AI Foundry supports agent development with:

Tool calling
Function calling
Prompt orchestration
Workflow execution
Agent memory
Retrieval integration

Prompt Flow

Prompt Flow is a key Foundry tool for building:

AI workflows
Prompt chains
Tool orchestration
Agent pipelines
Multi-step AI systems

Prompt Flow helps developers:

Test prompts
Connect services
Evaluate outputs
Build reusable workflows

Tool Calling and Function Calling

LLMs can interact with external systems using:

Tool calling
Function calling

Examples:

Query databases
Call REST APIs
Retrieve documents
Send emails
Trigger workflows

This is a critical AI-103 topic.

Agent Workflow Scenario

Scenario

An AI travel assistant must:

Search flights
Check hotel pricing
Access calendars
Generate itineraries

Recommended Services:

Azure OpenAI
Prompt Flow
Agent orchestration tools
Tool/function calling

Reason:

This solution requires multi-step agent workflows.

Multimodal Processing Services

What Is Multimodal Processing?

Multimodal AI systems process multiple types of input such as:

Text
Images
Audio
Video
Documents

These systems combine multiple modalities to improve understanding.

Azure Services for Multimodal Processing

Common services include:

Azure OpenAI multimodal models
Azure AI Vision
Azure AI Document Intelligence
Azure AI Speech

Azure AI Vision

Azure AI Vision supports:

Image analysis
Object detection
OCR
Face analysis
Caption generation
Scene understanding

Use Azure AI Vision when applications require:

Image processing
Computer vision
OCR tasks
Visual analysis

Azure AI Document Intelligence

Azure AI Document Intelligence extracts structured information from documents such as:

Invoices
Receipts
Contracts
Forms
IDs

Capabilities include:

OCR
Key-value extraction
Layout analysis
Table extraction
Custom models

Azure AI Speech

Azure AI Speech supports:

Speech-to-text
Text-to-speech
Translation
Voice assistants
Real-time transcription

Choosing the Correct Multimodal Service

Use Azure AI Vision When:

Analyzing images
Detecting objects
Extracting text from images

Use Azure AI Document Intelligence When:

Extracting structured document data
Processing forms and invoices
Understanding layouts and tables

Use Azure AI Speech When:

Processing voice input
Building voice assistants
Performing speech transcription

Use Azure OpenAI Multimodal Models When:

Combining conversational reasoning with image understanding
Performing multimodal interactions
Building advanced AI assistants

Safety and Responsible AI Services

AI solutions require safety and governance.

Azure AI Foundry includes services such as:

Azure AI Content Safety
Content filtering
Prompt injection detection
Harm detection

These services help:

Detect unsafe content
Prevent abuse
Improve compliance
Support responsible AI development

Evaluation and Monitoring Services

Azure AI Foundry provides evaluation tools for:

Groundedness
Relevance
Accuracy
Latency
Cost
Toxicity
Hallucination detection

Evaluation is important because AI quality can vary significantly.

Choosing the Correct Foundry Service

The AI-103 exam frequently tests scenario-based service selection.

Scenario 1: Enterprise Knowledge Chatbot

Requirements:

Conversational AI
Enterprise document grounding
Semantic retrieval

Recommended Services:

Azure OpenAI
Azure AI Search
Embedding models

Scenario 2: Invoice Processing System

Requirements:

OCR
Table extraction
Structured document understanding

Recommended Services:

Azure AI Document Intelligence

Scenario 3: AI Agent with Workflow Automation

Requirements:

Tool usage
API calls
Multi-step execution

Recommended Services:

Azure OpenAI
Prompt Flow
Agent orchestration tools

Scenario 4: Image Analysis Application

Requirements:

Object detection
Image captioning
OCR

Recommended Services:

Azure AI Vision

Scenario 5: Semantic Product Search

Requirements:

Similarity search
Semantic retrieval
Vector indexing

Recommended Services:

Azure AI Search
Embedding models

Common AI-103 Exam Tips

Understand Service Roles

Know which services specialize in:

Generative AI
Retrieval
Search
Vision
Speech
Documents
Agent workflows

Know Common Service Pairings

Azure OpenAI + Azure AI Search

Used for:

RAG systems
Enterprise chatbots
Knowledge assistants

Azure OpenAI + Prompt Flow

Used for:

AI agents
Multi-step workflows
Tool orchestration

Azure AI Vision + Azure OpenAI

Used for:

Multimodal assistants
Visual question answering

Remember Hybrid Search

Hybrid search combines:

Vector search
Keyword search
Semantic ranking

This is commonly tested on AI-103.

Know When Specialized Services Are Better

Example:

Azure AI Document Intelligence is better for invoice extraction than using only a general-purpose LLM.

Summary

Selecting the appropriate Azure AI Foundry services is essential for building scalable, accurate, and cost-effective AI applications.

For the AI-103 exam, you should understand:

Which services support generative AI
How grounding and RAG work
When to use vector search
How AI agents are orchestrated
Which services support multimodal processing
How Azure AI Search integrates into enterprise AI systems
How Prompt Flow supports AI workflows
The role of specialized services like Vision and Document Intelligence

Strong service-selection skills are critical for both certification success and real-world Azure AI solution development.

Azure AI Speech provides speech recognition and transcription capabilities.

Go to the AI-103 Exam Prep Hub main page