Refer to the exhibit. You are creating an Azure AI Search index. You want to enable semantic search using the 'content' field as both the title and the content. However, you receive an error that semantic search cannot be configured. What is the most likely reason?
Semantic search requires at least one field in title, content, or keywords; contentFields is empty.
Why this answer
Option D is correct because semantic search in Azure AI Search requires at least one field specified in the 'contentFields' list to provide the textual content for semantic ranking. If the 'contentFields' list is empty, the service cannot extract semantic meaning from the index, resulting in the configuration error. The 'content' field can serve as both title and content if properly assigned, but the error indicates the list itself is missing entries.
Exam trap
The trap here is that candidates may assume the 'content' field is inherently valid for semantic search without realizing the semantic configuration requires explicit assignment of fields to the 'contentFields' list, and an empty list triggers the error regardless of the field's properties.
How to eliminate wrong answers
Option A is wrong because 'Edm.String' is the standard field type for semantic search content; semantic search specifically requires fields of type 'Edm.String' that are also searchable. Option B is wrong because the error message about semantic search configuration does not relate to the field's searchable attribute; a non-searchable field would cause a different error when attempting to use it in queries. Option C is wrong because semantic search does not require a sortable field for the title; the title field only needs to be searchable and of type 'Edm.String', and sorting is irrelevant to semantic ranking.