You have a customer support agent that uses the Microsoft Foundry Agent Service.Sometimes, customers return to a session days later to continue the same support case, and the agent must resume with the full historical context. The agent must provide the following:▪ Multi-turn continuity within the session▪ Cross-session continuity for the same case▪ Access to the full interaction history, including user messages, agent messages, tool calls, and tool outputsYou need to ensure that the agent automatically reloads the complete history on each new turn.What should you do?
Answer(s): A
To achieve full, multi-turn, and cross-session continuity with complete historical context (including user messages, agent messages, tool calls, and tool outputs), you must leverage the durable Conversation lifecycle provided by the Microsoft Foundry Agent Service runtime.Because the underlying Agent Service can be stateless at the inference tier, managing continuity across days requires linking your agent interactions to a persistent, server-side conversation ID.Here is exactly what must be done to meet your requirements:*-> 1. Maintain a Durable Conversation IDInstead of creating a brand-new conversation session every time a user returns, your application must persist and map the unique support case to a Microsoft Foundry Conversation ID (typically prefixed with resp_* or conv_*) in your external database.New Case: Create a new session and capture the generated ConversationId.Returning Case: Retrieve the previously saved ConversationId associated with that customer's support case from your database.2. Resume Sessions via the SDKWhen the customer returns days later, initialize the agent's session by passing the existing Conversation IDinto the session creation method. This forces the Microsoft Foundry Agent Service to automatically reload the complete, un-summarized thread history on the backend before processing the next turn.
https://learn.microsoft.com/en-us/agent-framework/agents/conversations/session
HOTSPOT (Drag and Drop is not supported)You have a Microsoft Foundry project that contains a deployed chat model.You have a Python service that sends API requests to the model. The service is integrated with an automated validation system that compares generated outputs against approved response patterns.Stakeholders report that small wording differences are causing validation mismatches.You need to update the request parameters to improve output stability. The solution must maximize reasoning quality.How should you complete the Python code? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: 0The best configuration for the temperature is 0.Why Temperature 0 is BestMaximizes Predictability: Setting temperature to 0 makes the model deterministic.Reduces Mismatches: It always selects the most likely tokens. This minimizes the small wording differences causing your validation failures.Preserves Reasoning: Lowering temperature does not degrade the core reasoning capability of a model; it simply eliminates random variations in how that reasoning is phrased.Why Other Options FailTemperature 1: This is the default creative balance. It allows standard token variance, which will continue to trigger your pattern-matching mismatches.Temperature 2: This creates maximum randomness. The output will become chaotic, nonsensical, and completely break both your validation system and reasoning quality.Box 2: "high"High output effort is the best configuration for this scenario.Why High Effort is BestMaximizes Reasoning: High effort allocates more computational tokens for internal chain-of-thought processing.Improves Consistency: Better reasoning helps the model strictly adhere to the complex rules and approved response patterns you have defined.Reduces Edge Cases: Subtle wording deviations usually happen when a model rushes its generation without sufficient planning.
https://www.microsoftpressstore.com/articles/article.aspx?p=3192408https://medium.com/data-science/12-rag-pain-points-and-proposed-solutions-43709939a28c
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(s): B
An agentic Retrieval-Augmented Generation (RAG) architecture is the best fit for your requirements.Traditional, linear RAG pipelines struggle with complex, multi-turn dependencies, whereas an agentic approach natively solves them through iterative reasoning and tool orchestration.Here is how an agentic RAG pattern specifically satisfies each the three technical requirements:1. Complex Questions & Multi-Chunk RetrievalThe Challenge: Complex questions often require aggregating distinct pieces of information scattered across different documents or sections.The Agentic Solution: An agent uses a Reasoning and Acting (ReAct) loop. It evaluates the user's query,breaks it down into sub-questions, and executes multiple distinct search queries. It then synthesizes the information from these diverse chunks before generating a final response.2. Multi-Turn Conversations & Retrieval PlanningThe Challenge: Standard RAG often just passes the latest user message or a simple chat history summary to the search index, which can lose context or misinterpret the user's true intent in long conversations.The Agentic Solution: The agent acts as a query planner. It maintains the state of the conversation and dynamically decides if a retrieval is needed, what specific keywords or vectors to target based on past turns,and how to reformulate the query to bridge context gaps.3. Parallel Retrievals for Low LatencyThe Challenge: Sequential lookups drastically increase time-to-first-token (TTFT), harming the chat user experience.The Agentic Solution: Modern AI agent frameworks allow the LLM to emit multiple tool calls simultaneously.The application layer can intercept these calls and execute parallel asynchronous queries against your AzureAI Search vectorized index, drastically minimizing latency.
https://arxiv.org/html/2501.09136v1
HOTSPOT (Drag and Drop is not supported)You need to recommend a plan to create a customer support agent by using the Microsoft Foundry AgentService. The agent must meet the following requirements:▪ Retain user preferences across multiple conversations.▪ Enable users to provide contextual grounding by directly uploading documents during a chat.Which Foundry capability should you recommend for each requirement? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Agent memory that uses persistent storageRetain user preferences across multiple conversations.To enable a customer support agent built on the Microsoft Foundry Agent Service to retain user preferences across multiple distinct conversations, you must implement the platform's native managed long-term memory system.The solution architecture must include the following specific components and configurations:*-> 1. Dedicated Long-Term Memory StoreAgent-to-Store Mapping: Provision one dedicated memory store attached directly to your customer support agent to establish a clear knowledge boundary.Managed Lifecycle Operations: Rely on the service runtime to automatically manage the asynchronous extraction of preferences, consolidation (merging duplicates and resolving conflicting facts), and hybrid search retrieval.2. User-Scoped Partitioning (Memory Scope)Isolation Vaults: Define a mandatory Memory Scope for every interaction.Unique Identifiers: Bind the scope parameter to a persistent identifier like the customer’s Microsoft Entra ID or a custom system UUID. This ensures user preferences are securely isolated and do not leak into other customers' sessions.3. Dual Memory TypesBox 2: File Search toolTo enable users to directly upload documents during a chat for real-time contextual grounding, you should include the File Search tool.This built-in tool is specifically designed to augment agents with knowledge from uploaded files or proprietary documents. When users upload a document during a chat thread, the Foundry Agent Service File Search Tool automatically handles the extraction, chunking, embedding, and vector searching of that file to ground the agent's responses dynamically.Incorrect:* Azure AI SearchWhile it is a knowledge grounding tool, the Azure AI Search Tool is built to connect an agent to a pre-existing,centralized corporate search index. It does not handle ad-hoc user file uploads directly inside a chat session.* Code InterpreterThe Code Interpreter Tool is used for executing Python code in a sandboxed environment to perform advanced mathematical calculations, data analysis, and chart generation, rather than document vector retrieval.
https://learn.microsoft.com/en-us/azure/foundry-classic/agents/how-to/tools-classic/overview
You have a Microsoft Foundry project that contains an agent. The agent generates summaries from retrieved policy documents.You need to improve response completeness. The solution must be implemented in the logic of the application code before responses are returned.What should you do?
Correct:* Add a reflection pass before the responses are returned.A reflection pass acts as an internal verification step within your application's logic. It directs the agent to evaluate its own draft response against the retrieved policy documents to ensure no mandatory regulatory clauses were left out. If it detects that critical text is missing, it regenerates or amends the answer before sending it to the user. This directly fulfills the core requirement of improving response completeness.* Add a retry evaluation before the responses are returned.You should implement an evaluation and retry loop in your application code.You must wrap the agent call inside a conditional code loop that evaluates the output against required criteria(such as a checklist of regulatory clauses), and programmatically forces a retry if information is omitted.Incorrect:* Decrease the value of the max_tokens parameter.* Decrease the value of the temperature paramerer.* Enable response streaming.* Increase the value of the presence_penalty parameter* Replace the model with a smaller deployment.* Switch to Retrieval Augmented Generation (RAG).
https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/ai-search
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.