Pass the Microsoft Azure AI Engineer Associate AI-103 Questions and answers with ExamsMirror

Azure Resource Manager resource paths are scoped through the subscription , not the Microsoft Entra tenant. Therefore, the URL must contain:

subscriptions/8d3591aa-96b8-4737-ad09-00f9b1ed35ad

The tenant ID identifies the Microsoft Entra directory but does not replace the subscription portion of an ARM resource path.

The appropriate resource provider is Microsoft.CognitiveServices . Azure AI service accounts, including multi-service Azure AI resources, are provisioned under the Microsoft.CognitiveServices/accounts resource type.

A multi-service resource is required because the solution needs both Language sentiment analysis and Vision OCR while exposing a consolidated Azure resource with common key/endpoint management. Microsoft.ApiManagement manages API gateways, Microsoft.ContainerService manages Kubernetes services, and Microsoft.KeyVault manages keys and secrets rather than provisioning Azure AI capabilities.

A typical ARM resource path therefore contains:

/subscriptions/ < subscription-id > /resourceGroups/ < rg > /providers/Microsoft.CognitiveServices/accounts/ < name >

This aligns with the AI-103 requirement to design Azure infrastructure for AI apps and choose appropriate Foundry/Azure AI services . Microsoft Learn

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

Custom Vision model export is supported for compact domains . The existing project uses the ordinary General domain, so the first action is to change the domain to General (compact) .

A compact domain uses a model architecture specifically designed to support local/edge inference and export. Changing the domain alone does not transform the already-trained iteration into a compact model. Therefore, the second action is to retrain the model so that a new iteration is generated using the compact-domain architecture.

After the compact iteration has been trained, export the model in an appropriate supported format. The resulting model package can then be deployed within the disconnected environment and perform inference without contacting the Azure-hosted Custom Vision prediction service.

Creating a new classification model is incorrect because the existing scenario is object detection. Changing the classification type is also unnecessary and would not address exportability.

The required sequence is therefore:

General → General (compact) → retrain → export

This is a standard Custom Vision edge-deployment workflow and directly supports environments with restricted or unavailable internet connectivity.

Study Guide alignment: implement solutions that identify objects/components and deploy computer-vision functionality appropriate to the target environment .

The correct choice is to use a model cascade that routes the requests to different models . In Microsoft Foundry, this pattern aligns with model routing: simple, low-risk prompts can be handled by smaller, faster, lower-cost models, while complex prompts can be escalated to more capable or reasoning models. Microsoft’s Foundry model router guidance states that the router optimizes cost and latency while maintaining comparable quality by using smaller, cheaper models when they are sufficient and larger or reasoning models when the task requires more advanced capability.

This directly matches the scenario: most traffic consists of simple FAQs, so routing those requests to efficient models reduces average latency and token-processing cost. Advanced reasoning requests still receive high-quality responses because they are routed to models with stronger reasoning capability. Microsoft’s model router documentation also explains that routing decisions consider prompt difficulty, cost, quality, latency, and conversation context, making it suitable for diverse chat workloads.

Increasing max_tokens for all requests would usually increase cost and latency. Sending all requests to a smaller model risks poor quality for complex questions, while sending all requests to the most capable model wastes cost and latency on simple FAQs. Reference topics: Microsoft Foundry model routing, model selection, generative AI optimization, latency management, and cost-aware AI application design.

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 .

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

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.

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

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.