KaoGuTi是可以帶你通往成功之路的網站。KaoGuTi可以為你提供使你快速通過Microsoft AI-500 認證考試的詳細培訓資料，能使你短時間內多掌握認證考試的相關知識，並且一次性的通過Microsoft AI-500 認證考試。
| Section | Weight | Objectives |
|---|---|---|
| Secure, govern, and deploy multi-agent solutions | 20–25% | - Deploy and maintain solutions
|
| Develop multi-agent solutions in Azure | 30–35% | - Manage state and memory
|
| Evaluate, optimize, and monitor multi-agent solutions | 20–25% | - Assess performance and reliability
|
| Architect multi-agent solutions | 15–20% | - Design workflow and tool integration
|
我們KaoGuTi網站是在盡最大的努力為廣大考生提供最好最便捷的服務。速度和高效率當然不可避免，在當今的社會裏，高效率走到哪里都是熱議的話題，所以我們網站為廣大考生設計了一個高效率的培訓資料，可以讓考生迅速領悟，從而考試取得優異的成績。KaoGuTi Microsoft的AI-500考試培訓資料可以幫助考生節省大量的時間和精力，考生也可以用多餘的時間和盡力來賺去更多的金錢。
問題 #65
You need to recommend a Microsoft Foundry multi-agent solution that has the following domain-specific requirements:
* Agent responses must never include the names of two specific sanctioned companies.
* Agent responses must NOT expose customer account numbers
Which guardrail strategy should you include in the recommendation?
答案：B
解題說明：
Both stated restrictions concern content that must not appear in the agent ' s final output. A custom blocklist should therefore be applied to agent output so the two sanctioned company names are detected before a response is returned. The customer-account requirement likewise belongs at the output boundary, where PII
/sensitive-data detection can identify protected identifiers in generated content. Applying the controls only to user input would not stop the model from generating the prohibited names or identifiers itself. Task Adherence focuses on whether agent behavior stays within assigned procedures and is not a substitute for explicit output filtering. Microsoft Foundry guardrails are designed to attach controls to the intervention point where the relevant risk occurs. Because the risk is disclosure in the response, option C is the configuration that places both controls at the correct boundary. 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 Foundry guardrails - intervention points
問題 #66
HOTSPOT -
You have a multi-agent solution in a Microsoft Foundry project. The project is connected to an Application Insights resource.
You have the following code that implements tracing.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
答案：
解題說明：
Explanation:
No / No / Yes
The first statement is false because content recording is explicitly disabled, so prompt and generated response text are not stored as GenAI span content attributes even though tracing remains active. The second is false because the OpenAI client is obtained before trace-context propagation is enabled; Microsoft documents that clients created before the instrumentation change are not retroactively configured for that propagation behavior. The third statement is true because the tracing decorator for ordinary functions records supported function parameters as `code.function.parameter. < name > ` attributes. Those parameter attributes are separate from GenAI prompt-content recording, so disabling message content does not suppress them.
Consequently `email` and `loyalty_tier` can appear on the `lookup_customer` span. The correct sequence is No, No, Yes. The evaluation should also preserve correlation identifiers and version information where possible so a failed score can be traced back to the exact agent, model, tool call, or retrieval step that produced it. This turns the metric into an actionable diagnostic rather than only a dashboard number.
Official Microsoft reference: Microsoft Foundry - client-side agent tracing
問題 #67
You need to recommend a memory retrieval strategy to support the planned changes for claim Approval.
What should you recommend? To answer, drag the appropriate resources to the correct requirements. Each resource 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.
答案：
解題說明：
Explanation:
Prior claims: memory-store-490; Contact preferences: memory-store-490.
Both requirements describe information that should persist across conversations for the same customer:
previous claim information and stable contact preferences. Microsoft Foundry Memory is intended for durable, cross-session facts and summaries that agents can retrieve later, while a knowledge base is for shared reference content rather than user-specific history. The refund-processing and customer-refund tools are operational interfaces, not persistence layers. Using the existing memory store for both categories therefore matches the scenario ' s design objective. In production, the memory search tool should also be scoped to the end user so one customer ' s memory cannot be retrieved for another customer. Microsoft documents scope- based isolation for memory stores and supports a user-derived scope such as `{{$userId}}`. The key distinction is that the same memory store can hold multiple kinds of durable customer memory as long as retrieval is correctly scoped; there is no need to create separate tools or knowledge indexes for these two user- specific memory categories.
Official Microsoft reference: Create and use memory in Foundry Agent Service
問題 #68
You have a Microsoft Foundry Agent Service solution that includes two agents You need to configure memory for the agents. The solution must meet the following requirements:
* Isolate the memory between end users
* Isolate the memory between the agent domains.
* Support the deletion of one user ' s memory without deleting other users ' memory.
Solution: You create one memory store per end user and configure both agents to use each user ' s memory store with a static scope value.
Does this meet the goal?
答案：B
解題說明：
Creating one memory store for each end user separates users, but allowing both agents to use that user ' s store with the same static scope does not isolate the two agent domains. Memories produced by one agent can occupy the same logical collection as memories produced by the other agent. Microsoft Foundry Memory uses the `scope` parameter to partition a store, so a design that needs both user and domain isolation must preserve both dimensions, commonly through separate agent stores plus per-user scope. The per-user deletion requirement can also be handled more efficiently by deleting a user ' s scope rather than operating a separate store for every user. Because the proposed design fails agent-domain separation, it does not meet all requirements. Therefore B, No, is correct. In production, add telemetry and regression tests around this behavior so changes to prompts, models, tools, or orchestration do not silently alter the intended contract. The selected approach is the one that best matches the platform ' s native execution semantics.
Official Microsoft reference: Create and use memory in Foundry Agent Service
問題 #69
You have a Microsoft Agent Framework solution for customer support that includes the following agents:
* A triage agent
* A refund specialist agent that runs in the same process as the triage agent
* A compliance review agent that is exposed by a partner team as a remote service You need to identify which integration components the triage agent will use to coordinate interactions with the other agents.
What should you identify for each agent? To answer, drag the appropriate components to the correct agents Each component 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.
答案：
解題說明：
Explanation:
Refund specialist agent: Agent-as-tools; Compliance review agent: Agent-to-Agent (A2A) protocol.
The refund specialist runs in the same process as the triage agent, so exposing it as an agent-as-tool is the lightweight composition pattern. The outer triage agent can decide when to invoke the specialist while retaining overall task ownership. The compliance reviewer is different: it is a remote service owned by a partner team. Agent-to-Agent (A2A) is the interoperable protocol intended for independently hosted agents that may use a different runtime or framework. It supports capability discovery and remote task interaction without coupling the caller to the partner ' s implementation. Using A2A for the in-process specialist would add unnecessary network/protocol complexity, while treating the partner agent as an in-process tool would not match the deployment boundary. The two selections therefore reflect Microsoft ' s distinction between local agent composition and remote agent interoperability. The implementation should also preserve clear inputs and outputs around this step so that later agents receive only the information they require. This improves debuggability and keeps token, permission, and state growth under control as the workflow becomes more complex.
Official Microsoft reference: Microsoft Agent Framework - agents as tools and A2A
問題 #70
......
為了不讓你得生活留下遺憾和後悔，我們應該盡可能抓住一切改變生活的機會。你做到了嗎？KaoGuTi Microsoft的AI-500考試培訓資料是幫助每個想成功的IT人士提供的培訓資料，幫助你們順利通過Microsoft的AI-500考試認證。為了不讓成功與你失之交臂，趕緊行動吧。
AI-500通過考試: https://www.kaoguti.com/AI-500_exam-pdf.html