10 free Microsoft AB-620 practice questions with the correct answer and a full explanation for each, taken from the CertStash pack of 84 questions. Work through them, then open each answer to check your reasoning.
Get all 84 questions (US$39) · Download these 10 as a PDF
Question 1
Show the case study this question is based on
CASE STUDY
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study -To display the first question in this case study, select the "Next" button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the "Question" button to return to the question.
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 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 polic-ompliant 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.
Show answer and explanation
Correct answer: A, D
A. Configure prompt modifications to enforce tone, disclaimers, and refusal behavior at the system level. D. Configure Power Platform DLP policies to restrict unauthorized data connectors. Before deploying the agent to public and internal channels, you must configure syste-evel controls to ensure compliance across all deployments. Prompt modifications enforce tone, disclaimers, and refusal behavior consistently across generative responses without manual edits to individual topics, addressing the requirement that 'manual edits to individual topics must be avoided.' Power Platform DLP policies restrict unauthorized data connectors, enforcing the security requirement that 'Power Platform DLP policies must be enforced to block unauthorized data flows.' These actions prevent non-compliant deployments by establishing governance before the agent goes live.
Why the other options are wrong
- B. Manually adding disclaimers to each topic violates the explicit requirement to avoid manual edits to individual topics and doesn't scale across channels.
- C. Channel-level settings alone cannot enforce content moderation; system-level Responsible AI filters must be enabled before deployment.
- E. Filters must be enabled before publishing, not after, and they should be configured system-wide, not individually per channel.
Question 2
Show the case study this question is based on
CASE STUDY
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study -To display the first question in this case study, select the "Next" button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the "Question" button to return to the question.
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 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 polic-ompliant 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 Blue Yonder Copilot agent's responses in accordance with the company's content control and platform requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Show answer and explanation
Correct answer: B, C
B. Configure prompt instructions that include disclaimer text. C. Use Markdown syntax within response content. To configure responses in compliance with platform and content control requirements, you must use prompt instructions to include disclaimer text at the system level, ensuring consistent application across all generative responses without manual topic edits. Markdown syntax must be used for formatting responses because the platform constraint explicitly states 'Markdown must be used for formatting; HTML is not supported.' These two actions together meet the requirement of consistent disclaimers applied through system-level mechanisms while adhering to technical platform constraints.
Why the other options are wrong
- A. Adding disclaimers inside individual topics violates the requirement to avoid manual edits and doesn't scale efficiently.
- D. HTML is explicitly not supported in Copilot Studio; only Markdown formatting is permitted.
- E. Duplicating disclaimer text across topics violates the requirement to avoid manual edits to individual topics and creates maintenance issues.
Question 3
Show the case study this question is based on
CASE STUDY
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study -To display the first question in this case study, select the "Next" button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the "Question" button to return to the question.
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 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 polic-ompliant 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.
Show answer and explanation
Correct answer: A, D
A. Use a Microsoft Graph connector to index the partner's travel advisory content. D. Add the internal policy documents as a knowledge source. To configure the agent with internal and external knowledge sources while meeting the requirement to use 'scalable methods for knowledge integration' and not rely on manually authored Q&A topics, you must add internal policy documents as a knowledge source, enabling automatic indexing of unstructured content from SharePoint. Using a Microsoft Graph connector indexes partner travel advisory content from external sources, providing scalable integration without manual Q&A creation. These two actions implement knowledge integration as specified in the technical requirements without the inefficient approach of creating individual Q&A pairs.
Why the other options are wrong
- B. Creating individual Q&A pairs for each document contradicts the explicit requirement to not rely on manually authored Q&A topics and lacks scalability.
- C. Unrestricted web search is not mentioned as a requirement and would bypass the controlled knowledge sources the company has configured.
Question 4
Show the case study this question is based on
CASE STUDY
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study -To display the first question in this case study, select the "Next" button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the "Question" button to return to the question.
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 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 polic-ompliant 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.
Show answer and explanation
Correct answer: B, C
B. Add a prompt modification in the generative answers node settings. C. Create a disclaimer topic that always runs first. To ensure every AI-generated response includes a disclaimer while meeting governance policies, you must add a prompt modification in the generative answers node settings, applying the disclaimer at the system level to all generative responses without manual topic edits. Additionally, creating a disclaimer topic that always runs first provides an alternative mechanism ensuring the disclaimer appears in every conversation flow. Together, these actions guarantee compliance across all response types and channels as required by the compliance mandate.
Why the other options are wrong
- A. A greeting message only appears at conversation start and doesn't ensure disclaimers appear in every AI-generated response throughout the conversation.
- D. Disabling generative answers contradicts the requirement to use generative capabilities while ensuring compliance.
- E. Editing every topic's first message violates the requirement to avoid manual edits to individual topics and lacks scalability.
Question 5
An agent calls a flow. The agent requires structured output values to be returned.
The agent receives unexpected or empty values.
You need to configure the agent so that data is exchanged correctly between the agent and the flow.
What should you do?
Show answer and explanation
Correct answer: A. Validate parameter definitions.
When an agent receives unexpected or empty values from a flow, the root cause is typically misaligned parameter definitions between the agent's call and the flow's trigger schema. Validating parameter definitions ensures that the agent is correctly passing data that matches what the flow expects to receive, resolving the data exchange problem at the interface level.
Why the other options are wrong
- B. Changing the trigger schema may fix the issue but validation of existing parameters is the diagnostic step to identify what mismatch exists.
- C. Reviewing flow run history shows what happened but doesn't resolve the parameter definition mismatch causing empty values.
- D. Parse JSON is for processing data within a flow, not for correcting agent-to-flow parameter passing.
- E. Republishing the agent doesn't fix underlying parameter definition issues.
Question 6
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?
Show answer and explanation
Correct answer: C. Configure knowledge sources in a generative answers node.
To configure topic responses grounded in custom data sources, you must configure knowledge sources in a generative answers node, which allows the agent to retrieve information from specified data sources when generating responses. This directly implements the requirement that 'responses must be grounded in approved internal content' and 'the agent must be able to retrieve information from configured data sources in a topic.'
Why the other options are wrong
- A. Analytics reviews user behavior but does not configure data source integration for responses.
- B. A custom prompt instruction can guide behavior but does not configure actual data source connections.
- D. Adding SharePoint as a knowledge source only at the agent level does not enable topic-level grounding from multiple configured sources.
- E. Response length limits do not affect whether responses are grounded in configured data sources.
Question 7
A company is deploying an agent for employees.
The company has the following requirements:
Access must be restricted to the internal employees only.
End-user authentication must be enforced.
You need to configure the agent based on the company requirements.
What should you do?
Show answer and explanation
Correct answer: A. Select Authenticate with Microsoft Entra ID for the agent.
To restrict access to internal employees only and enforce end-user authentication, selecting 'Authenticate with Microsoft Entra ID' ensures that only users with valid organizational credentials can access the agent, meeting both the access restriction and authentication enforcement requirements for an internal deployment.
Why the other options are wrong
- B. Secure Access in the Web channel is for HTTPS enforcement, not for enforcing employee-only authentication.
- C. Publishing as a public website experience removes access restrictions and contradicts the requirement to limit access to internal employees.
- D. Personal account authentication allows external users and does not restrict access to employees only.
Question 8
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 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.
Show answer and explanation
Correct answer: C, E
C. Export the unmanaged solution that contains the agent. E. Create a custom solution and add the existing agent to the solution. To prepare an existing agent for production deployment using the solution-based approach, you must first create a custom solution and add the existing agent to that solution, establishing the exportable container. Then you export the unmanaged solution, which packages the agent and all its components in a format that can be imported into the production environment. This is the supported method for moving agents between environments.
Why the other options are wrong
- A. Removing agent topics from the solution would break the agent and prevent successful export.
- B. Converting to a managed solution is not necessary for export; unmanaged solutions are the standard export format.
- D. Publishing to a channel and exporting channel configuration is not the solution-based approach for environment migration.
Question 9
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
An agent uses a flow that calls an external service which can occasionally fail or time out.
When a failure occurs, the agent must meet the following requirements:
Must not terminate silently.
Must send a notification containing the error details.
You need to configure the agent flow so that failures are handled in a controlled and predictable way.
Solution: Retry the failing action without handling failure.
Does the solution meet the goal?
Show answer and explanation
Correct answer: B. No
Retrying a failing action without handling failure does not meet the stated requirements. The requirements explicitly state that the flow must not terminate silently and must send a notification containing error details. Simply retrying without implementing failure handling paths and notification logic leaves the agent vulnerable to silent termination and provides no mechanism to send error notifications. A controlled and predictable failure handling approach requires explicit error handling configuration, not just retries.
Why the other options are wrong
- A. Retrying without failure handling does not satisfy the requirement to send error notifications and prevent silent termination.
Question 10
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
An agent uses a flow that calls an external service which can occasionally fail or time out.
When a failure occurs, the agent must meet the following requirements:
Must not terminate silently.
Must send a notification containing the error details.
You need to configure the agent flow so that failures are handled in a controlled and predictable way.
Solution: Configure run after conditions for failure paths.
Does the solution meet the goal?
Show answer and explanation
Correct answer: A. Yes
Configuring run after conditions for failure paths directly enables controlled and predictable failure handling. This approach allows the flow to specify actions that should execute when the external service call fails, which provides the foundation needed to send notifications with error details and ensure the flow does not terminate silently. Run after conditions on failure paths are the standard mechanism in Power Automate and Copilot Studio for implementing failure-specific workflows.
Why the other options are wrong
- B. Run after conditions for failure paths are the appropriate mechanism for handling failures in a controlled manner.
That was 10 of 84.
The full Microsoft AB-620 pack has all 84 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. US$39, paid once, with free monthly updates and a pass-or-your-money-back guarantee.