Free Practice Questions for Microsoft AI-103 Exam

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

A common Azure AI Search security-trimming pattern stores the authorization information required to filter each document directly in the search index.

First, add the allowed groups to each index entry . This provides a filterable field describing which Microsoft Entra groups are authorized to access that document.

Second, when a user performs a search, retrieve the user ' s group memberships . Those group identifiers form the user ' s effective document-access context.

Third, supply those groups as a filter with the search request. Azure AI Search can then exclude documents whose allowed-groups field does not intersect with the groups associated with the current user.

Creating one index per group would duplicate documents and significantly increase indexing and operational complexity. Retrieving every group in the tenant is unnecessary; only the current user ' s memberships are relevant. An Entra token authenticates a caller to the Search service but does not by itself implement an arbitrary per-document group ACL field in the classic filtering pattern described by this question.

The resulting solution performs authorization trimming during retrieval, ensuring inaccessible content is not passed to a RAG agent.

Study Guide alignment: build secure retrieval and grounding pipelines for enterprise information . Microsoft Learn

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

Use Microsoft Entra ID authentication and pass an OAuth 2.0 bearer token in the REST request’s Authorization header. Assign the required inference role, such as Cognitive Services User , only to each application’s managed identity or service principal. This authenticates the applications as distinct security principals and supports resource-scoped RBAC, auditing, token expiration, and immediate access revocation. Microsoft recommends Entra ID for production workloads because API keys are static, resource-wide secrets that cannot identify individual callers or provide granular authorization.

Each application must specify its appropriate deployment name when making an inference request. Foundry deployments assign a unique name and configuration to each deployed model. In the deployment-level REST API, that name appears in the request route:

/openai/deployments/{deployment-name}/chat/completions

The resource endpoint and authentication mechanism can remain common across all three applications, while the deployment name directs each request to the GPT-3.5 deployment optimized for that application’s workload. A deployment type describes capacity or provisioning characteristics and does not select a particular deployed model.

Study Guide alignment: configure authentication, managed identities, RBAC, model deployments, and REST-based model consumption.

Yes, the solution meets the goal. The problem is not retrieval availability, because the required regulatory clauses are already present in the retrieved policy documents. The failure occurs during generation: the agent produces a summary that omits required content. A reflection pass is the correct application-level control because it adds a verification step before the response is returned. The pass can compare the draft answer against the retrieved clauses, detect missing mandatory content, and trigger regeneration or revision until the summary includes the required clauses.

This aligns with Microsoft Foundry’s evaluation and observability model, where generated responses are assessed for reliability, groundedness, relevance, and quality throughout the AI application lifecycle. Foundry observability guidance describes evaluation as a mechanism for measuring response quality and improving AI outputs across development and production workflows. The Azure AI evaluation SDK also defines completeness as the extent to which a generated response contains all necessary and relevant information with respect to the provided ground truth. Reflection operationalizes that quality check inside the application flow, rather than merely reporting the defect after the fact. Reference topics: model reflection, response completeness, RAG generation quality, retrieved context verification, and agent response optimization.

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

A Retrieval Augmented Generation evaluator is required because Agent1 will retrieve product-sheet content and use it as grounding context when generating answers. Foundry RAG evaluators assess both retrieval quality and the quality of the final grounded response. This directly supports Contoso’s requirement that answers based on the product sheets be relevant, complete, and accurate.

The appropriate evaluation suite can include groundedness , which determines whether the answer is supported by the retrieved product information without fabrication; relevance , which evaluates whether the answer accurately and completely addresses the customer’s question; and response completeness , which measures whether critical expected information is missing. Retrieval evaluators can additionally determine whether the indexing and search pipeline returned context chunks relevant to the query.

A coherence evaluator assesses readability and logical organization but does not establish that claims are supported by storage1. A custom guardrail controls or blocks behavior rather than measuring RAG quality. Fine-tuning changes model behavior and does not evaluate whether retrieved documentation was selected and used correctly.

The AI-103 Study Guide includes evaluating models and applications for fabrications, relevance, quality, and safety , as well as monitoring grounding quality and retrieval relevance.

Agent1 requires memory because the business requirement explicitly states that the agent must retain conversation context and recall relevant information during future interactions. Microsoft Foundry Agent Service memory provides persistent knowledge that can be retained and retrieved across separate conversations, sessions, devices, and workflows. It can store meaningful information extracted from prior interactions, including user preferences, relevant facts, and summarized context, and then retrieve that information when personalizing later responses.

Short-term memory maintains context within the current conversation. Long-term memory supports continuity across future sessions, which directly addresses Contoso’s requirement. Memory scopes should be associated with individual user identities so that one customer’s stored information cannot be retrieved during another customer’s interaction.

Guardrails enforce safety or behavioral restrictions but do not provide conversation recall. Tools enable the agent to access external systems, while instructions define the agent’s role and operating boundaries. Neither tools nor instructions persist user-specific information across sessions.

The AI-103 Study Guide maps this requirement to choose appropriate memory, tool, and knowledge integration services and build agents that integrate retrieval, function calling, and conversation memory .

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

Call client.videos.create() to submit the prompt and start a video-generation job against the model deployment. Video generation is asynchronous: the initial response represents a job and contains properties such as its unique ID and current status rather than immediately returning the completed video. Microsoft’s official Python example creates the job by using client.videos.create(model=..., prompt=...).

The application must then poll the job. After waiting between requests, client.videos.retrieve(video.id) obtains the latest state of that specific job. Polling continues until the status becomes completed, failed, or cancelled. list would enumerate jobs rather than refresh the selected job, while download_content is used only after successful completion to retrieve the generated video file.

To comply with Contoso’s prohibition on API keys, the client should use a Microsoft Entra bearer-token provider. The OpenAI Python client accepts this provider through its api_key constructor parameter even though no static API key is used.

Study Guide alignment: design and implement video-generation solutions and integrate generative workflows through Foundry SDKs.

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.