Scenario Recap

You are building a streaming Speech-to-Text solution using the Speech SDK.

Input audio format: MP3 encoding

You must configure the audio stream format and the recognizer properly.

Code Analysis

Audio Format

For MP3 streams, the correct method is:

AudioStreamFormat.GetCompressedFormat(AudioStreamContainerFormat.MP3)

This creates an audio format object for compressed MP3 input.

Recognizer

Since the task is speech-to-text transcription, you need the SpeechRecognizer class.

Other options like KeywordRecognizer, SpeakerRecognizer, or SpeechSynthesizer are not appropriate (they handle keyword spotting, speaker identification, or text-to-speech).

Completed Code Snippet

var audioFormat = AudioStreamFormat.GetCompressedFormat(AudioStreamContainerFormat.MP3);

var speechConfig = SpeechConfig.FromSubscription( " 18c51a87-3a69-47a8-aedc-a54745f708a1 " , " westus " );

var audioConfig = AudioConfig.FromStreamInput(pushStream, audioFormat);

using ( var recognizer = new SpeechRecognizer(speechConfig, audioConfig))

{

var result = await recognizer.RecognizeOnceAsync();

var text = result.Text;

}

Final Answer (Answer Area Selections)

AudioFormat: AudioStreamFormat.GetCompressedFormat

Recognizer: SpeechRecognizer

Microsoft References

Speech SDK – AudioStreamFormat

SpeechRecognizer class

To “recognize geographic locations” in Azure AI Search enrichment, add the EntityRecognitionSkill to your skillset. This built-in cognitive skill performs named entity recognition (NER) and extracts entities such as locations, people, and organizations from text.

EntityLinkingSkill links already-recognized entities to a knowledge base (e.g., Wikipedia) and is not required just to detect locations.

DocumentExtractionSkill parses file content/structure.

AzureOpenAIEmbeddingSkill creates vector embeddings, not entities.

Microsoft References

Azure AI Search – Entity recognition skill (extracts entities including locations).

Azure AI Search – Entity linking skill (disambiguates entities to a knowledge base; not for initial recognition).

The scenario:

You are building an in-vehicle application that uses Azure AI Speech for text-to-speech (TTS).

Requirement: Optimize the quality of synthesized voice output.

You must choose the most appropriate SSML (Speech Synthesis Markup Language) attribute.

Option A – style attribute of the mstts:express-as element

Used to apply expressive styles like " cheerful, " " empathetic, " or " angry. "

Helpful for emotion/tone, but not specifically about audio quality for clarity in motor vehicles.

Option B – level attribute of the emphasis element

Controls how strongly certain words are emphasized.

Improves meaning and focus, but does not optimize overall voice quality.

Option C – pitch attribute of the prosody element ✅

The < prosody > element allows adjustments to pitch, rate, and volume.

Adjusting pitch directly affects the naturalness and clarity of the synthesized speech.

Especially useful in noisy environments such as cars, because modifying pitch can make speech stand out better against background noise.

This directly improves perceived quality of voice output.

Option D – effect attribute of the voice element

Used for special voice effects (like whispering).

Not typically used for general clarity or quality improvements.

Correct Answer: C. the pitch attribute of the prosody element

Microsoft References

SSML support in Azure AI Speech

Prosody element in SSML

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.

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

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: When the response confidence score is low, ensure that the chatbot can provide other response options to the customers.

When no good match is found by the ranker, the confidence score of 0.0 or " None " is returned and the default response is " No good match found in the KB " . You can override this default response in the bot or application code calling the endpoint. Alternately, you can also set the override response in Azure and this changes the default for all knowledge bases deployed in a particular QnA Maker service.

Choosing Ranker type: By default, QnA Maker searches through questions and answers. If you want to search through questions only, to generate an answer, use the RankerType=QuestionOnly in the POST body of the GenerateAnswer request.

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.

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.