AI-103 Certification Exam Guide + Practice Questions Updated 2026

Home / Microsoft / AI-103

Comprehensive AI-103 certification exam guide covering exam overview, skills measured, preparation tips, and practice questions with detailed explanations.

AI-103 Developing AI Apps and Agents on Azure Exam Overview


The Microsoft Certified: Azure AI Apps and Agents Developer Associate certification validates your ability to design, build, and deploy advanced AI-driven applications on Microsoft Azure. This updated exam replaces AI-102 and focuses on modern AI development practices, including generative AI and intelligent agents using Microsoft Foundry. As an Azure AI engineer, you are expected to leverage Python and Azure AI services to create scalable, intelligent solutions. The certification demonstrates your expertise in building AI-powered applications that integrate natural language processing, computer vision, and information extraction capabilities.

Exam Details


Duration: 120 minutes
Passing Score: 700/1000
Price: $165
Language: English
Retirement Note: AI-102 will retire on June 30, 2026

This certification is ideal for professionals working with AI solutions, including developers, AI engineers, and cloud specialists.

Skills Measured in AI-103 Exam


The AI-103 exam evaluates your ability across five key domains:

1. Plan and Manage Azure AI Solutions
Design AI architectures using Azure services
Manage resources, security, and compliance
Monitor and optimize AI workloads

2. Implement Generative AI and Agentic Solutions
Build AI agents using Microsoft Foundry
Integrate large language models (LLMs)
Develop conversational AI and automation workflows

3. Implement Computer Vision Solutions
Analyze images and videos using Azure AI Vision
Perform object detection and image classification
Apply OCR for text extraction from images

4. Implement Text Analysis Solutions
Use natural language processing (NLP) capabilities
Perform sentiment analysis, key phrase extraction, and language detection
Build conversational and text-based AI systems

5. Implement Information Extraction Solutions
Extract structured data from unstructured content
Use Azure AI Document Intelligence
Automate document processing workflows

How to Prepare for the AI-103 Exam?


Preparing for AI-103 requires both theoretical understanding and hands-on experience with Azure AI services. Here’s a practical approach:

Understand the Exam Objectives: Focus on each skill domain and understand how Azure services apply in real scenarios.
Gain Hands-On Experience: Practice building AI solutions using Python and Azure AI tools like Azure OpenAI, Vision, and Document Intelligence.
Use Microsoft Learn: Follow official learning paths to cover core concepts and labs.
Work on Real Projects: Build small AI apps (chatbots, document analyzers, vision apps) to reinforce learning.
Review Generative AI Concepts: Understand prompt engineering, LLM integration, and agent workflows.
Take Practice Tests: Identify weak areas and improve time management.

Consistency and practical exposure are key to passing the AI-103 exam.

Why Choose Our AI-103 Practice Questions?


Our AI-103 practice questions are carefully designed to mirror the actual exam format and difficulty level. They cover all exam objectives and include detailed explanations to help you understand not just the correct answers, but also the reasoning behind them.

● Up-to-date with the latest AI-103 exam objectives
● Realistic exam simulation environment
● In-depth explanations for every question
● Helps identify knowledge gaps quickly
● Boosts confidence before the actual exam

Practice Questions for AI-103 Exam


Practicing with high-quality AI-103 exam questions is one of the most effective ways to ensure success. Practice tests help you become familiar with the exam structure, improve your time management skills, and reinforce key concepts. By simulating exam scenarios, they allow you to assess your readiness and focus on areas that need improvement - ultimately increasing your chances of passing the AI-103 exam on your first attempt.

Question#1

You have a Microsoft Foundry project that uses Azure AI Search to ground an agent in internal documentation.
After a recent content update, users report that the agent’s answers have become less accurate.
You need to identify whether the retrieved content is negatively influencing the model’s generated responses.
Which observability signal should you review?

A. indexer status and failure history
B. latency breakdown traces
C. prediction drift metrics
D. groundedness evaluation metrics

Question#2

You have a Microsoft Foundry project that contains an agent. The agent uses Azure AI Search for Retrieval Augmented Generation (RAG). You plan to ingest and index PDF product manuals. You need to build a solution that supports semantic similarity matching. The solution must ensure that the agent retrieves relevant data when user questions use different wording than the product manuals.

A. vector search
B. semantic ranking
C. suggesters
D. analyzers

Explanation:
Use vector search because it performs similarity matching based on semantic meaning rather than requiring literal keyword overlap. During ingestion, the product manuals should be divided into appropriately sized chunks. An embedding model converts each chunk into a numerical vector, which Azure AI Search stores in a vector field. At query time, the user’s question is also converted into an embedding, and the service retrieves chunks whose vectors are closest to the query vector. Consequently, wording such as “reset the device to factory settings” can match manual content such as “restore the unit’s original configuration,” despite minimal lexical overlap. Azure AI Search explicitly defines vector fields as enabling similarity searches over mathematically represented content and supports this retrieval pattern for RAG applications.
Semantic ranking improves the ordering of an existing result set but is not the indexing mechanism that stores embeddings and performs nearest-neighbor similarity matching. Suggesters provide search-as-you-type functionality, while analyzers control tokenization and lexical processing for text fields.
This aligns with the AI-103 Study Guide objectives for implementing RAG, configuring
Azure AI Search grounding, generating embeddings, and selecting vector retrieval techniques for agentic solutions.

Question#3

1. HOTSPOT

Case Study
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.

To answer the case study questions, you will bed to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.

A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.

To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions. When you are ready to answer a question, select the “Question” button to return to the question.

Overview
Company Information
Contoso, Ltd is a multinational retail company that builds, deploys, and manages generative AI and agent-based solutions by using Microsoft Foundry.

Existing Environment
Identity Environment
Contoso uses Microsoft Entra ID for identity management, authentication, and authorization capabilities that enable agents to access organizational resources and services.
Contoso recently formed a new AI engineering team named Agent1Dev Team to optimize and maintain existing AI solutions. The team collaborates with solution architects, DevOps engineers, and security engineers to design, implement. monitor, and secure AI applications.
Contoso also has a team named Agent1Test Team that is responsible for validating AI solutions before the solution deployments.

Generative Environment
Contoso has a Microsoft Foundry deployment that contains two projects named Project1 and Project2.

Project1
Project1 contains a customer support agent named Agent1 that assists customers with product inquiries and troubleshooting requests.
Agent1 has the following configurations:
Agent1 uses a base model deployment.
A safety evaluation pipeline is NOT enabled.
Tool invocation approval workflows are NOT enabled.
Conversation memory constraints are NOT configured.
Agent1 interacts with customers by using digital support channels and answers general questions about Contoso products.
Project1 is deployed to an Azure region located in the European Union (EU).
Agent1Dev Team will use Project1 to optimize and maintain Agent1.

Project2
Project2 contains a deployed video generation model. The marketing department at Contoso has access to Project2 and plans to use the model to develop a video creation solution.
Development of the solution is incomplete.

Data Environment
Contoso stores product-related information in Azure resources that support AI applications.
The Azure environment contains an Azure Blob Storage account named storage1 that stores product detail sheets for all the Contoso products.
The product sheets include specifications, feature descriptions, and product support information that Agent1 can use to answer customer questions. The product sheets are stored in the PDF format.

Problem Statements
Contoso identifies the following issues:
Agent1 has only general knowledge of the Contoso products.
A recent chat interaction with Agent1 was analyzed for sentiment. The results of the analysis have NOT been processed yet. Agent1 does NOT use the detailed product information in the product sheets stored in storage1 when responding to customer questions.
The finance department at Contoso reports that vendor invoices must be reviewed manually to ensure that the invoices match the terms defined in the vendor contracts. The invoices contain tables, logos, and varied layouts that make the documents difficult to process consistently.

Requirements
Planned Changes
Contoso plans to implement the following changes:
Implement a solution for Project1 that analyzes the vendor invoices by evaluating both the visual layout and the textual content of the invoices, so that the invoice details can be verified against the vendor contract terms.
Update the base model deployment used by Agent1 and standardize the model version to ensure continuity and consistent responses.
Enable Agent1 to retrieve and use the detailed product information from the product sheets stored in storage1.
Implement an indexing solution for the product sheets that Agent1 can use to answer customer questions.
Complete the development of the video creation solution.

Technical Requirements
Contoso identifies the following technical requirements:
The model deployment used by Agent1 must support scalable, high-throughput generative AI workloads and dynamically scale to handle variable customer support traffic, without requiring reserved throughput capacity.
The product sheets must be processed by using an indexing pipeline that enables semantic and vector search, so that Agent1 can retrieve the relevant product information.
Responses generated by using the product sheet information must be relevant, complete, and accurate.
Agent1 must be able to use the product sheets to answer natural language questions about product details.
The model version used by Agent1 must remain consistent to ensure stable responses.
The data processed by the model must remain within the EU.
Security and Compliance Requirements
Contoso identifies the following security and compliance requirements:
API keys must NOT be used to access Foundry-deployed models.
Access to the Azure resources must follow the principle of least privilege.
The developers at Contoso must authenticate to Microsoft Foundry resources by using Microsoft Entra authentication. Access to Project1 must be assigned to the members of Agent1Dev Team by using a security group named SC_Agent1_Dev. Access to Project1 must be assigned to the members of Agent1Test Team by using a security group named SC_Agent1_Test. Agent1 must never reveal customer information, even if a document that contains customer data is added erroneously to the product sheet repository in storage1.
The product sheets might contain images that include embedded text. Agent1 must be protected from malicious instructions potentially hidden within the images.

Business Requirements
Contoso identifies the following business requirements:
Users that interact with Agent1 must have a personalized experience in future interactions, including the ability for Agent1 to retain conversation context and recall relevant information from previous interactions. Agent1 must answer questions only about the products sold by Contoso.

You need to configure the model deployment for Agent1 to meet the technical requirements.
What should you configure? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.


A. 

Question#4

You have a Microsoft Foundry project that contains three agents as shown in the following table.



You need to orchestrate the agents to ensure that the customer requests meet the following requirements:
• Support a deterministic, step-based process that uses conditional branching and shared state across the agents.
• Optionally trigger a ticket action based on the triage result.
The solution must minimize development effort.
What should you include in the solution?

A. separate agent runs coordinated in the application code
B. a multi-agent group chat session
C. a workflow
D. threads and runs without a workflow

Explanation:
The correct answer is a workflow. Microsoft Foundry workflows are designed to orchestrate agents and business logic as declarative, predefined sequences of actions. The official workflow guidance states that workflows are ideal when you need to orchestrate multiple agents in a repeatable process, add branching logic such as if/else, and handle variables without writing application orchestration code. This directly matches the requirement for a deterministic, step-based process with conditional branching and shared state.
In this scenario, TriageAgent can classify the request first, the workflow can store the triage result, and conditional logic can determine whether to invoke PolicyAgent, ActionAgent, or both. The ticket action is optional, so it should be triggered through a workflow condition based on the triage output. This minimizes development effort because the branching, sequencing, and variable handling are managed in the Foundry workflow rather than being manually implemented across separate runs in application code.
A group chat session is better for dynamic agent handoff, not a strict deterministic process. Threads and runs or separate app-coordinated calls require more custom orchestration.
Reference topics: Microsoft Foundry workflows, multi-agent orchestration, conditional branching, variable handling, and agent-driven workflows.

Question#5

HOTSPOT
You have a Python application named App1 that integrates with a Microsoft Foundry project named Project1.
You need to ensure that App1 meets the following requirements:
• Authenticates by using a Microsoft Entra managed identity
• Sends prompts to a deployed model by using the Azure OpenAI Responses API
How should you complete the Python code? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.


A. 

Explanation:
credential = DefaultAzureCredential response = openai_client.responses.create
The correct authentication class is DefaultAzureCredential because the requirement is Microsoft Entra-based authentication, and this credential supports managed identity in hosted Azure environments. The Microsoft Foundry quickstart for Python shows the project client being created with AIProjectClient(endpoint=PROJECT_ENDPOINT, credential=DefaultAzureCredential()), which enables the Foundry SDK to authenticate without using API keys or embedded secrets. The same guidance shows creating an OpenAI-compatible client from the project by calling project.get_openai_client().
The correct Responses API method is create because the application must send a new prompt to the deployed model and receive generated output. Microsoft’s Foundry quickstart demonstrates the exact pattern: response = openai.responses.create(model="gpt-5-mini", input="..."), followed by reading response.output_text. The retrieve operation is used to fetch an existing response, not submit a new inference request, and compact is not the correct method for generating a model response. AzureKeyCredential would violate the Microsoft Entra managed identity requirement, while ClientSecretCredential uses an application secret rather than managed identity.
Reference topics: Microsoft Foundry SDK, AIProjectClient, Microsoft Entra authentication, DefaultAzureCredential, and Azure OpenAI Responses API.

Disclaimer

This page is for educational and exam preparation reference only. It is not affiliated with Microsoft, Microsoft Certified: Azure AI Apps and Agents Developer Associate, or the official exam provider. Candidates should refer to official documentation and training for authoritative information.

Exam Code: AI-103Q & A:  120  Q&As Updated:  2026-10-14

  Access Additional AI-103 Practice Resources