Microsoft Azure AI Fundamentals

→ Why the correct answer is right:

Sentiment analysis is needed for the customer-review requirement because it's the technique that assigns positive, neutral, or negative sentiment labels. Summarization is needed for the transcript requirement because it produces a condensed version of longer content. The question combines two different text-analysis goals: emotional polarity and shortening content, requiring two distinct techniques.

→ Why the other options are wrong:

Option A: Keyword extraction identifies main concepts/talking points (helps highlight themes), but doesn't directly tell if review is positive/negative OR generate condensed readable transcript version

Option C: Entity detection categorizes named items (people, locations, organizations) for structured info extraction, but neither requirement asks for named entities (doesn't replace polarity detection or create summary)

Option E: Detect language is preprocessing for multilingual systems (tells what language text is written in), not sentiment classification or summarization (out of scope for requirements)

Quick Memory Tip 🧠

"Sentiment = positive/negative, Summarization = condensed transcript"

→ Why the correct answer is right:

For a field like InvoiceNumber, the correct generation method is EXTRACT because the analyzer should pull a concrete value from the document rather than generate a summary or classify a category. Microsoft's custom analyzer tutorial shows document fields such as names and totals using GenerationMethod.EXTRACT. Extracted fields are grounded in the source document.

→ Why the other options are wrong:

Option A: GenerationMethod.GENERATE produces derived values like summaries (invoice number is not generated interpretation, it's concrete field pulled from source)

Option B: GenerationMethod.CLASSIFY categorizes into classes (document type, sentiment label), but invoice number is direct field value, not category

Option D: enum=["Invoice"] is used with classification fields to define allowed categories, but snippet missing field method for extracting document value (enum alone doesn't create extraction field)

Quick Memory Tip 🧠

"EXTRACT = pull concrete value from document"

→ Why the correct answer is right:

Keyword extraction is the correct choice because the retailer wants the main topics from the tickets, not a rewritten narrative. Microsoft describes key phrase extraction as a capability that quickly identifies the main concepts in text. The clue "They do not want a rewritten paragraph" rules out summarization and points toward returning important phrases or talking points.

→ Why the other options are wrong:

Option A: Summarization produces condensed version of content (rewritten paragraph), but question explicitly says user doesn't want rewritten paragraph

Option B: Entity detection identifies named items (people, organizations, locations) for metadata/indexing, not main topics across tickets (focuses on named entities, not topics)

Option C: Sentiment analysis measures positive/neutral/negative (useful for satisfaction/triage), but doesn't surface actual topics being discussed (sentiment score alone doesn't reveal main themes)

Quick Memory Tip 🧠

"Keyword extraction = main topics/phrases (not rewritten paragraph)"

→ Why the correct answer is right:

The correct method is analyze_sentiment because the code needs to return doc.sentiment for each input document. Microsoft's Python SDK documentation shows that analyze_sentiment determines whether text is positive, negative, neutral, or mixed and provides sentiment-focused results. The output property doc.sentiment is the biggest clue matching this method.

→ Why the other options are wrong:

Option A: extract_key_phrases identifies main talking points (surfaces concepts), not positive/negative attitude (would use doc.key_phrases, not doc.sentiment)

Option B: recognize_entities returns categorized entities (people, organizations, locations, dates, quantities), not review favorability (entity detection ≠ sentiment assessment)

Option D: detect_language identifies text language (helpful for multilingual preprocessing), not emotional polarity (doesn't calculate sentiment)

Quick Memory Tip 🧠

"analyze_sentiment = doc.sentiment (positive/negative/neutral)"

→ Why the correct answer is right:

Summarization is the right answer because the requirement is to create a shorter version of longer content. Microsoft documentation describes summarization as a capability for producing summaries, and extractive summarization specifically identifies key sentences that convey the main idea of a document. This directly matches the manager's need for a readable short version.

→ Why the other options are wrong:

Option A: Keyword extraction returns important phrases, not condensed narrative/sentence-based overview (list of phrases isn't enough for readable short version)

Option B: Entity detection identifies named elements (people, locations, organizations) for metadata/indexing, not shortened retelling of document

Option C: Sentiment analysis evaluates positive/neutral/negative (useful for reviews/feedback), but incident report summary is about condensing information, not assigning emotional tone

Quick Memory Tip 🧠

"Summarization = short condensed version of long content"

→ Why the correct answer is right:

Keyword extraction is used to identify main concepts in text, entity detection identifies and categorizes named items, and summarization condenses longer content. Those three pairings align directly with Microsoft's descriptions of the corresponding Azure Language capabilities. These are the key distinctions for understanding text analysis techniques.

→ Why the other options are wrong:

Option B: Sentiment analysis determines emotional tone (positive/neutral/negative), not categorizing people/places/organizations (entity detection does that)

Option E: Keyword extraction identifies main concepts/talking points, not polarity labels (sentiment analysis produces sentiment labels and confidence scores)

Option F: Summarization generates shorter representation of content, not extracting/categorizing named entities (entity detection identifies organizations/locations)

Quick Memory Tip 🧠

"Keywords = talking points, Entity = named items, Summarization = condensed text"

→ Why the correct answer is right:

Requiring a human reviewer for high-impact cases best reflects accountability because it preserves meaningful human control over decisions that can materially affect people. Microsoft states AI systems should not be the final authority on decisions affecting people's lives and humans should remain in control of highly autonomous systems. Accountability is about defining who reviews outcomes, who can override them, and who is responsible.

→ Why the other options are wrong:

Option A: Hiding escalation rules works against good governance and weakens oversight (reviewers need context for meaningful review; makes accountable oversight harder)

Option B: Replacing all reviewers with automation is opposite of accountability (removes human control, makes organizations defer responsibility to model)

Option C: Short data retention relates to privacy practices, not accountability (doesn't establish owners, sign-off process, or monitoring)

Quick Memory Tip 🧠

"Accountability = human reviewer for high-impact decisions"

→ Why the correct answer is right:

Statement 1 is incorrect. Microsoft's accountability guidance specifically says AI systems should not be the final authority on decisions that affect people's lives and that humans should maintain meaningful control over highly autonomous systems. Statements 2 and 3 are correct. Microsoft identifies lineage and governance data (who published models, why changes were made, when deployed) as accountability-supporting practices, and recommends governance structures, review boards, reporting mandates, and sign-off processes.

→ Why the other options are wrong:

Option A: Marks Statement 1 as Yes (main problem; accountability ≠ handing authority to AI) and Statement 3 as No (wrong; governance sign-off formalizes responsibility)

Option B: Still marks Statement 1 as Yes (wrong) and Statement 2 as No (wrong; logging supports accountability through traceability)

Option D: Correctly marks Statement 1 as No and Statement 3 as Yes, but incorrectly marks Statement 2 as No (logging who changed model supports accountability)

Quick Memory Tip 🧠

"Accountability = humans control, not AI final authority + logging + governance sign-off"

→ Why the correct answer is right:

Accountability is the principle that best fits this sentence. Microsoft describes accountability as requiring the people who design and deploy AI systems to remain responsible for how those systems operate, including how decisions are reviewed and corrected when needed. This shows up through governance, documented responsibilities, monitoring, review, and mechanisms that preserve human control over important decisions.

→ Why the other options are wrong:

Option A: Fairness is about avoiding unjust differences in treatment across similar people/groups (asks whether system behaves equitably, not about ownership/answerability)

Option B: Transparency is about helping people understand how AI decisions are made (explainability, disclosure), but doesn't establish who is responsible for system actions

Option D: Inclusiveness focuses on designing AI systems usable by people with diverse needs/abilities (accessibility/participation), not ownership of outcomes and governance

Quick Memory Tip 🧠

"Accountability = people remain answerable for AI system"

→ Why the correct answer is right:

Microsoft states that prebuilt analyzer definitions can change across API versions. To ensure consistent behavior, the documentation recommends making a copy of the prebuilt analyzer instead of relying on the prebuilt version directly in production. This is the production-safe customization path for Content Understanding analyzers in Foundry Tools.

→ Why the other options are wrong:

Option A: Calling prebuilt analyzer directly ignores Microsoft's warning that definitions can change across API versions (introduces unexpected behavior after service/API changes)

Option C: prebuilt-documentFields is a utility analyzer for key-value pairs, not a general replacement for version stability of customized analyzer behavior

Option D: tableFormat controls output format for tables (HTML vs markdown), not production stability across API versions (configuration distraction, not core answer)

Quick Memory Tip 🧠

"Copy prebuilt analyzer = stable production behavior across API versions"

→ Why the correct answer is right:

Evaluating results using real-world data from affected groups is the best practical step because Microsoft Learn explicitly highlights the importance of real-world data when assessing fairness. This helps teams see whether the system behaves equitably for the people who will actually be affected by it. AI-901 fairness questions usually focus on representative data, subgroup analysis, and unequal outcomes.

→ Why the other options are wrong:

Option A: Longer password policy supports privacy and security (access control), not fairness review (doesn't determine if model treats groups fairly)

Option C: Increasing batch size is ML tuning for training behavior/efficiency, not fairness evaluation (doesn't show if real users/groups treated equitably)

Option D: Disabling user feedback could reduce opportunities to identify harms or uneven impacts (removes feedback, doesn't improve fairness review)

Quick Memory Tip 🧠

"Fairness review = real-world data from affected groups"

→ Why the correct answer is right:

model="ops-assistant" is correct because Microsoft documents that the deployment name is used in the model parameter during inference. The Code tab exists to show programmatic access details for the deployment you created in the portal, so this is the correct argument to target that deployment. This tests the small implementation distinction between portal deployment and client call mapping.

→ Why the other options are wrong:

Option A: endpoint is useful (viewable from deployment details page), but deployment guide specifically says deployment name is used in the model parameter, not endpoint

Option B: deployment_type is a configuration choice, not the field that identifies which deployed model handles inference requests

Option C: project is a valid Foundry concept but Microsoft doesn't describe project name as the inference argument that routes requests to deployed model

Quick Memory Tip 🧠

"model parameter = deployment name for inference routing"

→ Why the correct answer is right:

enableOcr is appropriate because Microsoft documents it as the option that enables optical character recognition for images and scanned documents, directly matching image-based PDFs and scanned forms. estimateFieldSourceAndConfidence is also appropriate because it returns source location information (page number, bounding box) along with confidence for extracted field values.

→ Why the other options are wrong:

Option C: disableFaceBlurring is for image/video scenarios, not document field extraction from scanned forms

Option D: locales is for language-specific processing in audio/video transcription, not scanned document OCR and field-source validation

Option E: enableSegment is useful for classification/routing workflows, but doesn't replace OCR or field-source estimation capabilities

Quick Memory Tip 🧠

"enableOcr = scanned PDFs, estimateFieldSource = page + box + confidence"

→ Why the correct answer is right:

Those three pairings match Microsoft's documented Foundry workflow. You get the OpenAI-compatible client from the project client, use the deployment name in model, and create a conversation for multi-turn chat when needed.

→ Why the other options are wrong:

Option A: AIProjectClient is the project client, not the final chat client for direct responses.

Option C: previous_response_id is not required for the first request.

Option E: az login authenticates you; it does not create deployments.

Quick Memory Tip 🧠

Project client → get OpenAI client → use deployment name.

→ Why the correct answer is right:

Those three pairings are correct and reflect the main Azure Speech workloads: recognition, synthesis, and speaker separation in transcripts.

→ Why the other options are wrong:

Option D: SSML customizes synthesized speech; it does not train recognition models.

Option E: Batch transcription is recognition, not voice generation.

Option F: Speech Translation translates speech; it does not detect sentiment.

Quick Memory Tip 🧠

Know the three speech pillars: recognize, synthesize, separate speakers.

→ Why the correct answer is right:

Speech recognition turns audio into text, and text to speech turns text into audio. Speaker diarization does not control voice style; it separates speakers in audio.

→ Why the other options are wrong:

Option B: It wrongly says text to speech is not correct.

Option C: It wrongly denies speech recognition.

Option D: It incorrectly denies both the recognition and synthesis statements.

Quick Memory Tip 🧠

Diarization = who spoke, not how the voice sounds.

→ Why the correct answer is right:

The quickstart uses prebuilt-imageSearch and then reads the Summary field to print the image description. That is the field Microsoft shows for the returned description output.

→ Why the other options are wrong:

Option A: Transcript is for audio/video speech results.

Option B: ChartType belongs to the custom chart-image schema.

Option C: Sentiment is used in other analysis scenarios, not this one.

Quick Memory Tip 🧠

Image quickstart description = Summary.

→ Why the correct answer is right:

Reliability and safety is about dependable operation, safe handling of unexpected conditions, and resistance to harmful manipulation. Azure AI Content Safety is designed to detect harmful content, and harms modeling is used to anticipate ways technology could cause harm so mitigations can be designed.

→ Why the other options are wrong:

Option B: Encrypting stored data fits privacy and security, not fairness.

Option D: Assigning a final human owner for decisions fits accountability more than transparency.

Option F: Blocking self-harm content is a safety control, not inclusiveness.

Quick Memory Tip 🧠

Match the principle to the real goal.

→ Why the correct answer is right:

Speech recognition is the capability that turns spoken audio into text. In Azure Speech, that workload is handled by speech to text, which supports converting live audio streams and prerecorded audio into written output.

→ Why the other options are wrong:

Option A: Text to Speech is a synthesis feature, not a recognition feature.

Option C: Speech Translation is related to speech input, but its main goal is translation across languages rather than plain transcription in the same language.

Option D: Entity recognition is a text analysis task, not a speech recognition capability.

Quick Memory Tip 🧠

Calls to text = speech to text.

→ Why the correct answer is right:

Prompts shape the model's response, and fine-tuning can change the model's weights for a task. Those are both true descriptions of how generative AI systems are guided and adapted. The other statements are too absolute or describe different technologies.

→ Why the other options are wrong:

Option B: Outputs are not guaranteed to be identical in every context.

Option D: Base models do not automatically know private company data.

Option E: Embeddings are semantic vectors, not relational table rows.

Quick Memory Tip 🧠

Prompts guide output; fine-tuning changes weights.

→ Why the correct answer is right:

To translate from English into French, you add French as a target language on the translation configuration. The app listens in one language and adds one or more output target languages before creating the recognizer. That is the correct setup pattern.

→ Why the other options are wrong:

Option A: speak_text_async is for synthesis, not translation setup.

Option B: recognize_once_async is a recognizer method, not a configuration method.

Option C: remove_target_language does the opposite of what this app needs.

Quick Memory Tip 🧠

Translation setup = add target language.

→ Why the correct answer is right:

These three terms are foundational. Embeddings represent meaning numerically, prompts are the instructions you give the model, and fine-tuning updates model weights using task-specific examples. Together they describe how modern AI systems are guided, adapted, and represented.

→ Why the other options are wrong:

Option B: A base model is not yet customized.

Option D: Hallucination is unsupported output, not guaranteed grounding.

Option F: A completion token is generated text, not a form field.

Quick Memory Tip 🧠

Embedding, prompt, and fine-tuning are separate concepts.

→ Why the correct answer is right:

If the safety score drops below the threshold, the system should notify operators or trigger an alert. That is a practical reliability-and-safety response because it helps people react quickly when the model output is no longer within acceptable limits. Monitoring is useful only when it leads to action.

→ Why the other options are wrong:

Option A: A placeholder prompt does not respond to the safety issue.

Option B: Printing a model name does not alert anyone.

Option D: Setting the endpoint to None does not solve the problem.

Quick Memory Tip 🧠

Low safety score = alert operators.

→ Why the correct answer is right:

Text to speech is the Azure Speech capability that reads text aloud in a synthesized voice. That is exactly what a lesson-reading or narration app needs. The other options work in different directions or solve different problems.

→ Why the other options are wrong:

Option A: OCR extracts text from images.

Option B: Speech to Text converts audio into text.

Option C: Speech Translation translates speech, not lesson text narration.

Quick Memory Tip 🧠

Text in, voice out = text to speech.

→ Why the correct answer is right:

Microsoft's Python quickstart for speech recognition shows the recognizer calling recognize_once_async().get() to capture one utterance and return the recognition result. That matches the scenario here because the app is listening to the microphone and needs a speech-to-text result.

→ Why the other options are wrong:

Option A: speak_text_async is a text-to-speech method, so it belongs to synthesis rather than recognition.

Option C: SpeechSynthesizer is the class used for text-to-speech output, not for recognizing microphone input.

Option D: speak_ssml_async is also a synthesis method, specifically for synthesizing SSML input into speech.

Quick Memory Tip 🧠

One utterance from mic = recognize_once_async().

→ Why the correct answer is right:

Speech to text is the Azure Speech feature that listens to audio and converts it into text in real time. That makes it the right choice for live captions, dictation, and call transcription. The app needs recognition, not voice generation or search.

→ Why the other options are wrong:

Option A: Text to speech does the reverse job.

Option C: Agent Service is not the core speech-recognition capability.

Option D: Search is for retrieval, not transcription.

Quick Memory Tip 🧠

Live captions = speech to text.

→ Why the correct answer is right:

Microsoft's MAI image model documentation shows that image generation requests are sent to the mai/v1/images/generations endpoint path. This is specifically designed for producing new images from text prompts after a supported image generation model has been deployed.

→ Why the other options are wrong:

Option A: vision/v1/ocr is associated with reading and extracting text from existing images — the opposite of creating new ones.

Option B: speech/v1/synthesize is for generating spoken audio from text — wrong output modality entirely.

Option D: language/v1/entities is for entity recognition in text — a language analysis service, not image creation.

Quick Memory Tip 🧠

"MAI image generation endpoint = mai/v1/images/generations | OCR = vision/ocr | Speech = speech/synthesize | NLP = language/entities"

→ Why the correct answer is right:

Microsoft explains that dense captioning generates detailed captions for individual objects found in an image and returns bounding box coordinates for each. This makes it the right fit when you need separate descriptions for multiple parts of a photo — not just one overall sentence.

→ Why the other options are wrong:

Option A: OCR extracts readable text that already exists in the image — it doesn't generate descriptive captions for visual objects or regions.

Option C: Text-to-image generation creates new images from prompts — it doesn't analyze an existing photo and describe its individual parts.

Option D: Speech recognition converts spoken audio to text — it has no relationship to visual description of image regions.

Quick Memory Tip 🧠

"One sentence for whole image = Image Captioning | Separate descriptions for parts = Dense Captioning | Read text in image = OCR"

→ Why the correct answer is right:

Microsoft's video quickstart shows iterating through result.contents and accessing video_content.markdown when using prebuilt-videoSearch. The service packages extracted video content into richly formatted Markdown for downstream use in search, chat, or automation.

→ Why the other options are wrong:

Option B: deployment_name is used when selecting a deployed model — not a property on video extraction result objects.

Option C: temperature is a model generation parameter — not a content property returned by an analyzer result.

Option D: embedding represents vector data for retrieval — not the formatted content output returned by a video analyzer.

Quick Memory Tip 🧠

"video_content.markdown = access extracted video results | deployment_name = model selection | temperature = generation param"

→ Why the correct answer is right:

All three correct pairs align with Microsoft's documented capability definitions: OCR reads text from images, object detection identifies and localizes objects with bounding box coordinates, and image captioning generates a human-readable sentence describing an image.

→ Why the other options are wrong:

Option B: Sentiment scores come from text analysis (NLP) — not from image generation models. Image generation creates visuals, it doesn't classify sentiment.

Option D: Speech synthesis converts text to audio — it doesn't analyze photos or create image captions. Captioning is a vision task.

Option F: OCR reads existing text from images — it cannot create a new poster from a prompt. Creating content from a prompt is image generation.

Quick Memory Tip 🧠

"OCR = Read text | Object Detection = Locate + Coordinates | Image Captioning = Describe in a sentence | None of these CREATE images"

→ Why the correct answer is right:

Microsoft's image generation documentation states these models create images from user-provided text prompts, and in some workflows they also accept optional images as input (for tasks like variations or inpainting). Both are documented image generation capabilities.

→ Why the other options are wrong:

Option C: Returning people-detection bounding boxes is a computer vision analysis capability — it identifies and locates people in existing images, not a generation task.

Option D: Reading printed text from posters is OCR — a text extraction capability from existing images, not image creation.

Option E: Producing sentiment labels is a text analysis (NLP) task — completely different workload family from image generation.

Quick Memory Tip 🧠

"Image Generation = Create from prompt + Optional image input | NOT analysis, NOT OCR, NOT sentiment"

→ Why the correct answer is right:

Embedding models convert text into semantic vectors for retrieval and similarity. Multimodal chat models accept text plus image input. Image generation models create new images from text prompts. All three are directly documented in Microsoft Learn.

→ Why the other options are wrong:

Option B: Returning similarity vectors is the job of an embedding model, not an image generation model.

Option C: Azure AI Search is a retrieval service — it does not create images. That's an image generation model's job.

Option E: Speech synthesis converts text to audio — it does not extract invoice fields. That's a document intelligence task.

Quick Memory Tip 🧠

"Embedding = Vectors | Multimodal Chat = Text + Images | Image Generation = Create images | Azure AI Search = Retrieval only"

→ Why the correct answer is right:

Microsoft identifies privacy and security as one of its six Responsible AI principles. This principle focuses on protecting data, controlling access, and reducing risks of misuse or exposure — which directly covers protecting prompts, outputs, and personal data from unauthorized access.

→ Why the other options are wrong:

Option A: Fairness is about equitable treatment across groups and avoiding bias — not data protection or access control.

Option B: Transparency is about making system behavior and limitations understandable — it supports trust but doesn't directly govern data security.

Option D: Inclusiveness focuses on designing for diverse users and accessibility — not on preventing unauthorized data access.

Quick Memory Tip 🧠

"Microsoft's 6 Responsible AI Principles: Fairness | Reliability | Privacy & Security | Inclusiveness | Transparency | Accountability"

→ Why the correct answer is right:

client.embeddings.create(input=text, model="text-embedding-3-large") calls the embeddings endpoint and returns a response with a .data[0].embedding field containing the vector. This is the documented Python pattern for generating text vectors for use in semantic search.

→ Why the other options are wrong:

Option A: client.images.generate(...) creates images — its response contains image data, not an .embedding field.

Option B: client.audio.transcriptions.create(...) transcribes audio to text — the result is a text transcript, not a vector array.

Option C: client.responses.create(...) generates a chat response — the result is model text output, not an embedding array.

Quick Memory Tip 🧠

"Need a vector? → client.embeddings.create() | response.data[0].embedding = the vector | Not images.generate, not audio, not responses!"

→ Why the correct answer is right:

Microsoft Learn states that multimodal chat completion models can accept text input and other types such as images or audio. A model that handles more than one input modality — like text plus images — is by definition a multimodal model.

→ Why the other options are wrong:

Option A: Speech models handle audio workloads like speech recognition or synthesis — not text-plus-image chat completions.

Option B: Embedding models produce vector representations of text for similarity and retrieval — they don't reason over images in a chat flow.

Option D: A vectorizer is a retrieval pipeline component that calls an embedding model — it's not the model category for text-plus-image chat completions.

Quick Memory Tip 🧠

"Text + Images in chat = Multimodal Model | Vectors = Embedding | Audio in/out = Speech | Search pipeline = Vectorizer"

→ Why the correct answer is right:

Microsoft documents the prompt agent as declaratively defined. The agents playground is specifically for testing multi-turn conversations. Build > Tools is the documented navigation path to open the Foundry tool catalog for adding capabilities to agents.

→ Why the other options are wrong:

Option B: Hosted agents are code-based and containerized — not no-code portal-only agents. That description fits prompt agents.

Option D: Build > Tools opens the tool catalog, not billing. Billing is managed elsewhere in Azure administration.

Option F: Workflow agents handle complex orchestration and multi-agent coordination — not the best fit for a simple single-agent scenario.

Quick Memory Tip 🧠

"Prompt Agent = Declarative + No-code | Agents Playground = Multi-turn testing | Build > Tools = Tool catalog"

→ Why the correct answer is right:

Avoiding hard-coded secrets reduces the risk of credential leakage and unauthorized access to AI resources and connected data. This is a core privacy and security practice — one of Microsoft's six Responsible AI principles. It protects both the system and any data it processes.

→ Why the other options are wrong:

Option A: Transparency is about communicating system behavior and limitations to users — not about how credentials are stored or managed.

Option C: Fairness addresses equitable treatment across groups and avoiding bias — it has nothing to do with secret management or authentication design.

Option D: Summarization is a text-analysis AI capability — not a Responsible AI principle, and unrelated to credential security.

Quick Memory Tip 🧠

"No hard-coded secrets → Privacy & Security | Explain system behavior → Transparency | Equal treatment → Fairness"

→ Why the correct answer is right:

Microsoft Learn shows two supported image input approaches: (1) pass a public image URL for cloud-hosted images, and (2) use ImageUrl.load() to convert a local image file into a data URL. Both give the model actual image content for visual interpretation.

→ Why the other options are wrong:

Option A: OCR text output is extracted text from an image — not the image itself. The model needs image data, not a post-processed text substitute.

Option D: An embedding vector encodes semantic meaning for retrieval — it cannot represent image pixels for visual reasoning in a chat prompt.

Option E: A speech transcript is text derived from audio — not visual data. It belongs to a different modality entirely.

Quick Memory Tip 🧠

"Image input = Public URL OR Data URL (local file) | NOT vectors, NOT transcripts, NOT OCR text"

→ Why the correct answer is right:

Microsoft's image generation documentation states that these models create images from user-provided text prompts, and optionally from images too. The scenario involves no existing image to analyze — the goal is to synthesize brand-new visual content from a description, which is exactly what image generation does.

→ Why the other options are wrong:

Option A: OCR reads text that already exists in an image — it cannot create new images from prompts.

Option B: Image tagging analyzes an existing image and labels what it contains — a recognition task, not a creation task.

Option D: Entity recognition identifies named entities (people, places, organizations) in text — a language analysis task, not an image creation task.

Quick Memory Tip 🧠

"Create new image from text = Image Generation | Read text from image = OCR | Label image contents = Image Tagging"

→ Why the correct answer is right:

Microsoft Learn notes that model catalog Capabilities filters include reasoning and tool calling. A reasoning chat model is specifically built for working through complex tasks step by step and invoking tools — like web search or functions — during the response flow. This is the foundation of agentic AI behavior.

→ Why the other options are wrong:

Option B: Embedding models convert text into vectors for retrieval — they cannot reason through requests or call tools in a conversational flow.

Option C: Image generation models create visual content from prompts — not designed for reasoning steps or tool invocation.

Option D: Speech synthesis converts text to audio — it handles output format, not reasoning or tool orchestration.

Quick Memory Tip 🧠

"Reasoning + Tool Calling = Reasoning Chat Model | Vectors = Embedding | Images = Generation | Audio output = Speech Synthesis"