Pass the Microsoft Microsoft Certified: Agentic AI Business Solutions Architect AB-100 Questions and answers with CertsForce

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. "

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

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answers are A. Microsoft Purview and D. Microsoft Defender .

This question is asking for an enterprise security and governance design for Microsoft 365 Copilot agents . The requirements span three major control areas:

identify and mitigate AI-related risks

protect AI apps and sensitive data

retain/log interactions, detect policy violations, and investigate incidents

No single tool in the list fully covers all of those needs. The best solution is the combination of Microsoft Purview and Microsoft Defender .

Why A. Microsoft Purview is correct

Microsoft Purview is the strongest match for the requirements around:

protecting sensitive data

governance of AI usage

retaining and logging interactions

detecting policy violations

supporting investigation and compliance processes

Purview is central to Microsoft’s information protection, compliance, insider risk, auditing, and data governance capabilities. In the context of Microsoft 365 Copilot agents, Purview helps organizations:

classify and label sensitive data

apply data loss prevention controls

retain records and interactions

audit activity

investigate policy issues

support responsible AI governance practices

From an AI business solutions perspective, this is essential because copilots often process sensitive enterprise information, and organizations need visibility into how that information is used, exposed, and governed.

Why D. Microsoft Defender is correct

Microsoft Defender addresses the requirement to identify and mitigate potential risks that relate to AI use and to protect AI apps .

Defender is the broader security layer that helps monitor and protect applications, detect threats, identify vulnerabilities, and support incident response. In AI-enabled enterprise solutions, Defender helps secure the application environment and detect risk patterns that could affect AI systems or the data they use.

This is important because AI security is not only about content and compliance. It is also about:

threat detection

app protection

attack surface awareness

suspicious activity monitoring

incident investigation

Defender complements Purview by focusing more on the security posture and threat protection side of the solution.

Why the other options are incorrect

B. Azure AI Content Safety

Azure AI Content Safety is valuable for filtering harmful or unsafe AI-generated or user-supplied content. However, it does not fully address the broader requirements here around enterprise data protection, interaction retention, policy logging, governance, and incident investigation. It is useful, but not the best two-part answer.

C. role-based access control (RBAC) in Microsoft Foundry

RBAC is important for access management, but this option is too narrow and also not the best fit for Microsoft 365 Copilot agents in this question. It does not cover the required governance, retention, policy violation detection, or investigation capabilities.

Expert reasoning

A good way to solve this kind of question is to separate the requirements into two control domains:

data governance, retention, policy, compliance → Microsoft Purview

threat protection, risk mitigation, app security, investigation support → Microsoft Defender

That pairing gives the most complete answer across the listed options.

The key issue is that the agent will run in a Canadian environment and use:

Dataverse data stored in Canada

a connector to Azure OpenAI in the United States

That means data may need to move across regions . Before deployment, the organization must make sure this cross-region use is explicitly allowed under the platform’s data movement and residency controls.

That makes C the correct answer.

Why C is correct:

It directly addresses the fact that the solution uses services in different geographic regions

It ensures the environment and its connector dependencies are configured to allow that movement in line with platform policy

It is the most specific action tied to data residency and data movement compliance before deployment

Why the other options are not correct:

A. Ensure that the data processed by Azure OpenAI is stored in the United States. This does not address whether the cross-region movement itself is permitted.

B. From the Microsoft Purview portal, validate the Data loss prevention settings. DLP helps govern connector usage and data exfiltration, but the question is specifically about data residency and cross-region data movement .

D. Migrate the tenant to the United States. This is unnecessary and does not align with the stated Canadian deployment requirement.

The number of unanswered questions → Generated answer rate and quality; The number of abandoned sessions → Conversation outcomes

Why “Generated answer rate and quality” is correct

The requirement is to identify the number of questions unanswered by the agent . In Copilot Studio, unanswered-question behavior is tied to how often the agent successfully generates answers and the quality of those answers.

The Generated answer rate and quality insight is the right place to evaluate whether the agent is:

answering user questions

failing to generate answers

producing low-quality responses

missing knowledge coverage

From an AI business solutions standpoint, unanswered questions are a direct signal of knowledge gaps, grounding gaps, or prompt-response weaknesses. This is exactly what generated answer analytics are meant to surface.

Why “Conversation outcomes” is correct

The requirement also asks for the number of abandoned sessions between users and the agent.

Abandonment is a conversation-level outcome , not a reaction or survey result. The Conversation outcomes insight tracks what happened to the interaction, such as whether the conversation was:

resolved

escalated

abandoned

otherwise completed unsuccessfully

That makes it the correct metric for identifying abandoned sessions.

Why the other insights are not correct

Reactions

Reactions capture signals like positive or negative user feedback, but they do not directly measure unanswered questions or abandoned sessions.

Survey results

Survey results reflect user satisfaction feedback after interactions, but they do not directly quantify unanswered questions or abandonment counts.

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is A. Microsoft Cloud Adoption Framework for Azure .

In this scenario, Fabrikam is moving from a fully on-premises environment to a completely cloud-based topology , and the requirements explicitly state that:

Azure must be used for all future infrastructure workloads

the company must follow Microsoft-recommended methodologies for infrastructure migration to the cloud

That wording points directly to the Microsoft Cloud Adoption Framework for Azure .

The Cloud Adoption Framework is Microsoft’s primary guidance for planning and executing enterprise cloud migrations. It is not just a technical migration checklist; it is a full strategic framework that helps organizations move workloads to Azure in a structured and governed way. It covers key areas such as:

migration strategy

readiness assessment

governance

identity and security planning

landing zones

operations management

organizational alignment

adoption planning

From an AI-powered business solutions perspective, this matters because AI solutions only succeed when the underlying infrastructure is modernized correctly. Fabrikam’s goals include cloud migration, Dataverse consolidation, Dynamics 365 Sales adoption, and AI-first business operations. All of these depend on a strong Azure-based cloud foundation. The Cloud Adoption Framework helps ensure that this transformation is done in a way that is scalable, secure, and aligned to business outcomes.

Why the other options are incorrect:

B. Success by Design

This framework is mainly used for designing and implementing business applications in a way that improves adoption, usability, and solution quality. It is highly relevant for conversational experiences , application rollout, and ensuring users get value from solutions such as Dynamics 365 and Copilot-related implementations. However, it is not the primary framework for infrastructure migration to Azure .

C. Microsoft Power Platform Center of Excellence (CoE)

The CoE is used to establish governance, monitoring, best practices, and enablement for Power Platform usage across an organization. It helps manage makers, apps, flows, and adoption across Power Platform environments. While it is useful after adoption begins, it is not the framework used to migrate enterprise infrastructure to Azure .

D. Microsoft Power Platform Project Setup Wizard

This is more of a project setup and configuration aid for Power Platform implementations. It does not provide enterprise-scale migration guidance for moving an organization’s infrastructure from on-premises systems to Azure.

Expert reasoning:

When a question mentions infrastructure migration , Azure , and Microsoft-recommended methodology , the best match is almost always the Microsoft Cloud Adoption Framework for Azure . In Microsoft solution architecture and AI business transformation scenarios, this framework is the standard answer for cloud migration planning and execution.

For Microsoft Copilot Studio best practices:

???? Microsoft Power Platform Well ‑Architected Framework

Why?

Copilot Studio is part of the Power Platform.

Microsoft’s official guidance for building scalable, secure, compliant Power Platform solutions is the Power Platform Well ‑Architected Framework .

It includes governance, security, reliability, operational excellence, and cost optimization—exactly what Fabrikam needs for AI agent deployment, telemetry, compliance, and ROI.

For conversational user experiences:

???? Success by Design

Why?

Success by Design is Microsoft’s methodology for implementing Dynamics 365 and Power Platform solutions.

It includes conversational design checklists , solution blueprinting, risk assessments, and user ‑adoption strategies.

Fabrikam’s scenario emphasizes:

User adoption

Conversational UX quality

Escalation paths

Compliance

Telemetry

These are all covered in Success by Design’s structured implementation approach.

https://learn.microsoft.com/en-ca/power-platform/well-architected/experience-optimization/conversation-design