Microsoft AI-103 Developing AI Apps and Agents on Azure Exam Practice Test

The correct built-in analyzer is prebuilt-layout because the requirement is to preserve document layout while extracting content from scanned PDFs. Microsoft’s Content Understanding prebuilt analyzer guidance states that prebuilt-layout extracts content and layout elements such as words, figures, paragraphs, and tables, identifies document structure including sections and formatting, and provides detailed layout information beyond basic text extraction. It also states that prebuilt-layout does not require a language model or embedding model, which directly satisfies the no language model deployment requirement.

QR codes are handled through barcode extraction. The analyzer configuration reference states that enableBarcode detects and extracts barcodes and QR codes, returns decoded values, and supports QR Code and Micro QR Code among other barcode types. This option is supported by document-based analyzers, making it compatible with layout-oriented document processing.

prebuilt-read is insufficient because it provides OCR and barcode extraction but foundational text extraction without layout analysis. prebuilt-documentSearch is optimized for RAG ingestion and semantic analysis, which is broader than required. prebuilt-documentFieldSchema proposes extraction schemas rather than extracting full document layout. Reference topics: Content Understanding prebuilt analyzers, layout analysis, OCR, barcode detection, QR code extraction, and document-based analyzers.

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 D. Set the output_content_format=ContentFormat.MARKDOWN value . Azure Document Intelligence Layout API can return extracted document content in Markdown format, preserving semantic structure such as headings, paragraphs, sections, tables, and other layout elements. Microsoft’s Document Intelligence layout guidance shows the Python SDK pattern for analyzing a document with the prebuilt-layout model and setting output_content_format=ContentFormat.MARKDOWN in the begin_analyze_document call. The Markdown output is returned in the top-level content section of the analysis result.

This minimizes development effort because the service produces structure-preserving Markdown directly, rather than requiring custom post-processing to reconstruct sections and table formatting from raw OCR spans. Microsoft’s Markdown output documentation states that specifying Markdown output produces semantically structured content that maintains paragraphs, headings, tables, and other document elements in their proper hierarchy.

Option A only changes validation behavior and does not generate Markdown. Option B requests figures, not structured Markdown. Option C uses an incorrect parameter name; the documented SDK setting is output_content_format, not content. Reference topics: Azure Document Intelligence Layout API, Markdown output, PDF analysis, table extraction, and Foundry Tools document processing.

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.

Metrics to enable: Model Availability Rate and Provisioned Utilization

Diagnostic log to collect: trace

The correct metrics are Model Availability Rate and Provisioned Utilization . Model Availability Rate identifies whether failures are caused by service-side model unavailability because it is calculated from total calls minus server errors. Provisioned Utilization identifies resource-limit conditions because Microsoft states that when utilization reaches or exceeds 100%, calls are throttled and HTTP 429 errors are returned. This directly maps to the reported peak-hour rate-limit errors.

The correct diagnostic log is trace . For an internal Q & A scenario, trace logging is required to analyze question-answering behavior, including unanswered questions. Microsoft’s custom question answering analytics guidance states that diagnostic logging stores telemetry and chat logs and instructs enabling Trace in addition to Audit, RequestResponse, and AllMetrics. The sample Kusto queries for unanswered questions inspect the answer, question, score, and knowledge base ID, and filter unanswered results by a score of zero.

RequestResponse is useful for request status and latency, and Audit is for administrative operations, but neither is the best diagnostic category for analyzing Q & A inference behavior such as “No relevant information found.” Reference topics: Foundry monitoring, model availability, provisioned utilization, diagnostic logging, custom question answering analytics, and trace logs.

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.

Unsupported responses: Groundedness evaluation metrics

Policy violations: Risk and safety metrics

For unsupported responses, use Groundedness evaluation metrics . In a Retrieval Augmented Generation scenario, the key question is whether the generated answer is supported by the retrieved context. Microsoft Foundry built-in evaluators define Groundedness as the RAG metric that measures how grounded a response is in retrieved context and returns a model-based score; Groundedness Pro evaluates whether the response is grounded in retrieved context by using Azure AI Content Safety. This directly matches answers that are unsupported by internal documentation.

For policy violations, use Risk and safety metrics . Microsoft Foundry risk and safety evaluators assess generated responses for safety risks such as hate and unfairness, sexual content, violence, self-harm, protected material, indirect attacks, code vulnerability, ungrounded attributes, prohibited actions, and sensitive data leakage. The guidance states that these evaluators assign risk and safety severity or pass/fail outcomes for AI responses and agent behavior.

Latency breakdown traces diagnose performance, not correctness or policy compliance. Token usage analytics diagnose cost and prompt/response size, not unsupported claims or safety violations. Reference topics: Microsoft Foundry observability, RAG evaluators, groundedness, risk and safety evaluators, and agent quality evaluation.

The correct answer is B. Use real-time speech to text to process streaming audio input . The scenario requires live transcription from a continuous telephony stream, with transcript text appearing within a few seconds while the call is still in progress. Azure Speech in Foundry Tools real-time speech recognition is specifically intended for immediate transcription scenarios such as call center assistance, dictation, and live meeting captioning. Microsoft’s Speech guidance describes real-time speech to text as processing audio input and returning transcriptions in real time, which matches the supervisor monitoring requirement.

Batch transcription is inappropriate because it processes stored audio files after recording, not an active live stream. Speech translation is used when the primary goal is translating speech into another language, not simply producing live same-language call transcripts. Text to speech performs the reverse operation by generating spoken audio from text and does not transcribe inbound calls. Real-time speech to text provides the low-latency streaming recognition path required for live operational monitoring. Reference topics: Azure Speech in Foundry Tools, real-time speech recognition, streaming audio input, call center transcription, and live captions.

Access up-to-date information from public websites: Grounding with Bing Search

Perform calculations during conversations: Code interpreter

Retrieve information from documents uploaded directly to the agent: File search

The correct tool for public, current web information is Grounding with Bing Search . Microsoft Foundry Agent Service identifies Grounding with Bing Search as the built-in tool that enables an agent to access and return information from the internet, which fits the requirement for up-to-date public website data. ( learn.microsoft.com )

For calculations during conversations, use Code interpreter . Microsoft’s Foundry guidance states that Code Interpreter enables an agent to run Python code in a sandboxed execution environment and solve data analysis and math tasks iteratively. This is the correct fit for financial analysts who need calculations, analysis, and potentially chart generation during the conversation.

For documents uploaded directly to the agent, use File search . Microsoft describes File Search as the tool that enables Foundry agents to search through documents, retrieve relevant information, and augment model responses with knowledge from uploaded files such as PDFs, Word documents, and proprietary content.

Computer use is for interacting with graphical applications, not calculation or document retrieval. Microsoft Fabric is for enterprise data and analytics integration, not direct uploaded document retrieval. Reference topics: Foundry Agent Service tools, Code Interpreter, File Search, and Grounding with Bing Search.

The correct configuration is an API key security scheme . For Microsoft Foundry Agent Service OpenAPI tools, the OpenAPI specification must declare authentication through the components.securitySchemes section and use a scheme of type apiKey when the external service expects a key in a header. Microsoft’s OpenAPI tool guidance states that API key authentication requires updating the OpenAPI spec security schemes with one scheme of type apiKey, and the tool then uses the associated project connection to supply the key value at runtime. This allows the key stored in Project1’s connection to be injected automatically when the tool is invoked.

A header parameter defined separately for each operation is not the correct approach because credentials should not be modeled as ordinary operation parameters. The Foundry guidance explicitly indicates that parameters requiring the API key should be removed from the OpenAPI spec because the API key is stored and passed through a connection. A Bearer token security scheme is used for bearer-token-style authorization, not a generic weather API key passed in a custom HTTP header. Azure Key Vault is a secret store, but the scenario already stores the key in a Foundry project connection. Reference topics: Microsoft Foundry Agent Service, OpenAPI tools, project connections, API key authentication, and OpenAPI security schemes.

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.

credential = DefaultAzureCredential()

agent = project_client.agents.get(agent_name=myAgent)

The correct authentication option is DefaultAzureCredential() because the case study states that API keys must not be used to access Foundry-deployed models and that Contoso developers must authenticate to Microsoft Foundry resources by using Microsoft Entra authentication. It also states that access to Project1 must be assigned to Agent1Dev Team by using the security group SC_Agent1_Dev . Microsoft Foundry authentication guidance recommends Microsoft Entra ID for production workloads because it supports least-privilege RBAC, per-principal auditing, and keyless authentication. AzureKeyCredential() would violate the no-API-key requirement, and None would not provide a valid credential.

The correct agent operation is get because the task is to access an existing agent named Agent1, not create a new version or retrieve a specific published version. Microsoft Foundry SDK examples show AIProjectClient created with DefaultAzureCredential() and then using project agent operations to create, retrieve, or interact with agents by name. To meet the compliance requirement, the group SC_Agent1_Dev must also be granted the appropriate project-scoped Foundry role, such as Foundry User, for Project1. Reference topics: Microsoft Entra authentication, Foundry RBAC, AIProjectClient, and project agent access.

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.

Deployment type: Standard

Version update policy: Once the current version expires

The correct deployment type is Standard . The case study specifies that Project1 is deployed in an EU Azure region and that model-processed data must remain within the EU. It also requires scalable, high-throughput generative AI workloads that dynamically handle variable customer support traffic without reserved throughput capacity. In Microsoft Foundry Models, Standard is a pay-per-token deployment type that processes data in a single Azure region, while Global Standard can process requests across regions and Global Provisioned uses reserved provisioned throughput. Microsoft’s deployment-type guidance identifies Standard as single-region, pay-per-token, whereas Global Provisioned is cross-region with reserved capacity.

The correct version update policy is Once the current version expires . This keeps Agent1 on the selected model version during its supported lifecycle, which supports stable and consistent responses, but still preserves continuity by automatically moving to a supported replacement when the current version is retired. Microsoft’s model versioning guidance states that this policy updates only when the current model version expires, while upgrading when a new default is available changes the deployment sooner and opting out can cause the deployment to stop working after retirement. Reference topics: deployment types, regional data processing, model versioning, throughput capacity, and stable production deployments.

The correct answer is B. Modify the system message instructions . The case study states that Agent1 answers general questions about Contoso products and that the business requirement is for Agent1 to answer questions only about the products sold by Contoso . This is a behavioral boundary for the agent, so it should be implemented in the highest-priority instructions that define the agent’s role, allowed scope, and refusal behavior.

Microsoft Foundry guidance states that a system message is used to steer model behavior, define the assistant’s role and boundaries, and add safety or quality constraints for the scenario. The system message should instruct Agent1 to answer only when the question concerns Contoso products, use the configured Contoso product documentation as grounding, and politely refuse or redirect questions about non-Contoso products.

Top-p sampling and temperature control randomness, not business-domain scope. Increasing temperature would make responses less deterministic. Few-shot examples can support desired behavior, but examples alone are weaker than explicit system-level instructions for defining operating boundaries. Reference topics: system message design, prompt engineering, agent instructions, response constraints, and grounded generative AI behavior.

The correct built-in skills are Azure OpenAI Embedding and Text Split. The case study requires an indexing pipeline that enables semantic and vector search over the product sheets stored in Azure Blob Storage, so Agent1 can retrieve relevant product information for natural language customer questions. For a RAG pipeline, long PDF content must first be broken into retrievable chunks, and each chunk must then be vectorized for semantic similarity retrieval.

Microsoft’s Azure AI Search integrated vectorization guidance states that you create a skillset that calls the Text Split skill for chunking and the Azure OpenAI Embedding skill to vectorize the chunks. The Text Split skill breaks text into chunks and provides positional metadata, making it suitable when downstream embedding skills have input-length limits. The Azure OpenAI Embedding skill connects to an embedding model deployed in Azure OpenAI or a Microsoft Foundry project and generates embeddings during indexing.

Language Detection, Entity Recognition, and key phrase extraction can enrich text, but they do not create vector embeddings. Merge is useful for combining OCR text with document text, but it does not satisfy the core vector-search requirement. Reference topics: Azure AI Search skillsets, Text Split skill, Azure OpenAI Embedding skill, integrated vectorization, and RAG indexing.

The correct answer is B. Modify the system message instructions . The case study states that Agent1 answers general questions about Contoso products and that a business requirement is for Agent1 to answer questions only about products sold by Contoso. This requirement defines the agent’s allowed domain and refusal boundary, so it must be expressed in the agent’s system-level instructions. Microsoft Foundry guidance states that system messages steer Azure OpenAI chat model behavior and are used to define the assistant’s role, boundaries, output format, and safety or quality constraints.

The system message should instruct Agent1 to answer only Contoso-product questions, use Contoso product documentation when available, and decline questions about non-Contoso products. This directly enforces the intended business scope at the highest instruction level. Few-shot examples can reinforce desired behavior but are not the primary control for defining mandatory operating boundaries. Top-p sampling and temperature are decoding controls; they influence randomness and diversity, not whether the agent restricts answers to a specific product domain. Increasing temperature would likely reduce consistency. Reference topics: Microsoft Foundry agent instructions, system message design, prompt engineering, response boundaries, and grounded generative AI behavior.

The correct answer is B. Personally Identifiable Information (PII) Detection . The case study states that Agent1 must never reveal customer information , even if a document containing customer data is added accidentally to the product sheet repository in storage1. This is a privacy and compliance control requirement, so the appropriate capability is PII Detection.

Azure Language PII Detection is a Foundry Tools capability that identifies, classifies, and redacts sensitive information across text, conversations, and native documents. Microsoft states that PII Detection can be used to implement privacy controls, reduce sensitive data exposure, and support compliance requirements. In this scenario, PII Detection should be applied to retrieved product-sheet content and generated responses so customer names, contact details, identifiers, and other sensitive values are not exposed to users.

Prompt Shields are important for a separate requirement: protecting Agent1 from malicious instructions hidden in documents or embedded text. Microsoft describes Prompt Shields for documents as protection against hidden instructions embedded in external content. However, the option that directly satisfies the requirement to prevent disclosure of customer information is PII Detection. Self-harm and violence filters address harmful-content categories, not privacy leakage.