AI-102 Practice Question: Implement knowledge mining and document intelligence solutions
A company uses Azure AI Search to index documents from an Azure SQL Database. They need to ensure that deleted rows in the database are also removed from the search index during incremental indexing. They have configured the data source with change detection policies. What should they do to enable deletion detection?
⚠ Common exam trap
The trap here is assuming that change detection policies automatically handle deletions, when in fact a separate soft delete policy is required.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a soft delete column to the table that indicates when a row is deleted, and configure the data source with a soft deletion policy that references that column.
To enable deletion detection for Azure SQL Database in Azure AI Search, you must implement a soft delete column in the table and configure the data source with a soft deletion policy that references that column. The indexer then uses this column to identify and remove deleted documents from the index during incremental indexing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the indexer to use the high water mark change detection policy and set the deletion detection policy to 'none'.
Why it's wrong here
The high water mark policy tracks changes but does not detect deletions. Without a deletion detection policy, deleted rows remain in the index. Setting deletion detection to 'none' explicitly disables it, so deletions would not be propagated. This approach would leave stale documents in the index.
- ✗
Create a SQL trigger that calls the Azure AI Search REST API to delete the document when a row is deleted.
Why it's wrong here
While a SQL trigger could call the REST API, this is a custom solution that requires additional code and is not the built-in mechanism. It also may not be reliable or scalable. The native soft delete policy is the recommended and supported approach for Azure SQL Database deletion detection.
- ✗
Use a view that filters out deleted rows and configure the indexer to use that view as the data source.
Why it's wrong here
Using a view that filters out deleted rows would prevent the indexer from seeing deletions; it would only see the remaining rows. The indexer would not know which documents to remove from the index because it would not have a record of the deleted rows. This approach fails to propagate deletions.
- ✓
Add a soft delete column to the table that indicates when a row is deleted, and configure the data source with a soft deletion policy that references that column.
Why this is correct
Azure AI Search supports soft delete detection for Azure SQL Database. You must add a column (e.g., IsDeleted) to the table and set its value to true or a timestamp when a row is deleted. Then, in the data source definition, configure a soft deletion policy that specifies this column. The indexer will then remove corresponding documents from the index during incremental runs.
Go deeper
Related to this question
About these practice questions
This AI-102 question is part of Courseiva's 761-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This AI-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI-102 exam.