多くの人はAB-620試験は難しいと思っています。しかし、AB-620試験参考書を持たれば、自分の努力に加えて、きっとAB-620試験に合格できます。AB-620試験参考書について、もっと詳しいことを知りたい場合、Microsoft会社のウエブサイトを訪問して頂きます。
| Section | Weight | Objectives |
|---|---|---|
| Plan and Configure Agent Solutions | 30-35% | - Plan agent solutions
|
| Integrate and Extend Agents in Copilot Studio | 40-45% | - Build advanced agent solutions
|
| Test and Manage Agents | 20-25% | - Monitor and manage agent solutions
|
MicrosoftのAB-620試験準備は、テストヒット率が高いため、98％〜100％の合格率です。 したがって、当社のAB-620学習教材は効果的であるだけでなく、有用でもあります。 誰もが知っているように、時間は誰にとっても非常に重要です。 一部の候補者は、自分の仕事や家族で非常に忙しいです。 AB-620試験の審査に時間をかけることは非常に困難です。 ただし、AB-620試験の教材を使用する場合、学習する時間はほとんどなく、Designing and Building Integrated AI Agent Solutions in Copilot Studio合格率は高くなります。 AB-620学習教材はあなたの信頼に値します。
質問 # 124
Case Study 2 - Fabrikam Inc.
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.
Drag and Drop Question
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.
NOTE: Each correct selection is worth one point.
正解：
解説：
Explanation:
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.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-foundry-agent
質問 # 125
Drag and Drop Question
A company is building an agent in Copilot Studio that must answer questions using enterprise systems and must also perform authenticated operations.
To meet the business needs, the agent must meet the following requirements.
- The agent must provide searchable answers from indexed enterprise
content.
- The agent must retrieve up-to-date facts at runtime without indexing
data.
- The agent must perform an authenticated update operation during the
conversation.
You need to select the correct integration 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.
正解：
解説：
Explanation:
Box 1: Copilot connector knowledge source.
The most appropriate integration action for this requirement is to use a Copilot connector knowledge source.
Searchable Answers from Indexed Content: Copilot connectors index non-Microsoft enterprise data (like Salesforce, ServiceNow, or Confluence) directly into the Microsoft Graph. This allows the agent to perform comprehensive semantic and vector searches across your structured and unstructured enterprise content.
Authenticated Operations: These connectors respect source-level security and authentication rules, ensuring that users can only access content they are authorized to view.
Box 2: Power Platform connector for real-time knowledge.
The most appropriate integration action for your scenario is to use a Power Platform connector for real-time knowledge.
Retrieves up-to-date facts: Power Platform connectors for real-time knowledge connect directly to live operational systems without requiring you to ingest, crawl, or replicate data. This guarantees that your agent fetches the absolute latest information available.
Performs authenticated operations: These connectors operate in the end-user's context at runtime. This ensures that when the agent pulls data, it strictly honors your organization's permissions-so users only get answers to data they are already authorized to view.
Box 3: Power Platform connector tool
The correct integration action for this requirement is to use the Power Platform connector tool.
Action vs. Retrieval: The requirement specifically demands an authenticated update operation (a transactional, state-changing action) during the conversation. In Microsoft Copilot Studio, Tools are designed to execute actions, modify data, and trigger workflows in external systems.
Reference:
https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/overview
質問 # 126
Drag and Drop Question
An agent in Copilot Studio must retrieve real-time data from an external system that exposes a REST API. The API returns structured JSON responses and requires authentication.
To meet the business needs, the solution must meet the following requirements:
- The agent calls a REST API during a conversation.
- The REST API call runs with proper authentication.
- The REST API response is available to the topic at runtime.
You need to configure the REST API 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 au. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
正解：
解説：
Explanation:
Box 1: Configure a REST action and call it from a topic.
To enable a Microsoft Copilot Studio agent to query an external authenticated REST API during a conversation, you can configure a REST action (or custom HTTP request) and invoke it directly from a conversation topic.
Box 2: Build an authenticated connection for the API.
You must establish an authenticated connection for the REST API in Copilot Studio. When configuring a REST API action or using an HTTP request node to connect an agent to an external system, providing specific authentication details ensures the call executes securely and successfully.
Box 3: Store the API response in a topic variable.
You should store the API response in a variable, but you usually map specific JSON properties to individual variables rather than saving the entire raw JSON payload.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-http-node
質問 # 127
A team has deployed an agent in Copilot Studio and needs to evaluate whether the agent is meeting its intended goals before expanding usage to a broader audience.
The team must evaluate agent performance using a structured and repeatable approach that produces actionable insights.
You need to select and apply an appropriate evaluation method by performing the required actions in the correct order.
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.
正解：
解説：
質問 # 128
A company uses an agent in Copilot Studio to generate structured responses for internal users. The agent must meet the following requirements:
* Consistently follow a reusable instruction template for response tone and structure.
* Use an enterprise-approved foundation model for responses generated through the template.
You need to configure custom prompts so that the agent uses the Microsoft Foundry model catalog. Which two actions should you perform? Each correct answer presents part of the solution. Choose two.
NOTE: Each correct selection is worth one point.
正解：B、F
解説：
A custom prompt provides a reusable instruction template that controls how the model performs a specific task. The template can define tone, output structure, formatting, constraints, examples, and fallback behavior.
It can then be added as an agent-level tool, called from a topic, or used within an agent flow. This makes option A the correct mechanism for applying consistent instructions wherever the structured response is generated.
The prompt's model is configured separately in the prompt editor. The builder selects the required enterprise- approved model from the Model field or connects an approved deployment from the Microsoft Foundry model catalog. After that model is selected for the custom prompt, every execution of that prompt uses the selected model, making option E correct.
Publishing does not automatically select an appropriate Foundry model; the model must be explicitly configured. Azure AI Search controls retrieval and grounding, not model selection. Citations provide source traceability but do not limit execution to approved models. Defining instructions independently in individual topics would duplicate configuration and weaken consistency.
Relevant AB-620 study-guide topics are Configure advanced agent responses with custom prompts and Configure custom prompts to use the Foundry model catalog . See Use prompts in Copilot Studio and Use Foundry models for prompts .
質問 # 129
......
AB-620学習クイズの最も注目すべき機能は、簡単かつ簡単に試験のポイントを学習し、認定コースの概要のコア情報を習得するのに役立つ最も実用的なソリューションを提供することです。それらの品質は、他の資料の品質よりもはるかに高く、AB-620トレーニング資料の質問と回答には、利用可能な最良のソースからの情報が含まれています。初心者でも経験豊富な試験受験者でも、AB-620スタディガイドは大きなプレッシャーを軽減し、困難を効率的に克服するのに役立ちます。
AB-620ミシュレーション問題: https://www.certjuken.com/AB-620-exam.html