It-Pruefung ist eine Website, die den IT-Kandidaten, die an der Microsoft AB-620 Zertifizierungsprüfung teilnehmen, Lernhilfe bieten, so dass sie das Microsoft AB-620 Zertifikat erhalten. Die Lernmaterialien von It-Pruefung werden von den erfahrungsreichen Fachleuten nach ihren Erfahrungen und Kenntnissen bearbeitet. Die alle sind von guter Qualität und auch ganz schnell aktualisiert. Unsere Prüfungsfragen und Antworten sind den realen Prüfungsfragen und Antworten sehr ähnlich. Wenn Sie It-Pruefung wählen, können Sie doch die schwierige Microsoft AB-620 Zertifizierungsprüfung, die für Ihre Karriere von großer Wichtigkeit ist, bestehen.
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Test, deploy, and manage agents | 20–25% | - Test and validate agent performance
|
| Topic 2: Plan and configure agent solutions | 30–35% | - Configure agent foundations
|
| Topic 3: Build and extend agents in Copilot Studio | 40–45% | - Implement advanced capabilities
|
>> AB-620 Prüfungsmaterialien <<
It-Pruefung hat die spezielle Schulungsunterlagen zur Microsoft AB-620 Zertifizierungsprüfung. Sie können mit wenig Zeit und Geld Ihre IT-Fachkenntnisse in kurzer Zeit verbessern und somit Ihre Fachkenntnisse und Technik in der IT-Branche beweisen. Die Kurse von It-Pruefung werden von den Experten nach ihren Kenntnissen und Erfahrungen für die Microsoft AB-620 Zertifizierungsprüfung bearbeitet
121. Frage
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.
Antwort: B,E
Begründung:
[A]
You can configure prompt modifications at the system and agent level in Microsoft Copilot Studio to satisfy your organization's Responsible AI (RAI) guidelines.
[E]
Scenario:
Compliance and security
Responsible AI content moderation filters must be enabled.
Reference:
https://microsoft.github.io/agent-academy/operative/06-ai-safety/
122. Frage
Drag and Drop Question
A company needs to ground an agent in Copilot Studio answers using live enterprise data from a supported system via a Microsoft Power Platform connector. To meet the business needs, the builder must meet the following requirements:
- Authenticate using a valid connection.
- Add the connector as a real-time knowledge source.
- Select the tables for knowledge grounding.
You need to add a Power Platform connector as a real-time knowledge source for the agent.
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.
Antwort:
Begründung:
Explanation:
Step 1: Add a knowledge source
Initiate: You start in the Knowledge tab to trigger the addition.
Step 2: Select the real-time connector from the Add knowledge dialog
Identify: You pick the specific system/connector from the menu.
Step 3: Sign in and create a new connection or reuse an existing connection Authenticate: You log in to ensure permissions to the enterprise data.
Step 4: Select the tables to include as the knowledge source
Configure: You isolate the exact tables needed for grounding.
Step 5: Add the connector to the agent
Finalize: You save and bind the source to your agent.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-real-time-connectors
123. Frage
A company is building an agent in Copilot Studio topic that must retrieve real-time status information from an external REST API using a Send HTTP request node.
To meet the business needs, the topic must meet the following requirements:
The request must include the required authentication header.
The request must call the endpoint using the correct HTTP method.
The response must be configured with an appropriate response data type based on a schema and saved so the topic can reuse the returned values.
You need to configure the Send HTTP request node.
Which configuration should you use for each requirement? To answer move the appropriate configuration to the correct requirements.
Antwort:
Begründung:
Explanation:
Authentication # Add the required authentication headers; Retrieve data # Set the HTTP method to GET; Structured reusable response # Select a JSON/Record response type, define the schema, and save the response to a topic variable.
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The Send HTTP request node must express the API contract directly. If the service expects a token or key in a header, the required header is added using a protected variable or connection-derived value rather than hard-coded secret text.
GET is the correct method for retrieving status without changing the external resource; PATCH would imply a partial update. Selecting a structured JSON or Record response type and defining its schema allows Copilot Studio to type the returned fields. Saving that response to a topic variable makes values available for conditions, formatting, adaptive cards, or later tool calls. The schema must reflect optional fields, arrays, and nested records accurately; otherwise valid responses can be rejected or fields can appear empty. The topic also needs branches for non-success status codes, timeouts, invalid JSON, and authentication failure. Where a reusable connector or REST tool already exists, that managed abstraction may be preferable to embedding HTTP details in multiple topics, but the node configuration shown is correct for the stated direct-request requirement. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure advanced agent responses with API and Send HTTP requests.
124. Frage
Drag and Drop Question
A company plans to use Copilot connectors to ground answers from a third-party system for an agent in Copilot Studio.
To meet the business needs, responsibilities for configuring and using Copilot connectors must be separated, based on the following requirements:
- For tenant administration, the connector must be available at the
tenant level.
- For agent runtime behavior, answers must be grounded from authorized
sources.
- For builder configuration, you must add the connector to the agent.
You need to determine how Copilot connector set-up responsibilities are handled across tenant, runtime, and builder stages.
What should you configure for each requirement? To answer, move the appropriate configuration 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.
NOTE: Each correct selection is worth one point.
Antwort:
Begründung:
Explanation:
Box 1: Configure the Copilot connector in Microsoft 365 Admin Center
To make a Copilot connector available at the tenant level for grounding agent responses in Microsoft Copilot Studio, you must configure and deploy the connector in the Microsoft 365 Admin Center.
Tenant Administration (Microsoft 365 Admin Center): Tenant administrators must configure and deploy the specific Copilot connector (e.g., ServiceNow, Salesforce, Box) within the Microsoft 365 Admin Center. This process indexes the necessary content from your third-party system across the enterprise so it can be utilized by your organization's agents.
Box 2: Add the Copilot connector as a knowledge source
To use a Copilot connector as an enterprise knowledge source in Microsoft Copilot Studio, the prerequisite configuration requires the builder to add the Copilot connector as a knowledge source.
The Builder Stage: While your AI or tenant administrator is responsible for deploying and configuring the Copilot connector in the Microsoft 365 admin center, the builder stage handles agent-specific knowledge mapping. [Box 3 below] Knowledge Integration: As an agent builder, you must actively select the preconfigured Copilot connector from the available list and add it as a knowledge source to your agent's generative answers node.
Runtime Behavior: Once this is configured, the Copilot engine indexes and queries the third-party data securely at runtime. Because the connector is tied to your tenant's security parameters, the agent will only ground answers using authorized sources and fully respect source-level permissions.
Box 3: Configure the Copilot connector in Microsoft 365 Admin Center
The initial deployment and central management of a Copilot connector must be performed in the Microsoft 365 Admin Center by a tenant administrator. However, completing the builder configuration to add the connector as a knowledge source for a specific agent is done directly within Microsoft Copilot Studio.
Reference:
https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/deployment-overview
125. Frage
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 configure the agent in Copilot Studio to use internal and external partner knowledge sources to answer user questions about the airline services.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Antwort: A,D
Begründung:
[A] External
Scenario:
Data sources include:
Travel Advisory Content: Uses REST API with partner services.
Configuring a Microsoft Graph connector to index your external data and utilizing REST APIs are highly effective and distinct strategies for supplying knowledge and actions in Microsoft Copilot Studio.
[D] Internal
Scenario:
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.
Data sources include: Customer Support Knowledge Base: SharePoint library with PDFs and policy documents.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-copilot-connectors
126. Frage
......
Die Zertifikat der Microsoft AB-620 ist international anerkannt. Sie zu erwerben bedeutet, dass Sie den Schlüssel zur höheren Stelle besitzen. Die Microsoft AB-620 Prüfungsunterlagen von It-Pruefung werden von erfahrenen IT-Profis herstellt und immer wieder aktualisiert. Jetzt können Sie mit günstigem Preis die verlässliche Microsoft AB-620 Prüfungsunterlagen genießen. Nachdem Sie die Zertifizierung erwerbt haben, können Sie leicht eine höhere Arbeitsposition oder Gehalten bekommen.
AB-620 Echte Fragen: https://www.it-pruefung.com/AB-620.html