Microsoft AI-103 Practice Exam Questions & Answers

The correct answer is agentic Retrieval Augmented Generation (RAG) because the requirements describe the agentic retrieval pipeline in Azure AI Search. Agentic retrieval is designed for chat and copilot scenarios where a user's request can be complex, conversational, and dependent on prior turns. Azure AI Search agentic retrieval uses an LLM-assisted planning stage to break a complex request into focused subqueries, allowing the system to retrieve grounding information from multiple chunks rather than relying on a single query path. Microsoft's Azure AI Search guidance describes agentic retrieval as a multi-query pipeline for complex questions in chat and agent workflows, with subqueries that can include chat history for additional context.

This also satisfies the latency requirement because agentic retrieval runs the generated subqueries in parallel and then merges and reranks the best results for use by the generative model. Classic RAG is simpler and typically sends a single query to search, making it less suitable for multi-hop or conversational retrieval planning. Chain of thought is a reasoning technique, not an Azure AI Search retrieval approach, and iterative retrieval does not specifically provide the built-in query planning, conversation-aware retrieval, and parallel execution described here. Reference topics: Azure AI Search agentic retrieval, RAG with Azure AI Search, knowledge bases, query planning, and generative AI grounding.

The correct answer is B. Add a reflection pass before the responses are returned. A reflection pass is an application-orchestration step in which the generated summary is reviewed before final delivery, typically by asking the model or an evaluator step to check whether the answer covers the retrieved policy evidence and to revise the response when important details are missing. This directly addresses response completeness in application logic before the response is returned. The Microsoft Learn study guide explicitly includes Implement model reflection and Apply prompt engineering techniques to improve responses under optimization and operationalization of generative AI solutions.

This is also consistent with Microsoft Foundry agentic-loop guidance, which identifies reflection and planning cycles as patterns for multi-step reasoning in production agent systems. Completeness is a response-quality property: Azure AI evaluation defines completeness as whether a response contains all necessary and relevant information with respect to ground truth.

Option C is not correct because the scenario already says the agent generates summaries from retrieved policy documents, which is already a grounded retrieval pattern. Option A mainly reduces randomness, not missing content. Option D improves delivery experience, not answer completeness. Reference topics: model reflection, prompt engineering, agentic loops, response evaluation, and grounded generative AI solutions.

The correct answer is C because the requirement is a localized image edit: remove only the competitor logo while preserving the rest of the already generated image. Azure OpenAI image editing is designed for modifying existing images based on a text instruction, rather than regenerating the entire image from scratch. Microsoft's Azure OpenAI image guidance states that the Image Edit API modifies existing images and requires an input image as part of the request. In a mask-based inpainting workflow, the mask identifies the exact region to change, allowing the model to replace only the logo area while retaining surrounding background, composition, lighting, and product content.

Increasing prompt guidance strength would affect adherence during generation, but it would not safely remove a specific logo from a completed image. Modifying the original prompt and regenerating may create a different image and does not guarantee preservation of the approved visual content. Rerunning with a different random seed also changes the image unpredictably and may introduce new brand or legal issues. Mask-based inpainting is the minimal-change remediation method for post-generation brand cleanup. Reference topics: Azure OpenAI image editing, inpainting, mask-guided edits, image generation governance, and computer vision solutions.

The correct answer is A. Enable estimateFieldSourceAndConfidence. Azure Content Understanding document analyzers support an opt-in confidence and grounding capability for field extraction. Microsoft documentation states that to opt in for confidence and grounding, you set estimateFieldSourceAndConfidence = true in the analyzer configuration, or configure estimateSourceAndConfidence = true for specific fields. This enables each extracted field to include a confidence score and references back to the original document source location.

This directly satisfies both stakeholder requirements: source grounding allows users to verify where the extracted value came from in the scanned PDF, and the confidence score supports downstream automation rules, such as sending low-confidence fields to manual review. Microsoft's analyzer improvement guidance describes confidence scoring as a value between 0 and 1 and grounding as references or citations for extracted outputs to the original document content.

Generative extraction does not guarantee per-field confidence and source grounding. enableSegment is used for document segmentation, not confidence scoring. Labeled samples can improve extraction quality, but they do not by themselves enable confidence and grounding output. Reference topics: Content Understanding document analyzers, field extraction, confidence scoring, grounding, and RAG ingestion.

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.