You have a Microsoft Foundry project named Project1.Project1 contains an application that processes PDF vendor invoices.You need to configure Azure Document Intelligence in Foundry Tools to generate a Markdown output that preserves the sections and table structure of the PDFs. The solution must minimize development effort.What should you do?
Answer(s): D
Setting the output format parameter to Markdown is the correct and recommended action, but the exact property and enum name depend on whether you are interacting with the REST API directly or using thePython SDK.To process PDF invoices and preserve their tables, headings, and visual sections in GitHub FlavoredMarkdown (GFM), configure your Azure Document Intelligence layout model parameters using the precise syntax detailed below.Implementation DetailsPython SDK Syntax: In the Azure Python client library, the parameter name is output_content_format, and its required value is DocumentContentFormat.MARKDOWN (rather than ContentFormat.MARKDOWN, which is used in the .NET C# SDK)
https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/concept/markdown-elements
You have a Microsoft Foundry project that ingests scanned PDF invoices stored in Azure Blob Storage. Each invoice contains printed fine items and has a table-based layout.Extracted results are stored as structured JSON and used as grounding data for an agent in a RetrievalAugmented Generation (RAG) solution.You need to create a single analyzer that meets the following requirements:▪ Extracts the invoice number, invoice date, vendor name, and total amount across varying templates▪ Returns confidence scores so that results with confidence below 0.80 can be routed for supervisor reviewWhat should you use?
Answer(s): B
The best option in this scenario is a custom Azure Content Understanding in Foundry Tools analyzer that defines the required fields as the extracted fields and the returned confidence scores for routing.Custom Field Targeting with Confidence Scores: Azure Content Understanding allows you to build a document analyzer with a user-defined schema. By defining your required fields (InvoiceNumber, InvoiceDate,VendorName, and TotalAmount), the service will handle extraction across varying layouts and return a dedicated field-level confidence score. You can natively evaluate these confidence metrics to implement your supervisor routing workflow.RAG-Ready Output Structure: The service naturally returns highly structured JSON payloads. This makes it perfectly optimized to be ingested directly as grounding data for a Retrieval-Augmented Generation (RAG)agent.Incorrect:[Not C]The prebuilt-layout analyzer extracts raw structural elements such as blocks of text, hierarchy, selection marks,and complete tables. It does not automatically classify or cleanly isolate specific target entities (like vendor name or total amount) into dedicated schema properties, leaving you with heavy post-processing work to isolate the text.[Not D]The prebuilt-documentSearch analyzer is optimized for broad, layout-aware text extraction for indexing.Relying on Azure AI Search's search.score for supervisor routing is conceptually flawed; search.score represents a relevance score for a search query ranking rather than an accuracy metric for data extraction confidence.
https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/document/analyzer-improvement
You have a Microsoft Foundry project that uses Azure AI Search to ground an agent in internal documentation.After a recent content update, users report that the agent’s answers have become less accurate.You need to identify whether the retrieved content is negatively influencing the model’s generated responses.Which observability signal should you review?
The most interesting observability signal in this scenario is Retrieval Score vs. Response Quality(Groundedness Evaluation), specifically analyzing the Context Relevance metric alongside RetrievalConfidence Scores.Because your LLM agent uses a Retrieval-Augmented Generation (RAG) pattern via Azure AI Search, a sudden drop in accuracy after a content update usually implies that the search index is either surface-matching bad keywords, or the ranking algorithm is pulling technically relevant but contextually wrong documents.
https://blog.gopenai.com/how-to-prevent-context-loss-in-azure-ai-search-rag-pipelines-497c346c7077
You have a Microsoft Foundry project that contains a Retrieval Augmented Generation (RAG) chat solution used by customer support agents.You are adding an automated pre-production evaluation step to a CI/CD pipeline named Pipeline1. The evaluation will run against a labeled test dataset that contains support questions and the expected grounding context.You need to ensure that Pipeline1 fails if unsupported content or a retrieval mismatch exceeds a defined threshold:▪ responses include claims not supported by the retrieved source content▪ retrieved source content does not align with the labeled expected contextWhich two built-in evaluators should you use in Pipeline1? Each correct answer presents pat of the solution.Note: Each correct selection is worth one point.
Answer(s): A,D
The Groundedness Evaluator evaluator validates that the model's responses include only claims supported by the retrieved source contentIt flags ungrounded content or hallucinations. If the average score drops below your defined threshold, it triggers a pipeline failure.The correct additional built-in evaluator appropriate for the pipeline is Retrieval (specifically, theRetrievalEvaluator or DocumentRetrievalEvaluator).A standard RAG evaluation pipeline assesses both the generator (the LLM producing the answer) and the retriever (the search system pulling documentation). The CI/CD requirements specify two distinct failure thresholds:Responses including claims not supported by the retrieved source content: This checks for model hallucinations and is handled by the Groundedness Evaluator.Retrieved source content not aligning with the labeled expected context: This explicitly measures the performance of your search step against your ground-truth data. The built-in Retrieval evaluator maps to this requirement. It computes metrics like context recall to ensure your system successfully retrieves the exact reference documents specified in your labeled test dataset
https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/evaluations-cli-evaluators
You have a Microsoft Foundry project that contains a support-ticket triage agent built by using the FoundryAgent Service.The agent uses tools to classify the ticket type and set the ticket priority.Sometimes, the same support case continues across multiple sessions over several days.You need to persist state by using a durable ID to ensure that the agent can automatically reuse the full interaction history. The solution must preserve previous user messages, tool calls and tool outputs across turns and sessions.Which runtime component should you use?
Answer(s): C
To achieve state persistence and ensure that the agent automatically reuses the full multi-session interaction history (including previous user messages, tool calls, and tool outputs), you must include a conversation component.
https://learn.microsoft.com/en-us/azure/foundry/agents/concepts/runtime-components
Post your Comments and Discuss Microsoft AI-103 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AI-103 content, but please register or login to continue.