In order to improve query productivity, you decide to use suggester as offered in Azure Cognitive search. You enable suggestions on “city” as the key field. The response will provide users with matching documents. Review the code snippet given below and complete it by choosing the most appropriate query parameter to limit the search to 5 cities: 
<pre>POST /indexes/city/docs/suggest?api-version=2020-06-30 
{
"search": "new",
"............................": 5,
"suggesterName": "suggester1"
}
</pre>
 

Answer options:

A.select
B.top
C.filter
D.fuzzy

Correct Answer: B
Option A is incorrect. A select parameter is used when you need to include additional fields for differentiation. Hence it is not the correct parameter of choice here.
Option B is correct. Here is the completed code snippet. Parameter top is used for control search results to 5 cities.
<pre>POST /indexes/city/docs/suggest?api-version=2020-06-30 
{
"search": "new",
"top": 5,
"suggesterName": "suggester1"
}
</pre>
Option C is incorrect. Filter parameter uses filterable fields to provide results. Given the scenario, it is not an appropriate parameter.
Option D is incorrect. A fuzzy parameter requires a boolean value. It helps find missing or substituted characters in the search text. Given the scenario, it is not an appropriate parameter choice.
Reference: 
To learn more about autocomplete and suggestions in Azure cognitive search, use the link given below: 

https://docs.microsoft.com/en-us/azure/search/search-add-autocomplete-suggestions