TopexamのMicrosoftのAB-620試験トレーニング資料は全てのオンラインのトレーニング資料で一番よいものです。我々の知名度はとても高いです。これは受験生の皆さんが資料を利用した後の結果です。TopexamのMicrosoftのAB-620試験トレーニング資料を選んだら、100パーセントの成功率を保証します。もし失敗だったら、我々は全額で返金します。受験生の皆さんの重要な利益が保障できるようにTopexamは絶対信頼できるものです。
| Section | Weight | Objectives |
|---|---|---|
| Test, deploy, and manage agents | 20–25% | - Test and validate agent performance
|
| Plan and configure agent solutions | 30–35% | - Configure agent foundations
|
| Build and extend agents in Copilot Studio | 40–45% | - Integrate with services and systems
|
お支払い後、最初にAB-620練習資料を受け取りたい場合があります。心配しないで。支払いが完了するまで、オンラインワーカーが教材の注文を迅速に処理します。支払いプロセス全体は数秒続きます。それに加えて、AB-620学習ガイドについて知りたいことを尋ねることができます。質問を送信すると、すぐに詳細な説明が表示されます。 AB-620学習教材の練習中に問題に遭遇した場合でも、問題の解決もお手伝いします。 AB-620ラーニングガイドでお客様の問題に対応いたします。
質問 # 87
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.
Drag and Drop Question
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.
正解:
解説:
Explanation:
Box 1: Custom Connector
Internal Reservation
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.
Reference:
https://learn.microsoft.com/en-us/connectors/custom-connectors/
質問 # 88
Hotspot Question
You are setting up an evaluation for an agent in Copilot Studio before expanding access to more users.
You must configure the evaluation so that the agent is tested by using prepared interactions rather than impromptu conversations.
The evaluation should provide the following functionality for users:
- An administrator updates a sensitive configuration value. The
administrator requires 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
requires the updated value to be used by the published agent at
runtime.
You need to create a test set-based evaluation that supports consistent test runs for each scenario.
What should you configure for each scenario? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
正解:
解説:
Explanation:
Box 1: Secret environment variable
The correct configuration for updating a sensitive configuration value at runtime without having to republish the agent is a Secret environment variable.
Secret environment variables: Securely store secrets (like passwords, keys, or API tokens) within the environment and reference them directly inside the agent. These can be updated dynamically at runtime without needing to republish the bot, as they are evaluated in real-time.
Incorrect:
Only in production / Only after publishing: These configurations require a full publishing cycle to take effect. This means that any adjustments to bot topics, node logic, or regular environment variables require pushing the latest content updates out to end-users.
Box 2: Managed environment variable
A managed environment variable is the specific configuration needed. It enables makers to reference or confirm configuration values without permitting modifications directly within the studio interface, protecting agent integrity. Additionally, you can configure your testing using the Agent Evaluation in Copilot Studio feature.
Box 3: String environment variable
The specific configuration that allows an administrator to update a non-secret configuration value and requires the updated value to be used by the published agent at runtime is a string environment variable.
In Microsoft Copilot Studio, environment variables are used to manage configuration values dynamically. When an administrator updates a non-secret string environment variable, the change takes effect at runtime without requiring the agent to be rebuilt or modified in the authoring canvas.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-agent-evaluation-overview
質問 # 89
A company is extending agents in Copilot Studio with both external capabilities and enterprise content access. Some user requests require grounded answers, while other requests require executing actions.
To meet the business needs, the agent must meet the following requirements:
Ground answers using results from enterprise data.
Invoke callable functions exposed through a standardized tool interface.
Write an update to a system by using an authenticated action during the conversation.
You need to integrate the correct approach to meet the requirements.
正解:
解説:
質問 # 90
Drag and Drop Question
A company wants to extend an agent in Copilot Studio by calling an external REST API to retrieve and update data.
To meet the business needs, the REST API must be added following a correct dependency order.
You need to add a REST API to the agent so it can be invoked during conversations.
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.
正解:
解説:
Explanation:
You must configure authentication and the API tool before you can successfully configure the endpoint details and test it.
To add an external REST API to an agent in Copilot Studio, you must follow this exact dependency order:
Step 1: Configure authentication for the API
Setup security credentials first.
This includes API keys or OAuth.
Without this, the connection will fail.
Security First: Copilot Studio requires a valid connection object to save and route endpoint requests.
Step 2: Add the REST API tool.
Import or create the action connector.
This registers the tool in Copilot.
Tool Registration: The agent needs to recognize the tool wrapper before you can customize its internal endpoint paths.
Step 3: Configure the API endpoint details.
Define specific paths and methods.
Map input and output parameters.
Step 4: Test the API configuration
Run validation checks in real-time.
Ensure data flows correctly.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/agent-extend-action-rest-api
質問 # 91
Drag and Drop Question
A company is building an agent that uses an agent flow to retrieve data from an external system and return structured output.
The company needs to create a flow that the agent can invoke to process requests and return results. To support this business need, the flow must meet the following requirements:
- Accept parameters from the agent.
- Execute an action to retrieve data from the database.
- Ensure the agent receives the relevant output information.
- Validate before it is used by the agent.
You need to create a usable agent flow that the agent can invoke.
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.
正解:
解説:
Explanation:
Step 1: Create a new agent flow
Initialize the flow workspace from your platform's dashboard using a template or blank canvas.
Step 2: Define input values for the flow: Configure the flow's initial trigger parameters to accept structured data passed from the AI agent.
Step 3: Add the connector action and configure the connection
Set up the database or external system connector node to perform the data retrieval query using your defined inputs.
Step 4: Define output values for the flow
Map the retrieved system results into structured output parameters back within the response node so the agent can understand the payload.
Step 5: Test the flow run
Run a simulated diagnostic execution to validate that data transfers correctly and errors are handled before deploying it to production.
質問 # 92
......
私たちのAB-620試験問題集は、もちろん、さまざまな国で人気があります。同時に、私たちのグローバル市場は私たちが情報を収集するのにも役にだちます。私たちはあなたにAB-620試験問題集の更新を一年間無料で提供できます。あなたはほかの資料を購入する必要はありません。 AB-620試験問題集は、あなたのすべてのニーズを満たすことができます。 何を待っていますか?早く行動しましょう!
AB-620模擬試験: https://www.topexam.jp/AB-620_shiken.html