Microsoft Microsoft Azure AI Fundamentals (Updated Version) AI-901 Exam Dumps: Updated Questions & Answers (May 2026)

Evaluating model outcomes across demographic groups to reduce bias is an example of the Microsoft responsible AI principle of fairness .

The Microsoft responsible AI principle of fairness means AI systems should treat all people fairly and avoid unfair bias or discrimination across groups.

The other options are incorrect:

accountability means people and organizations remain responsible for AI systems and their effects.

privacy and security focuses on protecting data and controlling access.

transparency means users should understand when and how AI is being used, including system capabilities and limitations.

The requirement is to convert written customer notifications into natural-sounding spoken audio . This is speech synthesis , also known as text to speech .

Microsoft’s Azure Speech documentation describes text to speech as a capability that converts text into natural-sounding synthesized speech. Therefore, for playing written notifications over a phone system, the correct Azure Speech capability is speech synthesis .

Why the other options are incorrect:

A. speaker recognition identifies or verifies speakers by voice.

C. speech recognition converts spoken audio into text.

D. speech translation translates spoken audio between languages.

The Microsoft responsible AI principle of transparency requires that AI systems be explainable to users .

Transparency means users should understand when they are interacting with AI, what the system can and cannot do, and how outputs or predictions are generated at an appropriate level.

The other options map to different responsible AI principles:

protect sensitive user data = Privacy and security

reduce bias in decisions = Fairness

require human oversight = Accountability

When content is submitted to Azure Content Understanding in Foundry Tools, the analysis is asynchronous . This means the service does not return results immediately within the same HTTP request. Instead, it uses the standard Azure long-running operation (LRO) pattern — you call begin_analyze() to submit the content, which immediately returns a poller object, and then call poller.result() to wait for processing to complete and retrieve the structured extraction results.

Why the other options are wrong:

Synchronous is incorrect — the analysis pipeline involves multiple AI steps (OCR, speech transcription, schema mapping) that take time; a blocking synchronous call is not supported.

Returned only as unstructured plain text is incorrect — Azure Content Understanding returns richly structured JSON output with named fields mapped to your defined schema, not plain unstructured text.

Limited to OCR-only processing is incorrect — Content Understanding goes far beyond OCR; it supports document, audio, image, and video analyzers, and performs semantic field extraction using AI, not just character recognition.

This asynchronous design is consistent across all Azure AI services that perform complex, multi-step content processing.

Azure Content Understanding analyzers define the type of content to process, such as documents, images, audio, or video , and what to extract, such as text, layout, fields, transcripts, and structured JSON output. Microsoft lists base analyzer types such as prebuilt-document, prebuilt-audio, prebuilt-video, and prebuilt-image.

For scanned invoices in PDF format , the correct choice is document analyzer , because invoices are document/form content. Microsoft’s Content Understanding quickstart specifically uses the prebuilt-invoice analyzer to extract structured data from an invoice PDF.

For voicemail recordings in WAV format , the correct choice is audio analyzer , because voicemail is audio content. Content Understanding supports structured data extraction from audio files, and the analyzer reference identifies prebuilt-audio as the base analyzer for audio content.

Statement 1: Voice Live returns only transcribed text. = No

Voice Live is not limited to transcription. Microsoft documentation states that the Voice Live API supports real-time bidirectional voice applications, including speech recognition, text-to-speech synthesis, avatar streaming, animation data, and audio processing.

Statement 2: Voice Live requires you to separately implement speech to text and text to speech services. = No

Voice Live provides a single real-time voice API experience rather than requiring separate STT and TTS implementations for the conversational loop. Microsoft describes live AI voice conversations as combining speech capabilities for real-time interaction, and the Voice Live API includes speech recognition and text-to-speech synthesis features.

Statement 3: Voice Live combines speech to text, reasoning, and text to speech into a single conversational experience. = Yes

This is correct. Microsoft’s guidance explains that Azure OpenAI audio/realtime capabilities are for scenarios that combine audio with language understanding, reasoning, or generation in a single model call, and Voice Live supports real-time voice-enabled applications over WebSocket connections.

For vision-enabled Azure OpenAI / Microsoft Foundry model requests, image input can be provided by using an image URL or base64-encoded image data. Microsoft’s Azure OpenAI REST API reference states that the image content part URL field can contain either a URL of the image or the base64 encoded image data . It also states that the Responses API input_image.image_url value can be a fully qualified URL or a base64 encoded image in a data URL .

For a vision-enabled model, Microsoft documentation shows that multimodal prompts can include both text and image content in the same user message content array. Azure OpenAI vision models accept multimodal image-and-text input and return natural language responses.

The correct request structure is a user message with a content array containing both items, for example:

{

"role": "user",

"content": [

{"type": "input_text", "text": "What is in this image?"},

{"type": "input_image", "image_url": image_url}

]

}

This avoids sending separate requests and is therefore the best choice for quickest response time.

A and C are incorrect because they send the text and image separately.

B is incorrect because the image/question should be sent as a user message, while system messages are used for instructions and behavior.

The Model catalog is used for comparing and deploying a wide range of models for generative AI development in Microsoft Foundry.

Microsoft documentation states that the model catalog in Foundry portal is the hub for discovering and using a wide range of models to build generative AI applications . It also includes many models across providers such as Azure OpenAI, Mistral, Meta, Cohere, NVIDIA, and Hugging Face.

The Microsoft Learn module for Foundry models also states that the model catalog is used to explore and filter models , compare models using benchmark metrics , and deploy a model to an endpoint .

The completed code is:

poller = client.begin_analyze(

analyzer_id="invoice",

input_url=url

)

result = poller.result()

Azure Content Understanding analysis uses a long-running operation pattern. The Python SDK returns a poller from begin_analyze(), and Microsoft documentation states that the SDK poller handles polling automatically when you call .result() .

Therefore, to retrieve the analysis results after processing completes, the correct option is:

result

The other options are incorrect because status checks operation state, wait waits without returning the final analysis object, and get_results is not the method shown for retrieving the begin_analyze() result in this code pattern.