多くの時間とお金がいらなくて２０時間だけあって楽に一回にMicrosoftのAB-620認定試験を合格できます。CertShikenが提供したMicrosoftのAB-620試験問題と解答が真実の試験の練習問題と解答は最高の相似性があります。
| Section | Weight | Objectives |
|---|---|---|
| Integrate and Extend Agents in Copilot Studio | 40-45% | - Integrate agents with enterprise systems
|
| Plan and Configure Agent Solutions | 30-35% | - Plan agent solutions
|
| Test and Manage Agents | 20-25% | - Monitor and manage agent solutions
|
なぜみんなが順調にMicrosoftのAB-620試験に合格できることに対する好奇心がありますか。MicrosoftのAB-620試験に合格したいんですか。実は、彼らが試験に合格したコツは我々CertShikenの提供するMicrosoftのAB-620試験ソフトを利用したんです。豊富の問題集、専門的な研究と購入の後の一年間の無料更新、ソフトで復習して、自分の能力の高めを感じられます。MicrosoftのAB-620試験に合格することができます。
質問 # 83
Case Study 1 - Blue Yonder Airlines
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.
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.
正解：C、D
解説：
Under Compliance and Security, the requirements state: "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." Setting this up at the system level ensures broad, consistent compliance without violating the constraint against manual topic-level edits.
Under Compliance and Security, the case study explicitly states: "Power Platform DLP policies must be enforced to block unauthorized data flows." DLP (Data Loss Prevention) policies are environment-level safeguards configured before deployment to restrict data movement between custom/REST connectors and non-compliant channels/destinations.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-fundamentals-publish-channels
https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-dlp
https://learn.microsoft.com/en-us/microsoft-copilot-studio/nlu-generative-answers
質問 # 84
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?
正解：B
解説：
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.
Reference:
https://learn.microsoft.com/en-us/power-pages/configure/mcp-connect-clients
質問 # 85
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.
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.
正解：B、C
解説：
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.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/bring-your-own-model-prompts
https://learn.microsoft.com/en-us/microsoft-copilot-studio/nlu-prompt-node
質問 # 86
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.
正解：
解説：
Explanation:
Avoid indexing business records # Retrieve data without indexing; Preserve source-system controls # Use existing permissions; Access current data at runtime # Use a real-time Power Platform connector.
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Power Platform real- time knowledge connectors query the source system when the agent needs an answer. Microsoft indexes metadata needed to understand the available tables and fields, but the business records themselves are not copied into a separate content index. Because the request is executed through the established connection, the source system ' s permissions remain part of the access decision. This is materially different from a Copilot connector, which indexes external content into Microsoft Graph, and from Azure AI Search, which relies on a maintained search index. The real-time pattern is best when current operational records and source-enforced access are more important than broad document search. The connection must be governed with the same Power Platform data policies that apply to actions, and authentication should reflect whether access is user- delegated or provided by a service identity. Testing under users with different permissions is essential to confirm that the agent cannot return records a user could not access directly and that changes in the source appear without an indexing delay. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources > Connect to Microsoft Power Platform connectors.
質問 # 87
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.
正解：
解説：
質問 # 88
......
一般的には、あなたは多くの時間と精力を利用してAB-620試験を準備する必要があります。悩んでいるなら、弊社のAB-620資料を利用して、あなたは試験に関する情報を了解することができます。我々の問題集の的中率は高いですから、CertShikenの資料を利用して試験を準備して、あなたの学習効率を高めることができます。
AB-620日本語関連対策: https://www.certshiken.com/AB-620-shiken.html