🔷 Microsoft Azure

Free Microsoft Azure AI Fundamentals (AI-901) Study Resources

The exam that replaced AI-900 — and most prep online still teaches the retired one. Cover both skill areas as Microsoft writes them today: AI concepts and responsible AI, then hands-on Microsoft Foundry — agents, prompts, speech, vision, Content Understanding — now 55–60% of the paper. With an AI tutor, 12 blueprint-weighted mock exams, and a question bank written against current docs. Expects some Python.

663
Practice Questions
13
Mock Exams
89
Study Notes
587
Flashcard Decks
50
Source Materials
Start Studying — Free2 learners studying this hive

Microsoft Azure AI Fundamentals (AI-901) Study Notes & Guides

89 AI-generated study notes covering the full Microsoft Azure AI Fundamentals (AI-901) curriculum. Showing 10 complete guides below.

Curriculum Overview685 words

Curriculum Overview: Capabilities of Azure AI Language Service

Describe capabilities of the Azure AI Language service

Read full article

Curriculum Overview: Capabilities of Azure AI Language Service

This document outlines the structured learning path for mastering the Azure AI Language service, a core component of the Microsoft Azure AI Fundamentals (AI-900) certification. This service enables developers to build applications that understand, analyze, and respond to human language.

Prerequisites

Before starting this module, learners should have a foundational understanding of the following:

  • Cloud Computing Basics: Familiarity with Azure Resource Groups and the Azure Portal.
  • AI Fundamentals: Understanding of general AI workloads (Unit 1) and basic Machine Learning concepts.
  • NLP Concepts: A high-level grasp of what Natural Language Processing is (e.g., computers processing human speech or text).

Module Breakdown

ModuleTopicDifficultyFocus Area
1Language DetectionBeginnerIdentifying ISO 639-1 codes and confidence scores.
2Sentiment AnalysisIntermediateQuantifying emotional tone and opinion mining.
3Key Phrase & Entity RecognitionIntermediateExtracting main concepts and identifying known entities.
4Entity LinkingAdvancedDisambiguating terms using knowledge bases (e.g., Wikipedia).

Learning Objectives per Module

Module 1: Language Detection

  • Understand how to process multiple documents simultaneously.
  • Identify the ISO 639-1 language code (e.g., "en", "fr", "it") returned by the service.
  • Interpret the Confidence Score (a value between 0 and 1).

Module 2: Sentiment Analysis

  • Describe how the service generates sentiment scores (Positive, Neutral, Negative).
  • Analyze how mixed feedback (e.g., "Great camera but bad battery") results in balanced scores.

Module 3: Key Phrase Extraction & PII Detection

  • Identify main concepts to highlight major themes in large text bodies.
  • Recognize and redact Personally Identifiable Information (PII) like phone numbers or emails.

Module 4: Entity Linking

  • Explain the difference between recognizing an entity and linking it to a reference context.
  • Understand how the service differentiates between ambiguous terms (e.g., "Mars" the planet vs. "Mars" the chocolate bar).

Visual Anchors

Text Analysis Workflow

Loading Diagram...
Figure 1 — Mermaid diagram

Sentiment Analysis Spectrum

Below is a visual representation of how the service maps text to a sentiment coordinate system.

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Success Metrics

To demonstrate mastery of this curriculum, the learner should be able to:

  1. Identify the Correct Tool: Choose between Azure AI Language, Translator, and Speech based on the specific business requirement.
  2. Interpret Metadata: Correctly read a JSON response from the Language API to find the dominant language.
  3. Handle Ambiguity: Explain how Entity Linking solves the problem of words with multiple meanings.
  4. Evaluate Confidence: Determine if a result is reliable based on the confidence score provided by the model.

Real-World Application

[!TIP] Scenario: Customer Support Automation Imagine a global travel forum receiving thousands of posts daily.

  • Language Detection automatically routes the post to the correct regional support team.
  • Sentiment Analysis flags negative reviews for immediate manager intervention.
  • Key Phrase Extraction identifies trending complaints (e.g., "delayed flights") to help the company improve services.

[!IMPORTANT] Always remember that AI can have biases. When using Azure AI Language, apply Responsible AI principles to ensure fairness and inclusivity in how text is analyzed and acted upon.


Appendix: Quick Reference

FeatureResult TypeExample Output
Language DetectionISO Code"fr"
Sentiment AnalysisLabel & Score"Positive" (0.98)
Key Phrase ExtractionString List
Entity LinkingURL/Reference"https://en.wikipedia.org/wiki/Mars"
Curriculum Overview685 words

Curriculum Overview: Mastering Azure AI Speech Services

Describe capabilities of the Azure AI Speech service

Read full article

Curriculum Overview: Mastering Azure AI Speech Services

This curriculum provides a structured pathway for understanding the Azure AI Speech service, a core component of the Natural Language Processing (NLP) pillar within the Microsoft Azure AI ecosystem. This service enables applications to bridge the gap between spoken language and digital text.


Prerequisites

Before engaging with the Azure AI Speech modules, learners should have a foundational grasp of the following:

  • Cloud Fundamentals: Basic understanding of Microsoft Azure resource groups and API keys.
  • General AI Concepts: Familiarity with the difference between Artificial Intelligence and Machine Learning.
  • NLP Basics: Understanding that NLP involves both processing existing text (Language service) and converting speech (Speech service).
  • Data Formats: Basic knowledge of audio file types (WAV, MP3) and text encoding.

Module Breakdown

ModuleTopicDifficultyFocus Area
1Foundations of Speech AIBeginnerRecognition vs. Synthesis
2Speech-to-Text (STT)IntermediateReal-time & Batch Transcription
3Text-to-Speech (TTS)IntermediateNeural Voices & Customization
4Advanced FeaturesAdvancedDiarization & Pronunciation Assessment

Learning Objectives per Module

Module 1: Foundations of Speech AI

  • Define Speech Recognition (converting audio to text) and Speech Synthesis (converting text to audio).
  • Identify the core benefits of using a managed cloud service for speech tasks.

Module 2: Speech-to-Text (STT) Capabilities

  • Real-time Transcription: Learn how to use microphones for instant live captions.
  • Batch Processing: Understand how to process large volumes of pre-recorded audio files stored in Azure Blob Storage.
  • Fast Transcription API: Identify scenarios requiring synchronous, low-latency transcription for pre-recorded media.

Module 3: Text-to-Speech (TTS) Capabilities

  • Neural Voices: Explore how Azure uses deep learning to create lifelike, human-sounding synthesized speech.
  • Voice Customization: Understand how to adjust parameters like pitch, speed, and pronunciation to suit specific brand identities.

Module 4: Advanced Speech Scenarios

  • Speaker Diarization: Recognize the ability to identify "who spoke when" in a multi-person conversation.
  • Automatic Formatting: Utilize AI to add punctuation and capitalization to raw transcripts automatically.

Visual Anchors

Service Workflow

Loading Diagram...
Figure 1 — Mermaid diagram

The Recognition-Synthesis Loop

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Success Metrics

You will have mastered this curriculum when you can:

  1. Select the Right Tool: Correctly identify whether a business problem requires the Speech service or the Language service (e.g., transcribing a meeting vs. analyzing the sentiment of that transcript).
  2. Define STT Modes: Explain when to use Real-time transcription (live meetings) versus Batch transcription (archived call center recordings).
  3. Explain Diarization: Describe how the service distinguishes between different speakers in a single audio stream.
  4. Architect TTS Solutions: Propose a solution using neural voices to improve accessibility for visually impaired users.

Real-World Application

Azure AI Speech is not just a theoretical tool; it powers critical infrastructure across industries:

[!IMPORTANT] Accessibility: Real-time captions in livestreams or classrooms ensure that individuals who are deaf or hard of hearing can follow along without missing details.

  • Customer Service: Voice-activated IVR (Interactive Voice Response) systems allow customers to speak naturally to a system rather than pressing buttons on a keypad.
  • Productivity: Meeting transcription (like in Microsoft Teams) creates a searchable text record of a Zoom or Teams call, allowing participants to focus on the conversation rather than note-taking.
  • Media: Fast transcription APIs allow news organizations to quickly subtitle video content for social media within seconds of recording.

[!TIP] Use Speaker Diarization in legal or medical settings to ensure the transcript clearly labels which doctor or attorney made specific statements.

Curriculum Overview680 words

Curriculum Overview: Accountability in AI Solutions

Describe considerations for accountability in an AI solution

Read full article

Curriculum Overview: Accountability in AI Solutions

This curriculum focuses on the Accountability principle within the Microsoft Responsible AI framework. It explores the ethical responsibility of designers and deployers to ensure AI systems are safe, legal, and subject to human oversight.

Prerequisites

Before engaging with this module, students should have a foundational understanding of the following:

  • Basic AI Terminology: Familiarity with concepts like "models," "data," and "deployment."
  • The AI-900 Context: Understanding that Accountability is one of the six pillars of Microsoft’s Responsible AI framework.
  • General Ethics: A high-level awareness of social responsibility and the impact of technology on society.

Module Breakdown

ModuleFocus AreaDifficulty
M1: Foundational EthicsDefining accountability vs. responsibility in AI.Beginner
M2: Pre-Deployment StrategyImpact assessments and risk mitigation.Intermediate
M3: Operational OversightHuman-in-the-loop and internal review boards.Intermediate
M4: Compliance & LegalAligning with industry standards and laws.Advanced

Learning Objectives per Module

M1: Foundational Ethics

  • Define the principle of Accountability in the context of Azure AI.
  • Explain why accountability is critical for maintaining user trust.

M2: Pre-Deployment Strategy

  • Identify the purpose of an Impact Assessment.
  • Analyze how early-stage evaluations manage risks throughout the AI lifespan.

M3: Operational Oversight

  • Describe the role of Human Oversight in automated decision-making.
  • Explain the function of Internal Review Teams in overseeing high-stakes AI decisions.
  • Identify the intersection between ethical AI and legal/industry standards.
  • Describe the consequences of accountability failures (e.g., wrongful convictions or biased outcomes).

Visual Anchors

The Accountability Lifecycle

Loading Diagram...
Figure 1 — Mermaid diagram

The Balance of Accountability

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Success Metrics

To demonstrate mastery of this curriculum, the learner must be able to:

  1. Justify Oversight: Explain why an AI system should not "run the show" without human input, especially in high-stakes scenarios like facial recognition.
  2. Conduct Mock Assessments: Identify potential societal impacts for a hypothetical AI workload (e.g., a credit scoring model).
  3. Differentiate Principles: Distinguish Accountability from Transparency (Accountability is about who is responsible, Transparency is about how it works).
  4. Identify Key Actions: List the three primary actions for accountability: Impact Assessments, Human Oversight, and Internal Review Teams.

Real-World Application

Why This Matters in Your Career

  • Risk Mitigation: In a corporate environment, failures in AI accountability lead to massive legal liabilities and brand damage. Understanding these principles makes you a valuable asset in risk management.
  • Ethical Leadership: As AI becomes more autonomous, the demand for professionals who can implement "human-in-the-loop" systems is growing.
  • Social Impact: Preventing scenarios like the wrongful conviction example mentioned in the study guide is a direct application of these principles, ensuring technology serves humanity rather than harming it.

[!IMPORTANT] Accountability is not a "one-and-done" task at launch. It is a continuous process that requires monitoring the AI's outputs and stepping in when errors occur.

Curriculum Overview685 words

Curriculum Overview: Fairness in AI Solutions

Describe considerations for fairness in an AI solution

Read full article

Curriculum Overview: Fairness in AI Solutions

This curriculum covers the essential principles of Fairness as defined in the Microsoft Azure AI Fundamentals (AI-900) framework. Learners will explore how AI systems can impact individuals and groups, focusing on identifying, mitigating, and auditing for bias in automated decision-making.

Prerequisites

Before engaging with this module, students should have a foundational understanding of the following:

  • Basic AI Workloads: Familiarity with what AI is and common use cases (e.g., Computer Vision, NLP).
  • Data Literacy: Understanding that AI models are trained on datasets and that the quality of data influences the output.
  • Ethics Awareness: A general interest in the societal impact of technology and automated decision-making.

Module Breakdown

ModuleTopicFocus AreaDifficulty
1Defining FairnessCore principles and equal treatmentBeginner
2Sources of BiasData collection, historical bias, and design flawsIntermediate
3Mitigation StrategiesDiverse datasets and technical auditingIntermediate
4The Human ElementHuman-in-the-loop and accountabilityAdvanced

Learning Objectives per Module

Module 1: Defining Fairness

  • Define fairness in the context of AI as the principle of equal treatment for all users.
  • Identify high-stakes scenarios where fairness is critical, such as hiring, loan approvals, and medical treatments.

Module 2: Sources of Bias

  • Explain how AI can amplify existing societal biases.
  • Analyze how unrepresentative or "narrow" training data leads to skewed model predictions.

Module 3: Mitigation Strategies

  • Describe the importance of using diverse training datasets to ensure broad representation.
  • Explain the role of pre-deployment auditing to catch and fix biases early.

Module 4: The Human Element

  • Recognize that AI provides insights, but humans remain responsible for high-impact decisions.
  • Understand the limitations of AI predictions and the need for expert oversight.

Visual Anchors

The Fairness Lifecycle

Loading Diagram...
Figure 1 — Mermaid diagram

Bias Identification Process

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

[!IMPORTANT] Fairness does not happen by accident. It requires intentional design choices and continuous monitoring throughout the AI lifecycle.

Success Metrics

To demonstrate mastery of this topic, the learner must be able to:

  1. Identify Inequity: Given a scenario (e.g., a recruitment AI), identify which groups might be unfairly disadvantaged by specific data types.
  2. Propose Audits: Describe at least two specific actions a developer can take to audit a model before it goes live (e.g., performance testing across different demographic subsets).
  3. Explain Limitations: Articulate why an AI's recommendation should not be the sole factor in a decision that significantly affects a person's life.

Real-World Application

In the professional world, these considerations are applied in several key areas:

  • Financial Services: Ensuring loan algorithms do not discriminate based on zip codes or gender, which may correlate with protected characteristics.
  • Healthcare: Making sure diagnostic AI tools perform equally well across different skin tones or age groups.
  • Human Resources: Preventing automated resume-screening tools from favoring candidates based on historical data that reflects past discriminatory hiring practices.

[!TIP] Always ask: "Is the data we are using representative of the people this AI will serve?"

Curriculum Overview625 words

Curriculum Overview: Inclusiveness in AI Solutions

Describe considerations for inclusiveness in an AI solution

Read full article

Curriculum Overview: Inclusiveness in AI Solutions

This curriculum focuses on the Inclusiveness principle within Microsoft’s Responsible AI framework. It explores how to design AI systems that are accessible and usable by everyone, regardless of physical ability, gender, sexual orientation, or other demographic factors.

Prerequisites

Before starting this module, learners should have a foundational understanding of the following:

  • Basic AI Literacy: Understanding what Artificial Intelligence is and common workload types (Computer Vision, NLP).
  • Cloud Concepts: Familiarity with the Microsoft Azure ecosystem.
  • Responsible AI Awareness: Knowledge that AI development requires ethical guardrails beyond just technical performance.

Module Breakdown

ModuleFocus AreaDifficulty
1. Defining InclusivenessUnderstanding the ethical mandate and Microsoft's definition.Beginner
2. Barriers to InclusionIdentifying exclusions based on ability, language, age, and culture.Intermediate
3. Inclusive Design & TeamsThe role of diverse development teams and community partnerships.Intermediate
4. Technical AccessibilityImplementation of standards like Text-to-Speech and OCR for accessibility.Advanced

Learning Objectives per Module

Module 1: The Principle of Inclusiveness

  • Define inclusiveness as the goal to empower every person and every organization on the planet.
  • Distinguish Inclusiveness from other Responsible AI principles like Fairness and Transparency.

Module 2: Identifying Exclusionary Scenarios

  • Recognize how a lack of audio output can exclude visually impaired users.
  • Analyze how language barriers in AI models limit global accessibility.

Module 3: Strategies for Inclusive AI

  • Describe the importance of diverse teams in spotting hidden biases during development.
  • Explain the value of partnering with advocacy groups to represent underrepresented voices.

Module 4: Standards and Implementation

  • Identify specific Azure AI services (e.g., Azure AI Speech) that enhance inclusiveness.
  • Apply recognized accessibility standards to AI interface design.

Visual Overview of Inclusive Design

Loading Diagram...
Figure 1 — Mermaid diagram

Success Metrics

To demonstrate mastery of this topic, learners must be able to:

  1. Identify Exclusion: Given a scenario (e.g., a voice-only interface), identify which group of users is being excluded.
  2. Propose Mitigation: Suggest a technical or procedural fix (e.g., adding haptic feedback or visual cues) to improve inclusiveness.
  3. Explain the "Why": Articulate how diverse teams lead to better AI outcomes through a TikZ representation of perspective overlap.
Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Real-World Application

[!TIP] Inclusiveness is not just a moral checkbox; it is a market expander. By making a product accessible to the 15% of the global population with disabilities, companies reach a wider audience and drive innovation.

  • Education: AI-powered transcription services allow students who are deaf or hard of hearing to follow live lectures in real-time.
  • Healthcare: Using multi-language translation AI to provide medical advice in remote areas where specialists are unavailable.
  • Smart Homes: Ensuring home assistants recognize various accents and dialects, preventing "linguistic exclusion."

Success Check

[!IMPORTANT] If an AI solution works perfectly for 90% of users but is unusable for 10% due to a physical disability, it has failed the Inclusiveness test under the AI-900 framework.

Curriculum Overview625 words

Curriculum Overview: Privacy and Security in AI Solutions

Describe considerations for privacy and security in an AI solution

Read full article

Curriculum Overview: Privacy and Security in AI Solutions

This curriculum focuses on the essential principles of Privacy and Security within the context of the Microsoft Responsible AI framework. Learners will explore how to protect sensitive data, comply with global regulations, and secure AI models against emerging threats.

Prerequisites

Before engaging with this module, students should have a baseline understanding of the following:

  • Fundamental AI Concepts: Knowledge of what AI is and the common types of workloads (Computer Vision, NLP, Generative AI).
  • Data Basics: A general understanding of how data is used to train machine learning models.
  • Cloud Awareness: Familiarity with the basic concept of cloud computing services (though specific Azure expertise is not required for the introductory phase).

Module Breakdown

The following table outlines the progression of topics covered in this curriculum.

PhaseTopicFocus Area
1Foundations of PrivacyData collection, informed consent, and user control.
2Security Threats in AIProtecting against malicious actors and data manipulation.
3Regulatory ComplianceUnderstanding GDPR and other data protection laws.
4Case StudiesAnalyzing real-world failures and successes (e.g., Microsoft Tay).
5Best PracticesImplementing anonymity, integrity, and regular reviews.

Learning Objectives per Module

Upon completion of this curriculum, learners will be able to:

  • Explain the Privacy Principle: Define how AI systems must follow laws regarding data collection, storage, and usage.
  • Identify Security Risks: Describe how AI systems can be manipulated by "bad actors" (e.g., poisoning training data).
  • Evaluate Biometric Concerns: Analyze the specific privacy risks associated with facial recognition and unauthorized surveillance.
  • Apply Governance Standards: List the key practices for maintaining data integrity and performing regular security audits.

Privacy and Security Workflow

Loading Diagram...
Figure 1 — Mermaid diagram

Success Metrics

To demonstrate mastery of this topic, learners should be able to pass a series of assessments focusing on:

  1. Compliance Identification: Correctly identifying which laws (like GDPR) apply to a given AI scenario.
  2. Risk Mitigation: Proposing solutions to prevent "adversarial attacks" where users feed offensive content to a learning system.
  3. Transparency Analysis: Explaining how to give customers control over their personal information within an application.
  4. Scenario Troubleshooting: Analyzing a breach scenario (e.g., identity theft from a facial data leak) and identifying which principle was violated.

Real-World Application

Understanding privacy and security isn't just a theoretical exercise; it has massive implications for brand trust and legal standing.

[!IMPORTANT] The Tay Incident (2016): Microsoft's Twitter chatbot, Tay, learned from user interactions. Within 24 hours, bad actors manipulated its learning process to produce hate speech. This serves as a primary example of why security against data manipulation is vital.

Visualization of Privacy vs. Utility

In AI, there is often a balance between the amount of data accessed (Utility) and the level of protection (Privacy).

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Career Context

  • Data Officers: Ensure AI systems comply with international privacy standards.
  • AI Developers: Build content-filtering tools to prevent models from learning malicious behavior.
  • Security Analysts: Conduct regular reviews to protect the integrity of personal information stored in the cloud.
Curriculum Overview685 words

Curriculum Overview: Reliability and Safety in AI Solutions

Describe considerations for reliability and safety in an AI solution

Read full article

Curriculum Overview: Reliability and Safety in AI Solutions

This curriculum covers the essential principles of Reliability and Safety within the Microsoft Azure AI Fundamentals (AI-900) framework. Learners will explore how to build AI systems that are robust, consistent, and resistant to harm, ensuring they remain trustworthy even when operating in unpredictable real-world environments.

Prerequisites

Before engaging with this module, students should have a foundational understanding of the following:

  • Basic AI Concepts: Familiarity with what Artificial Intelligence is and common workloads (e.g., Computer Vision, Natural Language Processing).
  • Cloud Fundamentals: A high-level understanding of cloud computing services (though deep technical expertise is not required).
  • The Responsible AI Framework: An awareness that Reliability and Safety is one of the six pillars of Microsoft's Responsible AI principles (alongside Fairness, Privacy, Inclusiveness, Transparency, and Accountability).

Module Breakdown

ModuleTopicFocus AreaDifficulty
1Foundations of TrustDefining reliability, safety, and consistency in AI.Beginner
2Design & Stress TestingHandling edge cases, unexpected inputs, and malicious manipulation.Intermediate
3Deployment & MaintenanceOngoing auditing and preventing model degradation over time.Intermediate
4The Human ElementImplementing human-in-the-loop oversight and feedback loops.Beginner

Learning Objectives per Module

Module 1: Foundations of Trust

  • Define Reliability as the ability of a system to perform consistently under stated conditions.
  • Define Safety as the prevention of harm to people, property, or the environment.
  • Explain why reliability is the cornerstone of user trust in AI applications.

Module 2: Design & Stress Testing

  • Identify common "edge cases" where AI models might fail (e.g., unusual lighting for vision, rare dialects for NLP).
  • Describe methods for testing AI resilience against adversarial attacks or manipulation.
  • Understand the importance of involving diverse experts during the design phase.
Loading Diagram...
Figure 1 — Mermaid diagram

Module 3: Deployment & Maintenance

  • Explain Model Degradation: Why AI systems can become less accurate over time as real-world data changes.
  • Outline the necessity of regular system audits to verify ongoing performance.
  • Identify key actions for maintenance, such as retraining models with fresh data.

Module 4: The Human Element

  • Describe the role of Human Oversight in identifying blind spots and algorithmic biases.
  • Explain how user feedback loops improve system safety.
  • Discuss the responsibility of humans in making the final decision in high-stakes scenarios (e.g., medical or legal).

Success Metrics

To demonstrate mastery of this curriculum, the learner must be able to:

  1. Identify Vulnerabilities: Given a scenario (e.g., an autonomous delivery robot), list three potential "unexpected situations" the AI must handle safely.
  2. Propose Safeguards: Recommend specific actions (e.g., regular auditing, human review) to mitigate the risk of a system becoming unreliable.
  3. Explain Model Drift: Articulate why an AI system that was reliable at launch might fail six months later if left unmaintained.
  4. Differentiate Responsibility: Distinguish between the AI's role (processing data) and the human's role (governance and ethical judgment).

[!IMPORTANT] Reliability is not a "one-and-done" task. It is a continuous lifecycle that requires constant monitoring and human intervention.

Real-World Application

Understanding reliability and safety is critical for careers in AI development, data science, and IT governance.

The Balance of Oversight

The following diagram illustrates the relationship between AI performance and the necessity of human intervention to maintain a "Safety Zone."

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Practical Use Cases

  • Healthcare: Ensuring a diagnostic AI doesn't give a false negative due to a slightly blurry scan, which could lead to missed treatment.
  • Finance: Preventing a loan approval algorithm from crashing or making erratic decisions during a sudden economic shift (market volatility).
  • Manufacturing: Designing industrial robots that can detect the presence of a human worker and shut down immediately to prevent injury.

[!TIP] When evaluating an AI's maturity, always ask: "How does this system handle a situation it has never seen before?"

Curriculum Overview820 words

Transparency in AI Solutions: A Responsible AI Curriculum Overview

Describe considerations for transparency in an AI solution

Read full article

Transparency in AI Solutions: Curriculum Overview

This curriculum is designed to provide a deep dive into Transparency, one of the core pillars of Microsoft’s Responsible AI framework. It focuses on the ability to explain AI behavior, disclose usage, and ensure that AI-driven decisions are understandable to all stakeholders.

Prerequisites

Before starting this curriculum, learners should have a foundational understanding of the following:

  • AI Fundamentals: Basic knowledge of what Artificial Intelligence is and common workload types (e.g., Computer Vision, NLP).
  • Ethical Awareness: A high-level understanding of why ethics matter in technology, specifically regarding bias and fairness.
  • Data Literacy: Familiarity with the concept of training datasets and how data influences model outcomes.
  • Azure Basics: General awareness of cloud services, though deep technical expertise is not required for this conceptual module.

Module Breakdown

The curriculum is structured into four sequential modules, progressing from conceptual theory to practical implementation strategies.

ModuleTopicDifficultyKey Focus
1Foundations of Responsible AIBeginnerOverview of the 6 principles (Fairness, Reliability, etc.)
2Intelligibility & ExplainabilityIntermediateBreaking down "Black Box" models and simplifying logic
3Data & Model DisclosureIntermediateDocumenting datasets and informing users of AI presence
4Human Oversight & TrainingAdvancedTraining teams to interpret outputs and spot anomalies

Learning Objectives per Module

Module 1: Foundations of Responsible AI

  • Define the role of transparency within the broader Responsible AI framework.
  • Identify how transparency intersects with other principles like Fairness and Accountability.

Module 2: Intelligibility & Explainability

  • Explain the difference between a "Black Box" model and an interpretable model.
  • Describe strategies for simplifying complex AI behaviors for non-technical stakeholders.

Module 3: Data & Model Disclosure

  • Identify the key details about datasets that must be shared to boost trust (e.g., source, diversity, limitations).
  • Define the requirement for being "upfront" about when users are interacting with an AI (e.g., chatbots).

Module 4: Human Oversight & Training

  • Design a training plan for teams to properly interpret AI outputs.
  • Analyze the "Tay" chatbot case study to understand the consequences of failed oversight.

Visual Overview of Transparency

Understanding transparency requires looking at how information flows from the data to the end user.

Loading Diagram...
Figure 1 — Mermaid diagram

The Interpretability Trade-off

In AI development, there is often a trade-off between how accurate/complex a model is and how easy it is to explain. Transparency encourages choosing models that lean toward being "explainable."

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Success Metrics

How do you know you have mastered the concept of AI Transparency? You should be able to:

  1. Audit a Solution: Identify if an AI system provides enough information for a user to understand why a specific decision (like a loan denial) was made.
  2. Evaluate Intelligibility: Suggest a simpler model or an explanation layer for a high-stakes AI workload.
  3. Draft a Transparency Note: Create a document detailing the datasets used, the model's limitations, and its intended use cases.
  4. Identify Red Flags: Spot issues in AI behavior that stem from lack of transparency, such as "creeping bias" in unmonitored systems.

Real-World Application

[!IMPORTANT] Transparency is not just an ethical goal; it is a risk management strategy.

  • Building Public Trust: When AI affects lives (hiring, healthcare, finance), people are more likely to accept outcomes if the process is not a secret.
  • The "Tay" Lesson: Microsoft's 2016 chatbot, Tay, learned from Twitter interactions and quickly became biased. Transparency in how the model learned and better human oversight could have prevented this reputational disaster.
  • Legal Compliance: Newer privacy laws require organizations to be transparent about how data is collected and used in automated decision-making.
  • Career Impact: AI Developers and Architects who prioritize transparency are better equipped to build sustainable, legally compliant systems that survive long-term deployment.

[!TIP] Always ask: "If this AI makes a mistake, can I trace the decision back to a specific data point or logic step?" If the answer is no, your solution lacks transparency.

Curriculum Overview680 words

Curriculum Overview: Speech Recognition and Synthesis

Identify features and uses for speech recognition and synthesis

Read full article

Curriculum Overview: Speech Recognition and Synthesis

This curriculum provides a comprehensive guide to understanding how AI systems interact with human speech. It covers the dual capabilities of Speech Recognition (converting spoken audio to text) and Speech Synthesis (converting text to spoken audio), focusing on their features, real-world applications, and implementation within the Microsoft Azure ecosystem.

Prerequisites

Before starting this module, students should have a foundational understanding of the following:

  • Basic AI Workloads: Familiarity with the general categories of AI, such as Machine Learning and Natural Language Processing (NLP).
  • Cloud Fundamentals: A basic understanding of cloud computing services (ideally Microsoft Azure).
  • General NLP Concepts: Knowledge of how computers process human language (e.g., tokens, syntax).

Module Breakdown

ModuleTopicPrimary FocusDifficulty
1Foundations of Speech AICore definitions and the role of the Azure AI Speech service.Beginner
2Speech Recognition (STT)Processing sound features and phonemes to generate text.Intermediate
3Speech Synthesis (TTS)Generating natural-sounding speech from text strings.Intermediate
4Applied ScenariosReal-world implementation (Transcripts, Captions, Voice Assistants).Advanced

Learning Objectives per Module

Module 1: Foundations of Speech AI

  • Define the roles of Speech Recognition and Speech Synthesis in a conversational AI loop.
  • Identify the Azure AI Speech Service as the primary tool for speech workloads.

Module 2: Speech Recognition Features

  • Explain the process of analyzing sound features and phonemes to create text.
  • Describe use cases such as meeting transcription and real-time captioning for accessibility.

Module 3: Speech Synthesis Features

  • Identify the components of natural-sounding speech generation.
  • Explain how synthesis enables AI to "talk back" to users in interactive applications.

Module 4: Applied Scenarios

  • Differentiate between asynchronous (batch) and real-time speech processing.
  • Evaluate the effectiveness of voice-activated customer service systems.

Visual Overview

The Conversational Loop

Loading Diagram...
Figure 1 — Mermaid diagram

Signal Conversion Process

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Success Metrics

To demonstrate mastery of this curriculum, the learner must be able to:

  1. Categorize Scenarios: Correctly identify whether a business need (e.g., "We need to provide subtitles for a live stream") requires Recognition, Synthesis, or both.
  2. Define Technical Processes: Explain how speech is broken down into phonemes during the recognition process.
  3. Tool Selection: Identify the specific Azure SDKs or services needed to build a voice-activated bot.
  4. Accuracy Assessment: Understand confidence scores and how mixed-language environments affect AI speech performance.

Real-World Application

Speech AI is no longer a futuristic concept; it is a critical component of modern digital infrastructure:

  • Accessibility: Real-time captions in livestreams or meetings allow individuals with hearing impairments to participate fully.
  • Efficiency: Meeting transcription (e.g., in Microsoft Teams or Zoom) allows participants to focus on the conversation rather than note-taking.
  • Customer Experience: Voice-activated customer service IVR (Interactive Voice Response) allows users to speak naturally rather than navigating complex touch-tone menus.
  • Global Reach: Combining speech recognition with translation allows for near-instant cross-lingual communication.

[!IMPORTANT] Speech synthesis is the "voice" of AI, while recognition is the "ears." Together, they form the basis of human-computer interaction (HCI).

[!TIP] When designing for speech recognition, consider background noise and accents, as these are the most common factors that lower confidence scores in AI models.

Curriculum Overview685 words

Curriculum Overview: Common NLP Workload Scenarios

Identify features of common NLP Workload Scenarios

Read full article

Curriculum Overview: Common NLP Workload Scenarios

This curriculum provides a structured path for mastering the identification of Natural Language Processing (NLP) workloads, specifically tailored for the Microsoft Azure AI Fundamentals (AI-900) exam. NLP is a branch of AI that enables computers to understand, interpret, and generate human language.

Prerequisites

Before starting this module, students should have a foundational understanding of the following:

  • Basic AI Concepts: Familiarity with what Artificial Intelligence is and its core branches (Vision, NLP, Machine Learning).
  • Data Types: Understanding the difference between structured data (tables) and unstructured data (text, speech).
  • Cloud Fundamentals: Basic knowledge of cloud service models (SaaS, PaaS) and how they relate to API-driven AI services.

Module Breakdown

The curriculum is divided into three core pillars that progress from basic text extraction to advanced speech and translation services.

ModuleTopicComplexityDuration
1Text Analytics Essentials (Sentiment, Key Phrases, NER)Beginner45 Mins
2Privacy & Linguistics (PII Detection, Language ID, Modeling)Intermediate30 Mins
3Speech & Global Communication (Recognition, Synthesis, Translation)Intermediate45 Mins

Learning Objectives per Module

Module 1: Text Analytics Essentials

  • Identify Sentiment Analysis: Determine if a document is positive, negative, or neutral.
  • Identify Key Phrase Extraction: Extract the main talking points or concepts from a block of text.
  • Identify Named Entity Recognition (NER): Categorize specific items like people, places, dates, and organizations.

Module 2: Privacy & Linguistics

  • PII Detection: Identify and redact sensitive information (SSN, Phone Numbers, Emails).
  • Language Detection: Identify the language of a document and return the ISO code (e.g., 'en', 'fr').
  • Language Modeling: Understand how models predict the next word or phrase in a sequence.

Module 3: Speech & Global Communication

  • Speech Recognition: Convert spoken audio into text (Speech-to-Text).
  • Speech Synthesis: Convert written text into lifelike spoken audio (Text-to-Speech).
  • Translation: Convert text or speech from one language to another in real-time.

Visual Anchors

NLP Service Decision Tree

Use this flowchart to determine which NLP feature fits a specific business requirement.

Loading Diagram...
Figure 1 — Mermaid diagram

Speech Processing Pipeline

This TikZ diagram illustrates the flow of a Speech-to-Speech translation workload, combining multiple NLP features.

Compiling TikZ diagram…
Running TeX engine…
This may take a few seconds
Figure 2 — TikZ diagram

Success Metrics

To demonstrate mastery of this curriculum, the learner must be able to:

  1. Differentiate Features: Correctly choose between Key Phrase Extraction (concepts) and NER (categories) in 100% of practice scenarios.
  2. Scenario Mapping: Assign the correct Azure AI service (Language vs. Speech) based on a one-sentence business problem.
  3. Privacy Awareness: Explain when PII detection is required over standard entity recognition for compliance (e.g., GDPR/HIPAA).
  4. Output Knowledge: Identify that Language Detection returns an ISO code and a confidence score.

Real-World Application

[!TIP] NLP is not just for chatbots; it is the backbone of modern data-driven customer service and security.

  • Customer Support: Automatically routing support tickets based on Sentiment Analysis (prioritizing angry customers) and Key Phrase Extraction (identifying the product mentioned).
  • Security & Compliance: Scanning legal documents using PII Detection to ensure no private client data is accidentally published.
  • Global Accessibility: Using Speech Synthesis and Translation to provide real-time subtitles and audio for international webinars.
  • Content Moderation: Using Language Modeling and Sentiment Analysis to detect and flag toxic comments on social media platforms.

More Study Notes (79)

Curriculum Overview: Guiding Principles for Responsible AI

Identify guiding principles for responsible AI

585 words

Curriculum Overview: Responsible AI Considerations for Generative AI

Identify responsible AI considerations for generative AI

785 words

Agentic Mode: When the Answer Is Not on the Page

795 words

Agent Identity: Who the Agent Is When It Calls Something

861 words

Audio as a Modality: Prompting a Model with Sound Instead of Text

896 words

Audio: Turning Conversations Into Transcripts and Fields

886 words

Building an Extraction App: Resource, Deployments, and the Analyze Loop

898 words

Building Your First Prompt Agent in Microsoft Foundry

884 words

Carrying a Spoken Conversation Across Turns

862 words

Choosing a GPT-Image Model and Sizing a Generation Request

822 words

Choosing a Model in Foundry Models

876 words

Choosing an Endpoint, and Reading the First Error

826 words

Choosing a Speech to Text Path in Foundry

852 words

Classify, Split, Route: Sorting Content Before You Extract It

881 words

Confidence and Grounding: Deciding What a Human Must Check

887 words

Confidence, Grounding, and the Question of Who Checks the Result

858 words

Content-Processing Workloads: Use a Managed Tool or Build Your Own

911 words

Content Understanding as a Pipeline: How an Analyzer Turns Files Into Structure

890 words

Content Understanding: One Pipeline, Four Kinds of Content

874 words

Deploying a Model: Serverless API, Managed Compute, and Instant Access

816 words

Deployment Options: Serverless API, Managed Compute, and Instant Access

821 words

Deployment Types: Where Your Data Is Processed and How You Pay

777 words

Designing a System Message That Survives Real Users

809 words

Detail Level and the Token Cost of Looking Closely

872 words

Diagnosing a Refusal or a Vague Answer on an Image Prompt

853 words

Embeddings and Retrieval: Why Search Became a Text-Analysis Workload

842 words

Examples, Decomposition, and Output Contracts in Image Prompts

867 words

Extract, Classify, Generate: Designing a Field Schema for Text Analysis

891 words

Extract, Classify, Generate: The Three Shapes an AI Output Can Take

876 words

Field Descriptions Are Prompts: Writing Schemas the Model Can Follow

893 words

From Playground to Production: The Agent Development Lifecycle

894 words

From Voice Gallery to Running Code: The Text to Speech Authoring Path

856 words

Generating and Editing Images with Foundry Image Models

908 words

Grounding: Making a Model's Answers Checkable

846 words

Guardrails and Controls: Where Microsoft Foundry Intercepts Risk

885 words

Harm Categories and Severity: Deciding How Much Is Too Much

850 words

How a Generative Model Actually Produces an Answer

859 words

How a Multimodal Model Takes an Image as Input

898 words

How Benchmark Numbers Are Made, and Where They Mislead

851 words

Identify and Measure: Building the Harms Inventory

891 words

Identifying AI Workloads and the Foundry Piece That Serves Them

907 words

Image Generation Workloads: Prompt, Edit, and the Model That Went Away

799 words

Images as Evidence: What an Image Analyzer Is Good At

865 words

Inferred Fields: When Text Analysis Reasons Past What the Page Says

897 words

Information Extraction: The Structure Hiding Under the Text

822 words

Inside an Analyzer Definition: Base, Config, and Schema

841 words

MAI Image Models: Microsoft's Own Text-to-Image Family in Foundry

844 words

Masks, Input Fidelity, and the Mechanics of a Targeted Edit

895 words

Mitigating in Layers: Four Places to Intervene

902 words

Modality First: Sorting AI Workloads by What Goes In

874 words

Model Leaderboards: The Four Dimensions a Model Is Scored On

784 words

Model Versions, Upgrade Policies, and Retirement

834 words

Operate: Responsible AI After the Launch

870 words

Prebuilt Analyzers: Starting From Someone Else's Homework

851 words

Prompting Vision-Enabled Chat Models on Images

887 words

Prompt Layout: Order, Recency, Syntax, and the Token Budget

838 words

Prompt Transformation: The Prompt You Send Is Not the Prompt That Runs

872 words

Quotas, Rate Limits, and What a 429 Is Telling You

808 words

Reading Documents with Content Understanding: Extraction You Can Audit

905 words

Reasoning Models and the Reasoning Effort Dial

810 words

Recognizing Speech with Azure Speech in Foundry

870 words

Risk and Safety Evaluators: Measuring Harm Before Your Users Do

884 words

Scoping the Use Case: Where Responsible AI Starts

868 words

Speech Synthesis: Choosing a Voice Is Choosing a Commitment

853 words

Synthesizing Speech: Voices, Locales and Output in Foundry

886 words

Temperature, Top P, and the Settings That Shape a Response

841 words

The Anatomy of a Prompt: Instructions, Content, Examples, and Cues

851 words

The Catalogue's Two Families: Sold by Azure, and From Partners and Community

794 words

The Image Generation Tool: Giving an Agent a Second Model

894 words

The Playground as a Validation Surface, Not a Toy

836 words

Tokens and the Context Window: The Budget Every Request Spends

832 words

Tools and Knowledge: How an Agent Reaches Past the Model

868 words

Tuning Transcription Accuracy: Phrase Lists, Language Identification and Diarization

848 words

Turn-Taking in a Real-Time Voice Agent: Interruption, Echo and Noise

862 words

Video: Two Passes, Key Frames, and Segments

868 words

What Actually Makes Something an Agent

821 words

When Text to Speech Produces Nothing: Diagnosing Silent and Wrong-Sounding Output

877 words

Why Voice Live Collapses the Three-Box Voice Pipeline

870 words

Your First Chat Client: One Endpoint, Two Kinds of Client

844 words

Ready to practice? Jump straight in — no sign-up needed.

Take practice tests, review flashcards, and read study notes right now.

Take a Practice Test

Microsoft Azure AI Fundamentals (AI-901) Practice Questions

Try 15 sample questions from a bank of 663. Answers and detailed explanations included.

Q1easy

During a demo, a stakeholder asks why the model produced a confident answer to a question it plainly had no information about, instead of staying silent. Which explanation matches how the guidance describes the behaviour of these models?

A.

Whatever the prompt, the model produces what it determines is the most likely continuation, and for a question the most likely continuation is an answer

B.

The model matches the question against a stored question-and-answer database and returns the nearest record it finds

C.

A question mark switches the model onto a separate question-answering code path that must return something

D.

Content filters oblige the model to emit a response, so returning nothing is not possible

Show answer & explanation

Correct Answer: A

The article frames every generation the same way: the model continues the text with whatever it judges most likely given its training, so a question draws an answer because an answer is the likely shape of what follows a question. The guidance explicitly denies that a separate question-answering path exists, which disposes of the question-mark option. There is no lookup against a stored answer database, and content filtering screens content rather than forcing the model to speak.

Q2medium

A developer scripts a handful of REST calls against their project endpoint using a token obtained from the Azure CLI. The calls succeed all morning, then start failing with authorization errors a little over an hour later. What is the most likely cause?

A.

The temporary access token has expired and needs to be requested again

B.

The agent version was deleted once its first response completed

C.

The project endpoint URL rotates hourly and has to be copied again

D.

The model deployment scaled to zero while idle, which makes it reject credentials

Show answer & explanation

Correct Answer: A

A token fetched from the CLI is short-lived by design, lasting on the order of an hour before it has to be refreshed, which matches the symptom exactly. Agent versions persist until you delete them (B), the project endpoint is a stable address tied to the resource and project names (C), and a deployment scaling down affects availability or latency, not whether a credential is accepted (D).

Q3medium

A lightweight contract-review app depends on agentic mode, which is offered only in the preview API version of Content Understanding. The team lead asks what that means for the planned production launch. Which statement is correct?

A.

Preview API versions come with no service-level agreement and are not recommended for production workloads, so the launch plan has to account for that

B.

A preview API version is covered by the same service-level agreement as the generally available version once an analyzer has been created on it

C.

Preview capabilities are free of charge until they reach general availability, so cost planning can wait until then

D.

The team can call the generally available API version and still get agentic mode, because the workflow choice is stored on the analyzer

Show answer & explanation

Correct Answer: A

Agentic mode is a preview capability, and previews are offered without a service-level agreement and are not the recommended footing for production. That does not prevent evaluation, but a production plan has to account for it, for example by keeping a standard analyzer on the generally available version as the shipping path. Creating an analyzer does not promote a preview version to general-availability terms, previews are not automatically free, and the agentic workflow cannot be invoked from the generally available version because the capability is not offered there.

Q4easy

A support team builds an assistant that must answer strictly from a set of internal policy documents pasted into the prompt. In testing, whenever the documents do not cover a question the assistant invents a plausible-sounding answer instead of declining. Which change to the prompt does the guidance recommend to reduce this?

A.

Add an instruction telling the model to reply with not found when the answer is not present in the supplied text

B.

Raise the temperature so the model explores a wider range of possible answers

C.

Remove the system message so the model is not over-constrained

D.

Ask the model to answer in as few words as possible

Show answer & explanation

Correct Answer: A

This is the practice of giving the model an out. When a prompt asks a question over a supplied body of text, offering an explicit alternative path for the case where the answer is simply absent gives the model something acceptable to say instead of manufacturing content, and the guidance lists it among the core best practices for reducing false responses. Raising temperature increases randomness, which makes invention more likely rather than less. Deleting the system message removes constraints instead of adding the one that is missing. Asking for brevity limits how long the answer is but says nothing about whether it is supported by the documents.

Q5medium

A legal team is reviewing an agent built on Foundry Agent Service that answers customer questions with help from the Grounding with Bing Search tool. The team has assumed the Microsoft Products and Services Data Protection Addendum covers everything the agent touches. What should they be told?

A.

The Data Protection Addendum automatically extends to every external tool an agent is allowed to call.

B.

Bing results are covered by the same terms as model inferencing, because both run inside the customer's own tenant.

C.

Data handled by the Grounding with Bing Search tool falls under that tool's own data collection and privacy terms, and the service is excluded from the Data Protection Addendum.

D.

External tool data is covered by the addendum as long as the agent's resource sits in the customer's designated geography.

Show answer & explanation

Correct Answer: C

The addendum governs how Agent Service itself processes data, but it does not travel with the agent out to external services the agent calls. Grounding with Bing Search carries its own data collection and privacy terms, and because Microsoft acts as controller for that service it sits outside the addendum entirely. The search service does not run inside the customer's tenant, so it cannot inherit the terms that apply to inferencing. Geography is a separate question: where the agent's resource sits determines where data is stored at rest, not which contract applies to a third-party tool. The practical lesson is to review the terms of each connected tool on its own.

Q6hard

An insurance company is building an automated workflow to process incoming claim descriptions with Azure Language in Foundry Tools. The workflow must do three things: 1. Mask any mentions of policyholder phone numbers and home addresses before the text is stored. 2. Assign each claim to exactly one of five company-defined categories: Collision, Theft, Natural Disaster, Vandalism, or Other. 3. Judge whether the policyholder is expressing frustration or anger. Which combination of Azure Language capabilities best fits this workflow?

A.

PII detection, custom text classification, and sentiment analysis

B.

Named entity recognition (NER), key phrase extraction, and opinion mining

C.

Entity linking, custom named entity recognition (custom NER), and conversational language understanding (CLU)

D.

PII detection, summarization, and question answering

Show answer & explanation

Correct Answer: A

PII detection is the capability built to identify, classify, and redact sensitive values such as phone numbers and addresses, so it covers the masking requirement directly. Custom text classification lets the team label their own claims, train a model, and assign each document to one of a fixed set of classes they define; a single label classification project assigns exactly one class per document, which is what the five-category requirement asks for. Sentiment analysis returns positive, neutral, or negative labels with confidence scores at both the sentence and document level, which is how anger or frustration is surfaced. Prebuilt NER finds entities but does not provide the redaction workflow that PII detection does, and key phrase extraction returns the main concepts in a document rather than assigning it to a predefined class. Custom NER extracts spans of text, not whole-document categories. Summarization and question answering address neither categorization nor emotional tone. Answer: A

Q7medium

A developer is wiring up a lightweight app that reads screenshots. At startup it needs to list the connections configured on the project, and at request time it sends an image and a question to the deployed model. Which use of the two client types fits the SDK design?

A.

Use the project client for the connection listing and the OpenAI-compatible client for the model call

B.

Use the OpenAI-compatible client for both, because it also covers Foundry-native project operations

C.

Use the project client for both, because it wraps every OpenAI-style request

D.

Use two different SDKs, because these two kinds of call cannot share one project endpoint

Show answer & explanation

Correct Answer: A

The SDK splits into a project client for Foundry-native work such as inspecting connections and configuration, and an OpenAI-compatible client for anything built on OpenAI shapes, which is where model calls, agents, and evaluations live. Most applications use both against the same project endpoint, so neither one covers the whole job and no second SDK is needed.

Q8easy

According to Microsoft's guiding principles for responsible AI, which statement best defines the principle of inclusiveness?

A.

Ensuring that AI systems provide clear explanations for their underlying logic and decision-making processes.

B.

Designing AI systems to be usable by as many people as possible, ensuring that those traditionally excluded can access the benefits of AI.

C.

Subjecting AI systems to rigorous testing to ensure they function safely and reliably under diverse and unexpected conditions.

D.

Implementing organizational structures that ensure humans take responsibility for the impact and outcomes of AI systems.

Show answer & explanation

Correct Answer: B

Inclusiveness is the principle of creating AI systems that are accessible to everyone. It involves inclusive design that considers factors like ability, language, culture, gender, and age to prevent the exclusion of any group of people. Answer: B

Q9medium

A team has a client app that calls models through the resource-level Azure OpenAI endpoint with the OpenAI SDK. They now want the same app to call a Foundry agent and use platform tools such as file search. What should they change?

A.

Switch to the Foundry SDK and target the project endpoint

B.

Keep the same endpoint and list the tool names in each request body

C.

Keep the OpenAI SDK and add the project name as a request header

D.

Replace Entra ID authentication with an API key on the existing endpoint

Show answer & explanation

Correct Answer: A

Agents, evaluations and the platform tool set are project-scoped capabilities, so they are reachable only through the project endpoint that the Foundry SDK targets. The resource-level Azure OpenAI endpoint is a model surface: naming tools in the body or adding a header does not conjure a project context there. Changing the credential type is an authentication decision and has no bearing on which capabilities an endpoint exposes.

Q10medium

A developer wants to try inferencing today with a model from the Foundry catalog, but their subscription has no dedicated quota for it and they do not want to wait on a support ticket. What is the correct way to use Foundry shared quota here?

A.

Use shared quota to stand up a temporary test endpoint now, then request dedicated quota before the workload goes to production

B.

Use shared quota for the test endpoint and keep it for the production endpoint, since the pool is available to the whole subscription

C.

Use shared quota because it carries no charge, and leave the endpoint running to avoid paying later

D.

File a quota request first, because shared quota is only released after a quota increase is approved

Show answer & explanation

Correct Answer: A

The shared pool exists precisely so that a developer can borrow capacity for a limited time and test inferencing without first getting a quota request approved, which rules out the option that says a ticket must come first. It is meant only for temporary test endpoints, so carrying it into production is wrong, and anything going to production should have dedicated quota requested for it. Shared quota is also not free: consumption through it is billed on usage like any other, so leaving the endpoint running does not avoid cost.

Q11hard

A developer inspects the prebuilt invoice analyzer their lightweight app uses and sees that its models section names prebuilt-analyzer-completion instead of an actual model name. What does that tell them?

A.

It is a model alias that you map to one of your own deployments, which lets the service adopt a newer model without the analyzer definition changing

B.

It is a Microsoft-hosted deployment, so the team does not need to supply a deployment of their own

C.

It pins the analyzer to the exact model version it was published with, so its output can never change

D.

It marks an analyzer that runs without any generative model, using only optical character recognition

Show answer & explanation

Correct Answer: A

Prebuilt analyzers deliberately reference aliases rather than concrete model names, and you map each alias to a deployment you own. The point of the indirection is that the service can move the alias onto a newer model without anyone having to edit the analyzer definition. It does not mean Microsoft supplies the deployment, since you bring your own, and it is the opposite of pinning a fixed version. Prebuilt analyzers still lean on a generative model for field extraction, so the fourth option is wrong as well.

Q12easy

What is the primary characteristic that distinguishes a generative AI workload from other types of artificial intelligence workloads?

A.

It categorizes data into predefined labels based on historical patterns.

B.

It creates new, original content such as text, images, or computer code.

C.

It identifies and locates specific objects within a digital image.

D.

It calculates the probability of a future numerical outcome using regression.

Show answer & explanation

Correct Answer: B

Generative AI is specifically designed to generate new content, such as text, imagery, or computer code, based on the patterns it has learned from training data. In contrast, traditional AI workloads typically focus on classifying data (A), detecting objects (C), or predicting values (D). Answer: B

Q13easy

A marketing team spends Friday afternoon generating candidate clips in the video playground and plans to come back on Monday to choose between them. What should they be told before they leave for the weekend?

A.

Generated videos are kept for 24 hours, so anything they want on Monday must be downloaded to a local computer now

B.

The clips stay with the deployment until the deployment itself is deleted, so nothing needs doing

C.

Clips are kept for 30 days by default, and the retention period can be extended in the project settings

D.

Clips survive only while the browser tab stays open, so the machine should be left running

Show answer & explanation

Correct Answer: A

The video playground carries an explicit caution that generated videos are retained for only 24 hours for data privacy reasons, and the troubleshooting table repeats that downloading locally is the way to keep them longer. A weekend gap therefore loses the clips. Retention is not tied to the lifetime of the deployment, there is no 30-day default or configurable extension described, and closing the browser is not what ends retention.

Q14easy

A startup lets users upload voicemail recordings to a deployed gpt-4o-mini-audio-preview model so it can summarize them out loud. Short clips work, but one 45 MB uncompressed recording is rejected. What is the most likely cause?

A.

The recording is larger than the maximum audio file size the model accepts

B.

wav is not one of the audio formats the model can work with

C.

Chat completions can produce audio but cannot accept audio as input

D.

Audio prompts have to be captured live from a microphone rather than uploaded as files

Show answer & explanation

Correct Answer: A

Audio input to these models is capped at 20 MB per file, so a 45 MB recording is turned away on size alone; the team needs to compress or split the voicemail. The other choices contradict how the models work: wav is a supported audio format on both the input and the output side, audio is explicitly allowed as a prompt rather than only as a response, and the whole point of the file-based flow is that a stored recording is encoded and sent in the request, so a live microphone is not required.

Q15easy

A team lead tells a developer that prompt-based agents can only be assembled through the Foundry portal, so every tweak means leaving the editor. Is there another route to creating one?

A.

Yes — a prompt-based agent can also be created from your own development environment using the CLI, the SDK, or the REST API

B.

No — the portal is the only surface that can create a prompt-based agent; code can only invoke one that already exists

C.

Yes — but only by building a container image and letting Foundry Agent Service deploy it for you

D.

Yes — but creating agents from code is limited to hosted agents, so a prompt-based agent has to start in the portal

Show answer & explanation

Correct Answer: A

A prompt-based agent is a declarative thing — a model, some instructions, and optionally tools — so it can be expressed just as well in a script as in a form. Foundry supports both: build it in the portal, or create it from your own environment through the CLI, the SDK, or a plain REST call. The container route described in one distractor is how hosted agents work, and it is a different agent type entirely, not a prerequisite for prompt agents. The portal is a convenience for people who want to iterate visually, not a gate that code has to pass through.

These are 15 of 663 questions available. Take a practice test →

Microsoft Azure AI Fundamentals (AI-901) Flashcards

587 flashcards for spaced-repetition study. Showing 30 sample cards below.

Accountability in AI Solutions(10 cards shown)

Question

Accountability (Responsible AI Principle)

Answer

The guiding principle that ensures those who design and deploy AI systems are responsible for their operation, ensuring they are ethical, safe, and aligned with legal standards.

[!NOTE] Accountability is about being answerable for the outcomes of an AI system, especially when things go wrong.

Question

Impact Assessments

Answer

Evaluations conducted early in the AI development process to analyze how a solution might affect individuals, organizations, and society.

Loading Diagram...
Figure 1 — Mermaid diagram

[!TIP] Think of this as a "pre-flight check" for societal and ethical risks.

Question

Human Oversight

Answer

The practice of ensuring that AI does not operate without meaningful human intervention or control.

Purpose:

  • Prevents over-reliance on AI outputs.
  • Allows humans to step in during high-stakes situations.
  • Ensures the system remains under human command.

[!WARNING] Without oversight, an AI could scale errors or bias without any manual way to stop it.

Question

Internal Review Teams

Answer

A group within an organization that provides governance and oversight for AI projects, reviewing key decisions and ethical alignment.

FeatureInternal Review Team Role
FocusEthics and Compliance
TimingThroughout AI Lifespan
GoalMinimize risk and ensure accountability

Question

Lifespan Risk Management

Answer

The continuous monitoring of an AI system from initial design through deployment and maintenance to identify and manage evolving risks.

[!NOTE] Accountability does not end once the model is deployed; it requires constant vigilance to ensure continued safety and fairness.

Question

How Microsoft groups its Responsible AI principles

Answer

The set of principles in Microsoft's Responsible AI Standard, applied together across the AI lifecycle.

Includes:

  • Fairness
  • Reliability and Safety
  • Privacy and Security
  • Inclusiveness
  • Transparency
  • Accountability

Microsoft states these as one set of six — there is no separate 'Ethical AI' or 'Explainable AI' category.

Question

Meaningful Human Input

Answer

The requirement that human operators have the tools and understanding necessary to effectively supervise AI systems.

Components:

  • Interpretable outputs
  • Effective control interfaces
  • Training on system limitations

[!TIP] It's not just about a human being present; it's about the human being informed enough to make a better decision than the AI alone.

Question

Legal and Industry Standards

Answer

The external regulations and professional benchmarks that AI solutions must comply with to be considered 'Accountable'.

Example: GDPR (General Data Protection Regulation) for privacy, or specific regional laws governing facial recognition and law enforcement.

Question

Accountability Scenario: Facial Recognition

Answer

A high-stakes example where lack of accountability can lead to severe real-world consequences, such as wrongful convictions due to faulty matches.

Actionable Response:

  • Implement strict human-in-the-loop verification.
  • Conduct regular audits for bias and error rates.
  • Establish a clear path for legal recourse and system correction.

Question

Key Actions for Accountability

Answer

Summary of the three primary steps organizations take to uphold this principle:

  1. Conduct impact assessments.
  2. Maintain human oversight.
  3. Set up internal review teams.
Loading Diagram...
Figure 1 — Mermaid diagram

A chat client on the Foundry SDK(7 cards shown)

Question

What does a Foundry resource give an application access to?

Answer

Unified access to models, agents and tools — one resource rather than a separate service per capability, which is why one client can reach all three.

Question

Describe the Foundry SDK in one sentence.

Answer

A thin-client SDK that exposes all of the Foundry project APIs through a single project endpoint.

Question

Your app needs models today and agents next quarter. Does the endpoint change?

Answer

No — the project endpoint exposes the project's APIs, so adding agents later is a new call through the same endpoint rather than a new integration.

Question

Where do higher-level SDKs such as the agent framework sit relative to the Foundry SDK?

Answer

They build on top of it. The thin client is the foundation; the higher-level SDKs add abstractions above it, so choosing one does not mean leaving the platform.

Question

What is the first thing a lightweight chat client needs before it can call anything?

Answer

The project endpoint, and credentials to authenticate against it. Everything else — which model, which deployment — is a parameter of the call, not a separate connection.

Question

A developer asks whether to call the model's API directly or go through the project endpoint. What is the trade?

Answer

Direct calls tie the app to one model surface; the project endpoint keeps models, agents and tools reachable through one client, which is what makes swapping a deployment a configuration change.

Question

Which article answers 'which SDK and endpoint should I use?'

Answer

The Foundry SDKs and endpoints article — it exists specifically to route a scenario to the right SDK, and is the correct first stop rather than guessing from a quickstart.

A client application for an agent(8 cards shown)

Question

What is a hosted agent?

Answer

Your own agent code — packaged as a container — that Foundry runs for you with a managed endpoint, scaling, identity and observability.

Question

Which frameworks are named as options for writing hosted agent code?

Answer

Agent framework, LangGraph, the OpenAI Agents SDK, the Anthropic Agent SDK, the GitHub Copilot SDK, or your own code. The platform is deliberately framework-agnostic.

Question

What four things does Foundry provide once it hosts your agent container?

Answer

A managed endpoint, scaling, identity and observability — the operational surface you would otherwise build and run yourself.

Question

A client app needs to talk to an agent. What is it actually calling?

Answer

The responses API — the single entry point to the agent, whether that agent is a portal-authored prompt agent or a hosted container.

Question

Your agent runs today on a VM outside Azure. What is the lowest-friction way to adopt Foundry models and tools?

Answer

Call the responses API from the existing process. It gets Foundry models and platform tools without moving the code, so adoption does not start with a migration.

Question

When does a prompt agent stop being enough?

Answer

When the behaviour needs real code — custom orchestration, libraries, or logic that instructions and tool definitions cannot express. At that point the same agent becomes a hosted agent, keeping the same entry point.

Question

Why does packaging as a container matter for the client application?

Answer

Because the client keeps calling an endpoint regardless of what runs behind it. Containerisation is how arbitrary code gets a managed endpoint, so the client contract does not change with the implementation.

Question

What does 'use any framework, any supported model' protect you from?

Answer

Lock-in at two layers at once — the agent framework and the model. Both stay swappable behind one entry point, which is the platform's central design claim.

Adding image generation to an agent app(5 cards shown)

Question

What does attaching the image generation tool give a Foundry agent?

Answer

The agent can turn a request into a picture mid-conversation: its orchestrator model calls the tool, and the run comes back carrying base64 image bytes your app saves to a file.

Question

How many model deployments does the agent image generation tool need, and of what kind?

Answer

Two, in the same Foundry project: a chat model such as gpt-5 to run the conversation, and gpt-image-1 to draw. If either is missing, generation fails.

Question

Which image model does this tool require, and what gate stands in front of it?

Answer

gpt-image-1, which is limited access — you apply for approval before the deployment can be created. Planning a demo without allowing for that approval is a common stall.

Question

Which extra HTTP header must the request carry for the agent's image generation to work?

Answer

The image generation deployment header, set to the name of your image deployment. Omit it and the run returns ordinary text with no picture attached.

Question

How do you confirm from the response payload that the tool actually ran?

Answer

Look for an output item whose type is an image generation call, holding a result field of base64 data. Text-only output means the request never reached image generation.

Showing 30 of 587 flashcards. Study all flashcards →

Ready to ace Microsoft Azure AI Fundamentals (AI-901)?

Access all 663 practice questions, 13 timed mock exams, study notes, and flashcards — no sign-up required.

Start Studying — Free