Microsoft Azure AI Fundamentals

→ 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:

A, C, and E are correct because they match Microsoft's fairness guidance closely. Fairness is about treating similar groups fairly, using representative or real-world data for evaluation, and checking whether model behavior differs across groups that might be sensitive or impacted differently. These are the distinctions AI-901 expects candidates to recognize.

→ Why the other options are wrong:

Option B: Transparency is about making AI systems understandable (capabilities, limitations, behavior); encrypting data is privacy/security, not transparency

Option D: Accountability is about people remaining responsible for AI systems; increasing GPU capacity is infrastructure scaling, not accountability mechanism

Option F: Reliability/safety focuses on stable/safe/robust behavior; hiding demographic results makes fairness assessment harder (demographic review is fairness evaluation, not safety)

Quick Memory Tip 🧠

"Fairness = similar groups treated equally + representative data + compare across groups"

→ Why the correct answer is right:

Entity detection is the correct answer because this requirement is about finding and categorizing named items in text. Microsoft documents this capability as named entity recognition, which identifies entities such as people, places, organizations, and quantities in unstructured text. This directly matches the need to systematically extract and categorize people, organizations, and locations.

→ Why the other options are wrong:

Option A: Summarization shortens content while preserving central meaning (doesn't label specific phrases as person/location/organization entities)

Option C: Sentiment analysis measures positive/neutral/negative attitude (useful for satisfaction/reviews, not for categorizing names and places)

Option D: Keyword extraction finds main concepts/talking points (not meant to classify into entity categories like Organization or Location)

Quick Memory Tip 🧠

"Entity detection = people, places, organizations, quantities"

→ 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:

Representative is the correct answer because Microsoft guidance on responsible AI fairness emphasizes using diverse and representative data to reduce bias. If data doesn't reflect the people who will be affected by the AI system, some groups can be underrepresented and receive worse outcomes. Microsoft Learn also highlights using real-world data to evaluate fairness.

→ Why the other options are wrong:

Option A: Encrypted data protects confidentiality (privacy/security), but encryption doesn't make dataset balanced or representative (can be well-protected but still unfair)

Option C: Compressed data is storage/transmission concern, not fairness control (reducing file size doesn't address demographics or real-world usage)

Option D: Anonymized data supports privacy (reduces personal info exposure), but anonymization doesn't ensure all groups are fairly represented (can be anonymized but still biased)

Quick Memory Tip 🧠

"Reduce bias = representative data of affected people"

→ 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:

An audit trail of model changes, approvals, and deployment history supports accountability because it creates traceability. Microsoft's guidance highlights governance data, lineage, documented responsibilities, and approval processes as ways to make ownership, review, and follow-up clear across the AI lifecycle. Accountability means people remain answerable for how systems operate.

→ Why the other options are wrong:

Option A: Larger font improves accessibility and inclusiveness, but doesn't establish who is responsible for model behavior or deployment decisions

Option C: Multilingual voice output relates to accessibility/speech/inclusiveness, not ownership of outcomes or governance (doesn't identify approvers or reviewers)

Option D: Encrypting stored data is privacy and security (protects confidentiality), not accountability (doesn't document who made model decisions)

Quick Memory Tip 🧠

"Accountability = audit trail (changes + approvers + history)"

→ 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:

Statement 1 is correct because underrepresentation in training data can contribute to biased or uneven outcomes. Microsoft's responsible AI guidance emphasizes representative data and real-world evaluation as important fairness considerations. Statement 2 is incorrect because fairness and inclusiveness are separate responsible AI principles, even though they are related. Statement 3 is correct because comparing model behavior across demographic or sensitive groups is a practical fairness assessment step.

→ Why the other options are wrong:

Option A: Wrongly marks Statement 2 as true (fairness ≠ inclusiveness) and Statement 3 as false (group comparison is relevant for fairness evaluation)

Option C: Marks Statement 1 as false (wrong; underrepresentation is a common fairness concern) and Statement 2 as true (wrong; they are separate principles)

Option D: Marks Statement 1 as false (wrong) and repeats mistake on Statement 2; gets Statement 3 right but that's not enough

Quick Memory Tip 🧠

"Fairness ≠ Inclusiveness (separate principles), underrepresentation = fairness risk"

→ Why the correct answer is right:

Both situations point directly to fairness risk. Different outcomes for similar applicants suggest unequal treatment, and poor representation of an affected group in test data makes it harder to evaluate whether the system performs equitably in the real world. These are classic AI-901 fairness signals. Microsoft's material ties fairness to treatment across groups and stresses the value of representative real-world data when evaluating AI systems.

→ Why the other options are wrong:

Option B: TLS is a security control for data in transit (privacy/security), not a fairness indicator (secure systems can still show biased outcomes)

Option D: Dark theme is a UI preference, not a fairness indicator (doesn't tell you about bias, representation, or unequal treatment)

Option E: Version number in model card supports documentation/governance (accountability/traceability), but doesn't reveal unfair behavior or equitable treatment

Quick Memory Tip 🧠

"Fairness risk = different outcomes + poor representation in test data"

→ Why the correct answer is right:

Fairness is best described as treating similar people fairly across groups. Microsoft's current responsible AI material explains fairness in terms of avoiding different effects on similarly situated groups, which is the clearest match among the options. AI-901 fairness questions often test whether you can separate equitable treatment from explainability, privacy, and performance.

→ Why the other options are wrong:

Option A: Encrypting stored data belongs to privacy and security, not fairness (secure systems can still produce unfair outcomes)

Option B: Explaining internal parameters relates to transparency (making systems understandable), not fairness (centered on equitable treatment)

Option D: Responding within fixed latency is a performance/reliability concern (fast systems can still be unfair)

Quick Memory Tip 🧠

"Fairness = similar people treated similarly across groups"

→ Why the correct answer is right:

Evaluating model results across age-based groups is the best fairness-focused response because fairness issues are identified by checking whether similar people or groups are being affected differently. Microsoft's responsible AI guidance points to fairness assessment across sensitive groups as an important way to understand model behavior. This is the most relevant next step for potential bias in outcomes.

→ Why the other options are wrong:

Option A: Increasing model endpoints improves scale/availability but doesn't reveal whether system disadvantages one age group (operational, not fairness evaluation)

Option B: Removing audit trail reduces oversight rather than improving it (auditability supports accountability and bias investigation)

Option C: Publishing source code increases openness but doesn't directly test whether model treats age groups fairly (transparency ≠ fairness)

Quick Memory Tip 🧠

"Fairness issue = evaluate results across affected groups"

→ 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:

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:

SSML is used to control synthesized speech details like pitch, speaking rate, pronunciation, and voice style. It is the standard customization mechanism for text-to-speech output.

→ Why the other options are wrong:

Option B: Speaker diarization separates speakers in audio.

Option C: OCR extracts text from images.

Option D: Batch transcription converts prerecorded speech to text.

Quick Memory Tip 🧠

Voice styling = SSML.

→ Why the correct answer is right:

Microsoft's Azure AI Inference Python documentation shows that EmbeddingsClient uses the embed method to generate embeddings. The returned data includes embedding vectors, which are numeric representations of semantic meaning.

→ Why the other options are wrong:

Option A: complete is for chat or text generation, not for creating embeddings with EmbeddingsClient.

Option B: get_model_info retrieves endpoint metadata, not vectors for semantic comparison.

Option C: send_request is a lower-level transport method and not the intended high-level embeddings call shown in the SDK examples.

Quick Memory Tip 🧠

Embeddings client = embed().

→ 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:

Microsoft's Responses API examples use input for the user prompt text. So the prompt goes in the input parameter when you call responses.create(...). This is the documented pattern for simple requests.

→ Why the other options are wrong:

Option B: prompt is a common word, but not the documented field here.

Option C: message belongs to a different request style.

Option D: content is used in some message structures, not this top-level field.

Quick Memory Tip 🧠

Responses API prompt field = input.

→ Why the correct answer is right:

Reliability and safety includes resisting harmful manipulation from adversarial or unexpected prompts. In other words, the system should remain safe and dependable even when someone tries to push it into bad behavior. That is exactly what this sentence is describing.

→ Why the other options are wrong:

Option A: Model cards are documentation, not something the system resists.

Option B: Stakeholder mapping is part of risk analysis, not a threat the model resists.

Option D: Explainability relates more to transparency than to resisting manipulation.

Quick Memory Tip 🧠

Adversarial prompts = harmful manipulation.

→ Why the correct answer is right:

Generative AI models learn patterns from large datasets. Base models are not yet customized for a specific use case, and embeddings are useful for representing semantic similarity. So the right pattern is Yes / No / Yes.

→ Why the other options are wrong:

Option A: It wrongly claims a base model is already customized.

Option C: It wrongly denies that generative AI learns patterns from large datasets.

Option D: It wrongly denies both the training and embedding statements.

Quick Memory Tip 🧠

Base model = not customized yet.

→ Why the correct answer is right:

Medical summarization is a sensitive scenario. The most important reliability-and-safety step is to test how the system behaves in high-risk, unusual, or potentially harmful situations before it goes live. That is how teams catch unsafe behavior early instead of discovering it after deployment.

→ Why the other options are wrong:

Option B: A brighter theme affects appearance, not safety.

Option C: Marketing copy does not reduce clinical risk.

Option D: Renaming the workspace changes administration, not model safety.

Quick Memory Tip 🧠

High-risk use case = test edge cases first.

→ 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:

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:

When a moderation system misses harmful content or blocks safe content, you need tuning and control. Adjusting severity thresholds and using blocklists are direct ways to improve moderation behavior and align the system with your safety policy. They help reduce both false negatives and false positives.

→ Why the other options are wrong:

Option C: A color change has nothing to do with moderation quality.

Option D: Shortening the FAQ does not change safety behavior.

Option E: Changing an icon does not affect harmful-content detection.

Quick Memory Tip 🧠

Moderation tuning = thresholds + blocklists.

→ 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 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:

Statement 1 is Yes — multimodal chat models accept images in addition to text. Statement 2 is Yes — a public image URL is a valid and documented way to provide image input. Statement 3 is No — Microsoft Learn notes that some models support only one image per turn; not every multimodal model supports multiple images in the same turn.

→ Why the other options are wrong:

Option B: Incorrectly marks Statement 2 as No — public image URLs are explicitly documented as valid input.

Option C: Incorrectly marks Statement 1 as No — multimodal models are specifically designed to accept image input.

Option D: Incorrectly denies both Statements 1 and 2 — both are confirmed supported behaviors in Microsoft's documentation.

Quick Memory Tip 🧠

"Multimodal = text + images ✅ | Public URL = valid input ✅ | Every model = multiple images? NO — model-specific ❌"

→ 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:

Microsoft's image generation documentation states that image generation models create images from user-provided text prompts. The prompt field is the core input in the request payload — it contains the natural language description that the model uses to generate the new image.

→ Why the other options are wrong:

Option B: "ocr" is not a field for image generation. OCR is a reading capability for existing images — not a creation request field.

Option C: "objects": ["bicycle", "park"] resembles image analysis output, not the text prompt that drives creation. The API uses a natural language prompt, not an object list.

Option D: "caption": True is associated with image analysis (generating a description of an existing image) — the opposite of creating a new one.

Quick Memory Tip 🧠

"Image generation request = prompt field | OCR = reads existing image text | Caption = describes existing image"

→ Why the correct answer is right:

A RAG chatbot needs two key model types working together: an embedding model to convert knowledge base content and queries into vectors for semantic retrieval, and a chat completion model to generate grounded answers using the retrieved content. Microsoft Learn confirms this pattern in Azure AI Search RAG workflows.

→ Why the other options are wrong:

Option A: Image generation models create images — they don't retrieve knowledge or generate text answers grounded in a knowledge base.

Option D: Speech synthesis converts text to spoken audio — useful as an optional output layer but not a core RAG model choice.

Option E: OCR extracts text from images — useful during knowledge ingestion, but not the primary model choice for retrieval and answer generation.

Quick Memory Tip 🧠

"RAG = Embedding (find it) + Chat Completion (answer it) | These two always work together in grounded chatbots"

→ Why the correct answer is right:

Microsoft's quickstart shows that PromptAgentDefinition requires an instructions field to define the agent's behavior. Instructions tell the agent how to act — without them, the resource is just a model reference without any agent-specific behavior.

→ Why the other options are wrong:

Option B: temperature=AGENT_NAME is nonsensical — temperature expects a numeric value, and the quickstart shows instructions as the core definition field, not generation temperature.

Option C: conversation=conversation.id is used when calling an agent in a multi-turn flow — not when defining the agent's version.

Option D: agent_reference={"name": AGENT_NAME} is used when referencing an existing agent in a call — not when creating one with PromptAgentDefinition.

Quick Memory Tip 🧠

"Create agent = PromptAgentDefinition(model=..., instructions=...) | Call agent = agent_reference in extra_body | They are different steps!"

→ Why the correct answer is right:

Microsoft Learn describes image generation models as creating images from user-provided text prompts and optional images. The same documentation notes editing capabilities like inpainting (filling or replacing parts of an image). Both capabilities — original image creation and inpainting — are signature image generation features.

→ Why the other options are wrong:

Option B: Returning floating-point vectors is the role of an embedding model — not an image generation model.

Option C: Scoring semantic similarity depends on embedding vectors and cosine similarity — an embedding/retrieval concept, not image generation.

Option D: Retrieval optimization points to embedding models and Azure AI Search — not visual content creation.

Quick Memory Tip 🧠

"Image Generation = Create images + Inpainting | Embedding = Vectors + Similarity scores | Search = Retrieval optimized"

→ 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:

Microsoft's Azure Direct Models privacy documentation explicitly states that (A) prompts and completions are not available to other customers, and (B) customer data is not used to improve Microsoft or third-party products or services without explicit permission. These are strong, documented privacy commitments.

→ Why the other options are wrong:

Option C: This directly contradicts Microsoft's documentation — prompts and completions are NOT shared with model providers like OpenAI.

Option D: Fine-tuned models are exclusively available to the customer who created them — they are not shared across tenants.

Option E: Uploaded training data is not public — it is processed and stored under controlled conditions for features like fine-tuning.

Quick Memory Tip 🧠

"Azure Direct Models = Your prompts are PRIVATE | Your data is NOT used to train others | Fine-tuned models = YOURS only"

→ 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"