Free Microsoft AI-103 Practice Exam with Questions & Answers | Set: 2

The correct recommendation is Azure AI Search. The case study states that the product detail sheets are stored as PDFs in storage1, and that Agent1 must be enabled to retrieve and use detailed product information from those sheets. It also specifies that the indexing pipeline must enable semantic and vector search, and that Agent1 must answer natural language questions about product details by using the product sheet information. Azure AI Search is the Azure service designed to ingest content from sources such as Azure Blob Storage, create searchable indexes, and support keyword, semantic, hybrid, and vector retrieval for Retrieval Augmented Generation (RAG) solutions.

Microsoft’s Azure AI Search guidance states that integrated vectorization can chunk content and generate embeddings during indexing, enabling vector search over source documents. It also states that Azure AI Search supports text and vector queries and can improve raw content for search-related scenarios through enrichment pipelines. Azure Translator is unrelated to retrieval. Document Intelligence can extract document structure, but it is not the retrieval index for Agent1. Grounding with Bing Search retrieves public web content, not Contoso’s private PDFs in storage1. Reference topics: Azure AI Search, RAG, semantic search, vector search, Azure Blob Storage indexing, and agent grounding.

The correct selection is D . In Microsoft Foundry Agent Service, tool_choice is the runtime control used to influence whether the model may answer directly or must invoke a tool. Microsoft’s tool best-practice guidance states that auto lets the model decide whether to call tools, none prevents tool calls, and required means the model must call one or more tools. This directly addresses the issue where some runs answer from the base model and skip the knowledge base.

For an agentic retrieval solution backed by Azure AI Search through an MCP tool, Microsoft’s tutorial states that setting tool_choice= " required " ensures the agent always uses the knowledge base tool when processing queries. This produces grounded answers because the run is forced into tool invocation before responding. auto is incorrect because it preserves the nondeterministic behavior already causing missing citations. { " type " : " knowledge_base " } is not a valid Foundry tool-choice type. { " type " : " mcp " } describes an MCP tool type in some Responses API schemas, but the deterministic guarantee for this agent run scenario is the required tool-call mode. Reference topics: Microsoft Foundry Agent Service, MCP tools, Azure AI Search agentic retrieval, tool_choice, and grounded citations.

Extract the text: Azure Vision in Foundry Tools

Identify well-known locations: Azure Language in Foundry Tools

Azure Vision in Foundry Tools is the appropriate service for extracting text from road signs. Its pretrained Optical Character Recognition capability detects printed or handwritten text in images and returns recognized words, lines, and their coordinates. Microsoft specifically identifies street signs as an applicable OCR scenario. Because the OCR model is already trained, it avoids the data labeling and custom-model training that would increase development effort.

After OCR produces the text, Azure Language in Foundry Tools can analyze it through entity linking . Entity linking recognizes and disambiguates well-known entities and connects them to entries in a recognized knowledge base. This is suitable for determining that text on a sign represents a known geographic location rather than merely returning an unclassified text string. Named entity recognition can also classify extracted entities under categories such as Location, but entity linking provides the stronger interpretation implied by “well-known locations.”

Azure Document Intelligence is optimized for structured and text-heavy business documents, while Azure AI Search provides indexing and retrieval rather than primary OCR and linguistic analysis.

Study Guide alignment: implement OCR-based ingestion and use Foundry Tools to extract entities from text .

Create an AnalyzeTextOptions instance and set its required text property to the string stored in comment. Microsoft ' s Python SDK reference defines text as a required string containing the text to analyze. Microsoft Learn

Then submit the request through:

client.analyze_text(request)

The resulting AnalyzeTextResult exposes categories_analysis. The code can iterate through those results, locate the item whose category is TextCategory.SELF_HARM, and return its severity.

Azure AI Content Safety currently analyzes the primary categories Hate, SelfHarm, Sexual, and Violence and returns severity information that can be used by the application to enforce publishing policy. Microsoft Learn

analyze_image is inappropriate because the input is textual. A nonstandard client_moderate_text method is not the current SDK operation. The request ' s categories field, when used, expects a list of category identifiers and not the comment itself.

The technically correct current Python pattern is therefore AnalyzeTextOptions(text=comment) followed by client.analyze_text(request).

Study Guide alignment: configure detection of safety issues and sensitive content in text-analysis solutions . Microsoft Learn

====================

Azure Custom Vision uses a supervised machine-learning workflow. The first requirement is to create a Custom Vision project , where you select the project type and domain. Because the application must detect business-specific component faults, the model requires organization-specific labeled training images rather than relying solely on a general pretrained image-analysis capability.

Next, upload and tag representative images . For object detection, tagging includes drawing bounding regions around the faulty components or defect regions and associating those regions with appropriate tags. Training quality depends strongly on having sufficiently varied examples representing lighting, orientation, component position, normal conditions, and defect types.

Finally, train the object detection model . Custom Vision uses the annotated regions to create a model capable of returning both the predicted tag and the bounding box for each detected fault. “Train the classifier model” is inappropriate because classification assigns a category to the overall image and does not provide object locations. “Initialize the training dataset” is not a separate required Custom Vision portal/API lifecycle step.

The AI-103 Study Guide maps this scenario to implement solutions that identify objects, components, or regions within images or video . Microsoft Learn

====================

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

Yes. Moderate text content is exactly the Content Safety testing workflow Microsoft documents for analyzing sample text and tuning harmful-content filtering.

Microsoft ' s current quickstart instructs users to open the Moderate text content panel, provide sample text, and select Run test . The service returns detected harm categories together with severity levels. The user can then open Configure filters , adjust which severity levels are allowed or prohibited for each category, and run the text again to verify the behavior. Microsoft Learn

That directly satisfies the requirement to optimize the content-filter configuration by testing sample questions.

The Safety metaprompt capability influences generative model behavior but does not provide the same moderation-threshold testing. Protected material detection evaluates a separate protected-content concern and likewise is not the harmful-content filter test surface.

Therefore, the answer printed in the supplied document ( B, No ) conflicts with current Microsoft Learn documentation. The verified answer is A, Yes .

Study Guide alignment: configure safety filters, guardrails, risk detection, content moderation, and safety evaluations for generative AI and agentic systems . Microsoft Learn

====================

The solution requires a generative text model, so the Cognitive Services account must be created with the OpenAI kind from the values supplied in the exhibit.

The JSON object shown underneath contains Key Vault-based encryption settings such as the key source, key vault URI, key name, and key version. That JSON therefore belongs to the --encryption parameter.

Customer-managed key encryption lets the organization control the key used to protect supported stored data. This provides additional control over rotation, revocation, key governance, and separation of duties compared with relying solely on Microsoft-managed keys.

The Azure AI resource also needs permission to use the Key Vault key. In an operational deployment, this generally involves configuring a managed identity and granting the required Key Vault permissions.

--api-properties configures service-specific API properties rather than encryption. --assign-identity enables the account identity but does not itself supply the customer-managed encryption configuration shown in the question.

Therefore, the correct selections are OpenAI and --encryption .

Study Guide alignment: design Azure infrastructure, configure model resources, and secure AI systems through identity and resource-security controls . Microsoft Learn

====================

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

Use the Azure Content Understanding skill. Content Understanding combines multimodal document processing, layout understanding, semantic extraction, image/figure handling, and structured document interpretation in a single content-processing capability.

For citation-rich RAG scenarios, the generated output can retain page and spatial information associated with source content, allowing downstream applications to connect returned text and visual content to page-level locations and bounding regions. Its richer document analysis is also designed to handle complex structures such as tables, figures, and content relationships that span document pages.

The ordinary Document Extraction skill primarily performs document cracking and basic extraction. Document Layout focuses on layout structure but does not provide the same complete multimodal semantic processing required by the question. GenAI Prompt applies generative processing to already available content rather than serving as the primary multimodal document-extraction skill.

Content Understanding therefore minimizes the need to compose multiple separate skills for OCR, image extraction, layout, and semantic document processing.

The AI-103 Study Guide explicitly covers multimodal pipelines that combine OCR, layout analysis, and field extraction and producing clean grounded representations for agents and RAG by using Content Understanding. Microsoft Learn

====================

The correct answer is A. Speech recognition requests will fall back to the most recent base model for the same locale . Microsoft’s custom speech model lifecycle guidance states that when a model expires, it is no longer available for transcription. For the custom endpoint route, speech recognition requests fall back to the most recent base model for the same locale. The documentation also warns that recognition results might still be returned, but the transcription may no longer reflect the domain-specific adaptation of the custom model.

This distinguishes real-time custom endpoint behavior from batch transcription behavior. Batch transcription requests that specify an expired model fail with a 4xx error, but that is not the route described in this question. The agent is using a custom endpoint for real-time recognition, so fallback to the latest base model is the expected behavior. The model is not automatically deleted merely because it expires, and it does not continue to use the expired custom model indefinitely. The operational recommendation is to update the endpoint’s model before expiration by redeploying the endpoint with a newer custom model. Reference topics: Azure Speech custom speech model lifecycle, custom endpoints, model expiration, real-time speech recognition, and endpoint redeployment.