Explanation:
Correct Sequence:
Add the prebuilt domain ToDo
Add a new application
Train the application
Publish the application
Comprehensive Detailed Explanation
You are building a Conversational Language Understanding (CLU) model for a chatbot that supports task tracking. To minimize development time, the best approach is to use a prebuilt domain (like ToDo) instead of building intents/entities manually.
Steps in correct order:
Add the prebuilt domain ToDo
Prebuilt domains in CLU provide ready-to-use intents and entities for common scenarios (e.g., calendar, email, ToDo).
This significantly reduces development time since you don't need to create all intents/entities manually.
Add a new application
You must first create a CLU application that uses the prebuilt domain.
The application acts as the container for intents, entities, and utterances.
Train the application
Training is required after adding intents, entities, and utterances (or using a prebuilt domain).
This ensures the model can classify and extract information correctly.
Publish the application
Once trained, you must publish the application so it can be accessed via an endpoint and integrated into the chatbot.
Incorrect Actions in this Case
Add example utterances # Not required if you're using the prebuilt ToDo domain (utterances are already included).
Correct Sequence:
Add the prebuilt domain ToDo
Add a new application
Train the application
Publish the application
Microsoft References
Conversational Language Understanding (CLU) overview
Prebuilt domains in CLU (LUIS ToDo example)
Train and publish CLU models

The requirements state:
All AI solution responses must have a confidence score # 70%.
If the response confidence score is < 70%, the response must be improved by human input.
Members of the Consultant-Bookkeeper group must be able to process financial documents, which includes performing manual review when the AI confidence is below threshold.
Looking at the provided JSON:
" fields " : {
" ReceiptType " : {
" type " : " string " ,
" valueString " : " Itemized " ,
" confidence " : 0.672
},
" MerchantName " : {
" type " : " string " ,
" valueString " : " Tailwind " ,
" confidence " : 0.913
}
}
ReceiptType.confidence = 0.672 # this is below 0.7.
MerchantName.confidence = 0.913 # this is above 0.7.
Therefore, the correct condition for triggering manual review is:
documentResults.fields. < field > .confidence < 0.7
Now, evaluating the options:
A). documentResults.docType == " prebuilt:receipt "
Always true for receipts, does not check confidence. Not correct.
B). documentResults.fields.*.confidence < 0.7
This is the correct general expression: trigger manual review whenever any field confidence is below 0.7.
C). documentResults.fields.ReceiptType.confidence > 0.7
This would bypass manual review when ReceiptType has high confidence. The requirement is to trigger review when confidence < 0.7, so this is the opposite.
D). documentResults.fields.MerchantName.confidence < 0.7
This only checks one field (MerchantName). In the JSON, MerchantName has confidence 0.913 ( > 0.7), so this condition would not trigger, but ReceiptType clearly needs review. Too narrow.
The answer: B. documentResults.fields.*.confidence < 0.7
Microsoft References
Azure AI Document Intelligence - Confidence scores
Human-in-the-loop for Document Intelligence

Explanation:


To detect hateful content with Azure AI Foundry Content Safety - Text , you should read the category analysis results returned by the analyze_text call. The response exposes a collection named categories_analysis, where each item contains the analyzed category (e.g., TextCategory.HATE) and its severity level.
Hence:
Iterate over response.categories_analysis, filter the item where item.category == TextCategory.HATE.
Print the severity using hate_result.severity.
This uses category analysis (not blocklist matches), which is the correct mechanism for detecting hate content with a severity score.
Microsoft References
Azure AI Content Safety - Analyze text (Python quickstart/samples): iterate response.categories_analysis, check TextCategory.HATE, read item.severity.
Azure AI Content Safety - Text categories and severity levels: explains categories (Hate, Violence, Sexual, Self-harm) and severity output.