AI-103 Practice Questions and Answers

By the AI-103 Exam Questions team · 12 min read · Updated July 2026

TL;DRAI-103 replaces AI-102 and shifts the exam toward Azure AI Foundry, generative AI, and autonomous agents. Below are 10 original, scenario-based practice questions covering all 5 domains, each with a full explanation and a breakdown of why the wrong answers are wrong.

If you studied for AI-102 before, don't assume the old material transfers directly. AI-103 reorganizes everything around Azure AI Foundry as the central development platform, and generative AI plus agent-building now make up close to a third of the exam on their own.

AI-103 exam overview

AI-103, officially titled Developing AI Apps and Agents on Azure, is Microsoft's associate-level certification for developers who design, build, and secure AI applications and agents on Azure. Here are the fast facts.

Exam codeAI-103
Official titleDeveloping AI Apps and Agents on Azure
Certification earnedAzure AI Apps and Agents Developer Associate
Exam statusBeta, moving toward general availability in mid-2026
ReplacesAI-102 (Azure AI Engineer Associate), retiring June 30, 2026
Passing score700 out of 1000
Duration100 minutes
Question countRoughly 40 to 60 questions
PrerequisitesPython development experience, familiarity with Azure AI services

The five skill domains and their weightings

DomainWeightingQuestions in this guide
Plan and Manage Azure AI Solutions25–30%2
Implement Generative AI and Agentic Solutions30–35%2
Implement Computer Vision Solutions10–15%2
Implement Text and Speech Solutions10–15%2
Implement Information Extraction Solutions10–15%2

Jump to a domain

How to use these practice questions

Read the scenario first and try to answer it before looking at the explanation. These aren't memorization questions. They're built the way the real exam is built: a situation, a requirement, and four options that all sound plausible until you look closely.

Domain 1: Plan and Manage Azure AI Solutions

Choosing the right Azure AI service or Foundry setup for a scenario, plus the security and monitoring config around it.

Question 1

Several teams at your company are each building their own AI app, but leadership wants shared governance: one place to manage connections, network rules, and access policies across all of them. What should you set up?

  1. A separate Azure OpenAI resource for each team, managed independently
  2. A Foundry hub with one project per team, connected to the shared hub
  3. A single Azure AI Language resource that every team calls
  4. Separate resource groups with no shared hub

Why B is correct

A Foundry hub is built for exactly this. It holds the shared connections, network configuration, and security policy, while each team gets its own project underneath it for isolation. You get centralized governance without teams stepping on each other.

Why the other options are wrong

  • Separate resources per team means separate policies too, which is the opposite of centralized governance.
  • Azure AI Language handles text tasks, not the kind of cross-service resource management this scenario needs.
  • Resource groups without a hub still leave you configuring security and networking separately for every team.

Tip: Whenever a question mentions sharing governance or connections across teams, think Foundry hub first.

Question 2

You need your application to call Azure OpenAI without ever storing an API key in code, config files, or environment variables. Which setup meets this requirement?

  1. Store the key in an environment variable and reference it at runtime
  2. A managed identity with an Azure RBAC role assigned to the OpenAI resource
  3. Rotate the API key manually every 30 days
  4. Hard-code the key and restrict the source file's permissions

Why B is correct

Managed identity paired with an RBAC role assignment is the keyless pattern. The app authenticates as its own Azure identity, and there's no secret to store, rotate, or leak in the first place.

Why the other options are wrong

  • An environment variable is still a stored key, just in a different location.
  • Manual rotation reduces risk but doesn't remove the key from storage.
  • Hard-coding a key is the pattern this question is testing you to avoid, no matter how it's protected.

Tip: "Keyless" in a question stem almost always points to managed identity plus RBAC.

Domain 2: Implement Generative AI and Agentic Solutions

The biggest domain by far. Azure OpenAI models, prompt engineering, RAG, and building agents that call tools and hold memory.

Question 3

You're adding a text-classification feature to a mobile app. It has to run on the device itself, work without an internet connection, and respond in under 200ms. Which type of model fits this requirement?

  1. A large frontier LLM accessed through the Azure OpenAI API
  2. A small language model (SLM) deployed locally on the device
  3. A multimodal model with image and audio support
  4. An agent that calls multiple external tools

Why B is correct

Small language models are built for exactly this: a lightweight footprint, low latency, and the ability to run without a live connection to a cloud endpoint. A frontier LLM needs network access and has far more overhead than this task requires.

Why the other options are wrong

  • A large LLM needs an API call, which breaks the offline requirement immediately.
  • Multimodal capability isn't relevant here since the task is plain text classification.
  • An agent framework adds complexity this simple, single-step task doesn't need.

Tip: Offline, on-device, and low-latency in the same sentence is the classic signal for an SLM.

Question 4

You're building a chatbot that must answer questions using your company's internal documentation, and those documents change weekly. What's the right approach to keep the bot's answers current?

  1. Fine-tune the base model on the full document set
  2. Configure retrieval-augmented generation (RAG) with vector or hybrid search over an indexed copy of the documents
  3. Increase the model's max token limit
  4. Rely on keyword search only, without embeddings

Why B is correct

RAG grounds the model's answers in your indexed documents at query time, so updating the index updates the bot's knowledge without retraining anything. Fine-tuning weekly would be slow and expensive, and it still wouldn't guarantee grounded, current answers.

Why the other options are wrong

  • Fine-tuning bakes knowledge into the model weights, which is the wrong tool for content that changes every week.
  • A bigger token limit lets you stuff in more context, but it doesn't solve retrieval or relevance on its own.
  • Keyword search alone misses semantically related content that doesn't share exact wording with the query.

Tip: Frequently changing source data plus a chatbot is almost always a RAG question, not a fine-tuning one.

Domain 3: Implement Computer Vision Solutions

Image and video analysis, OCR, Custom Vision, and the newer Content Understanding pipelines.

Question 5

Your company's product photo library needs descriptive alt text generated automatically so the site meets accessibility guidelines. Which capability should you configure?

  1. Object detection with bounding boxes only
  2. Azure AI Vision's dense captioning and alt-text generation
  3. OCR to extract any text printed on the product
  4. A Custom Vision image classification model

Why B is correct

Azure AI Vision has built-in dense captioning and alt-text generation designed specifically to produce accessibility-aligned image descriptions, not just labels or bounding boxes.

Why the other options are wrong

  • Bounding boxes tell you where objects are, not a natural-language description of the image.
  • OCR only reads text that's visibly printed in the image; most product photos don't have usable embedded text.
  • A classification model returns a category label, which is far shorter than a proper accessibility description.

Tip: Accessibility and alt-text in a prompt point to Vision's captioning features, not object detection or classification.

Question 6

You're building a media catalog app that needs to identify and describe individual segments within uploaded video files, not just single frames. What should you configure?

  1. Single-frame object detection run on sampled screenshots
  2. A Content Understanding video analysis pipeline for segment-level interpretation
  3. Frame-by-frame OCR
  4. A Custom Vision classification model applied per frame

Why B is correct

Content Understanding's video pipeline is built to process and interpret video at the segment level, which is what this scenario actually asks for. Frame-based approaches lose the temporal context that makes a segment meaningful.

Why the other options are wrong

  • Sampling single frames throws away everything that happens between those frames.
  • OCR only helps if there's text in the video; it says nothing about what's happening visually.
  • A per-frame classifier gives you a label per frame, not a coherent description of a segment over time.

Tip: "Segments" or "over time" in a video question usually rules out single-frame approaches.

Domain 4: Implement Text and Speech Solutions

Azure AI Language for text (sentiment, intent, PII) and Azure AI Speech for voice interactions.

Question 7

A support bot needs to route each incoming customer message to the correct department based on what the customer is actually asking for. Which service should you use to build this?

  1. Sentiment analysis on the incoming message
  2. Conversational Language Understanding (CLU) with a custom intent model
  3. PII detection and redaction
  4. Azure AI Translator

Why B is correct

Routing based on intent is a classification problem, and CLU is the Azure AI Language feature built to train custom intent models for exactly this kind of task.

Why the other options are wrong

  • Sentiment tells you how the customer feels, not what department should handle the request.
  • PII detection is about finding and masking sensitive data, unrelated to routing logic.
  • Translator converts between languages; it doesn't classify intent at all.

Tip: "Route based on what the customer wants" is intent classification, which means CLU.

Question 8

A language-learning app needs to score how accurately a learner pronounces a phrase and highlight specific words that need work. Which Azure AI Speech feature fits this?

  1. Text-to-speech synthesis
  2. Pronunciation assessment
  3. Speech translation
  4. Custom neural voice

Why B is correct

Pronunciation assessment is built to score spoken input against a reference phrase and flag accuracy at the word and phoneme level, which is exactly what this scenario is asking for.

Why the other options are wrong

  • Text-to-speech generates audio from text; it doesn't evaluate a learner's spoken input at all.
  • Speech translation converts spoken content between languages, not a pronunciation score.
  • Custom neural voice builds a synthetic voice model; it has nothing to do with scoring a learner's speech.

Tip: Any question about scoring or grading spoken input points straight to pronunciation assessment.

Domain 5: Implement Information Extraction Solutions

Pulling structured data out of documents with Document Intelligence and Content Understanding, usually to feed a RAG pipeline.

Question 9

Your finance team processes thousands of standard vendor invoices every month and needs the key fields (vendor, total, due date, line items) extracted automatically. What's the fastest way to implement this?

  1. Train a custom extraction model from scratch on your invoice samples
  2. Use the prebuilt invoice model in Azure AI Document Intelligence
  3. Run plain OCR and parse the text with regular expressions
  4. Use Content Understanding for image classification only

Why B is correct

Document Intelligence ships a prebuilt invoice model that already knows how to extract standard invoice fields. It's the fastest path for a common, well-structured document type like a vendor invoice.

Why the other options are wrong

  • Training a custom model from scratch takes labeled data and time you don't need for a standard document type.
  • Regex over raw OCR text breaks the moment invoice layouts vary even slightly.
  • Image classification tells you what type of document it is, not the field values inside it.

Tip: Standard, common document types (invoices, receipts, ID cards) usually map to a prebuilt Document Intelligence model, not a custom one.

Question 10

You're building a RAG pipeline that needs to answer questions from scanned contracts. Before indexing, you need a clean, structured representation of each contract that preserves layout and section context. What should you use?

  1. Store the raw scanned PDFs directly in the vector index
  2. Use Content Understanding to produce structured markdown output, then index that
  3. Run plain OCR and index the raw extracted text only
  4. Skip extraction and embed the scanned images directly

Why B is correct

Content Understanding is built to turn documents into clean, structured markdown that preserves layout and section context, which is exactly the grounded representation a RAG pipeline needs before indexing.

Why the other options are wrong

  • Raw PDFs aren't searchable or embeddable in a useful way without extraction first.
  • Plain OCR text loses layout and section structure, which hurts retrieval quality on longer contracts.
  • Embedding raw images skips text-level retrieval entirely and isn't how RAG grounding works for documents.

Tip: When a question asks for structure preserved before indexing, Content Understanding's markdown output is the answer to look for.

Why AI-103 differs from AI-102

AI-102 tested each Azure AI service mostly on its own — Vision, Language, Speech, and so on, as separate tracks. AI-103 organizes everything around Azure AI Foundry as the platform that ties those services together, and it adds an entire domain's worth of content that AI-102 never covered: building autonomous agents that call tools, hold memory, and orchestrate multi-step workflows.

The other shift is depth in generative AI. AI-102 touched on Azure OpenAI as one service among several. In AI-103, generative AI and agentic solutions are worth 30 to 35% on their own, more than any other single domain.

Tips for answering AI-103 exam questions

Read for the actual requirement, not the topic. Two options can both technically involve "vision" or "generative AI" while only one fits the specific constraint in the question, like latency, cost, or offline access.

Watch for keyless and managed identity cues. Security questions on this exam lean hard on managed identity, RBAC, and private networking. If an option involves storing or rotating a key, it's usually the wrong one.

Know when RAG beats fine-tuning. If source content changes often, RAG is almost always the better answer. Fine-tuning shows up as a distractor far more often than as a correct answer.

Match the document type to the extraction method. Standard documents (invoices, receipts, IDs) usually point to a prebuilt Document Intelligence model. Anything unusual or company-specific points to a custom model or Content Understanding.

Frequently asked questions

Is AI-103 the same exam as AI-102?

No. AI-103 (Developing AI Apps and Agents on Azure) replaces AI-102 (Azure AI Engineer Associate), which retires on June 30, 2026. AI-103 shifts the focus toward Azure AI Foundry, generative AI, and autonomous agents rather than individual cognitive services.

Is AI-103 still in beta?

As of mid-2026, yes. Microsoft typically moves an exam from beta to general availability within a few months of launch, and pricing and scoring can shift slightly once that happens.

What's the passing score for AI-103?

700 out of 1000. The exam runs 100 minutes and includes roughly 40 to 60 questions across all five domains.

Do I need to know how to code for this exam?

Yes. Microsoft's own study guide lists Python development experience as a prerequisite, along with general familiarity with AI and Azure services.

Are these real leaked exam questions?

No, and they never will be. Every question on this page is original, written from Microsoft's published AI-103 skills outline. Real exam content is covered by an NDA that every candidate agrees to, and sharing it isn't something we do.

How is AI-103 different from AI-901?

AI-901 is the fundamentals-level exam — it tests conceptual understanding of AI on Azure with no coding required. AI-103 is an associate-level, hands-on exam that expects you to actually build and secure AI apps and agents using Python and Azure AI Foundry.

Sources

  1. Microsoft Learn. Microsoft Certified: Azure AI Apps and Agents Developer Associate. Accessed July 2026.
  2. Microsoft Learn. Study guide for Exam AI-103. Accessed July 2026.

This page is an independent study resource and is not affiliated with, endorsed by, or sponsored by Microsoft. AI-103 is in beta at the time of writing; exam weighting, format, and pricing may change before general availability.