10 free sample questions from a bank of 37, with the correct answers and explanations. No signup required — start practising right now.
Q1 - Correct answer: D. SpeechConfig.
Real-time spoken conversation in the Azure Speech SDK starts with a SpeechConfig: it carries your Speech resource key and region (or endpoint, host or authorization token) plus the source language, and you pass it into whichever engine you build. It answers "how do I reach the service", not "where does audio come from" or "how do I make audio".
SpeechConfig - the connection/configuration object: subscription key + region, endpoint, host or token, plus speech_recognition_language and service properties.SpeechRecognizer - speech-to-text engine; consumes SpeechConfig and an optional AudioConfig.SpeechSynthesizer - text-to-speech engine; also consumes SpeechConfig.AudioConfig / AudioOutputConfig - audio input selection (default microphone, file, stream) and audio output selection (file or stream).The stem asks which class "configures the connection to the Azure Speech service". That is precisely the role of SpeechConfig, created like speechsdk.SpeechConfig(subscription="YourSpeechKey", region="YourSpeechRegion") or from an endpoint / host / token. Every conversation turn - recognized user speech and synthesized replies - depends on that object holding the right credentials, region and language.
AudioOutputConfig - describes where synthesized audio is written, e.g. AudioOutputConfig(filename="output.wav"). It is output plumbing for speech synthesis and contains no connection information.SpeechSynthesizer - the text-to-speech engine. Real-time conversation needs it only to speak the agent's reply; it does not configure the connection to the service.AudioConfig - selects the audio input (default microphone, a WAV file, a push stream). You pass it to a recognizer to say where sound comes from, which is a different concern from how you authenticate and where you connect.Bucket every Speech SDK class into config / audio-IO / engine before you read the options. "Configure the connection" is always SpeechConfig; "read from microphone" is AudioConfig; "write to file or stream" is AudioOutputConfig; "recognize" and "synthesize" are the two engines.
Q33 - Correct answer: B. the Analyze API in Content Understanding.
Azure Content Understanding in Foundry Tools is driven by analyzers. You submit content (document, image, audio or video) to the Analyze operation of the analyzer you built or picked, and the service returns structured fields plus markdown/transcript content. Everything else on this row is either a different service or a different kind of API.
extract, generate, classify).POST {endpoint}/contentunderstanding/analyzers/{analyzerId}:analyze?api-version=2025-11-01; the REST reference summarises it as "Extract content and fields from input." Results come back asynchronously, so the SDK hands you a poller.transcriptPhrases, fields, key frames and timing data, which is what a video-understanding app consumes.The question asks how the application "extracts structured information from the videos". Structured extraction in Content Understanding is the analyzer's job, and the operation that runs it is the Analyze API. Submit the video URL or binary to the analyzer, poll the operation, then read fields (and transcriptPhrases) out of the result.
Learn the mapping: "extract structured fields from documents / audio / video / images" -> Azure Content Understanding analyzer + Analyze operation. "Describe an image" -> Azure AI Vision. "Explain, summarise or draft text" -> a generative AI model on Azure OpenAI Service.
Q3 - Correct answer: A. system instructions.
Foundry agents are defined by text. The instructions field states the agent's role - "you are a returns specialist for Contoso" - and the rules it must follow, and that text is replayed into every turn. Nothing about temperature, quota or token ceilings makes an agent behave like a particular role.
instructions - persistent, server-side prompting: "An agent defines core behavior. Once created, it ensures consistent responses in user interactions without repeating instructions each time."max_tokens - a deployment rate limit and a response-length ceiling respectively; capacity and cost controls.In the Foundry SDK an agent is created with a definition such as PromptAgentDefinition(model=..., instructions="You are a helpful assistant that answers general questions"). Role, audience, tone and hard boundaries all live in that string, which is why instructions - and only instructions - make the agent "follow a specific role and behavior".
Agent questions split cleanly: identity and behaviour -> instructions; output style -> temperature / Top P; spend and length -> max completion tokens; capacity -> TPM and deployment rate limits. Never pick a knob from the wrong column.
Q34 - Correct answer: B. client.extract_key_phrases().
"Return a list of important topics from unstructured text" is the textbook definition of key phrase extraction in Azure AI Language (Foundry Tools). The Python client method that does it is client.extract_key_phrases(...), which returns the salient phrases for each document. The other three methods on that client return something structurally different.
azure-ai-textanalytics) - TextAnalyticsClient; the docs' quickstart calls response = client.extract_key_phrases(documents = documents)[0] and then iterates response.key_phrases.extract_key_phrases() is the only method on the client that returns the main talking points of a body of text as a list of phrases, which is exactly the "list of important topics" the requirement asks for. It is synchronous and stateless, so it fits a request-response application.
client.begin_extract_summary() - a summarizer returns generated prose (an abstractive or extractive summary), not a list of topic phrases. It also has to be polled, which is unnecessary work for a topic list.client.recognize_linked_entities() - entity linking resolves mentions to entries in a public knowledge base such as Wikipedia and returns canonical IDs. That answers "who/what is this and where is it documented", not "what are the topics".client.recognize_entities() - plain named entity recognition returns people, organizations and locations with categories and confidence. It finds proper nouns, so it misses the topical themes ("refund policy", "shipping delay") that key phrase extraction returns.Learn the Azure AI Language method-to-capability map cold: extract_key_phrases = topics, recognize_entities = named entities, recognize_linked_entities = entities with knowledge-base IDs, begin_extract_summary = generated summary. The verb in the method is the give-away.
Q5 - Correct answer: C. an analyzer in Azure Content Understanding in Foundry Tools.
The schema is the giveaway. You declare fields - vendor, date, total, and nested line items - and an Azure Content Understanding analyzer maps document content onto them, returning typed values in a fields object. OCR, transcription and search each fail on at least one of the three requirements: structured output, nested values, your own schema.
extract, generate and classify methods.ContentField; arrays and objects allow nested line items.The application needs machine-readable line items with quantities and unit prices under a total, driven by a schema you own. That is precisely an analyzer's contract: you submit the invoice to the Analyze operation, poll it, and read the structured fields (including the nested array) out of the result - no hand-written parsing rules.
Memorise the four-way triage: schema-bound extraction -> Content Understanding analyzer; raw text from a page -> OCR / Document Intelligence; audio -> text -> Azure Speech; search over a corpus -> Azure AI Search.
Q35 - Correct answer: C. an audio input prompt.
The application already has the user's request as audio. To let a deployed multimodal model in Microsoft Foundry answer that spoken request, you send the audio itself in the request - an audio input prompt, i.e. a content item of type input_audio carrying the base64-encoded audio and its format (for example wav). The docs are explicit that audio-capable models "use audio inputs to prompt the model".
gpt-4o-audio-preview, gpt-4o-mini-audio-preview, or the Realtime family). Supported modality combinations include audio-in with text-out and audio-in with audio-out.content array can mix typed items: {"type": "text", ...} and {"type": "input_audio", "input_audio": {"data": encoded_string, "format": "wav"}}.data; the format field tells the service how to decode it (wav, mp3, ...).The requirement is "send the user's request to the model" and the request is a recording. The only option that delivers that request in its native form is an audio input prompt - the typed audio content item in the request payload. The model then reasons over the actual speech, which is what a multimodal deployment with audio input is for.
Read the scenario, not just the service name. If the app has raw audio and a multimodal model, the answer is an audio input prompt. If the app has audio but must use a text-only model, you must transcribe first with Azure Speech. Same input, different architecture, different answer.
Q36 - Correct answer: A. SpeechRecognizer.
In the Azure Speech SDK for Python, SpeechRecognizer is the class that performs speech-to-text recognition, and for a default-microphone stream you construct it with just the SpeechConfig. Everything else on this row is either the opposite direction (speech out) or a settings/IO object rather than the recognizer.
SpeechConfig - the connection object: resource key/region (or endpoint, host or authorization token), source language, and other service properties. Shared by recognition and synthesis.SpeechRecognizer - "a speech recognizer" that consumes a SpeechConfig and an optional AudioConfig, and returns recognition results.recognize_once() / recognize_once_async() for a single utterance; start_continuous_recognition() plus event callbacks for a continuous session; keyword recognition for wake-word flows.SpeechSynthesizer + AudioOutputConfig - the synthesis path: text in, spoken audio written to a file or stream.The requirement is speech-to-text from a default microphone, continuously. SpeechRecognizer is the class that owns that behaviour - the docs' microphone sample is speech_recognizer = speechsdk.SpeechRecognizer(speech_config=speech_config) followed by recognize_once_async(), with start_continuous_recognition() for an ongoing session.
SpeechSynthesizer - this is text-to-speech: it turns written text into audio. It is the answer to "read this notification aloud over the phone system", not to "transcribe what the microphone hears".SpeechConfig - configuration, not capability. You pass SpeechConfig into SpeechRecognizer; it carries the key, region and language but recognizes nothing on its own.AudioOutputConfig - an output-side helper describing where synthesized audio goes (AudioOutputConfig(filename="output.wav")). It belongs to the synthesis path and has nothing to do with recognizing microphone input.For the Speech SDK, sort every class into one of three buckets - config (SpeechConfig), input (AudioConfig, AudioStreamFormat, PushAudioInputStream), output (AudioOutputConfig) - and one of two engines (SpeechRecognizer in, SpeechSynthesizer out). Then read the direction of the data in the stem.
Q8 - Correct answers: A and E. Instructions define the agent's role and behavior, and define constraints on the model's responses.
When you prompt a generative AI model, the instruction text does two jobs. It tells the model who it is and how it should behave, and it states the limits on what it may produce. Neither job is about infrastructure: you cannot pick a model, a region or a throughput quota from inside a prompt.
instructions field.A. defines the agent's role and behavior - "you are a travel agent", "answer as a bank teller", "be concise and cite sources" are all role and behaviour statements, and they live in the instruction text.
E. defines constraints on the model's responses - "at most three bullets", "respond in Japanese", "never invent a booking reference" are output constraints. They work precisely because the instruction states them, which is what prompt engineering exploits.
model="gpt-5-mini"). Prompt text is interpreted by whichever model received it; it cannot retarget the request.https://<resource>.services.ai.azure.com/api/projects/<project>). No instruction moves compute.Split any option in half: does it describe what the model should do (instruction) or where/how much it runs (deployment)? Role and constraints are instructions; model, region and quota are not.
Q37 - Correct answers: A, D and E - the model deployment name, Microsoft Entra ID credentials, and the endpoint URL.
Any Foundry SDK sample that sends chat prompts reduces to three values: where the request goes (the project endpoint URL), which deployed model should answer (the model deployment name), and who you are (credentials - Microsoft Entra ID / DefaultAzureCredential, or an API key). Everything else in the options is descriptive metadata that never appears in the call.
https://<resource-name>.services.ai.azure.com/api/projects/<project-name>. The Foundry SDK is a thin client that exposes the project's APIs through this one endpoint.gpt-5-mini); it is passed in the model field and is what actually routes the request to a specific deployment inside the resource.DefaultAzureCredential from azure-identity, after az login, or an API key. Either way, unauthenticated calls are rejected.AIProjectClient(endpoint=..., credential=...), then project.get_openai_client() (or FoundryChatClient) for chat completions / Responses calls.A. the model deployment name - the deployment name identifies the model inside your resource. The quickstart instructs you to keep the deployment you created and to "update the model name in the sample code" if you deployed under a different name.
D. Microsoft Entra ID credentials - the documented Foundry SDK samples "authenticate by using DefaultAzureCredential, which comes from azure-identity", after signing in with az login. That credential is what turns an anonymous HTTP call into an authorized one.
E. the endpoint URL - the samples' first placeholder is the project endpoint, "in the format https://<resource-name>.services.ai.azure.com/api/projects/<project-name>". Without it the client has nowhere to send the prompt.
task_type on the completions client, but that is a deprecated API shape, not what the Foundry SDK takes.Memorise the triad for "what must the application include to call the model": endpoint + deployment name + credentials. In real code these are the .env values FOUNDRY_PROJECT_ENDPOINT / AZURE_OPENAI_ENDPOINT, FOUNDRY_MODEL_NAME / AZURE_OPENAI_DEPLOYMENT_NAME, and a token credential - three values, one request.
Q11 - Correct answer: D. SpeechConfig.
Every Azure Speech SDK call starts by building a SpeechConfig - it holds your Speech resource key and region (or endpoint / host / authorization token) and the source language, and you hand it to whichever engine you instantiate. It is configuration, not a capability, which is why it is the answer to "configure the connection".
SpeechConfig - the connection object: subscription key plus region, or an endpoint, host, or token. Also carries speech_recognition_language, endpoint IDs for custom models, and service properties.SpeechRecognizer - the speech-to-text engine that consumes a SpeechConfig and optional AudioConfig.SpeechSynthesizer - the text-to-speech engine; it also needs a SpeechConfig.AudioConfig / AudioOutputConfig - describe where audio comes from or goes to (a microphone, a file, a stream), not how you connect to the service.The stem asks which class "configures the connection to the Azure Speech service". SpeechConfig is exactly that: created with speechsdk.SpeechConfig(subscription="YourSpeechKey", region="YourSpeechRegion"), or from an endpoint / host / authorization token. Real-time spoken conversations need it whether the audio comes from a microphone or a stream, because the recognizer, the synthesizer and voice live detection all read their endpoint and credentials from it.
AudioOutputConfig - an output-side descriptor used by SpeechSynthesizer to say where synthesized audio is written (for example AudioOutputConfig(filename="output.wav")). It configures no connection to the service.SpeechSynthesizer - that is the speech-generation engine (text in, audio out). Real-time conversation needs a recognizer for what the user says; a synthesizer can optionally read the reply back.AudioConfig - it identifies the audio input device or file (default microphone, fromWavFileInput, a push stream). You pass it to a recognizer, but it carries no key, region or endpoint.Memorise the Speech SDK object model as three families: configuration (SpeechConfig), audio IO (AudioConfig, AudioOutputConfig, AudioStreamFormat, PushAudioInputStream) and engines (SpeechRecognizer, SpeechSynthesizer). "Configure the connection" is always the first family.
Want the full bank of 37 questions for Microsoft Azure AI Fundamentals (AI-901)? See all practice exams.