Question

A retail company exposes its Azure Cosmos DB for NoSQL product catalog through an Azure AI Search index using an indexer. Products are frequently discontinued, and when they are, the corresponding document is physically deleted from the Cosmos DB container. Users complain that discontinued products still appear in search results even after the indexer runs on schedule. Which action should you take so the indexer removes deleted products from the search index?

Accepted Answer

Enable the indexer's soft-delete deletion detection policy and add a soft-delete marker field to documents instead of physically deleting them.

Answer

Enable the high water mark change detection policy using the _ts field on the Cosmos DB documents.

Answer

Reset and re-run the indexer on a more frequent schedule so it performs a full re-crawl of the container each time.

Answer

Configure a field mapping that maps the Cosmos DB id property to the search index key field.