Microsoft AI-102 Actual Questions

Comprehensive Detailed Explanation

The screenshot shows a Bot Framework Composer dialog that collects user input:

user.name is an entity.

False.

user.name is a property in bot state (a variable), not an entity.

Entities are part of LUIS/NLU models (e.g., PersonName, DateTime).

The dialog asks for a user name and a user age and assigns appropriate values to the user.name and user.age properties.

True.

The dialog explicitly has:

A Bot Asks (Text) step → assigns user’s response to user.name .

A Bot Asks (Number) step → assigns response to user.age .

So the values are stored in those properties.

The chatbot attempts to take the first non-null entity value for userName or personName and assigns the value to user.name.

True.

On the right-hand side, the Value expression is:

=coalesce(@userName, @personName)

coalesce returns the first non-null value.

This means if userName entity is available, it is used; otherwise, personName is used.

That result is assigned to user.name .

Correct Answers:

No

Yes

Yes

Microsoft References

Bot Framework Composer - Manage variables and properties

Bot Framework Composer - Recognizers and entities

Coalesce function in Composer expressions

The wiki contains text in English, French and Portuguese.

Scenario: All planned projects must support English, French, and Portuguese.

The Document Extraction skill extracts content from a file within the enrichment pipeline. This allows you to take advantage of the document extraction step that normally happens before the skillset execution with files that may be generated by other skills.

Note: The Translator Text API will be used to determine the from language. The Language detection skill is not required.

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.

Correct Answer: B. documentResults.fields.*.confidence < 0.7

Microsoft References

Azure AI Document Intelligence – Confidence scores

Human-in-the-loop for Document Intelligence