AB-100 Agentic AI Business Solutions Architect Question and Answers

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

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

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.

For Microsoft Copilot Studio best practices:

👉 Microsoft Power Platform Well ‑Architected Framework

Why?

Copilot Studio is part of the Power Platform.

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

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

For conversational user experiences:

👉 Success by Design

Why?

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

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

Fabrikam’s scenario emphasizes:

User adoption

Conversational UX quality

Escalation paths

Compliance

Telemetry

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

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

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 requirement is to build a Microsoft Copilot Studio 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 is 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 requirements:

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.

This question separates two different kinds of agent behavior.

For orchestrating sales order fulfillment and shipping , the best fit is an Autonomous agent. That requirement involves coordinating multiple steps, making decisions across a process, and driving execution across a workflow with limited manual intervention. Autonomous agents are designed for this kind of end-to-end orchestration.

For analyzing historical data and trends to replenish stock , the best fit is a Task agent. This requirement is more focused and bounded: analyze data, identify patterns, and support a specific business function. That aligns with a task-oriented agent rather than a broad orchestration agent.

Why Prompt-and-response is not the best answer here:

It is better suited for direct user query/answer interactions

It is not the strongest fit for process orchestration or structured business analysis workflows

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.

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.

Ensure consistent AI responses → Define standardized prompt templates; Support governance and version control → Store prompts in a Git repository

The requirement says the shared prompt library must ensure consistent AI responses with reusable formats . The best way to achieve that is to create standardized prompt templates .

Standardized templates help multiple business units use the same structure for:

system instructions

response style

output formatting

safety guidance

business terminology

escalation behavior

This is important in AI-powered business solutions because prompt variability often leads to inconsistent outputs. A shared template approach creates repeatability and reduces drift across departments.

From an enterprise AI design perspective, standardized prompt templates improve:

response consistency

quality control

reusability

onboarding speed

compliance alignment

They also minimize administrative effort because teams do not need to invent new prompt structures from scratch.

Why “Store prompts in a Git repository” is correct

The requirement says the solution must support governance and version control while minimizing effort and cost.

A Git repository is the most appropriate answer because it provides:

version history

change tracking

rollback capability

collaboration support

approval workflows

auditability

This directly supports governance. It allows the organization to know:

who changed a prompt

what changed

when it changed

why it changed

That is extremely valuable for enterprise AI operations, especially when prompts influence business decisions, customer interactions, compliance behavior, or internal process automation.

Git also minimizes ongoing cost because it uses standard development and content management practices rather than requiring a separate expensive governance platform for prompt assets.

Why the other options are incorrect

Delegate department-specific prompt templates

This reduces consistency instead of improving it. Different departments creating their own templates introduces fragmentation, style drift, and governance challenges.

Maintain a prompt history

Keeping a history is useful, but it does not by itself ensure consistent reusable formats. It is more of a recordkeeping activity than a standardization mechanism.

Categorize prompts by business function

Categorization is helpful for organization and discoverability, but it does not provide version control or governance by itself.

Define standardized prompt templates for governance/version control

Standardization improves consistency, but version control specifically requires a system for tracking and managing changes. That is why Git is the better answer for the governance requirement.

Expert reasoning

A shared enterprise prompt library should usually follow this pattern:

Consistency and reuse → standard templates

Governance and versioning → Git-based repository

Low cost and low admin overhead → reuse existing tooling and centralized controls

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 Apps This 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 Functions This is far more custom-development-heavy and does not meet the goal of minimizing workflow customization effort.

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

The requirement is to evaluate the potential cost of an AI solution before deployment so the company can support a return on AI investment (ROAI) analysis .

The correct choice is C. Azure pricing calculator .

Why C is correct:

The Azure pricing calculator is used to estimate the expected cost of Azure services before implementation. For an AI solution such as sentiment analysis on customer product reviews , it helps estimate likely spending across the relevant Azure components and usage patterns. That makes it the right tool for cost forecasting as part of ROAI planning.

Why the other options are not correct:

A. Total Cost of Ownership (TCO) Calculator TCO is mainly used to compare broader infrastructure costs, often for migration or environment-level cost comparisons, not detailed service pricing estimation for a planned Azure AI solution.

B. Azure Reservations Reservations are a purchasing/discount mechanism, not the primary tool for estimating potential solution cost.

D. Azure Monitor Azure Monitor tracks operational metrics and runtime health after deployment; it is not used for pre-deployment cost estimation.

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.

Provide AI-driven insights from customer orders → AI Summaries with Copilot; Anticipate future product needs → Generative insights for Demand planning

The first requirement is to give managers AI-driven insights that surface key information from customer orders .

That aligns best with AI Summaries with Copilot , because summaries are designed to extract and present the most important information from operational records in a concise, business-friendly way. In a supply chain context, this helps managers quickly understand:

important order details

exceptions or risks

priority items

fulfillment context

notable changes or issues tied to customer orders

From an AI business solutions perspective, this is exactly the kind of feature used to reduce manual review effort and improve decision speed. Rather than reading through many order records, managers get a synthesized view of key information.

Why “Generative insights for Demand planning” is correct

The second requirement is to help planners anticipate future product needs more accurately .

This directly maps to Generative insights for Demand planning . Demand planning is the business function focused on forecasting future demand, identifying trends, and improving planning accuracy for inventory and supply decisions.

Generative insights in this area help planners by surfacing patterns, explaining forecast behavior, and supporting better forward-looking decisions about product demand.

From an agentic AI business solutions standpoint, this is the right fit because it applies AI to:

forecast interpretation

trend identification

planning support

future demand anticipation

more accurate product need estimation

Why the other options are incorrect

Workload insights with Copilot

This is not the best match for surfacing key information from customer orders . It is more associated with operational workload visibility than customer-order summarization.

Microsoft Power BI

Power BI is useful for analytics and dashboards, but the question specifically asks for a Microsoft Copilot feature to anticipate future product needs. The direct feature match is Generative insights for Demand planning .

The Customer credit and collections workspace

This is focused on finance and collections activity, not on supply chain customer-order insight summarization.

Product information management

This manages product data and attributes, not AI-driven future demand anticipation.

The Supplier Communications Agent

This is related to supplier communication workflows, not demand forecasting for future product needs.

Expert reasoning

A quick exam shortcut here is:

Surface key information from records/orders → think AI Summaries with Copilot

Anticipate future demand/product needs → think Generative insights for Demand planning

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 .