AB-100 Microsoft Agentic AI Business Solutions Architect Free Practice Exam Questions (2026 Updated)

Verified Answer: =

To expose 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 Model 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 knowledge/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 emphasizes 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 conceptually, but the most direct answer choice tied to the existing R & D technology is the MCP server.

Verified Answer: =

CISO → Azure Resource Graph Explorer

CIO → Microsoft Purview

Comprehensive and Detailed Explanation from Agentic AI Topics:

The CISO is responsible for discovering and inventorying AI resources for auditing across multiple Azure subscriptions. The best tool for that is Azure Resource Graph Explorer, because it is designed to query Azure resources at scale across subscriptions and provide visibility into what AI-related resources exist for governance and audit purposes.

The CIO is responsible for ensuring that appropriate security labels are assigned to the data used by the AI agents. The best tool for that is Microsoft Purview, because Purview supports data governance, classification, sensitivity labeling, and compliance management across enterprise data assets.

Why the other options are not correct:

Azure Blob Storage is storage, not the primary tool for discovery/inventory or labeling governance.

Copilot Studio is for building and managing agents, not for Azure-wide AI resource inventory or enterprise data labeling.

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 trigger phrases

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

The custom AI agent is a low-code Copilot 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 Management 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 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 dedicated Microsoft tool for responsible AI evaluation across those four dimensions.

Agent 1 = NLU

Agent 2 = NLU and NLU+

https://learn.microsoft.com/en-us/microsoft-copilot-studio/nlu-overview

Agent1 must support simple and short phrases for a given topic. That is the classic use case for NLU in Copilot Studio. NLU is designed for standard intent recognition where users enter brief, predictable utterances tied to a topic.

This makes NLU the best fit for:

narrow topic triggering

short phrase matching

standard, non-generative agent behavior

Why Agent2 = NLU+

Agent2 must integrate with Microsoft Dynamics 365 Contact Center voice channel. For that scenario, NLU+ is the correct recommendation among the listed standard models.

NLU+ extends the standard NLU approach and is the model aligned to scenarios that need stronger language understanding support in more advanced enterprise channel integrations such as voice experiences. Since the requirement explicitly says:

use a standard model

do not use generative orchestration

NLU+ fits better than Azure OpenAI or other generative options.

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.

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 answer is D. a file upload.

In this scenario, the company is using Microsoft Copilot in-app help and guidance in Dynamics 365 finance and operations apps and wants to extend the business-process knowledge available to Copilot without creating new topics.

That requirement matters because the solution is not asking for topic authoring or dialog design. It is asking for an additional knowledge source that Copilot can use directly for response generation.

A file upload is the correct choice because this approach allows you to provide business-process documentation directly as knowledge content for Copilot to reference, without requiring the creation of new conversational topics. This is especially useful for internal process guides, SOPs, policy documents, and operational instructions that already exist in document form.

Why D is correct

A file upload is appropriate when:

the knowledge already exists as documentation

you want Copilot to use that content directly

you do not want to build separate topics

the source is intended for internal business-process guidance

From an AI business solutions perspective, this is a strong pattern because it speeds up enablement. Instead of modeling every internal process as a structured dialog tree, the organization can ground Copilot on uploaded documentation and let it generate answers from that knowledge source.

This is a common enterprise AI design principle:

use topics when you need controlled conversation flow or task orchestration

use knowledge sources when you need grounded answers from existing documentation

Since the requirement explicitly says must NOT add new topics, the best fit is a knowledge source such as file upload.

Why the other options are incorrect

A. Microsoft Dataverse

Dataverse is ideal for structured business data and transactional records, but this question is about adding a knowledge source for business processes in in-app help and guidance. That points more toward document-based knowledge than table-based operational data.

B. a public website

A public website can be a knowledge source in some Copilot scenarios, but here the requirement is centered on internal business-process guidance in finance and operations apps. Internal process content is more appropriately supplied through uploaded files than through a public website source.

C. Azure AI Search

Azure AI Search is useful in more advanced custom retrieval architectures, but it is not the direct built-in answer for this scenario. The question is asking for the supported knowledge-source addition without topic creation, and file upload is the simpler and more direct fit.

Expert reasoning

The deciding phrase in the question is:

“must NOT add new topics”

That means the solution should rely on knowledge grounding, not conversational authoring. Among the available options, file upload is the most direct and supported way to provide internal business-process knowledge for Copilot in this scenario.

1. Centralized Workspace for AI Models

In the evolving Microsoft AI ecosystem, Azure AI Foundry (formerly Azure AI Studio) serves as the unified, centralized workspace for developers and organizations to build, manage, and deploy AI models.

Unified Hub: It provides a single location to access the Model Catalog, manage deployments, and perform prompt engineering.

Integration: While AI Builder is the " front-end " for citizen developers in Power Automate, Azure AI Foundry is the foundational " engine room " where the underlying models (including those used by prompts) are managed and governed at an enterprise level.

Scalability: It allows organizations to host their own custom models or utilize industry-leading foundation models (like GPT-4o) which then power the downstream capabilities in the Power Platform.

2. Generating Short Overviews Without Training or Coding

To summarize large amounts of unstructured text like case notes or transcripts without manual effort, AI Builder prebuilt prompts are the specific solution.

AI Builder Prebuilt Prompts: These are ready-to-use GPT-based instructions designed for common business tasks. Specifically, the " AISummarize " prebuilt prompt is engineered to take input text and generate a concise summary automatically.

Zero Training Required: Unlike " Custom Models " which require you to provide sets of historical data to teach the AI, prebuilt prompts leverage pre-trained Large Language Models (LLMs). This meets the requirement of " no additional training or coding. "

Ease of Use: In Power Automate, you simply add the " Create text with GPT using a prompt " action and select the prebuilt summary prompt, passing it the text from your case notes or transcripts.

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 that 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 itself. 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 see:

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

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 Microsoft 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 experiences 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 points more directly to Power Apps-native embedding for Agent2 and Semantic Kernel extensibility for Agent1.

The scenario is about a Microsoft Copilot Studio agent with:

low resolution rate

high escalation rate

To identify the issue, the most appropriate place is the Analytics tab in Copilot Studio, which is built specifically to evaluate agent performance, conversation outcomes, escalation behavior, and content quality.

Why D is correct:

It provides agent-specific operational insights

It helps diagnose patterns behind poor resolution and excessive escalation

It is the native monitoring surface for deployed Copilot Studio agents

Why the other options are not correct:

A. Insights tab in Microsoft 365 admin center is not the primary place for diagnosing a Copilot Studio agent’s conversation performance

B. Copilot hub in the Power Platform admin center is more administrative/governance-oriented than agent troubleshooting-focused

C. Agent dashboard of Dynamics 365 Customer Service historical analytics is tied to Customer Service analytics, but the question asks generally about a Copilot Studio agent, so the direct tool is Copilot Studio analytics

For Microsoft Copilot Studio agents, effective prompting depends on giving the model strong guidance and continuously improving that guidance from real interactions.

C. Use clear and specific instructions in the prompts is correct because well-written prompts reduce ambiguity, improve intent interpretation, and make the agent’s behavior more reliable and consistent.

D. Regularly test and refine the prompts based on user input is also correct because prompt quality improves through iteration. Reviewing how users actually interact with the agent helps identify unclear wording, missing instructions, and failure cases.

Why the others are not correct:

A. Measure system resource usage during prompt processing is an operations/performance activity, not a prompt best practice.

B. Analyze the prompt length distribution may be interesting analytically, but it is not a primary best practice for improving agent interactions.

E. Track the duration of the average user session is a usage metric, not a prompt-engineering best practice.

Test scenario → Run task-based scenarios that involve both apps; Metric → Track the successful completion of cross-app tasks

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is D:

Test scenario → Run task-based scenarios that involve both apps

Metric → Track the successful completion of cross-app tasks

Why this test scenario is correct

The question explicitly asks for an end-to-end testing design for a Copilot Studio agent that integrates with both:

Dynamics 365 Customer Service

Dynamics 365 Sales

The required capabilities are:

coordinating tasks and data interactions across both apps

interpreting user input and returning contextually relevant outputs

That means the testing approach cannot be isolated to one app at a time. It must validate the agent’s behavior across the full multi-application business workflow.

That is why the correct test scenario is:

Run task-based scenarios that involve both apps

This kind of test validates whether the agent can successfully move through realistic business processes such as:

reading customer context from one app

updating or retrieving related sales information in the other

maintaining context through the workflow

responding appropriately based on user intent across systems

From an agentic AI business solutions perspective, this is the right design because true enterprise agent validation must focus on workflow execution, not just component-level checks.

Why this metric is correct

The best metric is:

Track the successful completion of cross-app tasks

This is the most direct way to measure whether the agent is actually achieving the intended business outcome across both Dynamics 365 applications.

Why this matters:

The requirement is about coordination across apps

The test is end-to-end

The goal is not just speed or UI consistency

The agent must complete business tasks successfully across systems

A cross-app completion metric shows whether the agent can:

understand the user’s request

maintain context

retrieve or update the right information

finish the workflow correctly across app boundaries

This is much more meaningful than measuring clicks or simple response time.

Why the other options are incorrect

A. In each app, test isolated tasks without using workflows / Measure initial prompt response time

This fails the end-to-end requirement. Isolated tasks do not validate cross-app orchestration, and response time does not prove successful workflow execution.

B. Run task-based scenarios that involve both apps / Track average click rate across both apps

The scenario part is good, but average click rate is not the right success metric for Copilot task orchestration. Clicks do not reliably measure whether the business process was completed correctly.

C. Test visual consistency across both apps / Track successful completion of cross-app tasks

The metric is good, but the test scenario is wrong. Visual consistency is a UI concern, not an end-to-end functional validation of cross-app agent behavior.

Expert reasoning

For exam questions like this:

If the requirement says end-to-end across multiple apps, choose task-based scenarios involving both apps

If the goal is business workflow success, choose a metric tied to task completion, not visual design, click rate, or raw response speed

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 conversation 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 metrics 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.

The CTO wants to view available prebuilt agent templates in Dynamics 365 Supply 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 supports 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. Copilot Studio is primarily for building/customizing copilots and agents, not for selecting Dynamics 365 prebuilt Supply Chain Management agent templates