AI Agent Frameworks: Copilot Studio & Well-Architected
HOTSPOT
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
Fabrikam, Inc., is a global consumer goods company that is undergoing a digital transformation initiative to migrate its entire infrastructure to the Microsoft cloud. As a key element of this cloud migration, the company will implement Microsoft Dynamics 365 Sales, moving away from the current on-premises proprietary technologies used by its business-to-business (B2B) sales team.
As part of the cloud migration, Fabrikam will adopt an AI-first approach to its business solutions and implement AI solutions, wherever possible, to streamline operations.
Problem Statements
Fabrikam's infrastructure currently relies on various on-premises systems that require sales executives to use corporate computers with physical keyboards to access business information during customer interactions. Mobile phones cannot be used for these purposes, as the systems depend on keyboard input. As a result, the sales executives spend a lot of time using keyboards to search for data on several disparate systems and file servers, rather than focusing on the customers. This affects the customer experience.
Fabrikam stakeholders are concerned that users will be hesitant to adopt AI. If the AI initiatives are NOT adopted, cost savings will never be realized. Additionally, funding for future AI initiatives will depend on demonstrating an increase in AI adoption month over month. As the AI agent initiative for the sales team will be the first for Fabrikam, the rapid adoption of the agent is a high priority.
Planned Initiatives
General
Fabrikam management has prioritized AI-driven projects to improve efficiency, customer engagement, and responsible AI adoption. The current application infrastructure is on-premises and must be migrated to the cloud to support the adoption of these technologies.
Infrastructure Migration
Fabrikam plans to migrate from its current on-premises infrastructure to a completely cloud-based topology; this will include user authentication, the security framework, and, primarily, the adoption of the services by end users.
All the data from the different systems will be consolidated into a single data source - a common data model that will use a Microsoft Dataverse environment as a single source of truth (SSOT) for the sales team.
Sales Cycle Enablement
To achieve the company's objectives, Fabrikam intends to implement the following strategies to enhance the sales cycle:
Use low-code development to create a single AI agent that has Dataverse as its core component.
Ensure that sales managers can access unanswered correspondence from prospects and intervene as appropriate.
Replace the previous proprietary software with Dynamics 365 Sales to track sales cycles and customer interactions.
Have the sales executives use Dynamics 365 Sales to track interactions for open opportunities and send follow-up communications to prospects.
Have the sales executives use handsfree headsets to interact with an AI agent when they have questions about internal policies or customer data.
Requirements
Infrastructure Migration
Fabrikam has identified the following infrastructure migration requirements:
Azure must be used for all future infrastructure workloads.
The company must follow Microsoft-recommended methodologies for infrastructure migration to the cloud.
Any created AI agents must have their return on investment (ROI) calculated to ensure that the solution will save the company money.
Sales Cycle Enablement
Fabrikam has identified the following requirements for sales cycle enablement:
The final AI agent must follow Microsoft recommendations for a conversational user experience.
A designated checklist must be reviewed to ensure that the AI agent follows Microsoft deployment recommendations for a compliant solution.
Detailed telemetry must be logged for the first created AI agent to help troubleshoot and optimize the agent during the initial AI agent adoption process.
Unexpected AI agent actions must end in an escalation to a live representative. For example, a sales executive must be rerouted to a representative if the agent cannot answer a question after two failed attempts.
The return on investment (ROI) of switching from the current process to the future process is required for stakeholder sign off.
The sales team must use Dynamics 365 Sales to correspond with prospects more quickly and efficiently than currently.
Sales managers must report on the adoption of the AI agent to key Fabrikam stakeholders on a monthly basis.
Any sensitive information, such as user IDs and names, shared via the AI agent must be tracked for future auditing.
Which framework should you use to meet the AI agent requirements for the sales cycle enablement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Community Insight
The common trap is swapping the two frameworks; candidates must recognize that Success by Design (SBD) provides the implementation methodology and checklists for Copilot Studio, while the Well-Architected Framework governs the architectural principles like conversational UX.
This question tests the selection of Microsoft frameworks for AI agent design, specifically mapping Success by Design to Copilot Studio best practices and the Power Platform Well-Architected framework to conversational user experience requirements.
Learners often select 'Power Platform Well-Architected' for both slots because it is a broader governance framework. However, the specific requirement for a 'checklist' and 'deployment recommendations' points directly to the Success by Design methodology.
Community Discussion (12 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To meet the AI agent requirements, you must map the specific needs to the correct Microsoft methodologies. The Microsoft Power Platform Well-Architected Framework is the correct choice for ensuring the agent follows Microsoft recommendations for a conversational user experience, as it defines the architectural pillars including experience optimization. Conversely, Success by Design is the project implementation methodology that provides the structured guidance, checklists, and prescriptive steps required for deploying Copilot Studio solutions compliantly.Why Other Candidate Answers Are Wrong
While the Power Platform Well-Aachitected Framework covers broad governance and security, it does not provide the specific 'checklist' or step-by-step deployment methodology associated with Success by Design. Similarly, applying Success by Design to the 'conversational user experience' requirement is incorrect because SBD focuses on the implementation lifecycle rather than the specific design principles of conversation flow, which are detailed in the Well-Architected Framework's experience optimization pillar.Community Comment Notes
Community consensus confirms this split: users note that 'Success by Design' aligns with the need for a checklist and compliance verification, while the 'Well-Architected Framework' is cited for its specific guidance on conversational UX. As one commenter noted, SBD is the 'project implementation methodology,' whereas the Well-Architected Framework offers the 'principles and best practices' for design.Official Reference
Exam Strategy
Always distinguish between 'Design/Architecture' frameworks (Well-Architected) and 'Implementation/Methodology' guides (Success by Design). If the question mentions 'checklists', 'methodologies', or 'implementation steps', think Success by Design. If it mentions 'UX principles', 'pillars', or 'architectural best practices', think Well-Architected.
Frequently Asked Questions
What is the difference between Success by Design and Well-Architected?
Success by Design is an implementation methodology providing checklists and steps for deployment. The Well-Architected Framework provides architectural principles and best practices for design and quality.
Which framework handles conversational UX guidelines?
The Microsoft Power Platform Well-Architected Framework contains the specific guidance for Experience Optimization and Conversational User Experience design.