* The requirement is to allow User1 to add custom data sources to an Azure OpenAI resource (AI1).
* Following the principle of least privilege means granting only the specific rights required.
* The Cognitive Services OpenAI Contributor role allows management of Azure OpenAI resources, including attaching custom data sources for RAG (retrieval-augmented generation).
* The Cognitive Services Contributor role is broader and grants access to all cognitive services, which violates least privilege.
* Search Service Contributor and Search Index Data Contributor are roles for Azure AI Search, not for managing data sources on Azure OpenAI.
Microsoft References:
* Azure built-in roles: Cognitive Services OpenAI Contributor

In Azure Cognitive Service for Language (Question Answering), when users ask natural language questions, the service tries to match them to knowledge base content and synonyms.
In the scenario, the model correctly answers "What is the price of < product > ?" but fails on "How much does < product > cost?" .
This indicates that the service does not automatically recognize "price" and "cost" as equivalent terms.
Creating an entity for cost will not fix this issue. Entities in custom text classification or conversational language understanding are used for extracting structured data (like dates, names, or locations) from text, not for synonym matching in question answering.
The correct solution is to add alternate phrasing (synonyms/alternate questions) in the QnA project for each knowledge base entry. For example, under the QnA pair that contains "What is the price of < product > ?" , you would add "How much does < product > cost?" as an alternate question. This way, both variations trigger the same answer.
Therefore, the proposed solution (create an entity for cost) does not meet the goal.
The answer: B. No
Microsoft References
Add alternative questions to improve matching - Azure AI Language Question Answering Improve accuracy with synonyms and alternate phrasing Overview of Question Answering in Azure AI Language

Explanation:
Detect the incoming language:
Service: Speech to Text
Reasoning: The Speech to Text service can transcribe spoken language into text and includes language identification capabilities, allowing the system to detect whether the caller is speaking French or English.
Respond in the callers ' own language:
Service: Text to Speech
Reasoning: The Text to Speech service can convert text responses into spoken language in the detected language (French or English), enabling the system to respond to callers in their own language.
Ordered Mapping:
Detect the incoming language: Speech to Text
Respond in the callers ' own language: Text to Speech
Box 1: Text Analytics
The Language Detection feature of the Azure Text Analytics REST API evaluates text input for each document and returns language identifiers with a score that indicates the strength of the analysis.
Box 2: Translator
Translator is a cloud-based neural machine translation service that is part of the Azure Cognitive Services family of REST APIs. Translator can be used with any operating system and powers many Microsoft products and services used by thousands of businesses worldwide to perform language translation and other language- related operations.
Reference:
https://docs.microsoft.com/en-us/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to- language-detection
https://docs.microsoft.com/en-us/azure/cognitive-services/translator/translator-overview

Explanation:

Explanation:
Step 1: Create a new project and load sample documents
Create a new project. Projects store your configurations and settings.
Step 2: Label the sample documents
When you create or open a project, the main tag editor window opens.
Step 3: Train a custom model.
Finally, train a custom model.
Reference:
https://docs.microsoft.com/en-us/azure/applied-ai-services/form-recognizer/label-tool