Microsoft AI-500 : Designing and Implementing Multi-Agent AI Solutions

Correct Answer:

Explanation:
Quality of retrieved context: Retrieval evaluator; Directness of response to query: Relevance evaluator.
The dataset contains query, context, and response but does not contain document relevance labels. Microsoft ' s Retrieval evaluator is designed for exactly that situation: it uses an LLM judge to rate how relevant the retrieved context chunks are to the query and returns a 1-to-5 score with pass/fail behavior. The Relevance evaluator operates on the final response and measures whether the answer accurately, completely, and directly addresses the query. Document Retrieval is not appropriate because it requires retrieval ground truth such as known relevant documents or qrels. Groundedness answers a different question: whether response claims are supported by the provided context. Therefore the correct mapping is Retrieval for context quality and Relevance for response directness. For operational use, the measurement should be captured in a repeatable dataset, trace, or automated gate so that the same criterion can be compared across versions. That is more useful than a one-off manual observation and makes regressions visible before they become production incidents.
Official Microsoft reference: Microsoft Foundry - RAG evaluators

Correct Answer: A  🗳️

Explanation: Only visible for Free4Torrent members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
Orchestration pattern: Agent-as-tools; Context passed to specialists: Scoped claim data only.
The primary claims agent must retain task ownership and synthesize the final response, which is the defining property of the agents-as-tools pattern. The primary agent decides when to invoke each specialist, receives the specialist ' s result, and remains responsible for the overall conversation. Handoff orchestration would instead transfer control to another agent and therefore weaken the ownership requirement. Microsoft Agent Framework also makes it possible for the outer agent to pass only the arguments needed by the inner agent rather than sharing the entire conversation history automatically. That supports least-privilege context: each specialist receives only the claim fields required for its assigned work. Passing the whole claim or a shared transcript would unnecessarily expose data outside the specialist ' s domain. The selected combination therefore satisfies both control ownership and data minimization. The architecture should still be validated with representative end-to-end tests, but the selected component establishes the correct structural boundary first. Microsoft ' s AI-500 blueprint consistently favors explicit scopes, interfaces, and persistence or identity boundaries over prompt-only conventions.
Official Microsoft reference: Microsoft Agent Framework - Agents as tools

Correct Answer: B  🗳️

Explanation: Only visible for Free4Torrent members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
InvoiceValidationAgent and PaymentApprovalAgent: One blueprint and one agent identity per agent role; VendorNegotiationAgent: An independent blueprint, one agent identity, and one agent user account.
Invoice validation and payment approval are distinct finance roles with different ERP permissions, so each should have its own logical agent identity for least-privilege access and audit attribution. They can remain within the same finance trust boundary while using separate identities. The vendor-negotiation agent operates across an external supplier boundary and should therefore use an independent blueprint/trust boundary. Its dedicated Exchange Online mailbox introduces an additional Microsoft 365 requirement: Microsoft Entra Agent ID supports associating an agent identity with an agent user account when the agent needs resources that require a user object, such as Exchange mailboxes or Teams. Sharing a single identity across all roles would blur audit ownership and expand compromise impact. The answer therefore matches Microsoft ' s current agent-identity separation model. The same configuration should be paired with auditable identity, trace, and evaluation data so reviewers can prove which principal acted, which policy was applied, and why a request was allowed or blocked. That is particularly important for production multi-agent systems with external tools.
Official Microsoft reference: Microsoft Entra Agent ID - plan agent identity architecture

Topic 1, Contoso Ltd Case Study
Overview - Contoso, Ltd. is a health provider. The company is building an Azure-based multi-agent solution to streamline patient triage, access historical medical records, and schedule specialist appointments. Existing Environment - Microsoft Foundry - Contoso has a Microsoft Foundry project named HealthAssist that contains the following agents: Patient Intake: A public-facing chat interface where patients describe their symptoms Record Retrieval: An internal system that retrieves a patient ' s past medical history from a secure database Scheduling: Integrates with an external third-party booking system by using a Model Context Protocol (MCP) server Lead Orchestrator: A workflow agent that makes decisions based on the output of the other agents Knowledge Base - Contoso uses a Retrieval-Augmented Generation (RAG) system that contains clinical documents. Only the Patient Intake agent can access the RAG system. Problem Statements - Contoso identifies the following issues: The MCP server used by the Scheduling agent frequently times out during peak load. Patients report that during the intake process, the session frequently times out silently without indicating why. The issue occurs during workflow execution. Occasionally, the Patient Intake agent cannot extract relevant symptoms when patients provide verbose personal stories that are irrelevant to the medical issue. When the Patient Intake agent engages in long, multi-turn conversations with patients, the accumulating conversation history causes high latency due to massive prompt sizes and risks that exceed the model ' s context window. Requirements - Business Requirements - Contoso identifies the following business requirements: A physician must approve any triage assessments that recommend an emergency room visit.
HealthAssist must be able to handle large spikes in concurrent patient intake requests during flu season.
Before releasing updates to HealthAssist, the clinical team must review the accuracy of the Lead Orchestrator agent triage routing decisions against a set of historical test cases. Safety Requirement - Contoso identifies the following safety requirements: Implement a robust guardrail strategy to prevent HealthAssist from providing inappropriate medical diagnoses. Ensure that all public-facing agents block violence and hate speech. Prevent hardcoding new logic into the agents ' core prompt. Consultant Proposal - A consulting firm proposes the following solution to address various requirements and issues: Add a guardrail that has the highest sensitivity for all controls. Add a system prompt message to direct the agent to ignore hate speech. Implement a short- term memory context window that prompts patients multiple times to verify their symptoms. Add a system prompt message to direct the agent to recommend an emergency room visit if the patient is having heart palpitations. Security Requirements - Contoso identifies the following security requirements: Ensure that the agents do NOT have overlapping permissions to prevent lateral movement. Prevent the agents from accessing patients ' data outside of the current patient context. Ensure that all API keys are securely stored and rotated.
Follow the principle of least privilege, when possible. Performance Requirements - Contoso identifies the following performance requirements: Token usage must be monitored. Long-term semantic memory must be isolated by patient.