You have a Microsoft Foundry project that contains an agent for a customer support chat app. The agent uses a memory store and a memory search tool.You need to ensure that the conversation history does NOT persist across separate sessions.To what should you set the scope of the memory tool?
Answer(s): A
To ensure that conversation history does not persist across separate sessions, you must set the scope to session.The session scope restricts data access to the current active chat instance. It automatically wipes or ignores previous data when a new session starts.Incorrect:[Not C]user or {{$userId}} scope: Persists data across multiple sessions for that specific user. This would cause the exact issue you want to avoid by carrying historical context into new conversations.
https://ai.gopubby.com/agents-with-memory-conceptual-undestanding-part-01-f6caedfcd96d?gi=a9aa95df15c6
DRAG DROP (Drag and Drop is not supported)You have a Microsoft Foundry project that contains an agent.You need to enable long-term memory to ensure that the agent can recall user preferences across separate conversations. Stored memories must be isolated per authenticated user without the client application manually generating user IDs.How should you complete the Python code? To answer, drag the appropriate values to the correct targets.Each value may be used once, more than once, or not at all.Note: Each correct selection is worth one point.Select and Place:
Box 1: "{{$userId}}"User Isolation (Scope)Setting scope="{{$userId}}" instructs the Microsoft Foundry Agent Service to automatically map and partition memory to the logged-in individual using their Microsoft Entra user identity template. The platform handles this dynamically from request headers, removing the need for manual client-side user ID managementBox 2: [memory_tool]Tool List: The tools configuration parameter expects an iterable containing instantiated tool objects. Wrapping memory_tool inside a Python list ([memory_tool]) exposes the capability to the agent definition.
https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/memory-usage?pivots=python
You have a web app named App1 that processes user prompts by integrating with a Microsoft Foundry project named Project1. App1 performs the following actions:-▪ Sends prompts directly to a model by using the Azure OpenAI Responses API▪ Invokes the Azure AI Content Safety tool by using a Foundry connection within the same requestYou need to configure end-to-end visibility into each step of the request workflow.What should you do?
Answer(s): C
To configure end-to-end visibility into each step of the request workflow, you should Enable application tracing in the project.Project-Level Observability: Enabling application tracing allows Microsoft Foundry to natively track, trace, and monitor every component of the workflow—including calls to the Azure OpenAI Responses API and associated tools like Azure AI Content Safety—within the same request without requiring complex, separate SDKconfigurations.Centralized Tracking: Tracing captures the exact execution path across the project endpoints, allowing you to see metrics, latency, and inputs/outputs sequentially for both the model invocation and the content safety check.
https://learn.microsoft.com/en-us/azure/foundry-classic/how-to/develop/trace-production-sdk
You have a Microsoft Foundry project that contains an agent.The agent uses Azure Content Understanding in Foundry Too to process vendor onboarding packets. The packs include digital PDFs that contain tables and hyperlinks.The extracted content is indexed for search and provided to a downstream agent in the Markdown format.You need to generate a Markdown output that has a layout and a semantic structure optimized for RetrievalAugmented Generation (RAG) workflows.Which built-in analyzer should you use?
Answer(s): B
The appropriate built-in analyzer to use is prebuilt-documentSearch.RAG Optimization: The prebuilt-documentSearch analyzer is part of the dedicated Retrieval-AugmentedGeneration (RAG) analyzer suite within Azure Content Understanding. It is specifically built to perform semantic analysis and extract documents in structures optimized for chunking, indexing, and vector workflows.Native Markdown Layout: It extracts layout structures (such as paragraphs, complex multi-page tables, and hierarchical sections) directly into clean Markdown format. This structural preservation is ideal for downstream consumption by large language models (LLMs) or other AI agents.
https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/concepts/prebuilt-analyzers
You have a Microsoft Foundry project that contains an agent.The agent uses Azure AI Search for Retrieval Augmented Generation (RAG).You plan to ingest and index PDF product manuals.You need to build a solution that supports semantic similarity matching. The solution must ensure that the agent retrieves relevant data when user questions use different wording than the product manuals.Which indexing approach should you use?
Vector search is the correct indexing and retrieval type to use for this solution.Vector search versus semantic rankingWhile both features help bridge the gap between different wordings, vector search is specifically designed at the indexing and retrieval layer to handle semantic similarity matching by converting text into mathematical vectors (embeddings) based on conceptual meaning. Semantic ranking is a secondary re-ranking layer applied after initial retrieval to improve precision, but it cannot function as the primary indexing method on its own.
https://www.scribd.com/document/866453317/Agentforce-Specialist
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.