Azure AI Engineer Associate AI-103 Full Course Free

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 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.