P.S. Free & New AI-103 dumps are available on Google Drive shared by Test4Cram: https://drive.google.com/open?id=1i38otMsmNwV2KeWWov0TamovAM29BGvo
Thousands of Developing AI Apps and Agents on Azure AI-103 exam candidates have passed their exam and you should also try Microsoft AI-103 Exam Questions. Developing AI Apps and Agents on Azure AI-103 Exam and start preparation with Test4Cram AI-103 and pass it with good scores.
| Section | Objectives |
|---|---|
| Plan and Manage Azure AI Solutions | - Model selection and lifecycle management - Responsible AI principles and governance - Azure AI resource provisioning and configuration |
| Implement Computer Vision Solutions | - OCR and document intelligence - Image classification and object detection |
| Develop Generative AI Applications and Agents | - AI agents architecture
|
| Knowledge Mining and Information Retrieval | - Azure AI Search configuration - RAG (Retrieval Augmented Generation) patterns - Indexing and semantic search |
| Implement Natural Language Processing Solutions | - Translation and multilingual support - Text analytics and summarization - Language understanding and intent recognition |
To pass the AI-103 exam is not an easy task. It is a challenging exam. However, proper planning and preparation with AI-103 exam questions can enable you to pass the AI-103 exam easily. As far as the Microsoft AI-103 Practice Test are concerned, these AI-103 Practice Test questions are designed and verified by Microsoft AI-103 exam trainers. So you rest assured that with AI-103 exam real questions you can pass Developing AI Apps and Agents on Azure AI-103 exam easily.
NEW QUESTION # 106
Drag and Drop Question
You have a Microsoft Foundry project that contains an agent used by the financial analysts at your company.
You need to optimize the agent workflow by providing additional data access and processing capabilities. The solution must meet the following requirements:
- Ensure that the agent can perform calculations during conversations.
- Ensure that the agent can access up-to-date information from public
websites.
- Ensure that the agent can retrieve information from documents
uploaded directly to the agent.
What should you use for each requirement? To answer, drag the appropriate tools to the correct requirements. Each tool may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
NEW QUESTION # 107
You have a Microsoft Foundry project named Project1 that contains an agent. The agent uses an OpenAPI 3.0 specification to call an external weather service.
The weather service requires a key to be passed in an HTTP header. The key value is stored as a connection in Project1.
You need to ensure that the key value from the connection is included automatically whenever the OpenAPI tool is invoked.
What should you configure in the OpenAPI specification?
Answer: D
Explanation:
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.
NEW QUESTION # 108
You have a Microsoft Foundry project that contains an agent.
The agent uses a knowledge source built from documents stored in Azure Blob Storage. The documents include digitally scanned PDFs that contain multipage tables.
You have an ingestion job that extracts only plain text, causing loss of table structure, headings, and page-number metadata.
Users frequently ask questions that require the retrieval of specific table rows across the pages.
You need to configure an ingestion job for a Retrieval Augmented Generation (RAG) pipeline that performs optical character recognition (OCR) on scanned PDFs, preserves tables and headings as structure-aware chunks, and stores page-number metadata with each chunk.
How should you configure the ingestion job?
Answer: B
Explanation:
Use OCR and page-level chunking.
Structure Preservation: OCR combined with document layout analysis (such as layout-aware or page-level chunking) detects visual structures like tables, headers, and reading order.
Row-Level Granularity: Page-level chunking retains the boundaries and context of multipage tables, enabling the RAG system to isolate and retrieve specific rows effectively.
Metadata Enrichment: Processing documents page-by-page allows the ingestion pipeline to automatically tag each extracted text chunk with its source page-number metadata.
Incorrect:
[not C]
Use page-level OCR extraction and store each page as a single chunk:
While this captures page numbers, storing an entire page as a single chunk introduces too much noise. It prevents the model from pinpointing specific table rows and often exceeds the optimal context window size for precise RAG retrieval.
[Not D]
Use basic parsing and fixed-size chunking:
Basic parsing cannot read digitally scanned PDFs, resulting in empty or completely garbled text.
Furthermore, fixed-size chunking splits text at arbitrary character limits, which destroys table structures and splits individual rows across different chunks.
Reference:
https://pub.towardsai.net/unlocking-key-technologies-in-document-parsing-81bfe20d741b
NEW QUESTION # 109
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.
You have a multimodal Al generative model that accepts image uploads and uses extracted image text to generate responses.
You discover that users can upload unsafe images and embed hidden instructions into images to manipulate the model.
You need to implement controls to mitigate the risk.
Solution: You configure a prompt shield for user prompts.
Does this meet the goal?
Answer: A
Explanation:
The solution does not meet the goal. Prompt Shields for user prompts are designed to detect direct attempts by a user to manipulate the model through the prompt itself. In this scenario, the malicious instructions are embedded inside uploaded images and then introduced into the model context through extracted image text.
That pattern is an indirect prompt injection or document attack, not merely a direct user-prompt attack.
Microsoft's Prompt Shields guidance distinguishes between user prompt attacks and document attacks, and states that document attacks involve harmful instructions embedded in supplied documents or third-party content.
The solution is also incomplete because users can upload unsafe images. Azure AI Content Safety includes image APIs that detect harmful content in images and support moderation across modalities. A complete mitigation would combine image moderation for unsafe visual content with Prompt Shields for document attacks, and optionally Spotlighting, so OCR-derived or embedded image text is treated as lower-trust context.
Prompt Shields for user prompts alone would not reliably block unsafe images or hidden instructions extracted from those images. Reference topics: Azure AI Content Safety, Prompt Shields, user prompt attacks, document attacks, image moderation, and multimodal safety.
NEW QUESTION # 110
You have a chat app in a Microsoft Foundry project and an Azure AI Search vectorized index.
You need to connect to the index to meet the following requirements:
* Complex questions must retrieve information from multiple chunks.
* Multi-turn conversations must influence retrieval planning.
* Retrievals must run in parallel to reduce latency.
Which retrieval approach should you use?
Answer: A
Explanation:
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.
NEW QUESTION # 111
......
Preparation from reliable material is essential to get success in the real Developing AI Apps and Agents on Azure (AI-103) exam. One of the most crucial aspects of test preparation is relying on Developing AI Apps and Agents on Azure (AI-103) exam dumps. The authenticity of Developing AI Apps and Agents on Azure (AI-103) exam questions material plays a huge role in achieving a passing score. In the case of choosing, Developing AI Apps and Agents on Azure (AI-103) exam dumps outdated material, and one fails and loses resources. Test4Cram is committed to providing real AI-103 Questions, ensuring that applicants get success in a short time.
AI-103 Test Practice: https://www.test4cram.com/AI-103_real-exam-dumps.html
P.S. Free 2026 Microsoft AI-103 dumps are available on Google Drive shared by Test4Cram: https://drive.google.com/open?id=1i38otMsmNwV2KeWWov0TamovAM29BGvo