Your team is building an AI-powered search application using Azure AI Search with semantic ranking. During testing, the search results are not showing the expected relevance improvements. What should you check first?
Semantic ranking requires Standard S1 or higher and must be enabled in the service configuration.
Why this answer
Semantic ranking in Azure AI Search requires a service tier of at least Standard S1 (or higher) and the feature must be explicitly enabled on the index. Without meeting these prerequisites, the search results will not benefit from semantic reranking, regardless of other configurations. Therefore, confirming the service tier and semantic ranking enablement is the first and most critical check.
Exam trap
The trap here is that candidates often assume semantic ranking is automatically available on any paid tier or that configuration issues like CORS or RBAC are the root cause, when in fact the service tier and explicit enablement are the strict prerequisites.
How to eliminate wrong answers
Option A is wrong because CORS (Cross-Origin Resource Sharing) controls browser-based cross-domain requests and has no impact on the relevance improvements provided by semantic ranking. Option B is wrong because RBAC (Role-Based Access Control) assignments manage permissions for accessing the search service, not the activation or functionality of semantic ranking itself. Option D is wrong because the Free tier does not support semantic ranking at all; it is a limited tier with no SLA and lacks the capacity for semantic reranking, so ensuring it is on the Free tier would actually prevent the feature from working.