AB-620 Designing and Building Integrated AI Agent Solutions Studio in Copilot
Testlet 1 Case Study
Background
Blue Yonder Airlines is a global carrier headquartered in Los Angeles, California, operating domestic and international flights. The company serves millions of passengers annually through its website, mobile app, and call centers. To improve customer service efficiency and reduce call center volume, Blue Yonder is deploying an AI agent in Microsoft Copilot Studio.
The agent will handle customer inquiries across multiple channels – web chat, mobile app, and Microsoft Teams (for internal support staff). It will answer questions, retrieve data from enterprise systems, and escalate to human agents when needed.
The project is led by a cross-function team:
-
Product manager: Defines requirements and success metrics.
-
Lead agent author: Designs topics, intents, and generative behavior.
-
Flow designers: Build agent flows and integrations.
-
IT/security and compliance: Oversees identity, data protection, and Responsible AI (RAI) compliance.
Current environment
Channels
- Public website: Embedded web chat
- Mobile app: In-app chatbot
- Microsoft Teams: Internal support agent access
Identity and access
- Customers: Anonymous access for general inquiries (e.g., flight status, baggage policy).
- Authentication is required for personal data access (e.g., bookings, loyalty points).
- Internal staff: Authenticate via Microsoft Entra ID.
Data sources
- Reservation and Ticketing System (internal): REST API, no prebuilt connector with custom enterprise database.
- Flight Status and Weather APIs (external): REST APIs with API keys.
- Customer Support Knowledge Base: SharePoint library with PDFs and policy documents. Loyalty Program Data: Stored in Dynamics 365 and Dataverse.
- Travel Advisory Content: Uses REST API with partner services.
Integration mechanisms
- Custom connectors must be used for internal APIs that lack prebuilt connectors.
- HTTP request nodes may be used for lightweight external APIs.
- Knowledge sources must be used for unstructured content.
- Agent flows must be used to encapsulate reusable logic (e.g., rebooking).
Business requirements
Omnichannel support
Deploy the agent across web, mobile, and Teams with a consistent user experience. The Teams deployment must also support internal staff.
Self-service capabilities
-
The agent must handle common inquiries such as:
-
Flight status
-
Booking and rebooking
-
Loyalty program questions
-
Travel policies and baggage rules
Human escalation
- If the agent cannot resolve an issue or the user requests help, it must:
- Escalate to a human agent.
- Transfer the conversation transcript and relevant context.
- Redact any sensitive personal data before escalation.
Knowledge integration
The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.
Performance metrics
- First-contact resolution: +25%
- Tier-1 call deflection: ≥20%
- Response time: 90% of queries answered within 30 seconds
- Accuracy: ≥95% for known FAQs
- CSAT: ≥85% for AI-handled interactions
Technical requirements
Platform constraints
- No custom code is permitted; only Copilot Studio's built-in tools may be used.
- All backend logic must be implemented using agent flows.
- Markdown must be used for formatting (e.g., bold, bullet points); HTML is not supported.
Authentication
- Sign-in is required for personal data access.
- Anonymous access is allowed for general inquiries.
- User identity must be used for data access; shared or builder credentials must not be used.
Compliance and security
- Power Platform DLP policies must be enforced to block unauthorized data flows.
- Responsible AI content moderation filters must be enabled.
- Prompt modifications must be added to enforce tone, disclaimers, and refusal behavior.
- Disclaimers must be applied consistently across all generative responses. Manual edits to individual topics must be avoided.
Monitoring and maintenance
- All conversations and actions must be logged for auditing.
- Weekly reviews of transcripts and metrics must be conducted.
- Topics, flows, and knowledge sources must be updated as policies or systems evolve.
Issues and constraints
-
API rate limits: External APIs (e.g., flight status) have usage limits. Agent flows must handle retries and caching to avoid exceeding quotas.
-
Knowledge base limits: Copilot Studio has limits on the number and size of indexed documents. Large files must be split or summarized.
-
Generative answer risks: Generative responses must be constrained to avoid policy violations. Prompt modifications and filters must be used to enforce tone, safety, and compliance.
-
User input variability: Users phrase questions in diverse ways. Topics must include varied trigger phrases and fallback handling.
-
Authentication UX: The agent must clearly explain when sign-in is required and handle transitions smoothly across channels.
Problem statement
Blue Yonder Airlines must deploy a secure, scalable, and policy-compliant AI agent using Microsoft Copilot Studio.
The agent must deliver accurate, helpful, and safe responses across multiple channels, integrate with enterprise systems, and support both anonymous and authenticated users.
It must adhere to strict data protection and Responsible AI standards while improving customer service efficiency and satisfaction
QUESTION 1
You need to configure the agent in Copilot Studio to meet Blue Vender's Responsible AI and data protection requirements.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Responsible AI and data protection requirements
- Add custom prompt modifications.
- Conduct adversarial testing.
- Define Data Loss Prevention (DLP) policies.
- Integrate with Microsoft Purview.
- Disable generative answers.
- Configure content moderation filters.
Answer Area
- []
- []
- []
Explanation/Reference:
Explanation:
Scenario: Problem statement: The agent must adhere to strict data protection and Responsible AI standards while improving customer service efficiency and satisfaction.
Step 1: Define Data Loss Prevention (DLP) policies
Security and compliance must be established at the foundation level. Admins use the Power Platform admin center to configure DLP policies. This establishes environmental guardrails by restricting unauthorized data connectors or preventing the agent from leaking sensitive data.
Step 2: Add custom prompt modifications
Once the environment is secure, the maker configures the specific behavior of the agent. Custom prompt modifications and agent instructions shape the tone, define conversational topics, and establish explicit boundaries for the generative model (e.g., instructing the model to strictly stay within its knowledge base).
Step 3: Conduct adversarial testing
This is the final evaluation phase before deployment. After the guardrails and custom prompts are in place, you simulate real-world attacks (such as jailbreaks, prompt injections, or malicious user inputs) to verify that the agent reliably adheres to your corporate guidelines and Microsoft's Responsible AI standards.
QUESTION 2
You need to evaluate whether the current configuration decisions for the Blue Yonder Copilot agent comply with the company's security and governance policies.
Which compliance status should you assign to each configuration decision? To answer, move the appropriate compliance statuses to the correct configuration decisions. You may use each compliance status once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Compliance statuses
- Compliant
- Non-compliant
Compliance configuration
| # | Configuration decision | Compliance status |
|---|---|---|
| 1 | The agent allows anonymous access to general inquiries such as baggage policies. | |
| 2 | The agent uses an open web search to answer questions beyond internal knowledge. | |
| 3 | The team relies only on default content filters without custom RAI instructions. | |
| 4 | The agent uses one shared admin credential for all internal data access. |
Correct Answers
| # | Configuration Decision | Compliance Status | Explanation |
|---|---|---|---|
| 1 | The agent allows anonymous access to general inquiries such as baggage policies. | Compliant | Anonymous access is permitted for general inquiries. Authentication is required only when accessing personal data. |
| 2 | The agent uses an open web search to answer questions beyond internal knowledge. | Non-compliant | Open web search may introduce unverified information and conflict with requirements to constrain generative responses. |
| 3 | The team relies only on default content filters without custom RAI instructions. | Non-compliant | Custom prompt modifications are required to enforce tone, disclaimers, and refusal behavior consistently. |
| 4 | The agent uses one shared admin credential for all internal data access. | Non-compliant | Internal data access must use the user's identity rather than shared or builder credentials. |
explanation/Reference:
Explanation:
Box 1: Compliant Anonymous access is allowed for general inquiries.
Box 2: Non-compliant Should use only internal sources.
The agent must handle common inquiries such as:
Flight status Booking and rebooking Loyalty program questions Travel policies and baggage rules
Box 3: Non-compliant Responsible AI content moderation filters must be enabled.
Box 4: Non-compliant User identity must be used for data access; shared or builder credentials must not be used.
QUESTION 3
You need to deploy the Blue Yonder Copilot agent to the public website and Microsoft Teams while ensuring compliance with the company's security and Responsible AI requirements.
Which two actions should you perform before making the agent available on both channels? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Configure prompt modifications to enforce tone, disclaimers, and refusal behavior at the system level.
B. Manually add disclaimers to each topic before publishing.
C. Embed the web channel and then rely on channel-level settings to enforce content moderation.
D. Configure Power Platform DLP policies to restrict unauthorized data connectors.
E. Publish the agent and then enable Responsible AI filters individually for each channel.
QUESTION 3 — Correct Answers
Correct answers: A and D
- A. Configure prompt modifications to enforce tone, disclaimers, and refusal behavior at the system level.
- D. Configure Power Platform DLP policies to restrict unauthorized data connectors.
Why not the other options?
- B: Disclaimers should be applied consistently through shared/system-level configuration, not manually added to every topic.
- C: Embedding the web channel does not replace agent-level Responsible AI configuration.
- E: Responsible AI safeguards should be configured before publication, not postponed until afterward.
Exam tip: When the question emphasizes both consistent generative behavior and data protection, choose prompt modifications + DLP policies.
逐项分析
| 选项 | 判断 | 原因 |
|---|---|---|
| A | ✅ 正确 | 使用系统级或 Agent 级 prompt modifications,统一控制语气、免责声明和拒绝行为。 |
| B | ❌ 错误 | 场景明确要求统一配置,避免逐个 Topic 手动添加免责声明。 |
| C | ❌ 错误 | Web channel 的嵌入设置不能代替 Responsible AI 内容安全配置。 |
| D | ✅ 正确 | 场景明确要求强制实施 Power Platform DLP policies,限制未经授权的数据连接器和数据流。 |
| E | ⚠️ 有争议 | 启用 Responsible AI 内容过滤符合场景要求,但选项要求先发布,再逐个 Channel 启用,顺序不合理。 |
最终判断
- 按照题目给出的完整场景和选项措辞:A、D 更合理。
- 如果官方答案确实是 A、E: 出题者可能想考查 prompt modifications 和 Responsible AI content moderation filters 这两个功能,而忽略了 E 中发布顺序的问题。
考试记忆重点:
- Prompt modifications → 统一控制生成式回答的行为。
- Content moderation filters → 过滤不安全内容。
- DLP policies → 管控连接器及数据流。
因此,如果你正在准备考试并且已有可靠的官方答案来源,可以暂时记录 A、E(题库答案),但需要注意:从严格的技术和安全部署顺序来看,E 的措辞并不严谨。
QUESTION 4
You need to configure the Blue Yonder Copilot agent's responses in accordance with the company's content control and platform requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Add required disclaimer text inside each individual topic.
B. Configure prompt instructions that include disclaimer text.
C. Use Markdown syntax within response content.
D. Insert HTML formatting directly into topic responses.
E. Duplicate disclaimer text across reusable topics.
QUESTION 4 — Correct Answers: B and C
- B. Configure prompt instructions that include disclaimer text.
- C. Use Markdown syntax within response content.
Explanation
- B — Correct: Prompt instructions can define consistent disclaimer text for generative responses, avoiding manual edits to each individual topic.
- C — Correct: The scenario explicitly requires Markdown formatting and states that HTML is not supported.
- A — Incorrect: Adding disclaimers to every topic creates unnecessary manual work and does not ensure consistent handling across all generative responses.
- D — Incorrect: HTML formatting is not supported by the platform requirements.
Exam tip: Consistent disclaimers → prompt instructions; supported formatting → Markdown.
Correct Answer: BC Section: (none) Explanation/Reference:
Explanation:
Scenario: Platform constraints No custom code is permitted; only Copilot Studio's built-in tools may be used.
All backend logic must be implemented using agent flows.
[C] Markdown must be used for formatting (e.g., bold, bullet points); [Not D] HTML is not supported.
[B] Disclaimer text.
The best approach is to configure prompt instructions that include disclaimer text.
This method ensures the disclaimer is applied universally to all AI-generated responses without manual duplication across topics. It scales effectively and reduces maintenance overhead.
QUESTION 5
You need to configure the agent in Copilot Studio to use internal and external partner knowledge sources to answer user questions about the airline services.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Use a Microsoft Graph connector to index the partner's travel advisory content.
B. Write individual Q&A pairs for each document as separate topics.
C. Enable unrestricted web search for the agent.
D. Add the internal policy documents as a knowledge source.
[A] External Scenario:
Data sources include:
Travel Advisory Content: Uses REST API with partner services.
Configuring a Microsoft Graph connector to index your external data and utilizing REST APIs are highly effective and distinct strategies for supplying knowledge and actions in Microsoft Copilot Studio.
[D] Internal Scenario:
The agent will handle customer inquiries across multiple channels – web chat, mobile app, and Microsoft Teams (for internal support staff). It will answer questions, retrieve data from enterprise systems, and escalate to human agents when needed.
Data sources include: Customer Support Knowledge Base: SharePoint library with PDFs and policy documents.
Correct Answers: A and D
- A. Use a Microsoft Graph connector to index the partner's travel advisory content.
- D. Add the internal policy documents as a knowledge source.
Explanation
- A — Correct: A Microsoft Graph connector can make external partner content available through Microsoft Graph-based search and knowledge integration, when the partner source and connector are supported.
- D — Correct: Internal policy documents should be added as a knowledge source so the agent can answer questions using unstructured content.
Why the other options are incorrect
- B: Creating individual Q&A topics for every document is not scalable and contradicts the requirement to use knowledge sources.
- C: Unrestricted web search risks introducing unverified information and conflicts with the requirement to constrain generative responses.
Exam tip: Use knowledge sources for internal documents and supported connectors for external partner content.
QUESTION 6
You need to ensure that every AI-generated response from the agent in Copilot Studio includes a disclaimer that complies with the company's security and governance policies.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Add a greeting message that includes the disclaimer.
B. Add a prompt modification in the generative answers node settings.
C. Create a disclaimer topic that always runs first.
D. Disable generative answers and use only pre-authored responses.
E. Edit every topic's first message to include the disclaimer.
Correct Answer: AB Section: (none)
Explanation/Reference:
Explanation:
[A] Adding a mandatory disclaimer to your greeting message is the best practice for agent governance. You can enforce this by configuring your Greeting System Topic and adding formal "Output Rules" to the agent's core instructions.
[B] Using prompt modification in the Generative Answers node settings is an excellent and highly effective strategy for embedding compliance disclaimers into your agent's responses.
QUESTION 7
You need to determine which authentication model should be applied to each Blue Yonder Copilot interaction scenario to comply with the company's security and governance requirements.
Which authentication requirement should you apply to each scenario? To answer, move the appropriate authentication requirements to the correct user scenarios. You may use each authentication requirement once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Authentication requirements (Options)
- Allow anonymous access.
- Require customer sign-in using an account.
- Require internal agent sign-in using Microsoft Entra ID.
- Use agent author credentials for authenticated data calls.
| User scenario | Authentication requirement |
|---|---|
| A customer asks, "What is the baggage allowance for international flights?" | [ 空白框 ] |
| A customer asks, "Can I review my upcoming trips?" | [ 空白框 ] |
| An internal support agent accesses the Copilot agent from Microsoft Teams to look up a loyalty member's profile. | [ 空白框 ] |
Correct Answers — Authentication Requirements
| User scenario | Correct authentication requirement |
|---|---|
| 1. A customer asks, “What is the baggage allowance for international flights?” | Allow anonymous access. |
| 2. A customer asks, “Can I review my upcoming trips?” | Require customer sign-in using an account. |
| 3. An internal support agent accesses the Copilot agent from Microsoft Teams to look up a loyalty member's profile. | Require internal agent sign-in using Microsoft Entra ID. |
Explanation
- General information: Baggage policies are public information, so authentication is not required.
- Personal booking information: Upcoming trips contain personal data, so the customer must sign in.
- Internal staff access: Employees must authenticate through Microsoft Entra ID to access internal customer information.
Unused option: Use agent author credentials for authenticated data calls.
This option is incorrect because the scenario explicitly requires user identity for data access, not shared or maker credentials.
Box 1: Allow anonymous access.
Scenario: Customers: Anonymous access for general inquiries (e.g., flight status, baggage policy).
Box 2: Require customer sign-in using an account.
Scenario: Authentication is required for personal data access (e.g., bookings, loyalty points).
Box 3: Require internal agent sign-in using Microsoft Entra ID.
Scenario: Internal staff: Authenticate via Microsoft Entra ID.
Question Set 2
QUESTION 1
A company has an existing custom connector that is approved and available in the environment. A builder wants an agent in Copilot Studio to call the connector during a conversation to retrieve information from an internal system.
To meet the business needs, the solution must meet the following requirements:
- The agent must make the connector available for topic steps.
- The agent must run the connector call with a valid connection.
- The connector call must receive the required input values at runtime.
You need to configure the agent so the custom connector can be used as a tool.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Configurations (Options)
- Map topic variables to the tool inputs.
- Add the connector as a tool in the agent.
- Add the connector as a knowledge source.
- Create or reuse a connection for the connector.
| Requirement | Configuration |
|---|---|
| The agent must make the connector available for topic steps. | [ 空白框 ] |
| The agent must run the connector call with a valid connection. | [ 空白框 ] |
| The connector call must receive the required input values at runtime. | [ 空白框 ] |
Correct Answers
| Requirement | Configuration |
|---|---|
| 1. The agent must make the connector available for topic steps. | Add the connector as a tool in the agent. |
| 2. The agent must run the connector call with a valid connection. | Create or reuse a connection for the connector. |
| 3. The connector call must receive the required input values at runtime. | Map topic variables to the tool inputs. |
Explanation
- Add the connector as a tool in the agent — makes the custom connector available for the agent to invoke.
- Create or reuse a connection for the connector — provides the authenticated connection required to execute the API operation.
- Map topic variables to the tool inputs — passes the required runtime values to the connector.
Unused option: Add the connector as a knowledge source. A connector used to execute API actions is a tool, not a knowledge source.
Correct Answers
| Requirement | Configuration |
|---|---|
| 1. The agent must make the connector available for topic steps. | Add the connector as a tool in the agent. |
| 2. The agent must run the connector call with a valid connection. | Create or reuse a connection for the connector. |
| 3. The connector call must receive the required input values at runtime. | Map topic variables to the tool inputs. |
Explanation
- Add the connector as a tool in the agent — makes the custom connector available for the agent to invoke.
- Create or reuse a connection for the connector — provides the authenticated connection required to execute the API operation.
- Map topic variables to the tool inputs — passes the required runtime values to the connector.
Unused option: Add the connector as a knowledge source. A connector used to execute API actions is a tool, not a knowledge source.
QUESTION 2
A company needs to ground an agent in Copilot Studio answers using live enterprise data from a supported system via a Microsoft Power Platform connector.
To meet the business needs, the builder must meet the following requirements:
Authenticate using a valid connection.
Add the connector as a real-time knowledge source.
Select the tables for knowledge grounding.
You need to add a Power Platform connector as a real-time knowledge source for the agent.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
以下是提取并整理为 Markdown 格式的内容,您可以直接复制:
Select and Place:
REST API (Options)
- Select Sign in and create a new connection or reuse an existing connection.
- Select the tables to include as the knowledge source.
- Select Add knowledge from the agent Knowledge experience.
- Select the real-time connector from the Add knowledge dialog.
- Select Add to agent to complete the connection.
| Answer Area |
|---|
| 1 [ 空白框 ] |
| 2 [ 空白框 ] |
| 3 [ 空白框 ] |
| 4 [ 空白框 ] |
| 5 [ 空白框 ] |
Correct Order
| Step | Action |
|---|---|
| 1 | Select Add knowledge from the agent Knowledge experience. |
| 2 | Select the real-time connector from the Add knowledge dialog. |
| 3 | Select Sign in and create a new connection or reuse an existing connection. |
| 4 | Select the tables to include as the knowledge source. |
| 5 | Select Add to agent to complete the connection. |
Sequence to remember
Add knowledge → Select connector → Sign in → Select tables → Add to agent
This sequence first starts the knowledge-source setup, then selects the connector, establishes authentication, chooses the data to ground answers, and completes the configuration.
Step 1: Select Add knowledge from the agent Knowledge experience Initiate: You start in the Knowledge tab to trigger the addition.
Step 2: Select the real-time connector from the Add knowledge dialog Identify: You pick the specific system/connector from the menu.
Step 3: Select Sign in and create a new connection or reuse an existing connection Authenticate: You log in to ensure permissions to the enterprise data.
Step 4: Select the tables to include as the knowledge source Configure: You isolate the exact tables needed for grounding.
Step 5: Select Add to agent to complete the connection Finalize: You save and bind the source to your agent.
QUESTION 3
You deploy an agent in Microsoft Copilot Studio that triggers a cloud flow to update customer records in Microsoft Dataverse.
You observe the following after deploying the agent:
-
Several runs fail due to a temporary authentication issue.
-
The flow continues to trigger and generate additional failed runs.
You must:
- Stop additional failed executions while troubleshooting.
- Process a failed execution after resolving the authentication issue.
- Validate if the most recent executions succeeded immediately after resolution.
You need to use the appropriate monitoring and management actions to restore normal flow operation and validate successful execution.
Which action should you perform for each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Flow monitoring actions
| Requirement | Action |
|---|---|
| Stop additional failed executions while troubleshooting. | [ 下拉选项框 ] - Delete the flow. - Disable the flow. - Cancel the most recent run. - Modify the trigger condition. |
| Process a failed execution after resolving the authentication issue. | [ 下拉选项框 ] - Restart the flow. - Refresh the flow. - Resubmit the run. - Recreate the trigger. |
| Validate if the most recent executions succeeded immediately after resolution. | [ 下拉选项框 ] - Republish the flow. - Review the Activity history. - Export the flow to a solution. - Inspect the Analytics summary. |
Correct Answers
| Requirement | Correct action |
|---|---|
| 1. Stop additional failed executions while troubleshooting. | Disable the flow. |
| 2. Process a failed execution after resolving the authentication issue. | Resubmit the run. |
| 3. Validate if the most recent executions succeeded immediately after resolution. | Review the Activity history. |
Explanation
- Disable the flow — temporarily stops the flow from triggering new executions while you troubleshoot the authentication issue.
- Resubmit the run — reruns a failed execution after the authentication issue has been resolved.
- Review the Activity history — checks recent flow executions and their statuses to confirm whether the runs succeeded.
Exam tip: Disable → Resubmit → Review Activity history.
Box 1: Disable the flow
The most appropriate action to address this specific issue is to disable the flow. Immediate Stop: Turning off or disabling the flow completely prevents any new instances from triggering. This satisfies your urgent requirement to halt additional failed executions immediately while you troubleshoot.
Safe Troubleshooting: It pauses all activity without deleting or altering the internal logic of your automation, allowing you to safely fix the authentication token or connection issues.
Box 2: Resubmit the run
The best action to address this specific issue is to resubmit the run.
Efficiency: Resubmitting a failed run starts the cloud flow again from the exact same trigger point using the original data.
No Data Loss: It eliminates the need for the user or the Copilot Studio agent to manually recreate the request.
Targeted Fix: Since the root cause was a temporary authentication error that is now resolved, the original payload is valid and will now process successfully.
**Box 3: Review the Activity history **
In Microsoft Copilot Studio, the Activity history (specifically within the integrated Power Automate cloud flow management or the Copilot's topic run history) allows you to see the real-time execution status of individual runs. This is the only option that lets you immediately validate if the most recent executions succeeded right after resolving the authentication error.
QUESTION 4
A company is preparing an agent flow so that it can be invoked by an agent during conversations.
The agent flow must meet the following requirements:
The agent must be able to trigger the flow. The agent flow must be verified.
You need to prepare an agent flow so that it can be used by the agent.
In which order should you perform the actions to prepare the agent flow? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
以下是提取并整理为 Markdown 格式的内容,您可以直接复制:
Select and Place:
Agent flow readiness steps (Options)
- Configure the invocation trigger that allows the agent to call the agent flow.
- Make the agent flow available for agent usage.
- Validate the agent flow behavior with representative test runs.
- Configure the actions that implement the required behavior.
- Create a new agent flow artifact in the environment.
| Answer Area |
|---|
| 1 [ 空白框 ] |
| 2 [ 空白框 ] |
| 3 [ 空白框 ] |
| 4 [ 空白框 ] |
| 5 [ 空白框 ] |
Correct Order
| Step | Action |
|---|---|
| 1 | Create a new agent flow artifact in the environment. |
| 2 | Configure the invocation trigger that allows the agent to call the agent flow. |
| 3 | Configure the actions that implement the required behavior. |
| 4 | Validate the agent flow behavior with representative test runs. |
| 5 | Make the agent flow available for agent usage. |
Sequence to remember
Create → Configure trigger → Add actions → Test and validate → Make available
Explanation: First create the flow, then configure the agent-invocation trigger and required actions. Test the flow to verify its behavior, and finally make it available for the agent to use.
**Step 1: Create a new agent flow artifact in the environment **
You must first initialize the flow container within your Copilot Studio workspace before adding any logic.
**Step 2: Configure the invocation trigger that allows the agent to call the agent flow **
You must set up the specialized trigger first (i.e., "When an agent calls the flow"), because this defines the required input variables that the downstream behavioral actions will rely on.
**Step 3: Configure the actions that implement the required behavior **
With the trigger and input variables established, you build the functional core of the flow (e.g., pulling data, sending approvals) and finalize it with the "Respond to the agent" action.
Step 4: Validate the agent flow behavior with representative test runs
The workflow needs to be tested and verified directly within the flow authoring interface using test data to check for errors before exposing it to the orchestrator.
Step 5: Make the agent flow available for agent usage
Once verified, you publish the flow and add it to your agent as an active tool so the conversational orchestrator can dynamically call it during live interactions.
QUESTION 5
A company uses an agent flow that occasionally requires human input before continuing execution.
Some automated actions must pause until a human provides a decision or additional information. The flow must be configured to:
-
Capture a human response for use in later steps.
-
Continue processing within the same flow run after the response is submitted. Wait for a manual decision before proceeding.
-
You need to configure a human-in-the-loop agent flow.
Which setting should you configure for each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Human-in-the-loop flow configuration
| Requirement | Configuration |
|---|---|
| Capture a human response for use in downstream logic. | [ 下拉选项框 ] - Send a notification to a user. - Use the action's response outputs in subsequent steps. - Enable analytics logging for the response. |
| Continue processing within the same flow run after a response is submitted. | [ 下拉选项框 ] - Republish the flow after the decision is submitted. - Trigger a new flow run when a response is received. - Allow the action to wait for and return a response before continuing. |
| Wait for a manual decision before proceeding. | [ 下拉选项框 ] - Add a human approval action. - Add a manual trigger to the flow. - Send a message that asks for input. |
Correct Answers — Human-in-the-Loop Agent Flow
| Requirement | Correct configuration |
|---|---|
| 1. Capture a human response for use in downstream logic. | Use the action's response outputs in subsequent steps. |
| 2. Continue processing within the same flow run after a response is submitted. | Allow the action to wait for and return a response before continuing. |
| 3. Wait for a manual decision before proceeding. | Add a human approval action. |
Explanation
- Use the action's response outputs in subsequent steps — makes the human's response available to downstream actions and conditions.
- Allow the action to wait for and return a response before continuing — pauses execution until the response is received, then continues the same flow run.
- Add a human approval action — introduces an explicit approval or rejection decision before the flow proceeds.
Exam tip: Capture the response → wait and resume → use an approval action for the manual decision.
Explanation/Reference:
Explanation:
Box 1: Use the action's response outputs in subsequent steps.
The correct configuration is to use the action's response outputs in subsequent steps.
Data Persistence: Pausing for human intervention (often via a Power Automate "Approval" or "Wait for an Action" step) generates dynamic output variables based on the human's decision.
Flow Continuity: To use the decision or additional information later, the flow must explicitly capture these response outputs and map them to subsequent steps or variables within Copilot Studio.
**Box 2: Allow the action to wait for and return a response before continuing **
The valid configuration is to allow the action to wait for and return a response before continuing.
Same Flow Run: This setting explicitly pauses the current execution thread and waits for the human interaction to complete. Once the response is submitted, it resumes processing exactly where it left off within the same run.
Box 3: Add a human approval action.
The correct configuration is to add a human approval action.
Built-in pausing: An approval action natively pauses the workflow execution.
State preservation: The flow holds its current state and waits until the user selects an outcome (e.g., Approve or Reject). Simplicity: It does not require complex logic to save data and restart the process from
QUESTION 6
A company uses an agent that invokes an agent flow to exchange information during a conversation. The company requires that the agent send data into the flow and receive structured results back from the same flow run. To support this business need, the flow must be configured to do the following:
-
Capture the data provided by the agent.
-
Return data results to the agent.
You need to configure the flow so that it can exchange data with the agent.
What should you configure for each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Agent flow input and output configuration
| Requirement | Configuration |
|---|---|
| Capture the data provided by the agent. | [ 下拉选项框 ] - Use an internal variable. - Add a text input parameter. - Store values only in the topic. |
| Return data results to the agent. | [ 下拉选项框 ] - Log values to run history. - Store values only in the flow. - Add a text output parameter. |
Correct Answers
| Requirement | Correct configuration |
|---|---|
| 1. Capture the data provided by the agent. | Add a text input parameter. |
| 2. Return data results to the agent. | Add a text output parameter. |
Explanation
- Text input parameter: Defines an input that the agent passes to the agent flow when invoking it.
- Text output parameter: Defines an output that the flow returns to the agent after execution.
Exam tip: Agent → Flow = Input parameter; Flow → Agent = Output parameter.
Explanation/Reference:
Explanation:
Box 1: Add a text input parameter
To allow a Copilot Studio agent to pass data into a flow and receive structured results back, you must configure a Power Automate flow triggered by the "Run a flow from Copilot" trigger with custom input variables, and concluding with the "Respond to Copilot" action containing structured output parameters.
**Box 2: Add a text output parameter **
To return structured results from an agent flow to your agent in Microsoft Copilot Studio, you should configure the "Respond to the agent" action in your flow with an output parameter.
In Microsoft Copilot Studio, when a topic or bot calls a Power Automate flow, data is sent into the flow via input parameters. To pass data, objects, or structured results back to the copilot during the exact same flow run, you must explicitly define one or more output parameters (such as a text, number, or boolean output) in the "Return value(s) to Power Virtual Agents/Copilot Studio" final step of the flow.
QUESTION 7
You are configuring an agent in Copilot Studio for an organization. The organization uses Microsoft Dataverse, Dynamics 365, and SharePoint Online.
The agent must retrieve information from enterprise systems and internal documents. The agent must meet the following requirements:
-
Must retrieve the current balance of a customer account stored in Dataverse.
-
Must retrieve the real-time shipping status of an order that updates throughout the day in Dynamics 365.
-
Must answer questions based on the content of a static PDF policy document.
-
Must provide a welcome message that does NOT depend on enterprise data.
-
You need to configure the agent to meet the requirements.
How should the agent retrieve the data? To answer, move the appropriate solutions to the correct requirements. You may use each solution once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Solutions (Options)
- Create a manual response in the topic.
- Connect to a Power Platform connector.
- Upload a file to Agents Knowledge Base.
- Configure a generative answer without enterprise data.
| Requirement | Solution |
|---|---|
| Retrieve the current balance of a customer account stored in Dataverse. | [ 空白框 ] |
| Retrieve the real-time shipping status of an order that updates throughout the day in Dynamics 365. | [ 空白框 ] |
| Answer questions based on the content of a static PDF policy document. | [ 空白框 ] |
| Provide a welcome message that does NOT depend on enterprise data. | [ 空白框 ] |
答案
| Requirement | Solution |
|---|---|
| Retrieve the current balance of a customer account stored in Dataverse. | Connect to a Power Platform connector. |
| Retrieve the real-time shipping status of an order that updates throughout the day in Dynamics 365. | Connect to a Power Platform connector. |
| Answer questions based on the content of a static PDF policy document. | Upload a file to Agents Knowledge Base. |
| Provide a welcome message that does NOT depend on enterprise data. | Create a manual response in the topic. |
解析与考点说明
- Retrieve the current balance... (Dataverse) & Retrieve the real-time shipping status... (Dynamics 365)
- 选择:
Connect to a Power Platform connector.(连接到 Power Platform 连接器) -
原因: Dataverse 和 Dynamics 365 都有现成的 Power Platform 预构建连接器。当需要获取实时数据(如当前余额、全天更新的物流状态)时,必须使用连接器实时查询后端系统。不能使用知识库(知识库通常用于静态的非结构化文档)或手动回复。注意:在此类“选择并放置”题型中,选项可以被重复使用。
-
Answer questions based on the content of a static PDF policy document.
- 选择:
Upload a file to Agents Knowledge Base.(将文件上传到智能体知识库) -
原因: 静态的 PDF 文件属于非结构化数据。将其上传到知识库并配合生成式答案(Generative Answers),是 Copilot Studio 处理此类文档并基于其内容回答问题的标准做法。不需要为文档中的每一段内容手动创建主题。
-
Provide a welcome message that does NOT depend on enterprise data.
- 选择:
Create a manual response in the topic.(在主题中创建手动回复) - 原因: 欢迎语是固定的文本,不需要连接任何企业系统去检索数据。直接在主题(通常是系统默认的问候主题)中添加一个“消息(Message)”节点并输入文本即可。
未使用的选项: Configure a generative answer without enterprise data.(配置不含企业数据的生成式答案)在这个场景中不需要用到。生成式答案应当与知识库配合使用以提供有依据的回答,而纯粹的固定欢迎语用不上生成式节点。
**Box 1: Connect to a Power Platform connector **
To enable your Copilot agent to fetch specific, real-time structured data (such as a customer's current balance) directly from Dataverse or Dynamics 365, you should connect to a Power Platform connector (or use native Dataverse plugins/tools).
**Box 2: Connect to a Power Platform connector **
Real-Time Data Access: Dynamics 365 data resides in Microsoft Dataverse. Power Platform connectors (like the Dataverse connector) fetch data live from the source, ensuring the shipping status is perfectly accurate and updated throughout the day.
Box 3: Upload a file to Agents Knowledge Base.
Box 4: Create a manual response in the topic.
QUESTION 8
An agent calls a flow. The agent requires structured output values to be returned.
The agent receives unexpected or empty values.
You need to configure the agent so that data is exchanged correctly between the agent and the flow.
What should you do?
A. Validate parameter definitions.
B. Change the trigger schema.
C. Review the flow run history.
D. Add a Parse JSON inside the flow.
E. Republish the agent.
Correct Answer: A. Validate parameter definitions.
Explanation
The agent and flow must have matching input and output parameter definitions to exchange data correctly.
- A. Validate parameter definitions — Correct. Check that the flow's input and output parameters have the correct names, data types, and mappings so the agent receives the expected values.
- B. Change the trigger schema — Incorrect. The trigger schema is not the first thing to change when the issue may be caused by mismatched input/output definitions.
- C. Review the flow run history — Incorrect. Useful for troubleshooting, but it does not directly configure the data exchange.
- D. Add a Parse JSON inside the flow — Incorrect. Only necessary when JSON parsing is required; it does not fix general parameter mapping issues.
- E. Republish the agent — Incorrect. Republishing alone will not fix incorrect parameter definitions.
Exam tip: Unexpected or empty values between an agent and a flow → first validate the input/output parameter definitions and mappings.
Explanation/Reference: Correct Answer: A
Explanation:
Validating your parameter definitions is the correct first step. Unexpected or empty values typically occur because of a schema mismatch or because unsupported, nested data types are passed directly between the agent and the Power Automate flow.
QUESTION 9
A company is building an agent in Copilot Studio.
The agent must meet the following requirements:
-
Responses must be grounded in approved internal content.
-
The agent must be able to retrieve information from configured data sources in a topic.
You need to configure the agent so that topic responses are grounded from custom data sources.
What should you configure?
A. Enable analytics to review which topics users trigger most often.
B. Add a custom prompt that tells the agent to answer only from company data.
C. Configure knowledge sources in a generative answers node.
D. Add SharePoint as a knowledge source only at the agent level.
E. Increase the response length limit to improve answer completeness.
Correct Answer: C Section: (none)
Explanation/Reference:
Explanation:
To configure a Microsoft Copilot Studio agent so its topic responses are exclusively grounded in your custom data sources, you should leverage the Create generative answers node within a targeted custom topic. This setup ensures the agent strictly retrieves information from your approved internal content.
Correct Answer: C. Configure knowledge sources in a generative answers node.
Explanation
- C — Correct: Configuring knowledge sources in a generative answers node grounds the topic's responses in approved internal content and lets the node retrieve information from those sources.
- A — Incorrect: Analytics monitors usage; it does not ground responses.
- B — Incorrect: Prompt instructions guide behavior but do not configure or connect the actual data sources.
- D — Incorrect: Agent-level SharePoint knowledge alone does not meet the specific requirement to configure data sources within a topic.
- E — Incorrect: Increasing response length does not improve grounding or data retrieval.
Exam tip: When a question specifically says “in a topic” and “custom data sources,” choose Generative answers node → Configure knowledge sources.
QUESTION 10
A company is building an agent in Copilot Studio topic that must retrieve real-time status information from an external REST API using a Send HTTP request node.
To meet the business needs, the topic must meet the following requirements:
The request must include the required authentication header.
The request must call the endpoint using the correct HTTP method.
The response must be configured with an appropriate response data type based on a schema and saved so the topic can reuse the returned values.
You need to configure the Send HTTP request node.
Which configuration should you use for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Configurations (Options)
- Add required headers to the HTTP request.
- Set the method to GET in the HTTP request.
- Select JSON data type and save response to a variable.
- Set the method to POST and send JSON in a request body.
HTTP Request node configuration
| Requirement | Configuration |
|---|---|
| Configure authentication for the request. | [ 空白框 ] |
| Select the correct HTTP method for retrieving data. | [ 空白框 ] |
| Configure structured data handling and storage of data for reuse in the topic. | [ 空白框 ] |
| Requirement | Correct configuration |
|---|---|
| Configure authentication for the request. | Add required headers to the HTTP request. |
| Select the correct HTTP method for retrieving data. | Set the method to GET in the HTTP request. |
| Configure structured data handling and storage of data for reuse in the topic. | Select JSON data type and save response to a variable. |
Explanation:
- Headers: Include the required authentication header, such as an API key or bearer token.
- GET: Retrieves real-time status information from the API.
- JSON + variable: Parses the structured response and saves it in a variable for reuse in subsequent topic steps.
Unused option: Set the method to POST and send JSON in a request body. POST is typically used to submit data, not retrieve status information.
Explanation/Reference:
Explanation:
Box 1: Add required headers to the HTTP request
To configure the Send HTTP request node to include the required authentication header, you should add required headers to the HTTP request.
Authentication details for external REST APIs (such as API keys or Bearer tokens) are almost universally passed inside the metadata of the call, which is managed in the Headers.
Box 2: Set the method to GET in the HTTP request.
To retrieve real-time status information from an external REST API using a Send HTTP request node in Copilot Studio, you should set the method to GET in the HTTP request.
The standard HTTP GET method is specifically designed to fetch or retrieve data from a server without modifying it.
Box 3: Select JSON data type and save response to a variable
When retrieving real-time data, the primary configuration requirement is telling Copilot Studio how to interpret the incoming data (JSON) and storing it in a custom variable so subsequent nodes in your topic can use it.
QUESTION 11
A company is deploying an agent for employees.
The company has the following requirements:
Access must be restricted to the internal employees only. End-user authentication must be enforced.
You need to configure the agent based on the company requirements.
What should you do?
A. Select Authenticate with Microsoft Entra ID for the agent.
B. Enable Require Secure Access in the Web channel security.
C. Publish the agent as a public website experience.
D. Select Authenticate with personal account for the agent.
Correct Answer: A
Explanation/Reference:
Explanation:
To enforce strict internal-only access and require end-user authentication for a Microsoft Copilot Studio agent, you must configure Microsoft Entra ID authentication.
This setup stops external users from chatting with the agent and forces employees to sign in with their corporate accounts before they can access any data.
The implementation requires a mix of tenant-level governance policies and specific agent security configurations.
Reference:
Correct answer: A. Select Authenticate with Microsoft Entra ID for the agent.
Explanation:
- Microsoft Entra ID enforces employee authentication using the company’s organizational identities, restricting access to authorized internal users.
- B. Require Secure Access applies to Web channel security, but it is not the primary setting for enforcing employee authentication.
- C. Public website experience does not meet the internal-only access requirement.
- D. Personal account authentication is intended for personal Microsoft accounts, not organizational employee identities.
Exam tip: For an employee-facing Copilot Studio agent that requires organizational sign-in, choose Microsoft Entra ID authentication.
QUESTION 12
A company is integrating an agent in Copilot Studio into a custom application by using the Microsoft 365 Agents SDK.
The company has the following requirements for the application:
The deployment workflow must follow a dependency driven sequence.
The agent must be published before configuration values are retrieved.
End-to-end validation must occur before production deployment.
You need to plan the deployment workflow to integrate the agent.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Deployment workflow steps (Options)
- Configure and enable the agent's target integration channel.
- Retrieve current agent configuration values.
- Deploy the web app to production.
- Implement the Microsoft 365 Agents SDK in the app using the agent configuration.
- Publish the agent.
- Validate the end-to-end conversation workflow in a test environment.
| Answer Area |
|---|
| 1 [ 空白框 ] |
| 2 [ 空白框 ] |
| 3 [ 空白框 ] |
| 4 [ 空白框 ] |
| 5 [ 空白框 ] |
| 6 [ 空白框 ] |
Step 1: Publish the agent
Based on the second requirement, the agent must be published first before any configuration values can be generated or retrieved.
Step 2: Retrieve the current agent configuration values
Once published, you can extract the necessary configuration properties (such as the Agent ID and Tenant ID) required to connect your applications and infrastructure.
**Step 3: Configure and enable the agent's target integration channel **
Before configuring the SDK code, you must enable the target channel (such as the Custom App or Mobile App channel) within Copilot Studio Channels to permit incoming external connection requests.
Step 4: Implement the Microsoft 365 Agents SDK in the app using the agent configuration
With the channels enabled and configurations in hand, your developers can now write the code to implement the Microsoft 365 Agents SDK into your custom application.
Step 5: Validate the end-to-end conversation workflow in a test environment
Following the third requirement, end-to-end validation must happen prior to production deployment. This step ensures the chat interface, authentication, and SDK pipelines function flawlessly.
Step 6: Deploy the web app to production
Once validation passes successfully, the final step is to push your custom application live to your production environment.
QUESTION 13
An agent in Copilot Studio already exists in a development environment.
You need to prepare the agent so it can be moved to a production environment using the supported solution-based approach.
You need to create an exportable package that contains the existing agent.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point. A. Remove agent topics directly from the solution to prevent export errors.
B. Convert the solution to a managed solution so it can be exported.
C. Export the unmanaged solution that contains the agent.
D. Publish the agent to a channel and export the channel configuration.
E. Create a custom solution and add the existing agent to the solution.
Correct answers: C and E.
- C. Export the unmanaged solution that contains the agent.\ Export the solution from the development environment as a package.
- E. Create a custom solution and add the existing agent to the solution.\ Add the existing Copilot Studio agent to a solution so it can be exported and moved between environments.
Why not the others?
- A: Do not remove topics just to prevent export errors.
- B: You can export an unmanaged solution; converting it to managed is not required for export.
- D: Publishing the agent to a channel and exporting channel configuration is not the solution-based packaging approach.
Exam tip: For solution-based ALM, add the existing agent to a Power Platform solution, then export that solution from development.
???
Correct Answer: BE Section: (none)
Explanation/Reference:
Explanation:
To move a Copilot Studio agent to a production environment using a solution-based approach, you must create a custom unmanaged solution, add your existing agent [E] and its required objects to it, publish all customizations, and export the solution as a managed package [B] [.zip file].
QUESTION 14
A company wants to use content from a non-Microsoft enterprise knowledge base to ground agent responses.
To meet the business needs, the knowledge source must meet the following requirements:
- Support grounding from indexed data.
- Use existing access controls from the source system. Support read-only operations.
- You need to determine the correct behavior to meet the requirements.
Which behavior meets each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
以下是提取并整理为 Markdown 格式的内容,您可以直接复制:
Hot Area:
Copilot connector knowledge behavior
| Requirement | Configuration |
|---|---|
| Support grounding from indexed data. | [ 下拉选项框 ] - Retrieve indexed content - Execute runtime operations. - Retrieve live data at runtime. |
| Use existing access controls from the source system. | [ 下拉选项框 ] - Respect existing permissions. - Bypass permissions for faster retrieval. - Respect existing permissions from agent authors. |
| Support read-only operations. | [ 下拉选项框 ] - Prevent transactional updates. - Allow authenticated write operations. - Enable updates for enhanced performance. |
正确答案如下:
| Requirement | Correct option |
|---|---|
| Support grounding from indexed data. | Retrieve indexed content |
| Use existing access controls from the source system. | Respect existing permissions |
| Support read-only operations. | Prevent transactional updates |
解析:
- Retrieve indexed content:通过 Microsoft 连接器索引的数据检索内容,用于 grounding(回答依据)。
- Respect existing permissions:遵循源系统已有的访问权限,避免用户访问未经授权的数据。
- Prevent transactional updates:知识源用于只读检索,不执行写入或事务性更新操作。
考试记忆: Indexed data → Retrieve;Source permissions → Respect;Read-only → Prevent updates.
Box 1: Retrieve indexed content
To ground a Copilot agent in an external enterprise knowledge base using indexed data, you need to configure Retrieve indexed content.
This process relies on Retrieval-Augmented Generation (RAG). Instead of relying on a pre-trained model or executing live API queries during the conversation, the system references a periodically updated, synchronized index of your knowledge base.
Box 2: Respect existing permissions.
To ensure that the Copilot agent responses respect the existing access controls and source-level permissions of your non-Microsoft enterprise knowledge base, you must configure Respect existing permissions.
Respect existing permissions: This setting ensures the agent operates on a user-delegated permission model. The Copilot agent dynamically trims and limits search results at runtime, meaning the end-user will only receive answers derived from data they explicitly have authorization to view in the external source system.
Incorrect:
Respect existing permissions from agent authors: This incorrect option would ground responses based entirely on the author's access level during the creation process, potentially leaking sensitive data to unauthorized end-users.
Box 3: Prevent transactional updates
To ground Microsoft Copilot agent responses using a non-Microsoft enterprise knowledge base with read-only operations, you must configure Prevent transactional updates.
This configuration ensures that the Copilot agent can only fetch, read, and query data from your enterprise knowledge base. It explicitly blocks any modifications, insertions, or deletions, adhering strictly to your read-only requirement and protecting your source data from accidental alterations.
QUESTION 15
An agent uses a flow that calls an external service which can occasionally fail or time out. When a failure occurs, the agent must meet the following requirements:
Must not terminate silently.
Must send a notification containing the error details.
You need to configure the agent flow so that failures are handled in a controlled and predictable way. Solution: Retry the failing action without handling failure.
Does the solution meet the goal?
A. Yes
B. No
Correct answer: B. No.
Explanation: Retrying the failing action can help recover from temporary errors or timeouts, but retrying alone does not handle the failure or send a notification containing error details.
To meet the requirements, configure explicit failure handling in the flow, such as:
- Catch the failure using the appropriate error-handling path.
- Send a notification containing the error details.
- Optionally, retry transient failures before triggering the error-handling path.
Exam tip: Retry ≠ error handling. Failures must be handled explicitly, and the required notification must be sent.
Correct:
- Configure run after conditions for failure paths.
You should configure the "Run after" conditions in Power Automate (the underlying flow engine) to handle these failures in a controlled and predictable way.
By default, a cloud flow step only runs if the previous step is successful. If your external service fails or times out, all subsequent steps will normally skip, causing the flow to fail silently from the perspective of the Copilot Studio agent.
How to Configure the Flow for Failure Handling To meet your requirements, you need to create a parallel or sequential failure path using the following steps:
-
Add your Notification Action
-
Configure "Run After" Settings Incorrect:
-
Retry the failing action without handling failure.
-
Send a notification with relevant error details.
QUESTION 16
An agent uses a flow that calls an external service which can occasionally fail or time out.
When a failure occurs, the agent must meet the following requirements: Must not terminate silently.
Must send a notification containing the error details.
You need to configure the agent flow so that failures are handled in a controlled and predictable way. Solution: Configure run after conditions for failure paths.
Does the solution meet the goal?
A. Yes
B. No
Correct answer: A. Yes.
Explanation: Configuring Run after conditions in Power Automate allows subsequent actions to run when a previous action fails, times out, or is skipped.
This enables the flow to:
- Detect and handle failures explicitly instead of terminating silently.
- Execute a notification action containing error details.
- Provide predictable failure-handling behavior.
Exam tip: Use Configure run after to create failure-handling paths, such as sending an error notification when an external API call fails.
Correct:
- Configure run after conditions for failure paths.
You should configure the "Run after" conditions in Power Automate (the underlying flow engine) to handle these failures in a controlled and predictable way.
By default, a cloud flow step only runs if the previous step is successful. If your external service fails or times out, all subsequent steps will normally skip, causing the flow to fail silently from the perspective of the Copilot Studio agent.
How to Configure the Flow for Failure Handling To meet your requirements, you need to create a parallel or sequential failure path using the following steps:
-
Add your Notification Action
-
Configure "Run After" Settings Incorrect:
-
Retry the failing action without handling failure.
-
Send a notification with relevant error details.
QUESTION 17
An agent uses a flow that calls an external service which can occasionally fail or time out. When a failure occurs, the agent must meet the following requirements:
Must not terminate silently.
Must send a notification containing the error details.
You need to configure the agent flow so that failures are handled in a controlled and predictable way. Solution: Send a notification with relevant error details.
Does the solution meet the goal?
A. Yes
B. No
Correct answer: B. No.
Explanation: Sending a notification with error details satisfies the notification requirement, but it does not by itself ensure the flow handles failures in a controlled way or prevents silent termination.
You should also configure Run after conditions to detect failures or timeouts and route execution to the notification action.
Exam tip: A notification action alone is insufficient; configure the failure path so the notification is triggered when an error occurs.
Correct answer: B. No.
Explanation: Sending a notification with error details satisfies the notification requirement, but it does not by itself ensure the flow handles failures in a controlled way or prevents silent termination.
You should also configure Run after conditions to detect failures or timeouts and route execution to the notification action.
Exam tip: A notification action alone is insufficient; configure the failure path so the notification is triggered when an error occurs.
Correct Answer: B
Explanation/Reference:
Explanation:
Correct:
- Configure run after conditions for failure paths.
You should configure the "Run after" conditions in Power Automate (the underlying flow engine) to handle these failures in a controlled and predictable way.
By default, a cloud flow step only runs if the previous step is successful. If your external service fails or times out, all subsequent steps will normally skip, causing the flow to fail silently from the perspective of the Copilot Studio agent.
How to Configure the Flow for Failure Handling To meet your requirements, you need to create a parallel or sequential failure path using the following steps:
-
Add your Notification Action
-
Configure "Run After" Settings Incorrect:
-
Retry the failing action without handling failure.
-
Send a notification with relevant error details.
QUESTION 18
A company uses an agent in Copilot Studio that produces structured responses using a reusable instruction template. The responses follow the required tone and format. During a compliance review, the team discovers that the responses were generated using a model that is not on the approved list.
The company requires that the reusable instruction template continues to be used and the model used for prompt-driven responses meets governance requirements.
The solution must ensure that prompt-driven responses are generated using an approved model.
You need to configure the solution that meets the requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Select an approved model from the Microsoft Foundry model catalog in the configuration that is used for prompt-driven response generation.
B. Configure Azure AI Search as the grounding source so the approved model requirement is enforced during response generation.
C. Ensure the reusable instruction template is the one applied to the agent that generates the structured response.
D. Publish the agent so that the model used by prompt-driven responses is updated automatically.
E. Enable citations so generated responses can be traced and comply with governance requirements.
F. Add a line to the instruction template that requires the agent to use only approved models when generating responses.
Correct answers: A and C.
- A. Select an approved model from the Microsoft Foundry model catalog in the configuration used for prompt-driven response generation.
- C. Ensure the reusable instruction template is the one applied to the agent that generates the structured response.
Explanation:
- A directly addresses model governance by explicitly selecting an approved model.
- C preserves the reusable instruction template so the responses continue to follow the required tone and format.
Why not the others?
- B: Azure AI Search provides grounding; it does not enforce model approval.
- D: Publishing does not automatically switch the model to an approved one.
- E: Citations improve traceability but do not control model selection.
- F: Instructions cannot enforce which underlying model is used.
Exam tip: Model governance requires configuring the model itself; prompt templates control response behavior, not model selection.
To fix the compliance issue in Microsoft Copilot Studio, you must select an approved model from the catalog for generation and ensure the correct template is applied. The two necessary configuration steps are:
[F] Select an approved model from the model catalog in the configuration used for prompt-driven response generation.
[C] Ensure the reusable instruction template is the one applied to the agent that generates the structured response.
Configuration Steps Model Selection: Open your agent settings in Microsoft Copilot Studio and choose a compliant, approved foundation model from the catalog for your prompt responses.
Template Assignment: Verify and re-apply the correct reusable instruction template directly to the specific agent responsible for generating the structured output.
QUESTION 19
A company needs to ground an agent in Copilot Studio answers using live enterprise data from a supported system via a Microsoft Power Platform connector. To meet the business needs, the builder must meet the following requirements:
● Authenticate using a valid connection.
● Add the connector as a real-time knowledge source.
● Select the tables for knowledge grounding.
You need to add a Power Platform connector as a real-time knowledge source for the agent.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
REST API (Options)
- Select the tables to include as the knowledge source.
- Add the connector to the agent.
- Select a real-time connector from the Add knowledge dialog.
- Sign in and create a new connection or reuse an existing connection.
- Add a knowledge source.
Answer Area
| Step | Action |
|---|---|
| 1 | [ 空白框 ] |
| 2 | [ 空白框 ] |
| 3 | [ 空白框 ] |
| 4 | [ 空白框 ] |
| 5 | [ 空白框 ] |
Correct order
| Step | Action |
|---|---|
| 1 | Add a knowledge source. |
| 2 | Select a real-time connector from the Add knowledge dialog. |
| 3 | Sign in and create a new connection or reuse an existing connection. |
| 4 | Select the tables to include as the knowledge source. |
| 5 | Add the connector to the agent. |
记忆要点: Add knowledge → Select connector → Authenticate → Select tables → Add to agent.
Explanation/Reference:
Explanation:
Step 1: Add a knowledge source
Initiate: You start in the Knowledge tab to trigger the addition.
Step 2: Select the real-time connector from the Add knowledge dialog
Identify: You pick the specific system/connector from the menu.
Step 3: Sign in and create a new connection or reuse an existing connection
Authenticate: You log in to ensure permissions to the enterprise data.
Step 4: Select the tables to include as the knowledge source
Configure: You isolate the exact tables needed for grounding.
Step 5: Add the connector to the agent
Finalize: You save and bind the source to your agent.
QUESTION 20
An agent uses a flow that calls an external service which can occasionally fail or time out.
When a failure occurs, the agent must meet the following requirements:
● Must not terminate silently.
● Must send a notification containing the error details.
You need to configure the agent flow so that failures are handled in a controlled and predictable way.
Solution: Terminate the flow immediately on error.
Does the solution meet the goal?
A. Yes
B. No
Correct answer: B. No.
Explanation: Terminating the flow immediately on error stops execution, but it does not ensure a notification containing the error details is sent.
Correct approach: Configure Run after conditions to detect failures or timeouts, then execute a notification action that includes the error details.
Exam tip: Terminate on error stops the flow; Run after + notification handles the failure and alerts the appropriate recipient.
Correct Answer: B Section: (none)
Explanation/Reference:
Explanation:
Correct:
- Configure run after conditions for failure paths.
You should configure the "Run after" conditions in Power Automate (the underlying flow engine) to handle these failures in a controlled and predictable way.
By default, a cloud flow step only runs if the previous step is successful. If your external service fails or times out, all subsequent steps will normally skip, causing the flow to fail silently from the perspective of the Copilot Studio agent.
How to Configure the Flow for Failure Handling To meet your requirements, you need to create a parallel or sequential failure path using the following steps:
-
Add your Notification Action
-
Configure "Run After" Settings
Incorrect:
-
Retry the failing action without handling failure.
-
Send a notification with relevant error details.
-
Terminate the flow immediately on error.]
QUESTION 21
A company requires an agent in Copilot Studio to answer questions using content stored in a third-party knowledge base system and reuse that content for knowledge grounding.
The agent must ground answers using indexed enterprise knowledge from a non-Microsoft system.
You need to choose the correct integration approach.
What should you use?
A. Call the third-party API from a topic for each question.
B. Add a Copilot Studio tool as a real-time knowledge source.
C. Add a Copilot Studio tool and call it from a topic.
D. Add a Copilot connector knowledge source for authorized content.
Correct answer: D. Add a Copilot connector knowledge source for authorized content.
Explanation: Copilot connectors can index content from non-Microsoft enterprise systems and make that indexed content available for knowledge grounding. They can also respect the source system’s access permissions.
Why not the others?
- A: Calls the API separately for each question rather than reusing indexed enterprise knowledge.
- B: A Copilot Studio tool is for executing actions, not configuring a real-time knowledge source.
- C: A tool called from a topic performs an operation rather than directly providing indexed knowledge grounding.
Exam tip: Indexed third-party enterprise knowledge → Copilot connector knowledge source.
Correct Answer: D
Adding a Copilot connector is the correct approach to index and ground an agent using authorized nonMicrosoft enterprise knowledge.
Integration and Configuration Indexing data: Copilot connectors (formerly Microsoft Graph connectors) sync and index external data sources into Microsoft Graph.
Adding knowledge: Open your agent in Microsoft Copilot Studio, go to the Overview, Knowledge, or Properties page, and select Add knowledge.
Selecting the source: Choose your configured Copilot connector from the dialog menu and select Add to agent.
QUESTION 22
A company uses a supported Power Platform connector to provide real-time access to enterprise records for knowledge grounding in an agent in Copilot Studio.
To meet the business needs, the knowledge source must provide the following functionality:
● Avoid copying enterprise data into an index.
● Keep source-system access controls enforced.
● Access data by calling the system at runtime.
You need to configure the connector knowledge source.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
以下是提取并整理为 Markdown 格式的内容,附带正确答案及解析:
Select and Place:
Configurations (Options)
- Use real-time connector.
- Use existing permissions.
- Retrieve data without indexing.
- Add Azure AI Search as a knowledge source.
Knowledge source
| Requirement | Configuration |
|---|---|
| Avoid copying enterprise data into an index. | [ 空白框 ] |
| Keep source-system access controls enforced. | [ 空白框 ] |
| Access data by calling the system at runtime. | [ 空白框 ] |
正确答案如下:
| Requirement | Configuration |
|---|---|
| Avoid copying enterprise data into an index. | Retrieve data without indexing. |
| Keep source-system access controls enforced. | Use existing permissions. |
| Access data by calling the system at runtime. | Use real-time connector. |
解析:
- Retrieve data without indexing:避免将企业数据复制到索引中。
- Use existing permissions:遵循源系统现有的访问控制权限。
- Use real-time connector:在运行时调用源系统获取最新数据。
未使用的选项: Add Azure AI Search as a knowledge source。Azure AI Search 通常使用索引来检索数据,不符合避免建立索引的要求。
考试记忆: No index → Retrieve without indexing;Permissions → Use existing permissions;Runtime access → Real-time connector.
QUESTION 23
A tenant administrator configures a Copilot connector that indexes content from an external knowledge system into Microsoft Graph.
A builder is building an agent that must:
● Use the indexed enterprise knowledge during answer generation.
● Avoid duplicating or manually uploading the same content.
● Avoid invoking the system as a transactional tool.
You need to configure the agent so that responses are grounded in the authorized knowledge sources.
What should you do?
A. Add the configured enterprise knowledge source to the agent’s knowledge.
B. Create a new custom connector inside the agent configuration.
C. Add the connector as a tool and invoke it from a topic.
D. Upload documents from the external system directly into the agent’s file knowledge store.
Correct answer: A. Add the configured enterprise knowledge source to the agent’s knowledge.
Explanation:
- The Copilot connector has already indexed the external content into Microsoft Graph.
- Adding the configured enterprise knowledge source lets the agent use that indexed content for grounding during answer generation.
- This avoids duplicating or manually uploading documents and does not treat the connector as a transactional tool.
Why not the others?
- B: Creates a new connector unnecessarily; one is already configured.
- C: A tool invoked from a topic is for executing actions, not directly grounding answers from indexed knowledge.
- D: Manually uploading documents duplicates content already indexed by the connector.
Exam tip: Existing Microsoft Graph indexed content → Add the configured enterprise knowledge source to the agent’s knowledge.
Section: (none)
Explanation/Reference:
Explanation:
You should add the Copilot connector as a knowledge source for the agent.
Grounding via Microsoft Graph: Since the external knowledge system is already being indexed into Microsoft Graph via a Copilot connector, it is already optimized as a read-only semantic knowledge base. In Copilot Studio or the Agent Builder, you simply enable or select this existing Copilot connector from your available knowledge sources.
Avoids Duplication: Adding it as an existing knowledge source directly references the data already indexed in the Graph, preventing you from manually uploading files or duplicating content.
Avoids Transactional Invocation: Creating a new custom connector inside the agent configuration utilizes Power Platform connectors. Power Platform connectors are designed for tool invocation (real-time API calls, writing data, and performing transactional operations), which violates your requirement to avoid a transactional tool setup.
QUESTION 24
A solution containing an agent in Copilot Studio is deployed to multiple environments that require different configuration values.
Configuration values must vary by environment without modifying the solution contents.
Configuration values must meet the following requirements:
● Allow values to be set during import.
● Exclude values from the agent definition.
● Run a dedicated agent instance for each individual environment.
You need to associate each requirement with the configuration approach.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Configurations (Options)
- Use channel-specific settings.
- Define environment variables in the solution.
- Publish distinct agent versions for each environment.
- Hardcode the configuration values in the agent configuration.
ALM-related configurations
| Requirement | Configuration |
|---|---|
| Allow values to be set during import. | [ 空白框 ] |
| Exclude values from the agent definition. | [ 空白框 ] |
| Run a dedicated agent instance for each individual environment. | [ 空白框 ] |
正确答案如下:
| Requirement | Configuration |
|---|---|
| Allow values to be set during import. | Define environment variables in the solution. |
| Exclude values from the agent definition. | Define environment variables in the solution. |
| Run a dedicated agent instance for each individual environment. | Publish distinct agent versions for each environment. |
解析:
- Environment variables:将配置值与 Agent 定义分离,并允许在导入解决方案时为不同环境设置相应的值。
- Distinct agent versions:对应题目要求的每个环境使用独立的 Agent 配置或版本。
未使用的选项:
- Use channel-specific settings:用于配置特定渠道,不是通用的环境级配置管理方式。
- Hardcode the configuration values:将值写死在配置中,无法灵活适应不同环境。
Explanation:
Box 1: Define environment variables in the solution.
The correct ALM-related configuration to use for this requirement is Environment Variables.
You must use Environment Variables (specifically with the Current Value left blank in the development solution) to allow different configuration values across multiple environments without modifying the solution contents. When you export the solution as managed and import it into a target environment, the system will explicitly prompt the administrator to set the values during import.
Box 2: Define environment variables in the solution
Define environment variables in the solution is the correct Application Lifecycle Management (ALM) configuration to use for this requirement.
Separates Data from Code: Environment variables act as parameters that store configuration keys and values separately from your agent's definition.
Preserves Solution Integrity: You can transport the same solution across development, testing, and production environments without modifying any of its internal contents.
Excludes Hardcoded Values: They explicitly remove the need to embed sensitive or environment-specific data directly inside the agent, satisfying your exact requirement.
**Box 3: Define environment variables in the solution **
You should use Environment Variables combined with Connection References within Power Platform / Copilot Studio.
Define parameters centrally: Create environment variables inside your solution to act as placeholders for your configuration values (like URLs, IDs, or API keys).
Keep the solution generic: Your Copilot agent references these variables rather than hardcoded values. Set values per deployment: When you import the managed solution into a new environment (Test, Production, etc.), the deployment pipeline prompts you to provide the specific values for that environment. Isolate agent traffic: Because the variables point to environment-specific backend services, data sources, or IDs, a single solution definition naturally spins up and drives a dedicated, isolated agent instance in each environment.
QUESTION 25
A company is configuring an agent flow that uses multiple action types to perform operations and process data.
The flow must be configured as follows:
● An HTTP action must connect to an external service.
● A data action must reference the correct data to process.
You need to configure the settings for each action type.
Which setting should you configure for each action? To answer, move the appropriate configuration settings to the correct actions. You may use each configuration setting once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Configuration settings (Options)
- Input and mapping
- Table relationships and keys
- Endpoint and authentication
- Connection timeout and retry policy
Action level configuration settings
| Action | Configuration setting |
|---|---|
| HTTP action | [ 空白框 ] |
| Data action | [ 空白框 ] |
Explanation/Reference:
Explanation:
Box 1: Endpoint and authentication
Endpoint and authentication is the correct configuration setting to use.
To connect any HTTP action to an external service, the system fundamentally needs to know where to send the request and how to prove it has permission to access it.
Endpoint (URL): Specifies the exact web address of the external API or service.
Authentication: Credentials (like API keys, OAuth tokens, or Basic Auth) that verify the agent's identity.
Box 2: Input and mapping
The correct configuration setting to use is Input and mapping, because it directly links and passes the correct source data parameters into the data action
正确答案如下:
| Action | Configuration setting |
|---|---|
| HTTP action | Endpoint and authentication |
| Data action | Input and mapping |
解析:
- HTTP action → Endpoint and authentication:配置外部服务的 API 端点和身份验证信息。
- Data action → Input and mapping:指定需要处理的输入数据,并将数据映射到相应的操作参数。
未使用的选项:
- Table relationships and keys:用于特定的数据表关联场景。
- Connection timeout and retry policy:用于配置连接超时和失败重试策略。
QUESTION 26
A team uses environment variables to separate configuration from an agent so that the same solution can be moved between environments.
The team requires the following scenarios to be addressed:
● An administrator updates a sensitive configuration value and needs the change to take effect at runtime without republishing the agent.
● A builder needs to confirm a configuration value but must not be able to modify it from Copilot Studio.
● An administrator updates a non-secret configuration value and needs the updated value to be used by the published agent at runtime.
You need to apply the correct handling behavior for different environment-variable scenarios.
Which behavior should you apply for each scenario? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Multi environment behavior
| Scenario | Behavior |
|---|---|
| Update a sensitive configuration value; the change takes effect at runtime without republishing the agent. | [ 下拉选项框 ] - Republish the agent to apply the update. - Use a secret environment variable type to allow for runtime resolution. - Make the update directly in Copilot Studio. |
| Confirm a configuration value but do not modify it from Copilot Studio. | [ 下拉选项框 ] - Environment variables are stored as topic variables. - Environment variables are read-only in Copilot Studio. - Environment variables can be edited by any builder in Copilot Studio. |
| Update a non-secret configuration value and the updated value needs to be used by the published agent at runtime. | [ 下拉选项框 ] - The value can only be changed by hardcoding it into the agent. - The agent must be republished for the updated value to be effective at runtime. - The agent automatically pulls the updated Current Value from the environment at the start of every session. |
| Scenario | Correct behavior |
|---|---|
| Update a sensitive configuration value; the change takes effect at runtime without republishing the agent. | Use a secret environment variable type to allow for runtime resolution. |
| Confirm a configuration value but do not modify it from Copilot Studio. | Environment variables are read-only in Copilot Studio. |
| Update a non-secret configuration value and the updated value needs to be used by the published agent at runtime. | The agent must be republished for the updated value to be effective at runtime. |
解析:
- 敏感配置值:使用 Secret 类型的环境变量,避免将敏感值直接写入 Agent 定义,并支持运行时解析。
- 只查看、不修改:环境变量在 Copilot Studio 中作为配置引用使用,Builder 不应通过 Agent 编辑界面修改其值。
- 非敏感配置值:更新环境变量后,通常需要重新发布 Agent,才能确保已发布版本使用更新后的值。
考试记忆: Secret → Runtime resolution;View only → Read-only;Non-secret update → Republish.
QUESTION 27
A company has agents in Copilot Studio.
The company needs to prevent the agents from using disallowed connectors and insecure data flows. Administrators must be able to enforce the governance controls to prevent and report violations.
You need to enforce governance controls for agents.
What should you do?
A. Configure Application Insights to collect runtime telemetry.
B. Review security FAQs to understand default protections.
C. Review agent analytics to detect risky connector usage.
D. Configure data policies.
Correct answer: D. Configure data policies.
Explanation: Power Platform data policies (Data Loss Prevention, or DLP policies) allow administrators to govern Copilot Studio agents by restricting disallowed connectors and preventing insecure data flows. They can enforce these controls and help identify policy violations.
Why not the others?
- A. Application Insights: Monitors runtime telemetry; it does not enforce connector restrictions.
- B. Security FAQs: Provide guidance but do not enforce governance.
- C. Agent analytics: Helps monitor agent performance, not enforce connector-level security policies.
Exam tip: Prevent disallowed connectors and enforce data-flow governance → Configure DLP/data policies.
**Correct Answer: D **
Section: (none) Explanation/Reference:
Explanation:
To enforce governance controls, prevent Copilot Studio agents from using disallowed connectors, and restrict insecure data flows, the correct action to take is to Configure data policies.
Real-Time Prevention: Data policies (Data Loss Prevention or DLP) function as a critical build-time and runtime boundary. If an agent relies on a blocked or disallowed connector, Microsoft Copilot Studio immediately blocks execution or publishing and surfaces an error to the maker or user.
Connector Isolation: Admins use the Power Platform admin center to categorize connectors into Business, Non-Business, or Blocked groups. This directly prevents insecure data flows by ensuring data cannot be leaked from business systems (like Microsoft Dataverse) to unapproved external channels or APIs. Reporting & Auditing: Violations of these data policies are logged and can be tracked centrally by administrators to report and monitor compliance across environments.
QUESTION 28
A company is designing an agent flow that includes human in the loop stages during execution. The company requires that the agent flow perform the following actions:
● Must wait for a human decision before it resumes.
● Must collect information and then continue execution.
You need to configure the flow behavior.
Which flow behavior should you configure for each stage? To answer, move the appropriate flow behaviors to the correct stages. You may use each flow behavior once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Flow behaviors (Options)
- Wait for a response and capture inputs.
- Send a request and continue immediately.
- Send a notification for approval and continue.
- Wait for a response and branch based on the decision.
Flow behaviors
| Human in the loop stage | Flow behavior |
|---|---|
| Approval | [ 空白框 ] |
| Information collection | [ 空白框 ] |
正确答案如下:
| Human in the loop stage | Flow behavior |
|---|---|
| Approval | Wait for a response and branch based on the decision. |
| Information collection | Wait for a response and capture inputs. |
解析:
- Approval(审批):等待人工审批结果,并根据批准或拒绝的决定走不同的执行路径。
- Information collection(信息收集):等待人工提交所需信息,捕获输入后继续执行流程。
未使用的选项:
- Send a request and continue immediately.
- Send a notification for approval and continue.
考试记忆: Approval → Wait + branch;Information collection → Wait + capture inputs.
Explanation/Reference:
Explanation:
**Box 1: Wait for response and branch based on the decision **
The best action to take is Wait for response and branch based on the decision because a binary or multipath approval requires distinct logical paths (such as proceeding if approved or canceling/revising if rejected) rather than just logging the text input.
Box 2: Wait for response and capture inputs
The correct answer is Wait for response and capture inputs.
Captures Data: The prompt explicitly states that the agent must "collect information" before moving forward.
Pauses Execution: To collect this information from a human, the workflow must pause ("Wait for response") and hold the collected data ("capture inputs") to use in the subsequent steps.
QUESTION 29
A company is building an agent topic in Copilot Studio. The agent topic uses a generative answers node to respond to user questions based on authorized knowledge sources.
To meet the business needs, the generative answers node must meet the following requirements:
● Use the user’s message in the generative answers node.
● Scope the topic node to query only designated data.
● Restrict responses to approved enterprise data.
You need to configure the generative answers node to meet the requirements.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
以下是提取并整理为 Markdown 格式的内容,附带正确答案及解析:
Select and Place:
Configurations (Options)
- Select Search only selected sources.
- Select Activity.Text in the Input field.
- Enable generative orchestration for the agent.
- Clear Allow the AI to use its own general knowledge.
Generative answers node configuration settings
| Requirement | Configuration |
|---|---|
| Use the user's message in the generative answers node. | [ 空白框 ] |
| Scope the topic node to query only designated data. | [ 空白框 ] |
| Restrict responses to approved enterprise data. | [ 空白框 ] |
正确答案如下:
| Requirement | Configuration |
|---|---|
| Use the user's message in the generative answers node. | Select Activity.Text in the Input field. |
| Scope the topic node to query only designated data. | Select Search only selected sources. |
| Restrict responses to approved enterprise data. | Clear Allow the AI to use its own general knowledge. |
解析:
Activity.Text:将用户当前输入的消息传递给生成式答案节点。- Search only selected sources:将检索范围限制在指定的知识源。
- Clear Allow the AI to use its own general knowledge:禁止模型使用自身的一般知识作答,确保回答基于获准的企业数据。
未使用的选项: Enable generative orchestration for the agent。
考试记忆: User message → Activity.Text;指定数据源 → Search only selected sources;仅限企业数据 → Disable general knowledge.
Explanation/Reference:
Explanation:
Box 1: Select the Activity.
Text in the Input field To use the user's message inside a generative answers node in Microsoft Copilot Studio, map the node's Input field to the System.Activity.Text system variable. This variable captures the exact text of the user's most recent message or trigger phrase.
Box 2: Select Search only selected sources.
To scope a Generative Answers node to query only designated data within a specific topic in Microsoft Copilot Studio, you must use the "Search only selected sources" setting within the node's properties and isolate your knowledge base.
**Box 3: Clear Allow the AI to use its own general knowledge **
You configure this correctly by unchecking/clearing the "Allow the AI to use its own general knowledge" option.
When configuring a Create generative answers node in Microsoft Copilot Studio, the system handles external versus internal knowledge sources based on specific toggles:
Preventing Hallucinations: Leaving "Allow the AI to use its own general knowledge" enabled allows the large language model (LLM) to fall back on its public training data (e.g., ChatGPT data) when it cannot find answers in your custom sources.
Strict Enterprise Grounding: Turning this setting OFF explicitly mandates that the agent uses only the authorized enterprise repositories (like SharePoint sites, uploaded files, or custom databases) attached to your node or agent. If an answer isn't in those specific sources, the node stops and hands the query off to your fallback or error-handling flows instead of guessing.
QUESTION 30
A company is building an agent topic in Copilot Studio.
The topic must meet the following requirements:
● Collect structured user input in a single step.
● Store the submitted values for use later in the conversation.
You need to configure the topic based on the requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Use the latest Adaptive Card schema version in all channels to ensure full feature support.
B. Paste the card JSON into a Message node to collect the user’s response.
C. Add input fields to the card and include an Action.Submit button.
D. Add an Ask with Adaptive Card node to the topic.
E. Use Action.Execute for the button so the card can run commands across channels.
Correct answers: C and D.
- C. Add input fields to the card and include an
Action.Submitbutton
The input fields collect structured user data, and Action.Submit submits the entered values.
- D. Add an Ask with Adaptive Card node to the topic.\
This node displays the Adaptive Card, collects the user's response, and makes the submitted values available for use later in the conversation.
Why not the others?
- A: The latest Adaptive Card schema is not supported across all channels.
- B: A regular Message node is not the appropriate node for collecting Adaptive Card responses.
- E:
Action.Executeis associated with Universal Actions and is not the standard choice for this requirement.
Exam tip: Structured input in one step → Ask with Adaptive Card + input fields and Action.Submit.
Explanation/Reference:
Explanation:
To meet your requirements in Copilot Studio, you must use an Adaptive Card with input fields and an Action.Submit button within a Question node. This allows you to collect structured data in a single step, store the responses as variables, and ensure maximum compatibility by using the standard schema.
Step-by-Step Implementation
-
Add a Question Node: In your topic authoring canvas, add a new node and select Ask a question.
-
Set the Text Prompt: Type a brief message introducing the form (e.g., Please fill out the form below).
-
Change the Input Type: Click on the dropdown menu next to Identify in the Question properties panel. Change it from a standard entity type to Adaptive Card.
-
Paste the JSON Schema: Switch the card editor view to JSON edit mode and paste the schema provided below.
-
Map Your Variables: After saving the JSON, Copilot Studio will automatically detect the input fields based on their "id" attributes. Go to the Save response as section of the node to map these inputs to topic variables for later use.
Integrate and extend agents in Copilot Studio
Background
Blue Yonder Airlines is a global carrier headquartered in Los Angeles, California, operating domestic and international flights. The company serves millions of passengers annually through its website, mobile app, and call centers. To improve customer service efficiency and reduce call center volume, Blue Yonder is deploying an AI agent in Microsoft Copilot Studio.
The agent will handle customer inquiries across multiple channels – web chat, mobile app, and Microsoft Teams (for internal support staff). It will answer questions, retrieve data from enterprise systems, and escalate to human agents when needed.
The project is led by a cross-function team:
- Product manager: Defines requirements and success metrics.
- Lead agent author: Designs topics, intents, and generative behavior.
- Flow designers: Build agent flows and integrations.
- IT/security and compliance: Oversees identity, data protection, and Responsible AI (RAI) compliance.
Current environment Channels
Public website: Embedded web chat Mobile app: In-app chatbot Microsoft Teams: Internal support agent access
Identity and access
- Customers: Anonymous access for general inquiries (e.g., flight status, baggage policy).
- Authentication is required for personal data access (e.g., bookings, loyalty points).
- Internal staff: Authenticate via Microsoft Entra ID.
Data sources
- **Reservation and Ticketing System (internal): **REST API, no prebuilt connector with custom enterprise database.
- Flight Status and Weather APIs (external): REST APIs with API keys.
- **Customer Support Knowledge Base: **SharePoint library with PDFs and policy documents. Loyalty Program Data: Stored in Dynamics 365 and Dataverse.
- Travel Advisory Content: Uses REST API with partner services.
Integration mechanisms
- Custom connectors must be used for internal APIs that lack prebuilt connectors.
- HTTP request nodes may be used for lightweight external APIs.
- Knowledge sources must be used for unstructured content.
- Agent flows must be used to encapsulate reusable logic (e.g., rebooking).
Business requirements
Omnichannel support
Deploy the agent across web, mobile, and Teams with a consistent user experience. The Teams deployment must also support internal staff.
Self-service capabilities
The agent must handle common inquiries such as:
-
Flight status
-
Booking and rebooking
-
Loyalty program questions
-
Travel policies and baggage rules
Human escalation
If the agent cannot resolve an issue or the user requests help, it must:
-
Escalate to a human agent.
-
Transfer the conversation transcript and relevant context.
-
Redact any sensitive personal data before escalation.
Knowledge integration
The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.
Performance metrics
- First-contact resolution: +25%
- Tier-1 call deflection: ≥20%
- Response time: 90% of queries answered within 30 seconds
- Accuracy: ≥95% for known FAQs
- CSAT: ≥85% for AI-handled interactions
Technical requirements
Platform constraints
- No custom code is permitted; only Copilot Studio's built-in tools may be used.
- All backend logic must be implemented using agent flows.
- Markdown must be used for formatting (e.g., bold, bullet points); HTML is not supported.
Authentication
- Sign-in is required for personal data access.
- Anonymous access is allowed for general inquiries.
- User identity must be used for data access; shared or builder credentials must not be used.
Compliance and security
- Power Platform DLP policies must be enforced to block unauthorized data flows.
- Responsible AI content moderation filters must be enabled.
- Prompt modifications must be added to enforce tone, disclaimers, and refusal behavior.
- Disclaimers must be applied consistently across all generative responses. Manual edits to individual topics must be avoided.
Monitoring and maintenance
- All conversations and actions must be logged for auditing.
- Weekly reviews of transcripts and metrics must be conducted.
- Topics, flows, and knowledge sources must be updated as policies or systems evolve.
Issues and constraints
-
API rate limits: External APIs (e.g., flight status) have usage limits. Agent flows must handle retries and caching to avoid exceeding quotas.
-
Knowledge base limits: Copilot Studio has limits on the number and size of indexed documents. Large files must be split or summarized.
-
Generative answer risks: Generative responses must be constrained to avoid policy violations. Prompt modifications and filters must be used to enforce tone, safety, and compliance.
-
User input variability: Users phrase questions in diverse ways. Topics must include varied trigger phrases and fallback handling.
-
Authentication UX: The agent must clearly explain when sign-in is required and handle transitions smoothly across channels.
Problem statement
Blue Yonder Airlines must deploy a secure, scalable, and policy-compliant AI agent using Microsoft Copilot Studio. The agent must deliver accurate, helpful, and safe responses across multiple channels, integrate with enterprise systems, and support both anonymous and authenticated users. It must adhere to strict data protection and Responsible AI standards while improving customer service efficiency and satisfaction.
QUESTION 1
You need to implement tool usage in topics that meet the Blue Yonder design and governance requirements.
Which implementation method should you use for each requirement? To answer, move the appropriate implementation methods to the correct requirements. You may use each implementation method once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Implementation methods (Options)
- Add a tool node.
- Add an Adaptive Card.
- Enable generative orchestration.
- Display a static message instead of using a tool.
- Add a Question node for the user to choose the tool
Tool usage in topics
| Requirement | Implementation method |
|---|---|
| Let the agent decide when to run a tool based on user input. | [ 空白框 ] |
| Run a specific agent flow at a defined step in a topic. | [ 空白框 ] |
| Use a connector action to retrieve data during a conversation. | [ 空白框 ] |
正确答案如下:
| Requirement | Implementation method |
|---|---|
| Let the agent decide when to run a tool based on user input. | Enable generative orchestration. |
| Run a specific agent flow at a defined step in a topic. | Add a tool node. |
| Use a connector action to retrieve data during a conversation. | Add a tool node. |
解析:
- Generative orchestration:让 Agent 根据用户意图和上下文,动态决定何时调用适当的工具。
- Tool node:在 Topic 的指定步骤显式调用 Agent Flow 或 Connector Action,并将结果用于后续对话。
未使用的选项:
- Add an Adaptive Card.
- Display a static message instead of using a tool.
- Add a Question node for the user to choose the tool.
考试记忆: Agent 自主决定调用 → Generative orchestration;Topic 中显式调用 Flow / Connector → Tool node。
???
Explanation/Reference:
Explanation:
Box 1: Add a Question node for the user to choose the tool.
Let the agent decide when to run a tool based on user input.
Box 2: Add an Adaptive card
Run a specific agent flow at a defined step in a topic.
You can run a specific agent flow at a defined step in your topic by using an Ask with Adaptive card node to collect user input, and then triggering the flow using the submitted data.
Box 3: Add a tool node
Use a connector action to retrieve data during a conversation.
QUESTION 2
You need to determine how the agent in Copilot Studio should integrate with two different systems in the Blue Yonder environment, based on their characteristics and the tools available.
Which integration mechanism should you use for each system? To answer, move the appropriate integrations to the correct system or data sources. You may use each integration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Integrations (Options)
- HTTP request
- Custom connector
- Dataverse connector
- Generative AI knowledge
Copilot agent integration
| System or data source | Integration |
|---|---|
| Internal Reservation | [ 空白框 ] |
| Flight Status and Weather Service | [ 空白框 ] |
Box 1: Custom Connector
A Custom Connector is preferable to a HTTP request in this enterprise environment.
Scenario:
Data sources Reservation and Ticketing System (internal): REST API, no prebuilt connector with custom enterprise database.
Custom connectors must be used for internal APIs that lack prebuilt connectors.
Box 2: HTTP request
Flight Status and Weather Service
Scenario:
Flight Status and Weather APIs (external): REST APIs with API keys HTTP request nodes may be used for lightweight external APIs.
正确答案及解析如下:
答案配置
| System or data source | Integration |
|---|---|
| Internal Reservation | Custom connector |
| Flight Status and Weather Service | HTTP request |
| System or data source | Integration | 原因 |
|---|---|---|
| Internal Reservation | Custom connector | 内部预订系统通过 REST API 提供服务,且没有现成的连接器,因此应创建自定义连接器。 |
| Flight Status and Weather Service | HTTP request | 航班状态和天气属于外部 REST API,可通过 HTTP request 直接调用,并在请求中配置 API Key 等认证信息。 |
考试记忆要点:
- Custom connector:内部或第三方 API 没有现成连接器,需要封装成可复用的连接器。
- HTTP request:直接发送 HTTP 请求,适合轻量级 REST API 集成。
- Dataverse connector:访问 Dataverse 中的业务数据,例如 Loyalty 数据。
- Generative AI knowledge:检索和利用文档、知识库等内容生成回答,不适合执行预订系统的事务操作。
QUESTION 3
You need to determine an appropriate implementation related to the use of agent flows that is based on Blue Vender's design and compliance standards.
Which implementation method should you use for each scenario? To answer, move the appropriate implementation methods to the correct scenarios. You may use each implementation method once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Implementation methods (Options)
- Use a tool node.
- Use a generative answers node.
- Use a Go to another topic node.
- Prompt the user for manual input.
- Manually rebuild the logic in the topic.
Agent flow implementations
| Scenario | Implementation method |
|---|---|
| A topic includes a series of steps that replicate logic already defined in another flow. | [ 空白框 ] |
| A topic provides a natural language explanation of a process but does not execute it. | [ 空白框 ] |
| A topic includes a step that triggers a reusable process to update booking details. | [ 空白框 ] |
结合 Blue Yonder Airlines 的设计要求,正确答案如下:
| Scenario | Implementation method |
|---|---|
| A topic includes a series of steps that replicate logic already defined in another flow. | Use a tool node. |
| A topic provides a natural language explanation of a process but does not execute it. | Use a generative answers node. |
| A topic includes a step that triggers a reusable process to update booking details. | Use a tool node. |
解析
- 复用已有 Flow → Use a tool node:调用已有的 agent flow,避免在 topic 中重复实现相同逻辑。
- 只解释流程,不执行操作 → Use a generative answers node:根据知识来源生成自然语言说明。
- 更新预订信息 → Use a tool node:调用可复用的 agent flow 执行预订更新等业务操作。
考试记忆: 复用业务逻辑或执行事务操作,选择 Tool node;只回答问题、解释流程,选择 Generative answers node。
??????
Explanation/Reference:
Explanation:
Scenario:
Compliance and security
Disclaimers must be applied consistently across all generative responses. Manual edits to individual topics must be avoided.
Box 1: Use a Go to another topic node
You can use a redirect node (often referred to as a Redirect to another topic node) in Microsoft Copilot Studio.
Eliminate Duplication: Grouping shared conversation messages or logic nodes into a single, dedicated topic prevents you from building the exact same steps multiple times.
Easier Maintenance: When you need to make a change, a single update to the target topic automatically reflects across all the topics that redirect to it.
Maintain Context: You can easily pass variable values or input/output parameters between the topics so the agent doesn't lose track of the conversation.
Box 2: Use a generative answers node
You can use a generative answers node within your agent topic to summarize and deliver natural language explanations.
Generative answers are designed specifically for knowledge retrieval, FAQs, and providing informational summaries. They can instantly process enterprise data, documents, or company websites and convert them into plain-language guidance without you having to manually write branching logic for every scenario.
Box 3: Use a tool node
In a Microsoft Copilot Studio agent environment, you use a Tool node (specifically an Action node linked to a reusable Agent flow or connector) to trigger an external process like updating booking details.
Integrate and extend agents in Copilot Studio - Testlet 2
Background Fabrikam Inc. is a Canada-based manufacturer with a growing service organization that supports field technicians and internal operations teams. Fabrikam Inc. plans to launch a new internal agent solution named Operations Concierge to reduce time spent searching policy content, retrieving operational metrics, and executing routine transactions.
The agent will be used by three groups:
- Service coordinators who triage incoming service requests
- Field technicians who need guided procedures and parts availability
- Operations managers who monitor KPIs and exceptions
The agent solution must work in real-world operational conditions. Users often ask questions mid-call with a customer or while coordinating parts shipments. The agents require quick, reliable outcomes. As a result, Fabrikam Inc. requires the solution to:
-
Provide grounded answers with traceability when it provides guidance.
-
Retrieve real-time metrics when users ask for operational status.
-
Execute authenticated updates when users initiate a flow (such as creating a parts request).
Fabrikam Inc. also expects the solution to be maintained by multiple makers and developers across the year. The company has experienced duplicated logic and inconsistent behavior across different agents. This project emphasizes reuse, governance, and maintainability across teams.
Current environment
Fabrikam Inc. runs three Microsoft Power Platform environments for agent development and release: Dev, Test, and Prod.
The team plans to build the agent and validate it in Dev and Test, then promote to Prod by using a controlled release process that supports repeatable deployments.
Fabrikam Inc. already has two assets the team wants to reuse:
-
A partially completed Copilot Studio agent named Service Desk Agent, used by IT to create internal tickets and route requests
-
A Microsoft Foundry agent created by a central AI team that performs specialized summarization and classification for long-form text (for example, summarizing call transcripts into an incident narrative)
Fabrikam Inc. also has operational and knowledge data sources:
- A curated policy library (internal SOPs, service warranty rules, escalation criteria, and standard operating procedures)
- A set of indexed documents and procedures in an Azure AI Search service that supports vector search for the policy library
- A Microsoft Fabric workspace that includes a semantic model used by operations leadership for reporting
Business requirements
Fabrikam Inc. requires Operations Concierge to meet the following business requirements:
-
Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
-
Metrics requirement: When users ask about service performance (backlog, SLA risk, parts shortages, dispatch delays), the solution must return up-to-date metrics in a structured format that operations managers can use in weekly reviews.
-
Transaction requirement: The solution must support authenticated updates initiated during conversations, including creating a parts request and updating a service case status.
In addition, Fabrikam Inc. wants to avoid duplicating common assets across agents:
The team must reuse the same set of escalation topics, MCP tool definitions, and a standard safety disclaimer across three different agents.
Only the platform engineering group as allowed to edit shared assets. However, all agent authors must be able to use them.
Technical requirements
The Fabrikam Inc. solution architecture uses a multi-agent approach so that specialist responsibilities are isolated and can evolve independently.
The Operations Concierge (primary agent) must coordinate the following specialist capabilities:
-
Policy and procedure Q&A: Use an enterprise knowledge source that supports indexed retrieval across the curated policy library and service procedures.
-
Operational metrics: Delegate metric queries to a Fabric Data Agent that reads governed business data through the Fabric semantic model.
-
Authenticated updates: Use tools exposed by an existing internal Model Context Protocol (MCP) server that provides transactional operations for the service organization.
-
Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
Fabrikam Inc. will onboard two MCP servers as tools:
- PartsOps MCP server: exposes tools for parts availability checks and parts request creation. The server requires per-user authentication because actions must be traceable to the requesting user.
- WarrantyRules MCP server: exposes a read-only tool for validating warranty coverage. The server uses an API key shared by the agent team.
Fabrikam Inc. has also defined a collaboration requirement with the existing Service Desk Agent:
-
The primary agent must delegate IT-specific requests to the existing Service Desk Agent rather than reimplement ticket creation logic. Finally, Fabrikarn Inc. plans to support a partner integration:
-
For shipment tracking inquiries, Fabrikam Inc. will delegate to a partner-provided agent that is only available through a standardized agent-to-agent endpoint.
Issues and constraints
During early testing, Fabrikam Inc. found three recurring problems:
-
Makers are copying and modifying the same components across agents, resulting in inconsistent disclaimers and duplicated tools.
-
Users can obtain a correct answer, but the response is not consistently traceable to a source when the agent uses knowledge.
-
The primary agent can route some requests, but specialist capabilities are not consistently delegated (for example, some metric questions are answered generatively instead of being routed to the Fabric Data Agent).
You are part of the engineering team responsible for correcting the design and configuration to meet the preceding requirements and constraints.
QUESTION 1
You need to enable Operations Concierge to delegate shipment tracking inquiries according to Fabrikam Inc.'s defined architecture and technical requirements.
Which integration approach should you use?
A. Configure the partner capability as an enterprise knowledge source with indexed retrieval enabled.
B. Configure the partner capability as an MCP tool and invoke it as a transactional operation.
C. Configure the partner capability as an A2A integration and supply its endpoint information.
D. Configure the primary agent to handle shipment tracking through generative responses after publishing.
正确答案:C. Configure the partner capability as an A2A integration and supply its endpoint information.
解析
题目明确指出,合作伙伴提供的 Agent 只能通过标准化的 Agent-to-Agent (A2A) endpoint 访问。因此,应配置 A2A 集成,并提供对应的 endpoint 信息,让 Operations Concierge 能够将运输跟踪请求委派给合作伙伴 Agent。
| 选项 | 判断 | 原因 |
|---|---|---|
| A | ❌ | Enterprise knowledge source 用于检索文档和知识,不适合委派给外部 Agent。 |
| B | ❌ | MCP 适合通过工具调用执行操作,但题目明确要求使用 A2A endpoint。 |
| C | ✅ | A2A integration 支持通过标准化 Agent-to-Agent 接口委派任务。 |
| D | ❌ | 生成式回答不能满足指定的专业 Agent 委派要求。 |
考试记忆:
- A2A → 委派任务给其他 Agent。
- MCP → 调用工具或业务操作。
- Knowledge source → 检索企业知识并提供依据。
- Generative responses → 生成回答,不等于显式委派。
Correct Answer: C
Explanation/Reference:
Explanation:
In Microsoft Copilot Studio, when you need your primary agent to interact with a cross-platform, external agent owned by a partner organization, you use the standardized open Agent2Agent (A2A) protocol.
Scenario:
Fabrikarn Inc. plans to support a partner integration:
For shipment tracking inquiries, Fabrikam Inc. will delegate to a partner-provided agent that is only available through a standardized agent-to-agent endpoint.
QUESTION 2
You need to integrate Fabrikam Inc.'s existing Foundry agent so Operations Concierge can delegate summarization requests.
Which action should you perform for each requirement? To answer, move the appropriate actions to the correct requirements. You may use each action once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Actions (Options)
- Add an external agent of type Microsoft Foundry.
- Publish the Copilot Studio agent to enable external calls.
- Add the Foundry output as an indexed knowledge source.
- Enter the Foundry project endpoint URL to create the connection.
Foundry agent integrations
| Requirement | Action |
|---|---|
| The main agent must be able to call an external Foundry agent. | [ 空白框 ] |
| The external Foundry agent must reference the correct Foundry project and agent. | [ 空白框 ] |
正确答案如下:
| Requirement | Action |
|---|---|
| The main agent must be able to call an external Foundry agent. | Add an external agent of type Microsoft Foundry. |
| The external Foundry agent must reference the correct Foundry project and agent. | Enter the Foundry project endpoint URL to create the connection. |
解析
- 添加外部 Foundry Agent:让 Operations Concierge 能够将摘要生成和文本分类任务委派给现有的 Microsoft Foundry agent。
- 配置 Foundry project endpoint URL:建立与正确 Foundry 项目的连接,以便引用对应的 Agent。
考试记忆: 集成现有 Foundry agent,选择 Add an external agent of type Microsoft Foundry;配置连接目标,提供 Foundry project endpoint URL。
另外两个选项不适用:将输出添加为索引知识源不等于委派 Agent;发布主 Agent 也不是配置 Foundry 连接的核心步骤。
Box 1: Add an external agent of type Microsoft Foundry.
The main agent must be able to call an external Foundry agent.
The best action to take is to add an external agent of type Microsoft Foundry.
Add an external agent of type Microsoft Foundry: In multi-agent ecosystems (such as Microsoft Copilot Studio), connecting to specialized external agent frameworks—like Microsoft Foundry—is natively handled by registering or adding that specific system as an external agent type. This allows the orchestration layer of the main agent to properly discover, authenticate, and call the capabilities of the Foundry agent.
**Box 2: Enter the Foundry project endpoint URL to create the connection, **
The external Foundry agent must reference the correct Foundry project and agent.
QUESTION 3
You need to plan how Fabrikam Inc. will reuse shared components across multiple agents while limiting who can change the shared components.
Which approach should you use for each requirement? To answer, move the appropriate components to the correct requirements. You may use each component once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Select and Place:
Components (Options)
- Restrict component collection to the primary agent.
- Create a component collection and move shared components into it.
- Export the primary agent as a solution and copy assets into other agents.
- Share the component collection with teammates while controlling edit access.
Reusable components
| Requirement | Component |
|---|---|
| Prevent shared assets from being modified by most builders. | [ 空白框 ] |
| Reuse the same set of components across multiple agents without copying. | [ 空白框 ] |
| Limit a shared set of components so it can be used only by its intended primary agent. | [ 空白框 ] |
正确答案如下:
| Requirement | Component |
|---|---|
| Prevent shared assets from being modified by most builders. | Share the component collection with teammates while controlling edit access. |
| Reuse the same set of components across multiple agents without copying. | Create a component collection and move shared components into it. |
| Limit a shared set of components so it can be used only by its intended primary agent. | Restrict component collection to the primary agent. |
解析
- 控制编辑权限:通过共享组件集合并限制编辑权限,让大多数 Builder 可以使用共享资产,但不能随意修改。
- 跨 Agent 复用:创建组件集合,将通用的 escalation topics、MCP tool definitions 和标准安全免责声明放入集合中,供多个 Agent 复用,避免重复复制。
- 限制使用范围:将组件集合限制为仅供指定的主 Agent 使用。
考试记忆: 权限控制选 Share + control edit access;跨 Agent 复用选 Component collection;限定单个 Agent 使用选 Restrict component collection。
Explanation/Reference:
Explanation:
Box 1: Share the component collection with teammates while controlling edit access.
Prevent shared assets from being modified by most builders.
The best action to take is to share the component collection with teammates while controlling edit access.
In Microsoft Copilot Studio, component collections are designed specifically to centralize and reuse assets (like topics, knowledge sources, and actions) across multiple separate agents. When configuring a component collection, administrators or collection owners can utilize built-in sharing permissions to explicitly assign roles to individual makers or groups:
Box 2: Create a component collection and move shared components into it
Reuse the same set of components across multiple agents without copying.
The best action to take is to create a component collection and move shared components into it.
In Microsoft Copilot Studio, Component Collections provide a central container to package and share topics, knowledge bases, actions, and entities across multiple agents without duplicating the assets. Once a collection is created, you can establish governance controls (such as managing it within a managed solution) so that makers on other agents can utilize the shared resources but cannot modify them.
Box 3: Restrict component collection to the primary agent
Limits a shared set of components so it can be used only be its intended primary agent.
The best action to take is to restrict component collection to the primary agent. In Microsoft Copilot Studio, you can restrict a shared set of components so that it can be used only by its intended agent. This feature helps teams modularize large or sensitive agents and prevents unauthorized reuse.
Reference:
QUESTION 4
You need to configure Operations Concierge so that prompt-driven summarization behavior aligns with Fabrikam Inc.'s architectural requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Configure Azure AI Search as the grounding source for summarization prompts. B. Publish the agent to ensure the selected model is enforced for summarization.
C. Select a model from the Foundry model catalog in the custom prompt configuration.
D. Enable citations to control how summarization output is generated.
E. Create a reusable custom prompt template and apply it where summarization responses are generated.
正确答案:C 和 E。
| 选项 | 判断 | 解析 |
|---|---|---|
| A | ❌ | Azure AI Search 适合检索和 grounding 知识,不是控制摘要模型和复用提示词的核心措施。 |
| B | ❌ | 发布 Agent 不是选择或配置摘要模型的主要步骤。 |
| C | ✅ | Select a model from the Foundry model catalog in the custom prompt configuration. 在自定义提示词配置中选择符合架构要求的模型。 |
| D | ❌ | Citations 用于提供来源引用,不能控制摘要生成行为本身。 |
| E | ✅ | Create a reusable custom prompt template and apply it where summarization responses are generated. 创建并复用统一的自定义提示词模板,确保不同 Agent 的摘要行为一致。 |
考试记忆:
- 模型治理 → C:选择 Foundry model catalog 中的模型。
- 提示词复用与行为一致性 → E:创建并应用可复用的 custom prompt template。
Correct Answer: CE
Section: (none) Explanation/Reference:
Explanation:
Scenario: Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
[C] Model Selection: Choosing a specific model from the Foundry catalog ensures that your classification and summarization requests are routed directly to the correct, optimized LLM backend within the Microsoft Foundry ecosystem.
[E] Custom Prompt Templates: Creating and applying a reusable template ensures consistent formatting, tone, and logic across all areas where your agent handles summarization and classification tasks.
QUESTION 5
You need to connect Operations Concierge to Fabrikam Inc.'s Azure AI Search knowledge index while complying with security requirements.
Which configuration should you use for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Configurations (Options)
- Enable citations for grounded answers.
- Enter the name of the Azure AI Search index.
- Select the service principal as the authentication type.
- Provide the Azure AI Search Endpoint URL in the connection details.
Azure AI Search knowledge source connection
| Requirement | Configuration |
|---|---|
| Ensure the Azure AI Search connection complies with the governance requirement for authenticated access. | [ 空白框 ] |
| Ensure policy and procedure Q&A uses the required curated, indexed enterprise knowledge source. | [ 空白框 ] |
| Ensure the connection targets the Azure AI Search service instance that stores the indexed policy documents. | [ 空白框 ] |
正确答案如下:
| Requirement | Configuration |
|---|---|
| Ensure the Azure AI Search connection complies with the governance requirement for authenticated access. | Select the service principal as the authentication type. |
| Ensure policy and procedure Q&A uses the required curated, indexed enterprise knowledge source. | Enter the name of the Azure AI Search index. |
| Ensure the connection targets the Azure AI Search service instance that stores the indexed policy documents. | Provide the Azure AI Search Endpoint URL in the connection details. |
解析
- Service principal:使用服务主体进行身份验证,满足受控的身份认证与访问治理要求。
- Index name:指定存储已索引政策和操作流程文档的索引,让 Agent 检索正确的企业知识。
- Endpoint URL:指定 Azure AI Search 服务实例的地址,确保连接到正确的服务。
未使用的选项: Enable citations for grounded answers。引用有助于满足答案可追溯性要求,但它不是配置 Search 连接身份验证、索引或服务端点的设置。
????
Explanation:
**Box 1: Select the service principal as the authentication type **
Ensure the Azure AI Search connection complies with the governance requirement for authenticated access.
Scenario:
A set of indexed documents and procedures in an Azure AI Search service that supports vector search for the policy library
Box 2: Provide the Azure Search Endpoint URL in the connection details.
Ensure policy and procedure Q&A uses the required curated, indexed enterprise knowledge source.
Box 3: Provide the Azure Search Endpoint URL in the connection details.
Ensure the connection targets the Azure AI Search service instance that stores the indexed policy documents.
The best action to take is to Provide the Azure Search Endpoint URL in the connection details.
When connecting a Copilot agent to an external knowledge source like Azure AI Search, establishing the connection requires identifying the specific service host. Providing the Azure AI Search Endpoint URL ensures that the underlying connection infrastructure explicitly targets and authenticates against your specific Azure AI Search service instance. Once this service-level connection is validated, you are prompted in the next step to select or enter the specific index containing your documents.
QUESTION 6
You need to design a solution that provides Fabrikam Inc. with a multi-agent design approach with existing agents.
Which approach should you use for each requirement? To answer, move the appropriate approaches to the correct requirements. You may use each approach once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Approaches (Options)
- Delegate the request to a tools-first agent.
- Delegate the request to a data-access agent.
- Delegate the request to a knowledge-focused agent.
- Add all logic directly into a single agent and its child agents.
Multi-agent design patterns
| Requirement | Approach |
|---|---|
| Answer policy questions based on technical requirements. | [ 空白框 ] |
| Meet metric requirements. | [ 空白框 ] |
| Meet transaction requirements. | [ 空白框 ] |
正确答案如下:
| Requirement | Approach |
|---|---|
| Answer policy questions based on technical requirements. | Delegate the request to a knowledge-focused agent. |
| Meet metric requirements. | Delegate the request to a data-access agent. |
| Meet transaction requirements. | Delegate the request to a tools-first agent. |
解析
- Policy questions → Knowledge-focused agent:利用 Azure AI Search 等企业知识源检索政策和操作流程,并提供可追溯的依据。
- Operational metrics → Data-access agent:委派给 Fabric Data Agent,通过 Fabric semantic model 获取最新的运营指标。
- Transactions → Tools-first agent:通过 MCP 工具执行经过身份验证的业务操作,例如创建零件申请、更新服务工单状态。
考试记忆:
- 知识问答 → Knowledge-focused
- 数据与指标 → Data-access
- 业务操作与事务 → Tools-first
不要把所有逻辑都放进单一 Agent;这会增加重复实现和维护成本,不符合 Fabrikam 的模块化与复用要求。
Box 1: Delegate the request to a knowledge-focused agent
Scenario: Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
The best action to take is to delegate the request to a knowledge-focused agent. Pure Grounding and Citation Support: In Microsoft Copilot Studio and the Power Platform ecosystem, a knowledge-focused agent is explicitly engineered to retrieve information from designated repositories (such as SharePoint sites, Dataverse tables, or uploaded company policy manuals).
Built-in Transparency: When an agent relies on custom knowledge sources via Retrieval-Augmented Generation (RAG) or generative answers, it inherently provides inline citations and source links. This allows users to immediately verify exactly where the policy guidance or procedural recommendations originated.
Box 2: Delegate the request to a data-access agent.
Scenario: Metrics requirement: When users ask about service performance (backlog, SLA risk, parts shortages, dispatch delays), the solution must return up-to-date metrics in a structured format that operations managers can use in weekly reviews.
The best action to take is to delegate the request to a data-access agent.
Governed and Current Business Data: Tracking active metrics like backlog, SLA risk, and shortages demands direct, real-time query access to structured enterprise data stores (such as Microsoft Fabric or Microsoft Dataverse).
Optimized for Structured Reporting: Data-access specialists focus specifically on retrieving, grouping, and structuring current operational facts into accurate, review-ready formats for management.
Role Distinction: In contrast, a tools-first agent is designed primarily to trigger transactional processes or workflows across external systems (e.g., executing a parts request or updating a service case ticket) rather than retrieving and aggregating high-level analytics.
Box 3: Delegate the request to a tools-first agent.
Scenario: Transaction requirement: The solution must support authenticated updates initiated during conversations, including creating a parts request and updating a service case status.
The best action to take is to delegate the request to a tools-first agent.
Action-Oriented Design: A tools-first agent is specifically optimized to perform tasks, run workflows, and execute transactional actions—such as creating parts requests and updating status fields.
API Integration: It excels at leveraging connectors and Power Automate cloud flows to securely push updates back into your Microsoft Power Platform environment.
Separation of Concerns: Delegating to a specialized tools-first agent keeps your orchestration layer lightweight and prevents a single agent from becoming too complex to maintain.
QUESTION 7
You need to configure generative answers so the agent meets Fabrikam Inc’s business requirements. Which solutions should you use? To answer, move the appropriate solutions to the correct requirements. You may use each solution once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Solutions (Options)
- Upload documents directly into the agent.
- Select a model from the Foundry model catalog.
- Configure Azure AI Search as the grounding data source.
- Instruct the agent to cite sources in knowledge settings.
Azure AI Search and Foundry model solutions
| Requirement | Solution |
|---|---|
| Users must be able to trace each answer back to its source. | [ 空白框 ] |
| The agent must retrieve information from a centralized index. | [ 空白框 ] |
| Responses must be generated by an enterprise-approved foundation model. | [ 空白框 ] |
正确答案如下:
| Requirement | Solution |
|---|---|
| Users must be able to trace each answer back to its source. | Instruct the agent to cite sources in knowledge settings. |
| The agent must retrieve information from a centralized index. | Configure Azure AI Search as the grounding data source. |
| Responses must be generated by an enterprise-approved foundation model. | Select a model from the Foundry model catalog. |
解析
- 可追溯性 → Cite sources:让用户能够查看政策或流程回答的来源,满足 Traceability requirement。
- 集中式知识检索 → Azure AI Search:连接已有的 Azure AI Search 索引,避免重复上传文档,并统一管理企业知识。
- 模型治理 → Foundry model catalog:选择企业批准的基础模型,满足模型治理要求。
未使用的选项: Upload documents directly into the agent。因为 Fabrikam 已有集中式 Azure AI Search 索引,直接上传文档会造成知识重复管理。
Box 1: Instructing the agent to cite sources in the knowledge settings
Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
Instructing the agent to cite sources in the knowledge settings is a correct and effective action to meet this requirement.
In Microsoft Copilot Studio and Power Platform environments, configuring generative answers to include citations ensures transparency and compliance by allowing users to verify policy or procedural data directly from the original source files (such as SharePoint sites or uploaded documents).
Box 2: Configure Azure AI Search as the grounding data source
Configure Azure AI Search as the grounding data source is the best action to meet this requirement.
Centralized Indexing: Azure AI Search is explicitly designed to serve as a centralized external index. It allows you to connect Microsoft Copilot Studio agents directly to existing enterprise vector or keyword indexes rather than siloing information.Enterprise Scaling: Uploading documents directly into individual agents creates fragmented knowledge bases and hits file size limits, which breaks the requirement for a centralized index.Grounding Capabilities: Choosing this option automatically provides the agent with securely mapped data fields for retrieval, serving as the foundational knowledge source to ground the agent's generative answers.
Box 3: Select a model from the Foundry model catalog
To ensure that your Copilot agents generate responses using an enterprise-approved foundation model in Microsoft Power Platform environments, the best action is to select a model from the Foundry model catalog.
Model Selection vs. Grounding Data: The requirement explicitly specifies that the responses must be generated by an enterprise-approved foundation model.
Choosing a specific LLM from the Azure AI Foundry model catalog (or Power Platform's AI Builder models dropdown) directly controls which underlying LLM generates the text.
The alternative choices (such as uploading documents, configuring Azure AI Search, or instructing the agent to cite sources) deal exclusively with grounding data (RAG) and knowledge settings rather than selecting or restricting the actual text-generation foundation model itself.
QUESTION 8
You need to ensure that performance-related questions are handled in accordance with Fabrikam Inc.’s defined architecture and business requirements.
Which capability should Operations Concierge use?
A. A Foundry agent configured for summarization and classification.
B. A data agent integrated into the multi-agent solution.
C. An MCP server tool that executes transactional operations.
D. An Azure AI Search knowledge source configured for enterprise policy retrieval.
正确答案:
B. A data agent integrated into the multi-agent solution.
解析
Fabrikam 的性能相关问题包括 backlog、SLA risk、parts shortages 和 dispatch delays。根据题目架构要求,Operations Concierge 应将这些指标查询委派给 Fabric Data Agent,由它通过 Microsoft Fabric semantic model 访问受治理的业务数据,并返回最新指标。
| 选项 | 判断 | 原因 |
|---|---|---|
| A | ❌ | Foundry agent 用于摘要和分类。 |
| B | ✅ | Data agent 用于查询业务数据和运营指标。 |
| C | ❌ | MCP 工具用于事务操作,例如创建零件申请。 |
| D | ❌ | Azure AI Search 用于检索政策和流程知识,而不是实时运营指标。 |
考试记忆: 实时运营指标 → Data Agent;文档问答 → Knowledge source;业务事务 → MCP tools;摘要和分类 → Foundry agent。
Correct Answer: B Section: (none)
Explanation/Reference:
Explanation:
The agent best described by this scenario is a data agent integrated into the multi-agent solution, serving as the orchestrator or "orchestrator agent" that coordinates the other specialist capabilities.
The requirement explicitly states that this specific agent "must coordinate" multiple specialist capabilities (Q&A, metrics, updates, and specialized processing). In a Microsoft Copilot and Power Platform multiagent architecture, an orchestrator agent acts as the central router. It takes user intent and delegates tasks to specific specialized tools and sub-agents (like the Fabric Data Agent and the Foundry agent).
Scenario:
The Operations Concierge (primary agent) must coordinate the following specialist capabilities:
● Policy and procedure Q&A: Use an enterprise knowledge source that supports indexed retrieval across the curated policy library and service procedures.
● Operational metrics: Delegate metric queries to a Fabric Data Agent that reads governed business data through the Fabric semantic model.
● Authenticated updates: Use tools exposed by an existing internal Model Context Protocol (MCP) server that provides transactional operations for the service organization.
● Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
QUESTION 9
You need to enable collaboration requirements for Operations Concierge.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Enable allow connections from other agents on the Service Desk Agent.
B. Replace the Service Desk Agent with an MCP server.
C. Publish Operations Concierge to enable delegation automatically.
D. Add the Service Desk Agent as an indexed knowledge source.
E. Publish the Service Desk Agent.
正确答案:A 和 E。
| 选项 | 判断 | 解析 |
|---|---|---|
| A | ✅ | 在 Service Desk Agent 上启用 Allow connections from other agents,允许其他 Agent 连接并委派任务。 |
| B | ❌ | 不需要用 MCP server 替换现有 Agent。 |
| C | ❌ | 发布 Operations Concierge 不会自动启用 Agent 委派。 |
| D | ❌ | 将 Agent 作为索引知识源只能用于知识检索,不能实现任务委派。 |
| E | ✅ | Publish the Service Desk Agent,发布被委派的 Agent,使其能够被其他 Agent 调用。 |
考试记忆: 被委派的 Agent 必须允许其他 Agent 连接,并且需要发布才能参与协作。
Correct Answer: AE
Explanation/Reference:
Explanation:
Publish the Service Desk Agent and Enable "allow connections from other agents" on the Service Desk Agent are the correct actions to take.
To enable agent-to-agent delegation (also known as sub-agents or orchestrating multiple agents) in Microsoft Copilot Studio, the secondary agent must be explicitly configured to accept hand-offs and then be made live.
Enable "allow connections from other agents": This setting acts as the security and architecture toggle. It exposes the Service Desk Agent's capabilities, topics, and actions so that a primary orchestrator agent can discover and communicate with it.
Publish the Service Desk Agent: A Copilot Studio agent cannot be called or utilized by another system or agent until its latest configuration and logic are compiled and made live via publishing.
Scenario:
Fabrikam Inc. plans to launch a new internal agent solution named Operations Concierge to reduce time spent searching policy content, retrieving operational metrics, and executing routine transactions.
Fabrikam Inc. already has two assets the team wants to reuse:
*-> A partially completed Copilot Studio agent named Service Desk Agent, used by IT to create internal tickets and route requests
Fabrikam Inc. has also defined a collaboration requirement with the existing Service Desk Agent: The primary agent must delegate IT-specific requests to the existing Service Desk Agent rather than reimplement ticket creation logic.
QUESTION 10
You need to add Fabrikam Inc.’s MCP servers as a tool so the agent can perform the required operations during conversations.
Which setting should you configure for each requirement? To answer, move the appropriate settings to the correct requirements. You may use each setting once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
以下是提取并整理为 Markdown 格式的内容。由于图片中缺少具体的上下文(比如 PartsOps 或 WarrantyRules 的具体技术要求),以下基于 Copilot Studio 中 MCP (Model Context Protocol) 的一般最佳实践和安全标准提供答案及解析:
Select and Place:
Settings (Options)
- Use the same authentication type for the MCP servers.
- Configure a server description about the MCP server role.
- Select API key as the authentication type for the MCP server.
- Select OAuth 2.0 as the authentication type for the MCP server.
MCP onboarding options
| Requirement | Setting |
|---|---|
| Implement PartsOps MCP server actions in alignment with the technical requirements. | [ 空白框 ] |
| Configure the WarrantyRules MCP server in alignment with the technical requirements. | [ 空白框 ] |
| Ensure that the agent has enough server context to decide when to call the MCP server. | [ 空白框 ] |
正确答案如下:
| Requirement | Setting |
|---|---|
| Implement PartsOps MCP server actions in alignment with the technical requirements. | Select OAuth 2.0 as the authentication type for the MCP server. |
| Configure the WarrantyRules MCP server in alignment with the technical requirements. | Select API key as the authentication type for the MCP server. |
| Ensure that the agent has enough server context to decide when to call the MCP server. | Configure a server description about the MCP server role. |
解析
- PartsOps → OAuth 2.0:PartsOps 要求按用户身份进行认证,以便追踪是谁执行了零件查询或创建申请等操作。
- WarrantyRules → API key:WarrantyRules 使用团队共享的 API Key,符合题目给出的认证要求。
- Server description:描述 MCP server 的职责和用途,帮助 Agent 判断何时调用相应工具。
未使用的选项: Use the same authentication type for the MCP servers。两个 MCP server 的认证要求不同,因此不应强制使用相同的认证类型。
Box 1: Select OAuth 2.0 as the authentication type for the MCP server
Scenario:
PartsOps MCP server: exposes tools for parts availability checks and parts request creation. The server requires per-user authentication because actions must be traceable to the requesting user.
Select OAuth 2.0 as the authentication type for the MCP server is the best step.
Per-user authentication requirement: The prompt specifies that the server requires per-user authentication so that actions remain traceable to the specific requesting user.
OAuth 2.0 capabilities: OAuth 2.0 delegates user authentication to the identity provider and passes individual user tokens, satisfying the exact tracking requirement.
Box 2: Select API key as the authentication type for the MCP server
Scenario:
WarrantyRules MCP server: exposes a read-only tool for validating warranty coverage. The server uses an API key shared by the agent team.
The scenario states that the Model Context Protocol (MCP) server already requires an API key shared by the agent team. When configuring the onboarding options in the Microsoft Copilot Studio MCP onboarding wizard, you must align the authentication type with the credentials your backend server expects. Selecting "API key" ensures that Copilot properly formats and relays the shared team key during execution.
Box 3: Configure a server description about the MCP server role.
To ensure a specific Copilot agent knows exactly when to call your Model Context Protocol (MCP) server, you should configure a server description that defines the server's specialized function, its data limitations (read-only), and the specific user intents that trigger its use.
3 Integrate and extend agents in Copilot Studio Question Set 3
QUESTION 1
A company is building a Copilot Studio solution that must answer policy questions, retrieve operational metrics from structured data, and execute authenticated updates in backend systems. The company decides to use multiple specialized agents rather than a single monolithic agent. Custom agents for each action already exist.
To meet the business needs, the solution must meet the following requirements:
The solution must retrieve up to date metrics from structured data.
The solution must answer policy questions using curated knowledge. The solution must execute authenticated updates during conversations.
You need to select the appropriate agent design for each requirement.
Which approach should you use for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Configurations (Options)
- Delegate the request to a single agent.
- Delegate the request to a tools-first agent.
- Delegate the request to a data-access agent.
- Delegate the request to a knowledge-focused agent.
Multi-agent design patterns
| Requirement | Configuration |
|---|---|
| The solution must retrieve up to date metrics from structured data. | [ 空白框 ] |
| The solution must answer policy questions using curated data sources. | [ 空白框 ] |
| The solution must execute authenticated updates during conversations. | [ 空白框 ] |
正确答案如下:
| Requirement | Configuration |
|---|---|
| Retrieve up-to-date metrics from structured data. | Delegate the request to a data-access agent. |
| Answer policy questions using curated data sources. | Delegate the request to a knowledge-focused agent. |
| Execute authenticated updates during conversations. | Delegate the request to a tools-first agent. |
解析
- Data-access agent:访问结构化数据,获取最新运营指标。
- Knowledge-focused agent:检索经过整理的政策和知识来源,提供有依据的回答。
- Tools-first agent:调用已认证的工具执行后端操作,例如创建零件申请、更新服务工单状态。
考试记忆: Metrics → Data-access;Policy Q&A → Knowledge-focused;Authenticated updates → Tools-first。
Explanation/Reference:
Explanation:
Box 1: Delegate the request to a tools-first agent
To retrieve up-to-date operational metrics from structured data in a multi-agent Copilot Studio architecture, you should configure the parent system to delegate the request to a tools-first agent.
Specialized Actions: In Copilot Studio, custom connectors and APIs that query or update structured data are configured as tools.
Dynamic Execution: A tools-first agent is specifically designed to evaluate the user's intent, select the correct authenticated API/connector (the tool), and pass parameters to retrieve real-time data.
Delegation Overlap: Knowledge-focused agents are optimized for RAG (retrieval-augmented generation) over static, unstructured files/documents rather than dynamic operational metrics.
**Box 2: Delegate the request to a knowledge-focused agent. **
To meet the requirement of answering policy questions using curated knowledge within a multi-agent Copilot Studio solution, you should delegate the request to a knowledge-focused agent.
Box 3: Delegate the request to a tools-first agent
To execute authenticated updates and actions in backend systems, you should delegate the request to a tools-first agent in Copilot Studio. While other specialized agents handle document synthesis or data analysis, a tools-first agent is configured to process API-based actions and plugins with proper end-user authentication.
In multi-agent architecture within Microsoft Copilot Studio, agents are typically categorized by their core operational focus. A tools-first agent is explicitly designed to prioritize taking specific actions—such as executing backend APIs, running plugins, or triggering workflows—making it the designated agent type for processing transactional and authenticated system updates.
QUESTION 2
A company has an approved custom connector that uses a REST API for an internal system.
An agent in Copilot Studio must call this connector during conversations to retrieve or update data.
To meet the business needs, the solution must meet the following requirements:
Make the connector actions available for the agent to invoke.
Ensure authentication is handled at the service level, not per user.
Pass conversation context into the connector when it is called.
Surface the returned data of the connector to the user in the conversation.
You need to configure the agent and the connector action to meet the requirements.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Configurations (Options)
- Map topic variables to the tool inputs.
- Parse the JSON response and assign it to a topic variable.
- Add the connector as a tool in the agent.
- Create or reuse a connection for the connector.
REST API
| Requirement | Configuration |
|---|---|
| Make connector actions available for agent to invoke. | [ 空白框 ] |
| Handle authentication at service level, not per user. | [ 空白框 ] |
| Pass conversation context into connector when called. | [ 空白框 ] |
| Surface connector's returned data to the user. | [ 空白框 ] |
正确答案如下:
| Requirement | Configuration |
|---|---|
| Make connector actions available for the agent to invoke. | Add the connector as a tool in the agent. |
| Handle authentication at service level, not per user. | Create or reuse a connection for the connector. |
| Pass conversation context into the connector when called. | Map topic variables to the tool inputs. |
| Surface the connector's returned data to the user. | Parse the JSON response and assign it to a topic variable. |
解析
- Add the connector as a tool:将自定义连接器添加到 Agent,使其能够调用 REST API 操作。
- Create or reuse a connection:建立连接并配置连接使用的身份验证方式。要满足服务级认证要求,应使用配置好的共享连接或连接凭据,而不是要求每位用户单独登录。
- Map topic variables to tool inputs:把对话中收集的参数或上下文传递给连接器。
- Parse JSON response:将 API 返回的 JSON 数据保存到 topic 变量,再通过消息或后续节点展示给用户。
考试记忆: 注册工具 → Add as tool;连接与认证 → Create/reuse connection;传入参数 → Map variables;返回结果 → Parse JSON into variable。
Explanation/Reference:
Explanation:
Box 1: Add the connector as a tool in the agent
To make the custom connector actions available for the agent to invoke, the correct configuration action is to add the connector as a tool in the agent.
Box 2: Create or reuse a connection for the connector
The correct configuration action to ensure authentication is handled at the service level (and not per user) is to create or reuse a connection for the connector.
Service-Level Auth: In Copilot Studio, when you use a custom connector, you must establish a connection that determines how credentials are supplied.
Connection Creation: By creating a connection using a fixed service account or API key—and configuring it to be shared or run under that specific context—the agent authenticates at the system/service level.
Box 3: Map topic variables to the tool inputs
The correct configuration action is to map topic variables to the tool inputs.
When you add a custom connector to an agent in Microsoft Copilot Studio, it functions as a "tool" or an action. To pass specific data—such as conversation context or user details—from the ongoing chat into that connector, you must map the active Copilot Studio topic variables to the input parameters defined by the connector's REST API.
**Box 4: Parse the JSON response and assign it to a topic variable **
To surface the returned data of the connector to the user in Copilot Studio, the correct configuration action is to parse the JSON response and assign it to a topic variable.
Data Extraction: Custom connectors return raw JSON data from REST APIs.
Variable Storage: Copilot Studio cannot display raw JSON directly to users in a clean way.
QUESTION 3
A company has an Azure AI Search vector index that contains enterprise content and wants to use it as a knowledge source for an agent in Copilot Studio.
To meet business needs, the knowledge source must meet the following requirements:
-
The agent must connect to the Azure AI Search service.
-
The agent must use a supported authentication method for the connection.
-
The agent must ensure answers are grounded using the specified Azure AI Search index.
You need to connect to Azure AI Search as a knowledge source for the agent.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Azure AI Search knowledge source connection steps (Options)
- Configure the authentication method and provide the required connection details.
- Associate the configured knowledge source with the agent.
- Create a new Azure AI Search connection.
- Initiate the process to add a knowledge source to the agent.
- Specify the Azure AI Search index to use for grounding.
Answer Area
| Step | Action |
|---|---|
| 1 | [ 空白框 ] |
| 2 | [ 空白框 ] |
| 3 | [ 空白框 ] |
| 4 | [ 空白框 ] |
| 5 | [ 空白框 ] |
正确顺序如下:
| Step | Action |
|---|---|
| 1 | Initiate the process to add a knowledge source to the agent. |
| 2 | Create a new Azure AI Search connection. |
| 3 | Configure the authentication method and provide the required connection details. |
| 4 | Specify the Azure AI Search index to use for grounding. |
| 5 | Associate the configured knowledge source with the agent. |
解析
- Add a knowledge source:从 Agent 的知识配置入口启动添加流程。
- Create connection:创建 Azure AI Search 连接。
- Configure authentication and connection details:设置支持的身份验证方式,并提供 Search 服务的 Endpoint 等信息。
- Specify index:选择包含企业内容的指定索引,确保回答基于正确的数据。
- Associate with agent:完成配置并将知识源关联到 Agent。
考试记忆: 启动添加 → 创建连接 → 配置认证 → 选择索引 → 关联 Agent。
Explanation/Reference:
Explanation:
Step 1: Initiate the process to add a knowledge source to the agent
You start inside Copilot Studio by navigating to your agent's settings and choosing to add a new knowledge source.
Step 2: Create a new Azure AI Search connection
From the available knowledge source options, you select Azure AI Search, which prompts the creation of a new connection.
Step 3: Configure the authentication method and provide the required connection details
You input the necessary credentials (such as your Azure AI Search endpoint and API key or OAuth details) to authenticate the connection securely.
Step 4: Specify the Azure AI Search index to use for grounding
Once connected, you select the specific vector index that contains your enterprise content so the model knows where to look.
**Step 5: Associate the configured knowledge source with the agent **
Finally, you save and link this configured search source to the agent, enabling it to ground its responses using your enterprise data.
QUESTION 4
A company uses a primary agent in Copilot Studio to handle user intake.
For some requests, the company wants the primary agent to delegate work to another Copilot Studio agent that already exists.
To meet the business needs, the solution must allow agents to perform the following on the connected agent:
Must allow calls from other agents.
Must allow agents to use the connected agent for collaboration. Must allow agents to invoke the connected agent in conversations.
You need to integrate the existing Copilot Studio agent with the connected agent.
Which setting should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
Select and Place:
Configuration (Options)
- Publish the connected agent.
- Add the connected agent.
- Configure connections to the connected agent.
- Add the connected agent as an indexed knowledge source.
Copilot Studio agent-to-agent integrations
| Requirement | Configuration |
|---|---|
| Must allow calls from other agents | [ 空白框 ] |
| Must allow agents to use the connected agent for collaboration. | [ 空白框 ] |
| Must allow agents to invoke the connected agent in conversations. | [ 空白框 ] |
根据 Copilot Studio 中智能体到智能体(Agent-to-Agent)集成的官方机制,以下是该题的正确配置与解析:
正确答案
| Requirement | Configuration |
|---|---|
| Must allow calls from other agents | Publish the connected agent. |
| Must allow agents to use the connected agent for collaboration. | Add the connected agent. |
| Must allow agents to invoke the connected agent in conversations. | Add the connected agent. |
详细解析
1. Must allow calls from other agents(必须允许来自其他智能体的调用)
- 正确选项:
Publish the connected agent. - 解析: 在 Copilot Studio 中,一个智能体必须处于已发布(Published) 状态,才能被其他智能体发现并调用。Microsoft Learn 文档指出,连接另一个 Copilot Studio 智能体的前提条件之一就是“另一个智能体必须已发布”。此外,主智能体只能在该智能体发布后,才能使用其最新版本。
2. Must allow agents to use the connected agent for collaboration.(必须允许智能体使用连接智能体进行协作。)
* 正确选项: Add the connected agent.
* 解析: 要让主智能体(父智能体)与另一个独立的智能体进行协作,必须在主智能体的配置中添加(Add) 该连接智能体。官方步骤为:在主智能体的“智能体”页面选择“添加智能体”,并在“连接外部智能体”下选择 Copilot Studio,然后从列表中选择目标智能体。添加后,主智能体的编排运行时就能将请求路由到该连接智能体进行协作。
3. Must allow agents to invoke the connected agent in conversations.(必须允许智能体在对话中调用连接智能体。)
* 正确选项: Add the connected agent.
* 解析: 与上一题逻辑一致。只有在主智能体中添加了连接智能体,主智能体的编排器(Orchestrator)才能在对话过程中识别用户请求与哪个专业智能体的领域匹配,并调用(invoke) 它来处理任务。添加步骤包括选择智能体并调整其描述,以确保 Copilot Studio 能理解何时应该调用它。
为什么不选其他选项
- Configure connections to the connected agent:虽然连接认证是必要配置,但它不是实现“允许调用”或“添加以进行协作/调用”的核心操作。核心操作是发布和添加。
- Add the connected agent as an indexed knowledge source:连接智能体(Connected Agent)是用于委托任务和交接推理的,而不是作为静态知识源被索引。将其添加为知识源是一种误用。
Explanation/Reference:
Explanation:
Box 1: Publish the connected agent.
To allow a primary Copilot Studio agent to delegate work to an existing secondary agent, the secondary agent must be published. For an agent to accept calls and be selectable by other agents, you must enable its capability to be used as a connected agent.
Box 2: Add the connected agent.
Add the connected agent: This is the configuration action required within the primary agent. By navigating to your primary agent's build/agents panel and choosing to add a connected agent, you establish the relationship that allows the primary agent's orchestration runtime to dynamically invoke and delegate conversation tasks to it.
Box 3: Add the connected agent.
In Microsoft Copilot Studio's multi-agent architecture, a primary orchestrator agent routes tasks to independent sub-agents using the Connected agents capability. To make an existing agent available to your primary agent so the orchestrator can autonomously invoke it during conversations, you must go to the primary agent's build tab, navigate to the components panel, and choose to add a connected agent. Incorrect:
Configure connections to the connected agent: While connections exist in Copilot Studio, they are used to securely authenticate external systems, APIs, or tools (such as SharePoint or Dataverse), rather than connecting another standalone conversational agent.
Add the connected agent as an indexed knowledge source: Knowledge sources are used for uploading files, documents, websites, or databases to ground the AI's general knowledge. They are not used for routing workflows to independent agents.
Reference:
QUESTION 5
A company uses multiple Copilot Studio agents that perform specialized tasks.
The company needs to enable one agent to directly delegate and invoke another agent within Copilot Studio by using a standard Copilot Studio interface.
You need to configure collaboration among agents by using Copilot Studio.
What should you do?
A. Add the target agent as a Microsoft Fabric Data Agent.
B. Provide A2A endpoint information for the target agent.
C. Upload documentation about the target agent for referencing.
D. Add the target agent as an indexed knowledge source.
正确答案:B. Provide A2A endpoint information for the target agent.
解析
题目要求一个 Agent 通过标准化接口直接委派并调用另一个 Agent,因此应使用 Agent-to-Agent (A2A) integration,提供目标 Agent 的 endpoint 信息。
| 选项 | 判断 | 原因 |
|---|---|---|
| A | ❌ | Fabric Data Agent 用于访问结构化业务数据。 |
| B | ✅ | 提供 A2A endpoint 信息,实现跨 Agent 的委派与通信。 |
| C | ❌ | 上传文档只能帮助 Agent 了解目标 Agent,不能直接调用它。 |
| D | ❌ | 索引知识源用于知识检索,而不是执行 Agent-to-Agent 委派。 |
考试记忆:
- Copilot Studio 内通过标准界面连接现有 Copilot Studio Agent → 添加目标 Agent 并配置连接。
- 通过标准化的跨 Agent endpoint 委派 → A2A。
Correct Answer: B Section: (none)
Explanation/Reference:
Explanation:
The correct step to take is to provide A2A (Agent-to-Agent) endpoint information for the target agent.
Standard Multi-Agent Protocol: The Agent-to-Agent (A2A) protocol is the open, standard framework specifically designed to allow independent agents to directly communicate, discover capabilities via agent cards, and delegate workflows across standard interfaces. Providing the A2A endpoint information allows the orchestrating agent to securely hand off specialized tasks to the target agent.
Incorrect:
[Not A] Adding the target agent as a Microsoft Fabric Data Agent is a separate, specialized pattern reserved strictly for reasoning over heavy data science pipelines and querying enterprise data lakes (like Lakehouses or Semantic Models). It is not used for standard cross-framework agent collaboration or general delegation within the native Copilot Studio interface.
QUESTION 6
A company uses an agent in Copilot Studio that produces structured responses using a reusable instruction template. The responses follow the required tone and format. During a compliance review, the team discovers that the responses were generated using a model that is not on the approved list.
The company requires that the reusable instruction template continues to be used and the model used for prompt-driven responses meets governance requirements.
The solution must ensure that prompt-driven responses are generated using an approved model.
You need to configure the solution that meets the requirements.
Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
A. Publish the agent so that the model used by prompt-driven responses is updated automatically.
B. Enable citations so generated responses can be traced and comply with governance requirements.
C. Add a line to the instruction template that requires the agent to use only approved models when generating responses.
D. Configure Azure AI Search as the grounding source so the approved model requirement is enforced during response generation.
E. Ensure the reusable instruction template is the one applied to the agent that generates the structured response.
正确答案:A、E
解析
题目要求:必须继续使用可复用的指令模板,并且确保生成响应时使用的是合规批准的模型。
- E. Ensure the reusable instruction template is the one applied to the agent that generates the structured response.(确保将可复用的指令模板应用于生成结构化响应的智能体。)
-
正确。 题目第一句就强调“The company requires that the reusable instruction template continues to be used”,并且要维持原有的语调和格式。因此必须验证正确的模板已应用到目标智能体上。
-
A. Publish the agent so that the model used by prompt-driven responses is updated automatically.(发布智能体,以便提示词驱动响应所使用的模型自动更新。)
- 正确。 在 Copilot Studio 中,如果修改了智能体所使用的底层模型(例如在生成式 AI 设置或 Prompt Builder 中选择批准的新模型),这些更改在测试画布中虽然可见,但必须重新发布(Publish)智能体,新的模型配置才会被编译到运行环境中并生效。
- (注:由于您提供的选项中没有直接出现“从模型目录选择已批准模型”这个最直接的选项,A 是使平台级配置变更生效的必要动作。)
为什么不选其他选项:
- C. Add a line to the instruction template that requires the agent to use only approved models when generating responses.(在指令模板中添加一行,要求智能体只使用批准的模型。)
- 错误。 这是一个常见的技术误区。指令模板(Prompt)只能约束智能体的语言输出逻辑、语气和格式,它无法改变或约束平台底层所使用的物理大语言模型(LLM)类型。模型的选择是在平台的配置界面完成的,而不是靠提示词控制的。
- B. Enable citations...:引用功能用于显示答案来源,与确保底层模型是否合规无关。
- D. Configure Azure AI Search...:Azure AI Search 是知识检索服务(RAG),它不控制生成响应的大语言模型。
Explanation/Reference:
Explanation:
[A] You must publish the agent to ensure that the updated model settings take effect and that all promptdriven responses automatically
transition to using the approved model across your connected channels.
Changing the generative AI model in Microsoft Copilot Studio modifies the configuration in the authoring canvas, but it does not instantly apply to live users. Publishing the agent pushes these metadata changes to production, ensuring data compliance and governance standards are met.
[E] To ensure that prompt-driven responses are generated using an approved model while continuing to use your reusable instruction template, you must ensure the reusable instruction template is the one applied to the agent that generates the structured response (specifically by selecting the compliant model within the Copilot Studio agent's settings where the template is run).
Incorrect:
[Not C] Large Language Models (LLMs) cannot see or change the infrastructure they are running on.
The reality: Adding a text instruction like "Use GPT-4" into a prompt template does not physically change the underlying model being utilized by Copilot Studio. If the agent is configured to use an unapproved model, it will continue to use that model to read your new instruction.
[Not D] Grounding sources provide factual data, not model governance.
Azure AI Search acts as a Retrieval-Augmented Generation (RAG) data source to prevent hallucinations and provide internal documents to the agent. It does not dictate or enforce which underlying LLM orchestrates and generates the final response text.
QUESTION 7
A team has an agent in Copilot Studio that handles user intake. For some requests, the team wants the agent to delegate work to a Microsoft Foundry agent that performs specialized processing. The Foundry agent already exists.
To meet the business needs, the solution must meet the following requirements:
-
The primary agent must be able to call the Foundry agent.
-
The external agent connection must reference the correct Foundry project and agent.
You need to integrate the primary agent with the Foundry agent.
Which two actions should you take? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Add an external agent.
B. Configure the Copilot Studio endpoint URL.
C. Configure the project endpoint URL.
D. Add an indexed knowledge source.
E. Publish the Copilot Studio agent.
正确答案:A 和 C。
| 选项 | 判断 | 解析 |
|---|---|---|
| A. Add an external agent. | ✅ | 将现有 Microsoft Foundry agent 添加为外部 Agent,使主 Agent 能够委派专业处理任务。 |
| B. Configure the Copilot Studio endpoint URL. | ❌ | 这是针对 Copilot Studio 端点的配置,不是连接 Foundry 项目的关键设置。 |
| C. Configure the project endpoint URL. | ✅ | 配置 Microsoft Foundry project endpoint,确保连接到正确的 Foundry 项目和 Agent。 |
| D. Add an indexed knowledge source. | ❌ | 知识源用于检索内容,不用于调用外部 Agent。 |
| E. Publish the Copilot Studio agent. | ❌ | 发布操作本身不会建立 Foundry Agent 连接。 |
考试记忆: 集成现有 Foundry Agent = Add an external agent + Configure the project endpoint URL。
Explanation/Reference:
Explanation:
[A] To perform an agent-to-agent integration where a primary Copilot Studio agent delegates tasks to a specialized Microsoft Foundry agent, you must navigate to the primary agent's configuration pages and select the option to add an agent under the Connect to an external agent feature.
[C] Configuring the project endpoint URL is a nested requirement within the process of adding an external agent. When you create a new connection during the "Add an external agent" workflow, Copilot Studio will prompt you to enter the Foundry project endpoint URL to link to the correct project, followed by entering the specific Agent ID to link the correct agent.
QUESTION 8
A company must enable an agent in Copilot Studio to execute operations exposed by an external MCP server.
The MCP server publishes callable tools and requires authentication.
The agent must be able to invoke MCP tools during conversations.
You need to configure MCP tools so the agent can execute MCP tool calls.
What should you do?
A. Upload documentation about the MCP server so the agent can answer questions about it.
B. Enable generative answers so the model can automatically invoke MCP tools.
C. Publish the agent and rely on default settings for tool availability.
D. Add the MCP server to the agent's tool configuration.
正确答案:D. Add the MCP server to the agent's tool configuration.
解析
将外部 MCP server 添加到 Agent 的 Tools(工具)配置中,并配置所需的身份验证,Agent 才能在对话过程中调用 MCP server 提供的工具。
| 选项 | 判断 | 原因 |
|---|---|---|
| A | ❌ | 上传文档只能帮助 Agent 了解 MCP server,不能执行工具调用。 |
| B | ❌ | Generative answers 用于生成回答,不会自动完成 MCP 工具配置。 |
| C | ❌ | 发布 Agent 不会自动添加 MCP 工具。 |
| D | ✅ | 将 MCP server 添加到工具配置,使 Agent 能够调用其工具。 |
考试记忆: MCP 执行业务操作 → Add MCP server as a tool + configure authentication。
Correct Answer: D
Explanation/Reference:
Explanation:
You must add a new Model Context Protocol tool to your agent and configure it with OAuth 2.0 authentication settings. This registers the server's published capabilities as native actions that the agent can orchestrate during conversation.
QUESTION 9
A company needs an agent to answer questions using live enterprise records and to execute a limited set of operations in the same system. To meet the business needs, the agent must meet the following requirements:
-
The agent must update a record using authenticated access.
-
The agent must answer questions using live data at runtime.
-
The agent must avoid indexing enterprise data into a search index.
You need to select the correct Power Platform connector approach for each requirement.
Which option should you use for each requirement? To answer, move the appropriate solutions to the correct requirements. You may use each solution once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
以下是提取并整理为 Markdown 格式的内容,附带正确答案及解析:
Select and Place:
Solutions (Options)
- Power Platform connector tool.
- Power Platform connector as real-time knowledge.
- Copilot connector knowledge source for indexed content.
Power Platform connector solutions
| Requirement | Solution |
|---|---|
| The agent must update a record using authenticated access. | [ 空白框 ] |
| The agent must answer questions using live data at runtime. | [ 空白框 ] |
| The agent must avoid indexing enterprise data into a search index. | [ 空白框 ] |
正确答案如下:
| Requirement | Solution |
|---|---|
| The agent must update a record using authenticated access. | Power Platform connector tool. |
| The agent must answer questions using live data at runtime. | Power Platform connector as real-time knowledge. |
| The agent must avoid indexing enterprise data into a search index. | Power Platform connector as real-time knowledge. |
解析
- 更新记录 → Power Platform connector tool:通过连接器工具执行创建、更新等操作,并使用配置的连接进行身份验证。
- 运行时查询实时数据 → Power Platform connector as real-time knowledge:在回答问题时实时访问数据源,而不是只依赖预先索引的数据。
- 避免索引数据 → Power Platform connector as real-time knowledge:实时知识连接器可在运行时检索数据,无需将企业数据复制到搜索索引。
未使用的选项: Copilot connector knowledge source for indexed content,因为它适用于索引内容的检索,与避免索引数据的要求不符。
QUESTION 10
A company uses an agent in Copilot Studio to coordinate user interactions.
The company wants the agent to delegate requests to a Microsoft Fabric Data Agent that accesses governed business data.
The agent must retrieve structured analytical data while enforcing data security and scope controls. You need to select the integration approach that meets the requirements.
What should you use?
A. A Microsoft Fabric Data Agent and bind it to the model.
B. A REST API action that queries Fabric tables directly.
C. A Power Automate flow and call it from a topic.
D. A Copilot connector knowledge source that indexes Fabric data.
正确答案:A. A Microsoft Fabric Data Agent and bind it to the model.
解析
Microsoft Fabric Data Agent 可以通过 Fabric semantic model 访问受治理的业务数据,并利用数据模型的语义和安全控制来回答结构化分析问题。将其集成到多 Agent 方案中,可以让 Copilot Studio 主 Agent 将指标查询委派给专门的 Data Agent。
| 选项 | 判断 | 原因 |
|---|---|---|
| A | ✅ | 使用 Fabric Data Agent 访问结构化分析数据,并遵循相应的数据范围和治理控制。 |
| B | ❌ | 直接查询 Fabric 表会绕过题目要求的专用 Data Agent 集成方式。 |
| C | ❌ | Power Automate Flow 适合流程自动化,但不是此处指定的分析 Agent 集成方式。 |
| D | ❌ | Copilot connector 知识源侧重索引内容检索,不适合实时结构化分析查询。 |
考试记忆: Fabric 结构化分析与受治理的业务指标 → Microsoft Fabric Data Agent。
Correct Answer: A
Section: (none) Explanation/Reference:
Explanation:
To coordinate interactions while accessing governed data, you should create a Microsoft Fabric Data Agent and integrate it into Microsoft Copilot Studio using the Add Agent / Generative Orchestration feature. Agent-to-Agent Collaboration: Instead of writing custom APIs, you can publish a specialized Fabric Data Agent in Microsoft Fabric, and then simply bind it as an external agent within Copilot Studio.
Built-in Security & Scope: Fabric enforces existing data constraints. Data access runs under the authenticated user's identity, automatically respecting Power BI model-level read permissions, Row-Level Security (RLS), and Object-Level Security (OLS).
Seamless Context: This enables multi-step agent orchestration where Copilot Studio routes queries to the Fabric agent for complex analytical insights (translating natural language to SQL/DAX/KQL) without exposing raw data.