Microsoft AB-100 Exam Questions

The Business Value Toolkit (part of Microsoft's Power Platform and AI transformation guidance) is the only option that:

Helps calculate Return on AI Investment (ROAI)

Uses metadata, telemetry, and usage analytics

Provides structured templates for value tracking, effort reduction, automation impact, and financial justification

When deploying a Microsoft Foundry agent, the platform provides built-in:

Evaluation pipelines

Baseline accuracy checks

Drift monitoring

Observability dashboards

These features allow you to validate the agent against baseline metrics BEFORE deployment, which is exactly what the question requires.

This is the only option that directly addresses:

ALM

Pre-deployment evaluation

Accuracy validation

The requirements are classic Power Platform ALM requirements:

the custom connector must be deployed consistently across environments

it should be editable only in development

The correct design choice is to add the custom connector to Solution1.

Why B is correct:

Putting the custom connector inside the solution makes it part of the ALM package

It can then be exported and imported consistently across environments

In production, when deployed properly through managed solutions, it is not freely edited there, which supports the requirement that editing happens only in development

Why the other options are not correct:

A . Share the custom connector controls access, not ALM packaging and deployment consistency

C . Create the custom connector in the default solution is not the recommended ALM approach for controlled deployment

D . Add the custom connector to GitHub may help source control, but by itself it does not satisfy Power Platform deployment packaging across environments

The scenario describes a deployed AI solution using Azure OpenAI that exhibits bias (creating disparate outcomes based on customer traits). This directly impacts the Fairness principle of Microsoft's Responsible AI framework.

Why 'Modify the system instructions' is the Correct Strategy:

Direct Control via System Metaprompts: In large language model (LLM) applications like those powered by Azure OpenAI, the system instructions (or system message) define the behavior, constraints, and tone of the model. By modifying these instructions, you can explicitly direct the model to treat all customer segments equitably and ignore specific sensitive traits when drafting marketing content.

Mitigation without Re-engineering: * Option B and D (Training/Retraining): Azure OpenAI models are foundation models. Most companies use them via API and do not have access to the original 'training dataset' to modify it. While fine-tuning is possible, it is significantly more expensive and complex than prompt engineering.

Option C (Randomization): Randomization does not solve bias; it creates inconsistency and potentially irrelevant content, violating the Reliability and Safety principle.

Alignment with Responsible AI: Microsoft's documentation on Fairness recommends 'Instructional Mitigation.' This involves adding specific rules to the system prompt, such as: 'You must ensure the tone and value proposition of the email remain consistent across all demographic groups' or 'Do not use customer traits such as age or gender to influence the core marketing message.'

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is D. Centralize the product catalog data in Microsoft Dataverse and expose the data to both agents.

This scenario is about creating a consistent, reusable, governed product data source for multiple AI systems across:

Dynamics 365 Commerce

a Power Apps inventory management solution

multiple Copilot Studio agents

That requirement strongly points to Microsoft Dataverse as the shared business data platform.

Why D is correct

Dataverse is the best fit because it provides:

a centralized business data store

a consistent schema for product catalog records

native integration with Power Platform

strong compatibility with Dynamics 365

governed access and reuse across multiple AI systems

From an AI business solutions perspective, a product catalog is core enterprise reference data. It should not be fragmented across agents or scraped from documents. It should exist as a single source of truth that can serve multiple applications and copilots.

By centralizing the catalog in Dataverse, the company gains:

consistency across apps and agents

easier maintenance

better governance

cleaner analytics and grounding

less duplication and drift

This is exactly the kind of design pattern used for scalable agentic business solutions.

Why the other options are incorrect

A . Let each agent scrape product details from Microsoft SharePoint Online libraries

This is brittle, less structured, and not ideal for maintaining a consistent enterprise product catalog. SharePoint is not the best source of truth for structured operational catalog data.

B . Store the product catalog data in a separate custom table for each agent

This creates duplication, inconsistency, and governance problems. It directly conflicts with the requirement for a consistent source across multiple AI systems.

C . Configure prompts to pull product details from the PDFs of external vendors

PDFs are a weak source for central operational product master data. This would increase inconsistency and reduce reliability.

Expert reasoning

When a question asks for a shared, consistent business data source across:

Copilot Studio

Power Apps

Dynamics 365

the best answer is usually Microsoft Dataverse.

So the correct choice is:

Answe r: D