Exam AI-102 topic 1 question 32 discussion

A is the answer. https://learn.microsoft.com/en-us/azure/search/search-performance-analysis#throttling-behaviors Throttling occurs when the search service is at capacity. Throttling can occur during queries or indexing. From the client side, an API call results in a 503 HTTP response when it has been throttled. During indexing, there's also the possibility of receiving a 207 HTTP response, which indicates that one or more items failed to index. This error is an indicator that the search service is getting close to capacity. A simple fix to most throttling issues is to throw more resources at the search service (typically replicas for query-based throttling, or partitions for indexing-based throttling). However, increasing replicas or partitions adds cost, which is why it's important to know the reason why throttling is occurring at all. Investigating the conditions that cause throttling will be explained in the next several sections.

The answer is A. According Microsoft materials: A simple fix to most throttling issues is to throw more resources at the search service (typically replicas for query-based throttling, or partitions for indexing-based throttling).

I think the answer should be B. Aditional replicas can improve query latency. However, you can allocate up to 12 replicas in a Standard search service and 3 replicas in a Basic search service. As there is no information about the actual number of configured replicas, I think upgrading the princing tier is the only sure solution because it comes with more cpu and memory for each replica.

"add replicas" is correct.

Some question sets might have more than one correct solution,so A.

The correct answer is B. No. Here’s why: Adding replicas does not directly address the issue of query throttling in Azure Cognitive Search. Query throttling occurs when the service limits the number of requests it can handle within a given time frame. It is typically related to the service’s capacity, rate limits, and resource availability. To reduce the likelihood of query throttling, consider other factors such as: Service capacity: Ensure that your service tier (including replicas and partitions) can handle the query volume. Optimize query design: Efficiently structure your queries to minimize resource usage. Index composition: Smaller indexes tend to perform better, but also consider schema complexity and field attribution. Therefore, adding replicas alone does not meet the goal of reducing query throttling. You need to address other aspects of your search service to achieve better performance and avoid throttling

A is right.

According to Microsoft's training material: **Use the best service tier for your search needs** You've seen that you can scale out service tiers by adding more partitions. You can scale out with replicas if you need to scale because of an increase in load. You can also scale up your search service by using a higher tier.

add replicas can help read performance; write performance needs adding partittions

correct

The answer is correct.

Quote "In Cognitive Search, replicas are copies of your index." at https://learn.microsoft.com/en-us/azure/search/search-reliability

From : https://learn.microsoft.com/en-us/azure/search/search-performance-tips#index-size-and-schema However, if the index is right-sized, the only other calibration you can make is to increase capacity: either by adding replicas or upgrading the service tier So adding replicas and upgrading the sku is two valid answers for this question

Answer is correct

Shouldn't it be Cognitive Search with a higher tier?