AB-100 Agentic AI Business Solutions Architect Questions and Answers

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.

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.

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.

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

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