Microsoft 인증AB-620인증시험공부자료는Itcertkr에서 제공해드리는Microsoft 인증AB-620덤프가 가장 좋은 선택입니다. Itcertkr에서는 시험문제가 업데이트되면 덤프도 업데이트 진행하도록 최선을 다하여 업데이트서비스를 제공해드려 고객님께서소유하신 덤프가 시장에서 가장 최신버전덤프로 되도록 보장하여 시험을 맞이할수 있게 도와드립니다.
| Section | Weight | Objectives |
|---|---|---|
| Integrate and Extend Agents in Copilot Studio | 40-45% | - Build advanced agent solutions
|
| Test and Manage Agents | 20-25% | - Monitor and manage agent solutions
|
| Plan and Configure Agent Solutions | 30-35% | - Plan agent solutions
|
Microsoft인증 AB-620시험을 패스하는 지름길은Itcertkr에서 연구제작한 Microsoft 인증AB-620시험대비 덤프를 마련하여 충분한 시험준비를 하는것입니다. 덤프는 Microsoft 인증AB-620시험의 모든 범위가 포함되어 있어 시험적중율이 높습니다. Microsoft 인증AB-620시험패는 바로 눈앞에 있습니다. 링크를 클릭하시고Itcertkr의Microsoft 인증AB-620시험대비 덤프를 장바구니에 담고 결제마친후 덤프를 받아 공부하는것입니다.
질문 # 73
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.
정답：A,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
질문 # 74
Users can add content to a paragraph field in a team-managed project, but they cannot @mention other users.
Identify the cause.
정답：D
설명：
Comprehensive and Detailed Explanation From [Atlassian Jira Cloud Documentation] The cause is the Jira Browse users and groups global permission. Atlassian states that users with this permission can view user names when working with user-picker fields or @mentioning users. Without it, Jira cannot provide the affected users with the complete user directory required to search for and select another person through an @mention.
The fact that users can enter and save ordinary text in the paragraph field confirms that the field is present, editable, and available on the applicable work-item layout. Therefore, field settings and screen settings are not responsible. Notification settings determine how users receive updates after an event and do not control whether names appear in the mention picker.
Project permissions and issue-level security can affect whether a particular person can access the project or work item. However, a general inability to search for or mention other users indicates that the initiating users lack the site-wide user-browsing capability.
A Jira administrator should review Settings → System → Global permissions and grant Browse users and groups to an appropriate group containing the affected users, subject to the organization's privacy policies.
Relevant documentation topic: Jira Cloud administration → Global permissions → Browse users and groups. See What are global permissions, and what do they control?.
질문 # 75
A company uses an agent flow that calls a connector action. The flow sends an administrative notification if the action fails or times out Administrators require the following configuration to help troubleshoot and manage failures:
* Handle failure and timeout outcomes explicitly.
* Continue execution after a failure is handled.
* Avoid retrying the failed action automatically.
You need to configure the agent flow so that failures are handled in a controlled and predictable way.
Which two actions should you perform? Each correct answer presents part of the solution. Choose two.
NOTE: Each correct selection is worth one point.
정답：C,D
설명：
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The connector action ' s retry policy should be set to None when the business requirement explicitly says not to retry automatically.
Otherwise, platform retries can repeat a non-idempotent operation or delay the controlled failure path. The notification action must then use Configure run after so it executes when the connector action fails or times out and can include the available error details. This combination directly addresses the three requirements:
explicit failure and timeout handling, continuation into the notification branch, and no automatic retry. A scope can be valuable for grouping a try block and evaluating its aggregate result, but grouping alone does not disable retries or define the notification ' s run-after conditions. Increasing the timeout changes how long the action waits and can make recovery slower without handling the error. The flow should also end with a deliberate final status, avoid exposing secrets in the notification, and distinguish transient dependency errors from validation failures. If the external operation is non-idempotent, a correlation or idempotency key should be used to prevent duplicate effects when an administrator later resubmits the run manually. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Implement error handling in agent flows.
질문 # 76
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.
정답：
설명：
질문 # 77
You need to prevent an agent from using connectors that could send data to non-approved cloud services outside your organization. What should you configure?
정답：D
설명：
DLP policies classify connectors as business or non-business and block data flow between them, preventing an agent from combining approved and unapproved connectors in the same flow.
질문 # 78
......
Itcertkr덤프를 IT국제인증자격증 시험대비자료중 가장 퍼펙트한 자료로 거듭날수 있도록 최선을 다하고 있습니다. Microsoft AB-620 덤프에는Microsoft AB-620시험문제의 모든 범위와 유형을 포함하고 있어 시험적중율이 높아 구매한 분이 모두 시험을 패스한 인기덤프입니다.만약 시험문제가 변경되어 시험에서 불합격 받으신다면 덤프비용 전액 환불해드리기에 안심하셔도 됩니다.
AB-620최고기출문제: https://www.itcertkr.com/AB-620_exam.html