Free Microsoft AB-100 Exam Dumps Questions & Answers

Case Study 1 - Fabrikam, Inc
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.
Hotspot Question
Which components should you use to meet the sales cycle enablement requirements? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation:
Scenario:
Use low-code development to create a single AI agent that has Dataverse as its core component.
Box 1: Microsoft Copilot Studio
For AI agent creation
Scenario:
A designated checklist must be reviewed to ensure that the AI agent follows Microsoft deployment recommendations for a compliant solution.
The Microsoft tool that should be used to create the AI agent is Microsoft Copilot Studio.
It is a low-code platform specifically designed for building and managing intelligent agents that integrate with Microsoft Dataverse as a core component for storing data and providing business context. To ensure the agent follows Microsoft's deployment recommendations, users should consult the implementation checklist provided within the Microsoft Copilot Studio documentation.
Key Features of Microsoft Copilot Studio:
Low-Code Interface: Uses a graphical builder or natural language to design agent behaviors and conversation flows.
Dataverse Integration: Leverages Dataverse as the enterprise data platform to ground agents in organizational knowledge and store shared context.
Governance and Compliance: Includes built-in responsible AI features and aligns with enterprise security standards.
Multi-Channel Deployment: Allows publishing agents across Microsoft Teams, websites, and mobile apps.
Box 2: a Fallback topic
For unexpected AI agent actions.
Scenario:
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.
In a low-code environment using Microsoft Copilot Studio with Dataverse, you can ensure unexpected AI actions lead to a live representative by configuring specific system topics.
1. Configure the System Fallback Topic
The Fallback system topic triggers when the AI agent cannot match a user's intent to any existing topic or knowledge source with sufficient confidence.
Enable Fallback: In Copilot Studio, navigate to Settings > General Settings > System fallback and click Add.
Action: Edit the Fallback topic to include a Go to topic node that redirects to the Escalate system topic.
2. Implement the Escalate System Topic
The Escalate topic is the primary mechanism for handoffs.
3. Handle Errors and Infinite Loops
Reference:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/low-code-plugins-copilot-studio

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 Canada
- A connector that connects to an Azure OpenAI instance in the United
States
You need to ensure that the agent adheres to data residency and data movement policies before being deployed. What should you do?

• A.From the Microsoft Purview portal, validate the Data loss prevention settings.
• B.Ensure that the data processed by Azure OpenAI is stored in the United States.
• C.Migrate the tenant to the United States.
• D.Ensure that cross-region data movement is enabled for the Canadian environment and connector dependencies.

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?

• A.Enable incremental indexing in Azure AI Search.
• B.Create custom prompts.
• C.Implement Microsoft Power Platform connectors.
• D.Implement a model router for query handling.

Case Study 1 - Fabrikam, Inc
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 tool should you use for the prospect communication requirements in Dynamics 365 Sales?

• A.the Voice template Microsoft Copilot Studio
• B.Deep Research in Microsoft Foundry Agent Service
• C.Copilot email assist
• D.Azure AI Search

Hotspot Question
You need to design a shared prompt library that will be used across multiple business units. The solution must meet the following requirements:
- Ensure consistent AI responses with reusable formats.
- Support governance and version control.
- Minimize administrative effort.
- Minimize ongoing costs.
What should you recommend for each requirement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation:
Box 1: Define standardized prompt templates
Ensure consistent AI responses with reusable formats.
To ensure consistent AI responses across multiple business units, your shared prompt library should be built on a foundation of standardized, modular templates that balance centralized governance with unit-specific flexibility.
Box 2: Store prompts in a Git repository
Support governance and version control.
Storing AI prompts in a Git repository allows you to treat prompts as "first-class artifacts" with the same accountability and lifecycle management as source code. For an enterprise solution serving multiple business units, this approach provides the necessary structure for governance, collaboration, and scalability.
1. Repository Organization for Business Units
2. Governance and Version Control Workflow
Branching Strategy: Use a dedicated branch for each experiment or new use case (e.g., feature/marketing-seo-v2) to ensure the main branch remains stable.
Pull Requests (PRs): Mandate PRs for all changes to enable peer reviews. PRs should include descriptions of changes, linked issues, and test results.
Semantic Versioning: Apply tags (e.g., v1.0.1) to mark significant updates, allowing business units to pin their applications to specific, stable prompt versions.
Auditability: Git maintains a full historical record of who changed a prompt, what was modified, and when it occurred.
Reference:
https://www.leeboonstra.dev/prompt-engineering/prompt_engineering_guide6
https://launchdarkly.com/blog/prompt-versioning-and-management