Comprehensive Detailed Explanation along with All References available from Microsoft Azure AI Solution at the end of the explanation

Typing: In a .chat transcript, you can simulate the bot’s typing indicator with the Typing activity, optionally followed by a [Delay=...] . This matches the intent to pause before sending the next message.

AttachmentLayout=carousel: When sending multiple attachments (the two watch images), set the layout to carousel so the Emulator displays the attachments horizontally as a card carousel.

Adaptive Card attachment: The JSON file cards\watchProfileCard.json represents an Adaptive Card; specify adaptivecard so the Emulator renders the card.

Resulting .chat snippet (essentials):

user =User1

bot=watchbot

user : I want a new watch.

bot: [Typing][Delay= 3000 ]

bot: I can help you with that! Let me see what I can find.

bot: Her e ' s what I found.

bot:

[AttachmentLayout=carousel]

[Attachment=https://contoso.blob.core.windows.net/watch01.jpg]

[Attachment=https://contoso.blob.core.windows.net/watch02.jpg]

user: I like the first one.

bot: Sure, pulling up more information.

bot: [Attachment=cards\watchProfileCard.json adaptivecard]

user: That ' s nice! Thank you.

bot: Sure, you are most welcome!

References

Bot Framework Emulator transcript ( .chat ) activities and typing indicator: Bot Framework Activity schema; Emulator supports typing and delay in transcripts.

https://learn.microsoft.com/azure/bot-service/bot-service-debug-emulator

https://learn.microsoft.com/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference#activity-object

Attachment layout ( carousel / list ) for multiple attachments:

https://learn.microsoft.com/azure/bot-service/nodejs/bot-builder-nodejs-send-rich-cards#carousel-layout

Adaptive Cards in Bot Framework:

https://learn.microsoft.com/adaptive-cards/get-started/bots

https://learn.microsoft.com/azure/bot-service/bot-builder-howto-add-media-attachments#adaptive-cards

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

C: Analyze Receipt - Get Analyze Receipt Result.

Query the status and retrieve the result of an Analyze Receipt operation.

Request URL: https://{endpoint}/formrecognizer/v2.0-preview/prebuilt/receipt/analyzeResults/{resultId}

E: POST {Endpoint}/vision/v3.2/read/analyze

Use this interface to get the result of a Read operation, employing the state-of-the-art Optical Character Recognition (OCR) algorithms optimized for text-heavy documents.

Scenario: Contoso plans to develop a document processing workflow to extract information automatically from PDFs and images of financial documents

The document processing solution must be able to process standardized financial documents that have the following characteristics:

- Contain fewer than 20 pages.

- Be formatted as PDF or JPEG files.

- Have a distinct standard for each office.

*The document processing solution must be able to extract tables and text from the financial documents.

The document processing solution must be able to extract information from receipt images.

Can search content in different formats, including video

Audio and video insights (multi-channels). When indexing by one channel, partial result for those models will be available.

Keywords extraction: Extracts keywords from speech and visual text.

Named entities extraction: Extracts brands, locations, and people from speech and visual text via natural language processing (NLP).

Topic inference: Makes inference of main topics from transcripts. The 2nd-level IPTC taxonomy is included.

Artifacts: Extracts rich set of " next level of details " artifacts for each of the models.

Sentiment analysis: Identifies positive, negative, and neutral sentiments from speech and visual text.

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.

 Stream processing has access to the most recent data received or data within a rolling time window. → Yes

 Batch processing must occur immediately and have latency in the order of seconds or milliseconds. → No

 Stream processing is used for simple response functions, aggregates, or calculations such as rolling averages. → Yes

Comprehensive Detailed Explanation

Stream processing has access to the most recent data received or data within a rolling time window.

Correct.

Stream processing handles real-time or near real-time data.

It operates on a continuous data stream and often uses a rolling time window for analytics.

Answer: Yes

Batch processing must occur immediately and have latency in the order of seconds or milliseconds.

Incorrect.

Batch processing is designed for large volumes of data collected over time.

It typically has high latency (minutes, hours, or even days), not immediate execution.

Answer: No

Stream processing is used for simple response functions, aggregates, or calculations such as rolling averages.

Correct.

Common stream analytics tasks include event-driven responses, real-time aggregations, anomaly detection, and rolling averages.

Answer: Yes

Correct Answers:

Yes

No

Yes

Microsoft References

Batch vs. Stream processing in Azure

Azure Stream Analytics overview

Box 1: Azure Blob storage

At the start of the pipeline, you have unstructured text or non-text content (such as images, scanned documents, or JPEG files). Data must exist in an Azure data storage service that can be accessed by an indexer.

Box 2: Computer Vision API

Scenario: Provide users with the ability to search insight gained from the images, manuals, and videos associated with the products.

The Computer Vision Read API is Azure ' s latest OCR technology (learn what ' s new) that extracts printed text (in several languages), handwritten text (English only), digits, and currency symbols from images and multi-page PDF documents.

Box 3: Translator API

Scenario: Product descriptions, transcripts, and all text must be available in English, Spanish, and Portuguese.

Box 4: Azure Files

Scenario: Store all raw insight data that was generated, so the data can be processed later.

Box 1: " categories " : [ " Locations " , " Persons " , " Organizations " ],

Locations, Persons, Organizations are in the outputs.

Scenario: Contoso plans to develop a searchable knowledgebase of all the intellectual property

Note: The categories parameter is an array of categories that should be extracted. Possible category types: " Person " , " Location " , " Organization " , " Quantity " , " Datetime " , " URL " , " Email " . If no category is provided, all types are returned.

Box 2: { " name " : " entities " }

The include wikis, so should include entities in the outputs.

Note: entities is an array of complex types that contains rich information about the entities extracted from text, with the following fields

name (the actual entity name. This represents a " normalized " form)

wikipediaId

wikipediaLanguage

wikipediaUrl (a link to Wikipedia page for the entity)

etc.

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

If a bot uses multiple LUIS models and QnA Maker knowledge bases (knowledge bases), you can use the Dispatch tool to determine which LUIS model or QnA Maker knowledge base best matches the user input. The dispatch tool does this by creating a single LUIS app to route user input to the correct model.

Scenario: All videos must have transcripts that are associated to the video and included in product descriptions.

Product descriptions, transcripts, and all text must be available in English, Spanish, and Portuguese.

Step 1: Upload the video to blob storage

Given a video or audio file, the file is first dropped into a Blob Storage. T

Step 2: Index the video by using the Video Indexer API.

When a video is indexed, Video Indexer produces the JSON content that contains details of the specified video insights. The insights include: transcripts, OCRs, faces, topics, blocks, etc.

Step 3: Extract the transcript from the Video Indexer API.

Step 4: Translate the transcript by using the Translator API.