Microsoft AB-100 Agentic AI Business Solutions Architect Exam Practice Test

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answers are B. Microsoft Copilot Studio and E. Cust omer engagement hub .

This question focuses on enabling a Dynamics 365 Contact Center agent to hand off a conversation to a live customer service representative . That requires both:

the tool used to build and configure the conversational agent

the service environment where live customer engagement and routing occur

Why B. Microsoft Copilot Studio is correct

Microsoft Copilot Studio is the platform used to build, configure, and manage the contact center agent experience. It enables you to define conversation flows, escalation logic, triggers, and handoff behavior.

In this case, the requirement is specifically that the agent must be able to transfer the conversation to a live representative. Copilot Studio is where that escalation or transfer behavior is designed as part of the agent experience.

Why E. Customer engagement hub is correct

The Customer engagement hub provides the operational environment for customer service interactions and live-agent engagement within Dynamics 365. Once the AI agent determin es that escalation is required, the live representative needs an environment to receive and continue that engagement.

From a business solutions architecture perspective, this makes sense:

Copilot Studio defines the agent and transfer logic

Customer engagem ent hub supports the human service experience after transfer

Together, they satisfy the end-to-end requirement for AI-to-human handoff.

Why the other options are incorrect

A. Microsoft Foundry

Foundry supports AI model and agent development scenarios, but it is not the specific component needed for live-agent transfer in Dynamics 365 Contact Center.

C. Microsoft 365 Agents Toolkit

This is not the core component for enabling Dynamics 365 Contact Center handoff to a live service representative.

D. an Azure AI Bot Service skill

Bot skills can extend capabilities, but they are not the primary required components for enabling the standard transfer from a Dynamics 365 Contact Center agent to a live customer service representative.

Expert reasoning:

For Contact Center escalation questions, think in two layers:

agent authoring/orchestration → Microsoft Copilot Studio

human service environment / live representative experience → Customer engagement hub

So the correct choices are:

Answer: B, E

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answers are B. session information and session outcomes and E. quality of generated answers .

This scenario is focused on a knowledge base-driven Copilot Studio agent where users report t hat the agent sometimes gives inaccurate answers . The question asks which Analytics tab metrics should be used to identify the cause of those inaccuracies.

That means you need metrics that help you examine:

how the answer was generated

what happened in the conversation when the bad answer occurred

Why E. quality of generated answers is correct

This is the most direct metric for this scenario.

Because the agent is answering from a knowledge base , the problem is tied to the quality of the generated response i tself. The quality of generated answers metric helps assess whether the generated responses are relevant, useful, and accurate enough for the user’s request.

From an AI business solutions perspective, this metric is essential because it helps diagnose problems such as:

weak grounding from the knowledge source

irrelevant retrieval

poor answer formulation

hallucination-like behavior

mismatch between user question and available source content

If the issue is inaccurate answers, the first place to investigate is the quality signal tied to generated answers.

Why B. session information and session outcomes is correct

To find the cause of inaccuracies, you also need to inspect the broader conversational context. Session information and session outcomes help you se e:

what the user asked

how the agent responded

whether the conversation was resolved

whether the user abandoned, escalated, or retried

where the conversation broke down

This is important because an inaccurate answer may not come only from poor generation quality. It may also come from:

the way the user phrased the request

lack of sufficient grounding context

repeated failed attempts in a session

escalation after an unhelpful answer

patterns in unsuccessful conversations

In other words, quality of generated answers tells you about answer quality, while session information and outcomes help you understand the operational context in which those inaccuracies appear.

Together, these two give the strongest diagnostic view.

Why the other options are incorrect

A. survey results

Survey results can tell you whether users were happy or unhappy, but they do not directly help identify the cause of inaccurate knowledge-based responses. They are more of a feedback signal than a root-cause metric.

C. topic usage and topics with low resolution

This is more relevant for agents built around explicit topics and topic flows. The scenario specifically describes an agent that provides answers based on a knowledge base , so generated-answer analytics are more appropriate than topic-r esolution analysis.

D. engagement, resolution, and escalation rates

These are useful high-level operational KPIs, but they are not the best metrics for diagnosing why answers are inaccurate. They show outcome trends, not the direct cause of answer-quality issues.

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is D. Conf igure Microsoft Graph access .

Microsoft 365 Copilot grounds its responses in Microsoft 365 data through the Microsoft Graph . If employees need to query content from a subset of SharePoint Online sites and Teams using natural-language prompts, the solution must ensure Copilot can access and use the right Microsoft 365 content context through Graph-connected permissions and data access patterns.

Why D is correct

Microsoft Graph is the core data and context layer for Microsoft 365 Copilot. It connects Copilot to organizational content such as:

SharePoint sites

Teams messages and files

OneDrive content

Outlook data

calendar and collaboration context

Because the requirement is to provide contextually relevant responses in Microsoft 365 Copilot, the design must rely on the platform’s native grounding mechanism. That mechanism is Graph-based access to Microsoft 365 content.

From an AI business solutions perspective, this is the right design because it ensures:

natural-language prompts can retrieve relevant organizational knowledge

responses are grounded in authorized enterprise content

access remains aligned to Microsoft 365 permissions

employees only see content they are allowed to access

This is especially important when only a subset of SharePoint sites should be included. The relevance and security model depend on the Microsoft 365 content graph and its permission-aware access behavior.

Why the other options are incorrect

A. Build a Microsoft Power Automate desktop flow to read the SharePoint content and post the responses to Teams

This is not how Microsoft 365 Copilot should be designed for grounding enterprise content. It is overly manual, indirect, and does not provide native contextual grounding for Copilot responses.

B. Modify SharePoint settings

SharePoint settings may affect site permissions or content availability, but they do not by themselves enable Microsoft 365 Copilot’s natural-language grounding across SharePoint and Teams.

C. Create a custom REST API that crawls the SharePoint content

This adds unnecessary custom complexity and bypasses the native Microsoft 365 Copilot architecture. The requirement is best met through Microsoft Graph-based access, not by building a parallel crawler.

Expert reasoning

For Microsoft 365 Copilot questions:

if the requirement is to query Microsoft 365 content with natural language

and return contextually relevant responses from SharePoint and Teams

the key design element is usually Microsoft Graph

The requirement is to build a Microsoft Copilot Studi o agent that can securely retrieve product warranty data from a REST API while minimizing development effort .

The best choice is D. Create a custom connector in Copilot Studio and use the connector to call the API.

Why this is correct:

A custom connector i s the standard low-code way to integrate Copilot Studio with a REST API. It lets the agent call the external warranty service securely, using supported authentication methods, without requiring heavy custom development. This directly satisfies both key req uirements:

secure retrieval of warranty data

minimal development effort

Why the other options are incorrect:

A. Use a Microsoft Power Automate desktop flow to screen scrape the warranty data. Screen scraping is brittle, less secure, and unnecessary when a REST API already exists.

B. Export the agent as a managed solution and customize the agent in Power Apps. This does not directly solve secure API access and adds unnecessary complexity.

C. Add the warranty data to the Fallback topic. The Fallback topic is for unclear user input, not for live secure retrieval of external data.

Restricts access to grounding data → Microsoft Purview access policies; Restricts model fine-tuning → Role-based access control (RBAC) in Microsoft Foundry

Why Microsoft Purview access policies is correct

The grounding data is stored in Microsoft Fabric , and the requirement is to restrict access to that data to only assigned roles.

That is a data governance and access control requirement. Microsoft Purview access policies are the best fit because they are designed to govern and control access to data across enterprise data estates. In this case, they hel p ensure that only authorized roles can access the grounding data used by the agents.

From an AI business solutions perspective, grounding data is often one of the most sensitive parts of the solution because it can contain:

proprietary business knowledge

internal documents

regulated operational information

contextual data used to shape model outputs

Purview helps enforce governed access to that data layer rather than relying only on general infrastructure controls.

Why RBAC in Microsoft Foundry is correct

The second requirement is to ensure that only the AI engineering team can perform model fine-tuning .

That is an action-level platform permission requirement. The best control for that is role-based access control (RBAC) in Microsoft Foundry .

RBAC allows the organization to assign permissions based on job function, so only authorized users or groups can:

create or modify fine-tuning jobs

manage model assets

update training configurations

control deployment-related AI resources

This is the right governance pattern because fine-tuning changes model behavior and can introduce:

security risk

compliance risk

quality drift

misuse of proprietary datasets

Restricting that capability to the AI engineering team through RBAC creates a clear separation of duties.

Why the other options are incorrect

Azure AI Content Safety

This is used to detect and filter harmful content. It does not control access to Fabric grounding data.

Azure Monitor alerts

Alerts help observe activity, but they do not enforce role-based access to data.

Azure Policy compliance rules

Azure Policy is useful for enforcing resource configuration standards, but it is not the best answer for role-based access to Fabric grounding data or for limiting fine-tuning actions to a specific team.

Azure Resource Manager (ARM) resource locks

Resource locks help prevent deletion or modification of Azure resources, but they do not provide the right permission model for controlling who can perform model fine-tuning operations.

Microsoft Entra Conditional Access

Conditional Access is mainly about sign-in and access conditions, such as device, location, or risk context. It is not the best direct control for restricting fine-tuning permissions inside Foundry.

Expert reasoning

Use this exam shortcut:

Need to control access to enterprise data → think Purview access policies

Need to restrict who can perform AI platform actions like fine-tuning → think RBAC in the AI platform

So the correct mapping is:

Restricts access to the grounding data: Microsoft Purview access policies

Re stricts model fine-tuning: Role-based access control (RBAC) in Microsoft Foundry

The requirement is to secure agents in a Microsoft Power Platform environment so that they:

use only approved connectors and services

are prevented from accessing sensitive data

The correct recommendation is B. Deploy data loss prevention (DLP) policies in Power Platform.

Why B is correct:

DLP policies in Power Platform are specifically designed to control which connectors can be used together and wh ich services are allowed in an environment. They help administrators classify connectors as business or non-business and restrict unsafe data flows. This directly supports both requirements:

limiting agents to approved connectors/services

preventing data from being exposed through unapproved or risky connector usage

Why the other options are not correct:

A. Enable customer-managed keys in Microsoft Dataverse This helps with encryption control, not with restricting connector usage or preventing data movement through agents.

C. Configure Azure Monitor to capture connector activity logs Monitoring logs is useful for visibility, but it does not enforce connector restrictions or prevent sensitive data access.

D. Enable a Microsoft Dataverse audit Auditing records activity after the fact. It does not proactively block unapproved connectors or sensitive data exposure.

AI Builder lead scoring models are used to score and prioritize leads. They do not control how opportunity summaries in Dynamics 365 Sales Copilot are generated or displayed.

The requirement is specifically about customizing:

how opportunity summaries are generated , or

how they are pre sented to users

Configuring a lead scoring model affects lead qualification insights, not Copilot’s opportunity summary generation or presentation layer.

Verified Answer : =

Agent1 → Microsoft Foundry

Agent2 → Copilot in Power Apps

Comprehensive and Detailed Explanation from Agentic AI Topics:

For Agent1 , the requirement is that it must be extendable by using Semantic Kernel and connect to multiple business apps and APIs . The best fit is Microsoft Foundry because Foundry-based agents are designed for extensibility and developer-oriented orchestration, including integration patterns that work well with Semantic Kernel and external tools/APIs.

For Agent2 , the requirement is that it must connect directly to M icrosoft Dataverse and be embeddable in a Power Apps canvas app . The best fit is Copilot in Power Apps , because it is designed for Power Platform-native experiences, works naturally with Dataverse-backed app data , and is intended for embedding AI experienc es inside canvas apps .

Why the other options are not the best match:

Azure Logic Apps is for workflow orchestration, not the primary platform for building these agents.

Microsoft Copilot Studio is strong for conversational agents, but the wording here poin ts more directly to Power Apps-native embedding for Agent2 and Semantic Kernel extensibility for Agent1.

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answers are C. Use Microsoft Power Platform pipelines and D. Include the components in a solution .

This question is about implementing a proper ALM process for Copilot components in Microsoft Dynamics 365 Customer Service so they can be:

developed safely

tested consistently

promoted to production in a controlled way

That directly aligns with standard Power Platform ALM practices.

Why D. Include the components in a solution is correct

In Power Platform and Copilot-related environments, components should be packaged into a solu tion so they can be managed and transported across environments in a structured way.

Including the components in a solution enables:

dependency tracking

packaging of related assets together

environment-to-environment movement

better governance and change control

cleaner release management

From a business solutions architecture perspective, this is foundational. Without solutions, Copilot components are much harder to move consistently and govern properly across dev, test, and production.

Why C. Use Microsoft Power Platform pipelines is correct

Once the components are organized into a solution, Microsoft Power Platform pipelines provide the automated mechanism to promote them across environments.

Pipelines help with:

standardized deployments

safe promotion from development to test to production

reduced manual deployment errors

traceability of releases

repeatable and governed ALM execution

This is exactly what the question is asking for: an automated ALM process .

From an agentic AI business solutions perspective, automation in deployment is especially important because Copilot components can influence business workflows, customer interactions, and service operations. That means changes must be promoted in a disciplined and auditable way.

Why the other options are incorrect

A. Use an unmanaged solution in production

This is not recommended as a best practice for controlled enterprise production ALM. Production deployments should be governed and managed carefully, and unmanaged solutions are not the preferred pattern for that.

B. Rebuild the agents in each environment

This is inefficient, error-prone, and not an ALM best practice. It destroys consistency and traceability because each environment may end up with slight differences.

E. Store the agent transcripts in source control

Transcripts may be useful for analysis or audit in some contexts, but they are not a core ALM action for safely developing, testing, and promoting Copilot components.

Expert reasoning

For Microsoft business application ALM questions, the best-practice pattern is usually:

package artifacts in a solution

move them with Power Platform pipelines

That gives the cleanest answer for automated, governed promotion across environments.

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 requiremen ts 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 Framewor k 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. Succes s 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 g et 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 mi grate 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 organ ization’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.

The CTO wants to view available prebuilt agent templates in Dynamics 365 Suppl y Chain Management to decide which one should be prioritized for deployment. Agent management is the feature used to discover, review, and manage available agent templates and capabilities for Dynamics 365 business applications.

Why this is correct:

It sup ports discovering available prebuilt agents

It helps evaluate which agent can deliver the most business value

It aligns with the requirement to preview and assess candidate agents during the selection phase

Why the other options are not correct:

B. Immersive Home is more of an experience surface, not the primary tool for selecting prebuilt agent templates

C. Lifecycle Services (LCS) is used for environment and application lifecycle management, not for browsing Dynamics 365 AI agent templates

D. Copil ot Studio is primarily for building/customizing copilots and agents, not for selecting Dynamics 365 prebuilt Supply Chain Management agent templates

The CFO’s quarterly analysis is focused on comparing:

estimated ROI

actual measured efficiencies

actual adoption

The case study explicitly says the CFO will use the Copilot Studio agent usage estimator . For that kind of analysis, the most relevant design components are the on es that affect how the agent is used operationally and how interactions are processed.

Why C. the average session time per agent is correct:

Average session time is a practical usage and adoption indicator. It helps the CFO understand how much users are en gaging with the agent and whether the agent is reducing effort efficiently or creating long, costly interactions.

Why D. the agent orchestration method is correct:

The orchestration method affects how the agent handles requests, invokes tools, uses knowled ge sources, and consumes resources. Since this can influence both operational efficiency and cost, it is important for ROI analysis.

Why the other options are not the best fit:

A. the GPT models used for the agent Model choice can matter technically, but t he CFO’s quarterly Copilot Studio estimator-based analysis is more centered on usage and orchestration behavior than on model selection details.

B. the average characters in a chat message This is too granular and is not a primary business-facing metric fo r ROI or adoption analysis.

Verified Answer : =

To exp ose the data to the agent, create: a custom connector

Add to the agent: the MCP server

The custom agent must answer questions about product specifications and compliance information , and the case study states that the R & D department already has a custom M odel Context Protocol (MCP) server containing that information.

The best design is:

create a custom connector to expose that external capability cleanly to the low-code Copilot solution

add the MCP server to the agent so the agent can use that external kno wledge/tooling source

Why this is correct:

The MCP server already exists and contains the needed product-specification and compliance data.

In a Copilot/agent design, you need a way to expose external functionality and data in a reusable, secure way. A custom connector is the low-code integration mechanism that fits this requirement.

Then the agent can use the MCP server as the connected external capability for answering those questions.

Why the other options are not correct:

Azure AI Bot Service channel is for communication channels, not for exposing this knowledge source.

a custom OData entity is not the right pattern for integrating the existing MCP-based capability.

the Semantic Kernel is a developer orchestration framework, but the requirement emphas izes using the existing MCP technology in a low-code solution.

an event trigger is unrelated to exposing R & D specification/compliance knowledge.

a REST API is too generic here; the scenario specifically points to the existing MCP server .

a tool is close co nceptually, but the most direct answer choice tied to the existing R & D technology is the MCP server .

The custom AI agent is a low-code Copilo t Studio/Power Platform solution, but it also must integrate with Dynamics 365 Supply Chain Management and use business logic stored outside of the application . That means the ALM process must cover both the Power Platform artifacts and the Supply Chain Ma nagement extension artifacts.

Why D. a Microsoft Power Platform solution is correct:

Copilot Studio agents are packaged and moved across environments through Power Platform solutions

This is the standard ALM container for the custom agent and related low-code components

Why A. an X++ model is correct:

In Dynamics 365 Finance and Supply Chain Management, custom business logic is packaged as part of an X++ model

Since the agent must use Supply Chain Management business logic stored outside the app, that logic belongs in the Dynamics 365 application ALM path

Why the other options are not correct:

B. a ZIP package is too generic and not the standard ALM artifact for this scenario

C. an Azure package is not the core artifact type described in the case

E. a Cloud Scale Unit (CSU) package is mainly for Commerce-specific deployment scenarios, not this custom Supply Chain Management agent requirement

The custom AI agent must select topics based on a description of the purpose of the query , rather than relying on fixed trigger phrases . That is exactly the scenario where generative orchestration is the right configuration.

Why B is correct:

It enables the agent to choose the best topic, tool, or action based on the semantic meaning of the user’s request

It supports more conversational interactions

It aligns directly with the requirement that topic selection should not depend on trigger phrases

Why the other options are not correct:

A. Azure OpenAI reasoning models concerns model capability, not topic-routing behavior in Copilot Studio

C. classic orchestration relies more on predefined topics and t rigger phrases

D. AI-assisted evaluators are for assessment/testing, not runtime orchestration

The CEO’s responsibility is to ensure that all AI solutions adhere to industry-standard responsible AI practices . The case study also explicitly says the CEO wants a quarterly assessment that must verify:

reliability

interpretability

fairness

compliance

The best recommendation is D. the Responsible AI dashboard .

Why this is correct:

The Responsible AI dashboard is the Microsoft-recommended capability for evaluating AI systems against responsible AI dimensions such as fairness, interpretability, error analysis, and model behavior assessment. It aligns directly with the CEO’s governance-focused responsibility.

Why the other options are not the best fit:

A. Compliance Center focuses more broadly on Microsoft 365 compliance and governance, not full responsible AI evaluation dimensions like fairness and interpretability.

B. Microsoft Foundry Tools is too broad and not the specific assessment tool for responsible AI measurement.

C. the Microsoft Service Trust Portal provides compliance documentation and trust information, but it does not assess Contoso’s AI solutions for fairness and interpretability.

E. Microsoft Purview is strong for data governance, classification, compliance, and auditing, but it is not the dedic ated Microsoft tool for responsible AI evaluation across those four dimensions.

Verified Answer : =

CFO concerns about Copilot Studio credit usage → Effectiveness

CTO concerns about poor feedback on AI agent responses → Satisfaction

Comprehensive and Detailed Explanation from Agentic AI Topics:

The correct mapping is based on what each executive is trying to measure in Copilot Studio analytics .

For the CFO , the concern is about abandoned interactions compared to resolved conversations and whether Copilot Studio credits are being used efficiently. That aligns with Effectiveness , because effectiveness metrics focus on c onversation outcomes such as whether interactions are successfully resolved or dropped before completion.

For the CTO , the concern is specifically about user feedback on the quality of AI agent responses . That maps to Satisfaction , because satisfaction met rics capture user sentiment and feedback about the interaction quality.

Why the other metrics are not the best fit:

Use is more about adoption and interaction volume.

Tool use focuses on how often tools/actions are invoked, not on abandonment versus resolution or feedback quality.