DRAG DROP (Drag and Drop is not supported)You are designing end-to-end test scenarios for a business solution that uses Microsoft Dynamics 365 Sales and Dynamics 365 Finance.You need to ensure that the business solution meets the following test requirements:Properly exchanges data between the Dynamics 365 appsAligns with defined user workflows and business processesWhich type of testing should you use for each requirement? To answer, drag the appropriate testing types to the correct requirements. Each testing type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Answer(s): A
Box 1: IntegrationProperly exchanges data between the Dynamics 365 appsFor a project involving Dynamics 365 Sales and Dynamics 365 Finance, the best testing type to verify proper data exchange is Integration Testing, specifically within a System Integration Testing (SIT) phase.Integration TestingThis is the primary method for validating that data flows correctly between Sales (Customer Engagement) and Finance (Finance & Operations).Purpose: Ensures seamless information flow, communication protocols, and data synchronization. Example Scenario: Creating a new Account in D365 Sales and verifying it automatically triggers the creation of a Customer in D365 Finance via Dual-write.Box 2: User acceptanceAligns with defined user workflows and business processesThe best testing type to ensure a Microsoft Dynamics 365 solution aligns with defined user workflows and business processes is User Acceptance Testing (UAT).While other testing phases (like Functional or Integration) verify that the system works technically, UAT is the final "road test" where the business confirms that the solution actually supports their day-to-day operations.
https://community.dynamics.com/blogs/post/?postid=a4d91139-67c5-4746-9451-064b87d15d96https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp- implementations/
A company has a Microsoft 365 tenant in Canada and multiple Microsoft Power Platform environments in Canada and the United States.The company plans to deploy a Microsoft Copilot Studio agent to the Canadian environment that will use:Microsoft Dataverse data stored in CanadaA connector that connects to an Azure OpenAI instance in the United StatesYou need to ensure that the agent adheres to data residency and data movement policies before being deployed.What should you do?
Answer(s): D
Manage Cross-Geo Data Movement SettingsBecause your agent in Canada connects to Azure OpenAI in USA, data will leave your primary geography.Explicit Opt-in: You must navigate to the Power Platform Admin Center and explicitly allow data movement across regions for generative AI features.Regional Scope: If this toggle is off, Copilot features requiring the external Azure OpenAI instance will be disabled to protect residency.Security Assurance: Microsoft does not log or retain prompt/response data during this cross-region transit for the purpose of training foundation models.
https://ragnarheil.de/mastering-microsoft-copilot-studio-data-loss-prevention-and-governance-tips
HOTSPOTA company has a Microsoft Copilot Studio agent for customer support.You are reviewing and validating the following prompts:A prompt that has instructions to "help the customer as best you can"A prompt that helps retrieve product information from a knowledge baseYou need to ensure that the agent delivers consistent and accurate responses.What should you do for each prompt? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Rewrite the prompt with clear and task-specific instructions.To ensure a Microsoft Copilot Studio agent delivers high-quality support, you must move beyond vague instructions like "help as best you can." Generative AI requires constraints, structured data, and persona definitions to remain consistent.Here is how to optimize your agent for accuracy and reliability:Refine the System PromptA vague prompt leads to "hallucinations" (made-up facts). Replace the general instruction with a Persona and Boundary script.Define the Persona: "You are a professional Support Specialist for [Company Name]. Your tone is empathetic, concise, and helpful."Set Boundaries: "Only answer questions based on the provided uploaded documents. If the answer is not in the documentation, politely state you don't know and offer to connect to a human."Establish Steps: "Always greet the user, identify their core issue, and provide a step-by-step solution."Box 2: Use responses with only reference sources and limit the response scope. To ensure your Microsoft Copilot Studio agent remains grounded, accurate, and avoids "hallucinations," you must configure the System Prompt to enforce strict grounding. This tells the AI to act only as a retrieval tool rather than a general-purpose assistant.Restrict Search Scope:In the Generative Answers node, ensure "Search only selected sources" is toggled on. Upload specific PDFs, Manuals, or SharePoint folders rather than using the entire public web.
https://www.sbtpartners.com/how-to-have-the-best-copilot-conversations https://blog.prodwaregroup.com/artificial-intelligence/microsoft-copilot-studio-explained/
HOTSPOTYou are designing a testing solution for Microsoft Copilot Studio agents.You need to validate prompt engineering best practices to ensure that the agents generate accurate and contextually relevant responses.Which prompt validation techniques and metrics should you include in the solution? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Use prompts that have varied phrasingHere is why this technique is superior to the others for validating prompt engineering best practices:Robustness and Generalization: Using varied phrasing (synonyms, different sentence structures) tests whether the agent understands the underlying intent rather than just matching keywords. This ensures the agent is not brittle and can handle real-world user queries that vary in phrasing.Best Practice Validation: Microsoft encourages testing agent responses by iterating and refining prompts.Testing with variations helps identify if a prompt is too rigid or if it correctly captures the context.For a comprehensive validation strategy, this technique is typically paired with Batch Testing, where you upload a set of varied test cases to evaluate the AI's consistency and accuracy.Incorrect:* Exclude domain-specific terminologyThis is incorrect. Effective prompting often requires using domain-specific terms to ensure the AI understands the specialized context.* Use only simple, one-word promptsThis is ineffective. Simple prompts lack the context required for high-quality, accurate responses.Box 2: Response Relevance and accuracyBy using Response Relevance and Accuracy as your primary metrics, you ensure the agent remains grounded in its knowledge sources while remaining flexible to user intent.
https://support.microsoft.com/en-us/topic/learn-about-copilot-prompts-f6c3b467-f07c-4db1-ae54-ffac96184dd5 https://www.microsoft.com/en-us/microsoft-copilot/blog/copilot-studio/build-smarter-test-smarter-agent- evaluation-in-microsoft-copilot-studio
A company has two Microsoft Power Platform environments named Dev1 and Prod1. A Microsoft Copilot Studio agent named Agent1 is built into a solution in the Dev1 environment.You plan to deploy Agent1 to Prod1.You need to make Agent1 available to the users in Prod1. The solution must minimize administrative effort.What should you do?
Answer(s): C
To deploy a Microsoft Copilot Studio agent to a second environment while minimizing administrative work, you should use managed solutions and Power Platform Pipelines (or manual export/import if pipelines are not configured).Follow these steps to move and share the agent effectively:1. Prepare the Solution (Source Environment)Since your agent is already in a solution, ensure all its dependencies are included to avoid "missing component" errors during import.2. Export and ImportTo minimize manual labor, use a Managed Solution for the target environment. Managed solutions are easier to update or remove later and prevent accidental direct edits in production.
https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-solutions-import-export
A company has a Microsoft Power Platform environment that contains Microsoft Dataverse data.You create a Microsoft Copilot Studio agent named Agent1 that processes the Dataverse data.You discover that Agent1 fails to return relevant or accurate results.You need to improve the quality and reliability of data grounding.What should you do?
Answer(s): B
To improve the reliability and accuracy of a Microsoft Copilot Studio agent grounded in Dataverse, you must focus on Dataverse data preparation, which includes cleaning, structuring, and enriching the data to ensure the agent retrieves relevant information. When Copilot fails to return accurate results, it is often due to poor data quality (garbage in, garbage out), excessive, unstructured data, or misconfigured search indexing.
https://dev.to/farahkim/the-dark-side-of-building-ai-agents-on-poor-data-quality-l18
A company plans to deploy a Microsoft Copilot Studio agent to enhance customer support.The company stores customer data across ServiceNow, Microsoft Dynamics 365 Finance, Dynamics 365 Supply Chain Management, and Excel files in SharePoint Online.You need to recommend a solution to ensure that the agent can deliver accurate and timely responses.What should you recommend?
To deploy a Microsoft Copilot Studio agent that delivers accurate responses from ServiceNow, Dynamics 365 (F&O), and SharePoint, you should centralize your data in Azure AI Search and implement incremental indexing to capture updates in real-time or on a schedule.Immediate Solution: Enabling Incremental IndexingIncremental indexing ensures only new or modified records are processed, reducing latency and cost.High-Water Mark Detection: Configure your indexers to use a "high-water mark" policy based on a last_modified timestamp field from your sources (ServiceNow/Dynamics).Change Tracking: For ServiceNow and Dynamics 365, use the native change tracking features in their respective connectors to signal the indexer which records have changed.SharePoint Incremental Crawling: The Azure AI Search SharePoint indexer (currently in preview) automaticallysupports incremental crawling, detecting changes in Excel files by tracking the file's metadata.Incorrect:[Not C]Microsoft Power Platform connectors does not cover all the data sources.Architecture OverviewYour agent will use three primary integration methods:Knowledge Base Connectors: For high-volume unstructured data (SharePoint, ServiceNow KB).Power Platform Connectors: For structured, real-time data (Dynamics 365, ServiceNow Incidents).Virtual Entities: For native integration with Dynamics 365 Finance & Supply Chain.
https://www.lewisdoes.dev/blog/building-copilot-studio-agents-with-azure-ai-search-and-mapped-citations/
A manufacturing company wants to deploy an agent that will automate supplier invoice processing.You are designing a solution to evaluate the financial implications of the deployment. The company is especially concerned about budget overruns.You need to ensure that the solution considers the total cost of ownership (TCO), the expected savings from using automation, and whether to extend the existing AI capabilities.What should you include in the design?
This design plan outlines the financial and operational framework for deploying a Microsoft-based AI agent for supplier invoice processing. By leveraging current industry benchmarks and Microsoft's own agentic AI frameworks, this plan focuses on maximizing Return on AI Investment (ROAI) while mitigating the risk of budget overruns.
https://www.investing.com/news/swot-analysis/microsofts-swot-analysis-cloud-and-ai-fuel-growth-but- challenges-loom-93CH-4197719
Post your Comments and Discuss Microsoft AB-100 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AB-100 content, but please register or login to continue.