AB-100 Sample Questions Answers

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.

This scenario is centered on Dynamics 365 service operations, with two distinct user groups:

dispatchers/staff who organize and resolve work orders

frontline technicians who perform on-site service appointments

The best two components are:

Copilot in Field Service

Dynamics 365 Field Service mobile app

Why C. Copilot in Field Service is correct:

Copilot in Field Service is designed to help service teams work more efficiently with work orders, scheduling context, task assistance, and service-related operational support. This matches the requirement to provide AI-driven assistance to help staff organize and resolve work orders.

Why D. the Dynamics 365 Field Service mobile app is correct:

Frontline workers and technicians use the Field Service mobile app while preparing for and completing appointments. That is the right surface for delivering contextual AI support in the flow of field work.

Why the other options are not the best fit:

A. Copilot in Customer Service is focused more on customer support agents than on field dispatch/service execution.

B. Copilot in Outlook is too generic and not purpose-built for field service operations.

E. Dynamics 365 Customer Service is not the primary app for technician appointment execution.

F. Copilot Service workspace is more aligned with service agents in customer support environments rather than frontline field technicians.

This scenario requires an AI solution for invoice processing across multiple systems and formats, while also allowing direct user interaction in Microsoft Teams and keeping workflow customization effort low.

The best option is Microsoft Copilot Studio and AI Builder.

Why this is correct:

AI Builder can be used for document-focused automation tasks such as extracting data from invoices and supporting structured business document processing.

Microsoft Copilot Studio can provide the conversational and workflow-driven layer, including interaction through Microsoft Teams.

Together, they support multi-step automation, including:

document analysis

extracted data handling

validation steps

routing for human review and approval

This combination also aligns with the requirement to minimize development effort, because Copilot Studio and AI Builder are low-code tools designed for rapid business solution delivery.

Why the other options are less suitable:

A. Azure Document Intelligence in Foundry Tools and Azure Logic AppsThis can handle extraction and workflow automation, but it usually requires more implementation effort and does not as naturally satisfy the Teams-centric low-code user interaction requirement as Copilot Studio does.

C. Azure OpenAI and Azure FunctionsThis is far more custom-development-heavy and does not meet the goal of minimizing workflow customization effort.

D. a SharePoint agentA SharePoint agent is too narrow for this broader multi-system invoice processing and approval workflow scenario.

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

Answer: D

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 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 ones 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 engaging 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 knowledge 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 agentModel choice can matter technically, but the 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 messageThis is too granular and is not a primary business-facing metric for ROI or adoption analysis.

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

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 WellArchitected 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 WellArchitected 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 useradoption 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

Provides effective and relevant responses → Generated answer rate and quality

Provides conversational outcomes → Topics by outcome

Why “Generated answer rate and quality” is correct

The requirement says the agent must provide effective and relevant responses. In Microsoft Copilot Studio, the metric that most directly evaluates whether the agent is successfully generating useful answers is Generated answer rate and quality.

This metric helps assess whether the prompt-and-response agent is:

returning answers consistently

producing responses that are useful

generating content of acceptable quality

handling user requests with enough relevance

From an AI business solutions perspective, response effectiveness is not just about whether the agent says something. It is about whether the generated output is meaningful, accurate enough for the scenario, and valuable to the user. That is exactly what generated answer rate and quality is designed to measure.

This metric is especially important in prompt-and-response solutions because these agents depend heavily on the quality of generated outputs rather than only predefined topic flows.

Why “Topics by outcome” is correct

The second requirement says the agent must provide conversational outcomes. The best metric for understanding whether conversations are reaching meaningful end states is Topics by outcome.

This metric helps evaluate what happens to conversations, such as whether they:

are resolved successfully

escalate

fail

abandon

complete a desired path

In enterprise AI and conversational business solutions, outcomes matter because stakeholders want to know whether the agent is actually driving the intended business result, not just generating text. A conversation can sound good but still fail operationally. Topics by outcome reveals whether the conversation reached a useful business conclusion.

For example, in a support or business-process scenario, leadership often wants to know:

how many conversations were resolved

how many required escalation

which flows underperform

where users get stuck

That is outcome measurement, and this metric aligns directly with that requirement.

Why the other metrics are not the best fit

Reactions

Reactions can provide feedback signals such as likes or dislikes, but they are not the strongest primary metric for determining whether responses are effective and relevant at a system level.

Satisfaction

Satisfaction is useful as a user sentiment metric, but it does not directly measure conversational outcomes. A user may be satisfied with tone but still not complete the intended business process.

Tool use

Tool use measures whether tools or actions are invoked, but it does not directly tell you whether responses are effective or whether conversations ended in successful outcomes.

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: =

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

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

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.