AI-103 Practice Exam — AI-103: Developing AI Apps and Agents on Azure

1. The question bank is cloud-based and updates automatically, with no need for re-acquisition.

2. Available in Chinese and English. It supports online practice, mock exams and PDF downloads.

3. You can practice questions via mini-program or desktop web page. The service is valid for one year.

4. Activation codes can be purchased directly or from our official Tmall flagship store.

5. For inquiries, please contact customer service via WeChat, WhatsApp or Line.

6. Drag-and-drop, hotspot and dropdown questions are currently under development.

Exam information

AI-103: Developing AI Apps and Intelligent Agents on Azure

- Exam Overview: Targeted at developers, this exam verifies the ability to build AI applications and intelligent agents using Microsoft Foundry, Azure OpenAI, and other services. It is the upgraded replacement certification for AI-102.

- Key Specifications:

 - Exam Duration: 120 minutes

 - Number of Questions: 40-60 (Including complex scenario cases and multi-step process design questions)

 - Total Score / Passing Score: 1000 / 700

 - Exam Fee: Approximately $165 USD

 - Supported Languages: Simplified Chinese, English, etc.

 - Official Registration Link: https://learn.microsoft.com/zh-cn/credentials/certifications/exams/ai-103/

- Core Topics:

 - Planning and resource management for Azure AI solutions (25-30%)

 - Developing generative AI applications and intelligent agents (30-35%)

 - Implementing computer vision, text analytics, and information extraction solutions

 - Multi-agent orchestration, tool integration, and enterprise-grade AI application deployment

Sample questions

AI-103 · Q1
Topic 1 Question #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. " target="_blank" rel="nofollow noopener">https://cdn.zhangxuetu.online/download/AknEJvg2nY-odtyr.png">
  • A.
    错误
  • B.
    正确
  • .

Answer: B

Analysis: The correct selections are: Deployment type = Standard, Version update policy = Opt out of automatic model version upgrades. The technical requirements mandate dynamic scaling without reserved throughput capacity, which matches Standard deployment type (Global Provisioned requires reserved capacity, and Global Standard is not appropriate for this regional EU workload). To keep the model version consistent for stable responses, you must opt out of automatic model version upgrades to prevent unintended version changes that would alter response behavior. Key Concept: Microsoft Foundry model deployment types and version update policies are configured to meet scalability, version stability, and compliance requirements for generative AI workloads. References: Deploy and configure models in Microsoft Foundry, Azure OpenAI Service model deployment types, https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models#deployment-types
AI-103 · Q2
Topic 1 Question #2 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 RequirementsContoso 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 Agent1 to meet the security and compliance requirements.What should you use?
  • A.
    self-harm content filtering
  • B.
    prompt shields
  • C.
    Personally identifiable information (PII) Detection
  • D.
    violence content filtering

Answer: C

Option Analysis: A. Self-harm content filtering is incorrect because it is designed to block content related to self-harm, which does not address the requirement of preventing Agent1 from revealing erroneously added customer information. B. Prompt shields are incorrect because they protect against prompt injection attacks like hidden malicious instructions in images, which is a separate requirement and does not address customer information protection. C. PII Detection is correct because it identifies and redacts personally identifiable customer information from responses, meeting the requirement that Agent1 must never reveal customer information even if it is erroneously added to the product sheet repository. D. Violence content filtering is incorrect because it is designed to block content promoting or depicting violence, which does not address the requirement of protecting customer information. Key Concept: Microsoft Foundry AI content safety PII detection helps organizations meet compliance requirements to prevent unauthorized disclosure of customer personal data in generative AI agent responses. References: PII detection in Azure AI Content Safety, Overview of Azure AI Content Safety, https://learn.microsoft.com/en-us/azure/ai-services/content-safety/overview
AI-103 · Q3
Topic 1 Question #3 You are planning a Microsoft Foundry project named Project1 that will contain multiple agents. Each agent will access the same Azure AI Search resource.You need to recommend a solution to centrally manage the Azure AI Search credentials within Project1. The solution must be implemented across all the agents.What should you recommend?
  • A.
    Enable role-based access control (RBAC) for the Azure AI Search resource.
  • B.
    Disable key-based access control on the Azure AI Search resource.
  • C.
    Add a connection to the Azure AI Search resource.
  • D.
    Create a managed private endpoint that connects to the Azure AI Search resource.

Answer: C

Option Analysis: A. Option A is incorrect because enabling RBAC on Azure AI Search manages access to the resource at the Azure control plane level, it does not provide centralized credential management for all agents within a Microsoft Foundry project. B. Option B is incorrect because disabling key-based authentication only removes one authentication method, it does not implement centralized credential management for agents in the project. C. Option C is correct because adding a project-level connection to Azure AI Search in Microsoft Foundry centrally stores and manages credentials, making the connection available to all agents in the project out of the box. D. Option D is incorrect because a managed private endpoint secures network connectivity to Azure AI Search, it does not handle centralized credential management for the project's agents. Key Concept: In Microsoft Foundry, project-level connections centrally manage shared credentials for external resources like Azure AI Search that are used by multiple agents in the project. References: Connect to Azure resources from Azure AI Foundry projects, Manage connections in Azure AI Foundry
AI-103 · Q4
Topic 1 Question #4 HOTSPOT - Your company is piloting a customer support agent in a Microsoft Foundry project name Project1. Project1 is connected to an existing Application Insights resource, and the company’s support team reviews runs in the Traces tab. The Foundry Agent Service is configured to perform the following actions: Retrieve the Application Insights connection string by calling project_client.telemetry.get_application_insights_connection_string(). Call configure_azure_monitor(connection_string=...) to enable telemetry. A separate LangChain service is configured to use OpenTelemetry and has the following configurations: Uses AzureAIOpenTelemetryTracer(connection_string=..., enable_content_recording=False) Passes the tracer by using config={“callbacks”:[azure_tracer]} Company policy has the following requirements: Telemetry from LangChain and OpenTelemetry must be distinguishable within the same Application Insights resource. Secrets and credentials must NOT be stored in prompts, tool arguments, or span attributes. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. " target="_blank" rel="nofollow noopener">https://cdn.zhangxuetu.online/download/Gu6CkiXW4xXkoVwD.png">
  • A.
    错误
  • B.
    正确
  • .

Answer: B

Analysis: Correct answers: Statement 1: No; Statement 2: Yes; Statement 3: No. For the first statement, the separate LangChain service requires an explicitly configured tracer passed via callbacks to send telemetry to Application Insights, so it will not appear in Traces without tracer configuration. For the second statement, OTEL_SERVICE_NAME is the standard OpenTelemetry environment variable that defines the service name for telemetry, so different values will correctly separate LangChain and Foundry Agent Service telemetry in the same Application Insights resource, meeting the first policy requirement. For the third statement, setting enable_content_recording=False disables capturing of prompt content, tool arguments and other message content in span attributes and telemetry to prevent secret exposure, so prompts and tool data will not be captured, matching the company's second policy requirement. Key Concept: OpenTelemetry-based telemetry configuration for Azure AI Foundry and LangChain in Application Insights controls visibility, service segmentation, and content capture compliance. References: Enable Azure monitoring for Azure AI Foundry, OpenTelemetry instrumentation for LangChain on Azure
AI-103 · Q5
Topic 1 Question #5 DRAG DROP - You have a Microsoft Foundry project that processes procurement documents submitted by suppliers. You need to implement two pipelines by using Azure Content Understanding in Foundry Tools. The solution must meet the following requirements: Include a pipeline named Pipeline1 that supports cost-effective, high-volume processing of standalone PDF invoices. Include a pipeline named Pipeline2 that supports cross-document validation by using multi-step reasoning and reference data. How should you configure each pipeline? To answer, drag the appropriate configurations to the correct pipelines. Each configuration may be used once, more than once, of not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. " target="_blank" rel="nofollow noopener">https://cdn.zhangxuetu.online/download/DuejnkDG3zlEnnm8.png">
  • A.
    错误
  • B.
    正确
  • .

Answer: B

Analysis: Correct answer: Pipeline1: Single-file task in standard mode; Pipeline2: Multi-file task in pro mode. Pipeline1 processes standalone single-document PDF invoices, and standard mode is more cost-effective for high-volume simple single-document processing, matching the requirements for low-cost high-volume single file workloads. Pipeline2 requires cross-document validation across multiple documents with multi-step reasoning and reference data, which is supported by multi-file pro mode that enables advanced multi-document workflows. Key Concept: Azure Content Understanding in Microsoft Foundry uses single-file vs multi-file tasks and standard vs pro modes to match workload requirements, with standard mode for cost-effective high-volume single-document processing and pro multi-file tasks for advanced cross-document reasoning. References: What is Azure Content Understanding?, https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/overview Azure Content Understanding modes and tasks

FAQ

How many practice questions are available for AI-103?

This question bank includes 65 AI-103 practice questions covering single and multiple choice, each with answers and explanations.

Are AI-103 practice questions available in Chinese and English?

Yes, AI-103 practice questions are provided in both Chinese and English.

Can I try AI-103 practice questions for free?

Yes. Free sample questions are available on this page, and the full question bank is available after signing up on Zhangxuetu.