Microsoft AB-620 Deluxe Study Guide with Online Test Engine
AB-620 dumps review - Professional Quiz Study Materials
NEW QUESTION # 49
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.
Answer:
Explanation:
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
NEW QUESTION # 50
Drag and Drop Question
A company needs an agent in Copilot Studio to complete tasks by interacting with a legacy desktop application that does NOT have APIs.
To meet the business needs, the solution must meet the following requirements:
- The agent must interact with the application's UI.
- The execution must run on supported infrastructure.
- The builder must be able to observe how the tool runs during
execution.
You need to configure the agent based on the requirements.
Which setting should you configure for each requirement? To answer, move the appropriate settings to the correct requirements. You may use each setting 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.
Answer:
Explanation:
Explanation:
Box 1: Enable Compute use tool for the agent.
To enable an agent in Microsoft Copilot Studio to interact with a legacy application's UI, you must configure and add the Computer Use capability.
Box 2: Use a platform-hosted execution environment.
In Microsoft Copilot Studio, you should configure the agent to use a platform-hosted execution environment to automate tasks on legacy desktop applications without APIs.
Box 3: Monitor run details in the agent runtime view.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/computer-use
NEW QUESTION # 51
A company is building an agent in Copilot Studio.
The agent must meet the following requirements:
- Responses must be grounded in approved internal content.
- The agent must be able to retrieve information from configured data
sources in a topic.
You need to configure the agent so that topic responses are grounded from custom data sources.
What should you configure?
- A. Add a custom prompt that tells the agent to answer only from company data.
- B. Increase the response length limit to improve answer completeness.
- C. Enable analytics to review which topics users trigger most often.
- D. Add SharePoint as a knowledge source only at the agent level.
- E. Configure knowledge sources in a generative answers node.
Answer: E
Explanation:
To configure a Microsoft Copilot Studio agent so its topic responses are exclusively grounded in your custom data sources, you should leverage the Create generative answers node within a targeted custom topic. This setup ensures the agent strictly retrieves information from your approved internal content.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-copilot-studio
NEW QUESTION # 52
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.
Answer:
Explanation:
NEW QUESTION # 53
A company uses multiple Copilot Studio agents that perform specialized tasks.
You need to configure a Copilot Studio agent in your environment to connect to an external agent.
What should you do?
- A. Add the target agent as an indexed knowledge source.
- B. Enable generative answers to call the other agent.
- C. Add a Power Platform connector tool that calls the other agent.
- D. Provide A2A endpoint information for the target agent.
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: An external agent that supports Agent2Agent is connected by supplying its A2A endpoint and the required authentication configuration. The endpoint represents a collaboration interface between independently orchestrated agents, enabling the Copilot Studio agent to delegate a task and receive the partner agent's response. Generative answers cannot call another agent merely because both use generative AI; they retrieve and synthesize from knowledge sources. A Power Platform connector could wrap an ordinary API, but it would not use the specified A2A agent contract and would lose agent-to-agent semantics. Adding the target as indexed knowledge would only make a corpus searchable and would not execute the target agent. The endpoint must be the A2A message endpoint, not just a website or agent-card URL. The builder should give the connection a discriminating description, configure authentication if the endpoint is protected, and validate handoff behavior in the test pane. Production planning should include timeout, failure, logging, and data-sharing boundaries between the two agents. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Create a multi-agent solution by using A2A protocol.
NEW QUESTION # 54
A company integrates a Model Context Protocol (MCP) service that exposes ticket-management operations.
The MCP service requires authenticated requests and exposes multiple callable operations that must be selectively governed for agent use.
To meet the business needs, the MCP configuration must meet the following requirements:
Only the allowed capabilities must be callable during conversations.
Requests must succeed without embedding credentials in topic steps.
The agent must be configured to send requests to the correct backend.
You need to configure MCP tools for the agent.
Which setting should you configure for each requirement? To answer, move the appropriate settings to the correct requirements. You may use each setting once, more than once, or not at all.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
NEW QUESTION # 55
You need to enable collaboration requirements for Operations Concierge
Which two actions should you perform? Each correct answer presents part of the solution Choose two. NOTE: Each correct selection is worth one point
- A. Replace the Service Desk Agent with an MCP server.
- B. Publish the Service Desk Agent
- C. Enable allow connections from other agents on the Service Desk Agent.
- D. Add the Service Desk Agent as an indexed knowledge source
- E. Publish Operations Concierge to enable delegation automatically.
Answer: B,C
Explanation:
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The Service Desk Agent must be both published and available for connections from other agents. Publishing establishes a runtime version that the primary agent can call; an unpublished draft is not a valid connected-agent target. On the Service Desk Agent, the setting that allows other agents to connect and use it must also be enabled. Microsoft additionally requires the connected agent to be in the same environment and the maker to own it or have it shared, but those conditions are not offered as choices. Replacing the agent with an MCP server would discard the existing agent's orchestration and ticket-routing logic. Adding it as a knowledge source would expose content for retrieval, not delegate an IT request to another agent. Publishing Operations Concierge alone does not satisfy the prerequisites of the target agent. After connection, the local description in Operations Concierge should clearly define when IT-specific work is delegated, because descriptions influence routing. Any later changes to the Service Desk Agent must be published before the main agent can use the updated version. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate an existing agent in Copilot Studio.
NEW QUESTION # 56
A company is building an agent topic in Copilot Studio. The agent topic uses a generative answers node to respond to user questions based on authorized knowledge sources.
To meet the business needs, the generative answers node must meet the following requirements:
Use the user's message in the generative answers node.
Scope the topic node to query only designated data.
Restrict responses to approved enterprise data.
Answer:
Explanation:
NEW QUESTION # 57
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: Create a custom prompt tool in the specific topic that instructs the model to respond using an executive-summary structure.
Does the solution meet the goal?
- A. Yes
- B. No
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A separate custom prompt tool that merely requests an executive-summary structure does not, by itself, guarantee that the existing generative answers node and its configured knowledge sources remain in the response path. Prompt tools have their own inputs, knowledge configuration, model settings, and completion behavior. If the tool is invoked independently, it can generate correctly formatted text without using the sources selected for the topic's generative answer, which violates a stated requirement. The safer design is to keep the generative answers node and apply topic-specific custom instructions or prompt modification to that node, or explicitly pass its grounded output into a downstream formatting prompt with a controlled contract. Connector security remains enforced by the underlying connections and data policies; wording in a prompt cannot override those controls. Therefore, the proposed solution is incomplete and does not meet the goal as written. Testing should confirm not only the output format but also the sources used and the identity under which any connector retrieval occurred. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure advanced agent responses with custom prompts and custom knowledge sources.
NEW QUESTION # 58
Drag and Drop Question
A company has an approved custom connector that uses a REST API for an internal system.
An agent in Copilot Studio must call this connector during conversations to retrieve or update data.
To meet the business needs, the solution must meet the following requirements:
- Make the connector actions available for the agent to invoke.
- Ensure authentication is handled at the service level, not per user.
- Pass conversation context into the connector when it is called.
- Surface the returned data of the connector to the user in the
conversation.
You need to configure the agent and the connector action to meet the requirements.
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.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
Box 1: Add the connector as a tool in the agent
To make the custom connector actions available for the agent to invoke, the correct configuration action is to add the connector as a tool in the agent.
Box 2: Create or reuse a connection for the connector
The correct configuration action to ensure authentication is handled at the service level (and not per user) is to create or reuse a connection for the connector.
Service-Level Auth: In Copilot Studio, when you use a custom connector, you must establish a connection that determines how credentials are supplied.
Connection Creation: By creating a connection using a fixed service account or API key-and configuring it to be shared or run under that specific context-the agent authenticates at the system/service level.
Box 3: Map topic variables to the tool inputs
The correct configuration action is to map topic variables to the tool inputs.
When you add a custom connector to an agent in Microsoft Copilot Studio, it functions as a "tool" or an action. To pass specific data-such as conversation context or user details-from the ongoing chat into that connector, you must map the active Copilot Studio topic variables to the input parameters defined by the connector's REST API.
Box 4: Parse the JSON response and assign it to a topic variable
To surface the returned data of the connector to the user in Copilot Studio, the correct configuration action is to parse the JSON response and assign it to a topic variable.
Data Extraction: Custom connectors return raw JSON data from REST APIs.
Variable Storage: Copilot Studio cannot display raw JSON directly to users in a clean way.
User Delivery: You must parse that JSON payload to isolate specific fields and save them into topic variables, which can then be inserted into message nodes for the user to read.
Reference:
https://learn.microsoft.com/en-us/power-platform/release-plan/2024wave2/microsoft-copilot-studio/create-rest-api-copilot-connectors-copilot-studio
NEW QUESTION # 59
A team has an existing agent in Copilot Studio and must move it to a different target location without rebuilding the agent. Some builders use Copilot Studio in the web app, while others use Copilot Studio in Microsoft Teams.
You need a supported approach to move the existing agent to the target location using ALM practices. The solution must avoid rebuilding the agent.
You need to move the existing agent to the target location using a supported method.
What should you do?
- A. Create a custom solution, add the existing agent to the solution, export the solution with the agent, and import the solution into the target environment.
- B. Duplicate the agent in the source and manually recreate the changes in the target to avoid solution dependencies.
- C. Remove agent components directly from the solution so that export and import will succeed.
- D. Publish the agent to a channel and use the channel configuration as the transport mechanism to the target environment.
Answer: A
Explanation:
Using Power Platform Application Lifecycle Management (ALM) practices, creating a custom solution, packaging the existing agent (and its dependent objects), exporting it, and importing it into the target environment is the standard way to transport a Copilot Studio agent without rebuilding it.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-solutions-import-export
NEW QUESTION # 60
Drag and Drop Question
A company has an existing custom connector that is approved and available in the environment.
A builder wants an agent in Copilot Studio to call the connector during a conversation to retrieve information from an internal system.
To meet the business needs, the solution must meet the following requirements:
- The agent must make the connector available for topic steps.
- The agent must run the connector call with a valid connection.
- The connector call must receive the required input values at runtime.
You need to configure the agent so the custom connector can be used as a tool.
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.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
Box 1: Add the connector as a tool in the agent.
To make an approved custom connector available for topic steps within Copilot Studio, you must add the connector as a tool in the agent.
In Copilot Studio, actions and custom connectors must be explicitly registered as "Tools" within the agent's capabilities before they can be recognized or called by topics.
Box 2: Create or reuse a connection for the connector
The appropriate action is to create or reuse an existing connection for the custom connector.
Because the connector is already approved and available in your environment, you can simply select it from your tools and link the predefined connection Use connectors in Copilot Studio agents.
Box 3: Map topic variables to the tool inputs
The correct configuration action is to Map topic variables to the tool inputs.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-connectors
NEW QUESTION # 61
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 configure the agent in Copilot Studio to meet Blue Vender's Responsible AI and data protection requirements.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Explanation:
Explanation:
Scenario: Problem statement: The agent must adhere to strict data protection and Responsible AI standards while improving customer service efficiency and satisfaction.
Step 1: Define Data Loss Prevention (DLP) policies
Security and compliance must be established at the foundation level. Admins use the Power Platform admin center to configure DLP policies. This establishes environmental guardrails by restricting unauthorized data connectors or preventing the agent from leaking sensitive data.
Step 2: Add custom prompt modifications
Once the environment is secure, the maker configures the specific behavior of the agent. Custom prompt modifications and agent instructions shape the tone, define conversational topics, and establish explicit boundaries for the generative model (e.g., instructing the model to strictly stay within its knowledge base).
Step 3: Conduct adversarial testing
This is the final evaluation phase before deployment. After the guardrails and custom prompts are in place, you simulate real-world attacks (such as jailbreaks, prompt injections, or malicious user inputs) to verify that the agent reliably adheres to your corporate guidelines and Microsoft's Responsible AI standards.
Reference:
https://learn.microsoft.com/en-us/troubleshoot/power-platform/copilot-studio/generative-answers/agent-response-filtered-by-responsible-ai
NEW QUESTION # 62
Drag and Drop Question
A company configures an agent flow that interacts with multiple systems to complete user requests.
The company must integrate external services, retrieve data, and notify users as part of the same automated flow run. To support this scenario, the agent flow must be able to do the following:
- Call an external API.
- Retrieve stored data from a supported internal data source.
- Send a Teams message.
You need to select a connector or action type for each requirement.
What should you use? To answer, move the appropriate connectors or actions to the correct requirements. You may use each connector or 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.
Answer:
Explanation:
Explanation:
Box 1: Make an HTTPS request.
To call an external API within a Copilot agent flow, you should make an HTTPS request.
Direct API Integration: It allows the flow to send HTTP requests (GET, POST, PUT, DELETE) directly to any external REST API endpoint.
Data Retrieval & Actions: It can both fetch data from external systems and send data to trigger external processes in a single automated run.
Flexibility: It does not require a pre-built ecosystem connector, meaning you can connect to any custom or proprietary external service as long as you have the API URL and authentication details.
Box 2: Add a standard connector.
You should add a standard connector.
Standard and custom Power Platform connectors provide the communication interface required for a Copilot agent flow to read from or write to external systems in real-time. They act as wrappers around APIs, enabling the agent to securely authenticate, integrate external services, retrieve stored data from internal data sources, and trigger actions across multiple business applications within a single automated flow run.
Box 3: Trigger a notification
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/integrations
NEW QUESTION # 63
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.
Answer:
Explanation:
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/
NEW QUESTION # 64
An agent's flow-based tool intermittently fails when passed nested JSON objects as input parameters. What is the most likely cause?
- A. The environment variable is misnamed
- B. The agent has too many topics
- C. The flow trigger doesn't support the data type/schema being passed
- D. The knowledge source is offline
Answer: C
Explanation:
Power Automate flow triggers used as agent tools generally expect flat, well-defined parameter schemas; complex nested objects often need to be flattened, serialized as a string, or parsed with a Parse JSON action inside the flow.
NEW QUESTION # 65
......
Exam Questions Answers Braindumps AB-620 Exam Dumps PDF Questions: https://www.passsureexam.com/AB-620-pass4sure-exam-dumps.html
AB-620 Test Prep Training Practice Exam Questions Practice Tests: https://drive.google.com/open?id=1L4Bcn8KqLYt_8ZDCUz1LWg3ufU1kx_Yw