AI-103 Exam Dumps : Developing AI Apps and Agents on Azure

The correct recommendation is Azure Content Understanding in Foundry Tools . The case study states that Contoso’s finance department must manually review vendor invoices to verify that invoice details match vendor contract terms, and that the invoices contain tables, logos, and varied layouts that make consistent processing difficult. It also states that the planned solution must evaluate both the visual layout and textual content of the invoices.

Azure Content Understanding is designed for this type of multimodal document-processing workload. Microsoft describes Content Understanding as a Foundry Tool that processes unstructured and multimodal content, including documents and images, and transforms it into structured output for AI applications. It can use document analyzers to extract text, layout, tables, fields, and relationships from diverse document types.

Chat completions alone would not reliably extract structured invoice fields from complex layouts. Azure Document Intelligence can extract OCR, layout, and tables, but Content Understanding is the better end-to-end Foundry capability for combining visual and textual understanding with structured extraction for downstream verification. Image Analysis focuses on image-level visual features and is insufficient for invoice field and table review. Reference topics: Content Understanding, document analyzers, multimodal extraction, invoice processing, tables, layout, and structured JSON output.

The correct answer is C. Split the mixed-language segments into single-language segments and translate each segment separately . Azure Translator has a known limitation for text that contains mixed-language input within the same sentence or segment. Microsoft’s Translator known-issues guidance states that the Text translation API does not support translating sentences that contain mixed-language text and that translations can be incorrect or incomplete when a single sentence includes multiple languages. The documented workaround is to specify the intended source language, remove the mixed-language sentence, or split the text into single-language segments.

In this scenario, specifying English for all segments would fail when Spanish content is present. Automatic language detection can detect a dominant language, but it does not reliably solve a segment that contains both English and Spanish. Document translation is also not the right fix because the issue is mixed-language content inside transcript segments, and Microsoft notes similar incomplete results for mixed-source-language documents. Splitting the transcript into language-homogeneous segments ensures each translation request has a clear source language and lets the entire transcript be translated reliably. Reference topics: Azure Translator in Foundry Tools, text translation, language detection, mixed-language input, and transcript preprocessing.

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.