DumpTOP사이트에서 제공하는Microsoft 인증AB-620 덤프의 일부 문제와 답을 체험해보세요. 우리 DumpTOP의 를Microsoft 인증AB-620 덤프공부자료를 선택해주신다면 우리는 최선을 다하여 여러분이 꼭 한번에 시험을 패스할 수 있도록 도와드리겠습니다.만약 여러분이 우리의 인증시험 덤프를 보시고 시험이랑 틀려서 패스를 하지 못하였다면 우리는 무조건 덤프비용 전부를 환불해드릴것입니다. DumpTOP제품으로 자격증을 정복합시다!
| Section | Weight | Objectives |
|---|---|---|
| Test, deploy, and manage agents | 20–25% | - Deploy and manage agent lifecycle
|
| Build and extend agents in Copilot Studio | 40–45% | - Develop agent flows and logic
|
| Plan and configure agent solutions | 30–35% | - Configure agent foundations
|
DumpTOP에서 Microsoft인증 AB-620덤프를 구입하시면 퍼펙트한 구매후 서비스를 제공해드립니다. Microsoft인증 AB-620덤프가 업데이트되면 업데이트된 최신버전을 무료로 서비스로 드립니다. 시험에서 불합격성적표를 받으시면 덤프구매시 지불한 덤프비용은 환불해드립니다.
질문 # 33
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.
NOTE: Each correct selection is worth one point.
정답：
설명：
Explanation:
Trace each answer to its source # Instruct the agent to cite sources in knowledge settings; Retrieve from the centralized index # Configure Azure AI Search as the grounding data source; Use an enterprise- approved foundation model # Select a model from the Foundry model catalog.
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Each requirement is controlled by a different configuration layer. Source traceability is a presentation and grounding requirement, so citations must be enabled or explicitly required for knowledge-based responses. That allows users to inspect the material used to support a policy answer; it is not achieved merely by choosing a model.
Centralized retrieval is provided by connecting the existing Azure AI Search vector index as the knowledge source. This preserves the curated index, semantic or vector retrieval behavior, and enterprise management of the policy corpus instead of copying documents into the agent. Model governance is handled in the prompt configuration by selecting the approved model from the Microsoft Foundry model catalog. Publishing does not automatically replace an unapproved model, and Azure AI Search does not enforce the foundation-model selection. Together, the three settings form a complete RAG path: Azure AI Search retrieves authoritative passages, the governed model produces the response, and citation settings expose provenance. The configuration should then be tested with representative policy questions to confirm that the response is grounded and that the cited source actually supports the answer. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure generative answers by using Azure AI Search with Foundry; Configure custom prompts to use the Foundry model catalog.
Topic 2, 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. 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 summariz ed.
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.
질문 # 34
A company is configuring an agent in Copilot Studio that uses a generative answers node inside multiple topics.
The company requires responses to meet the following requirements:
Must use an executive summary format.
Must apply only within a specific topic.
Must continue using configured knowledge sources.
Must comply with connector security controls.
You need to configure a custom prompt to meet the formatting requirements.
Solution: Remove the generative answers node and rely only on the custom prompt to produce formatted responses.
Does the solution meet the goal?
정답：B
설명：
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Removing the generative answers node eliminates the component that searches the configured knowledge sources and produces the grounded topic response. A standalone custom prompt can format or transform supplied input, but it does not automatically inherit the topic's selected knowledge sources or reproduce the node's retrieval behavior. The resulting answer could therefore have the requested executive-summary style while failing the grounding requirement. The correct design retains the generative answers node and applies topic-scoped custom instructions to its response, or captures the grounded output in a variable and sends that content through a carefully configured formatting prompt. General knowledge should remain disabled when the topic must use only approved enterprise sources. Connector security and data policies continue to govern the actual source connections and cannot be replaced by prompt text. The proposed removal is consequently not a valid solution. Validation should inspect the retrieved sources, generated answer, final format, and behavior when no authorized source returns relevant content. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure generative answers node; Configure advanced agent responses with custom prompts.
질문 # 35
A company needs an agent in Copilot Studio to complete tasks by interacting with a legacy desktop application that does not use APIs. The builder needs to validate that UI automation can run in the supported execution context and needs a way to inspect how the automation behaves during testing conversations.
To meet the business needs, the solution must meet the following requirements:
- Enable the agent to perform UI automation against the legacy
application.
- Inspect execution details for the automation during conversations.
You need to configure the agent 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,C
설명：
[B] Add a Power Platform Desktop flow to control the desktop app
Power Automate for Desktop is Microsoft's dedicated Robotic Process Automation (RPA) solution designed specifically to automate legacy desktop applications without APIs.
Fulfills Requirement 1 (UI Automation): You can easily trigger these desktop flows directly from a Copilot Studio agent as an action. The flow runs in either attended or unattended mode within a supported Windows execution context.
Fulfills Requirement 2 (Inspect Execution): Power Automate provides a visual designer and detailed run logs. When testing your agent conversations, you can inspect the exact desktop flow execution logs, variable inputs/outputs, and step-by-step actions to see how the automation behaves.
[E]
Direct UI Automation without APIs: The query specifically states that the legacy desktop application does not use APIs. The Computer use capability (powered by Computer-Using Agents or CUAs) is designed exactly for this scenario. It allows the AI agent to interact directly with graphical user interfaces (GUIs) by visually interpreting screens, clicking buttons, and entering text just like a human operator.
Incorrect:
[Not A]
Custom Connectors require a target application to expose standard APIs (like REST). Since the legacy desktop application does not use APIs, a custom connector cannot interact with it directly.
[Not C]
You cannot access a live remote session directly within the testing pane to monitor real-time desktop interactions.
[Not D]
Publishing is a final deployment step. You should not publish an untested agent to production simply to validate its behavior; testing and inspection should always happen in the authoring environment before publication.
Reference:
https://techcommunity.microsoft.com/blog/copilot-studio-blog/automate-agent-evaluation-with-the-evaluation-apis/4511653
질문 # 36
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 by 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,E
설명：
First, create a custom solution in the development environment and add the existing agent by selecting Add existing # Agent # Agent . The solution acts as the application lifecycle management package that contains the agent and its dependent components. Required objects such as agent flows, environment variables, connection references, and custom connectors should also be included when applicable.
After the agent and its dependencies are included, export the solution from the development environment.
Microsoft's documented procedure starts from the list of unmanaged solutions and exports the solution containing the agent. During the export process, the maker can select the appropriate package type.
Production deployments commonly use a managed export, but the source development solution remains unmanaged; it does not need to be converted before export.
Removing topics directly from the solution is specifically discouraged because changing or removing agent components outside the standard Copilot Studio authoring interface can cause export or import failures.
Publishing the agent to a channel is also unrelated to creating a solution package. After the solution is imported into production, the imported agent must be configured, tested, and published in that environment.
Relevant study-guide area: Test and manage agents # Implement application lifecycle management for agents in Copilot Studio # Create a solution and add existing agents to a solution . See Export and import agents using solutions .
질문 # 37
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 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,E
설명：
[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.
[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.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/nlu-boost-node
https://www.reddit.com/r/copilotstudio/comments/1pje5fy/how_do_you_handle_ai_disclaimers_in_copilot/
질문 # 38
......
DumpTOP의 Microsoft인증 AB-620시험덤프자료는 IT인사들의 많은 찬양을 받아왔습니다.이는DumpTOP의 Microsoft인증 AB-620덤프가 신뢰성을 다시 한번 인증해주는것입니다. Microsoft인증 AB-620시험덤프의 인기는 이 시험과목이 얼마나 중요한지를 증명해줍니다. DumpTOP의 Microsoft인증 AB-620덤프로 이 중요한 IT인증시험을 준비하시면 우수한 성적으로 시험을 통과하여 인정받는 IT전문가로 될것입니다.
AB-620최신버전 시험자료: https://www.dumptop.com/Microsoft/AB-620-dump.html