Practice Free AB-100 Agentic AI Business Solutions Architect Exam Questions Answers With Explanation

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 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 agent Model 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 message This is too granular and is not a primary business-facing metric for ROI or adoption analysis.

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

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

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.

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.

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

The deciding factor here is that Env1 uses a customer-managed key (CMK) for encryption, while the requirement is to add Microsoft Copilot components without changing the existing security or encryption setup of that environment.

In Power Platform, Copilot and generative AI capabilities have environment-level support requirements. A CMK-enabled environment can limit or prevent the use of certain Copilot capabilities . Because of that, the clean recommendation is to place the app in a different environment that supports Copilot features , specifically one using Microsoft-managed keys , instead of changing Env1.

Why D is correct:

It allows Copilot components to be used in a compatible environment.

It avoids changing the existing encryption/security configuration of Env1 .

It satisfies the requirement that Env1’s current configuration must remain untouched.

Why the other options are not correct:

A. Duplicate App1 and republish the app in Env1 This keeps the app inside the same CMK-based environment, so it does not solve the compatibility issue.

B. Enable Copilot features for Env1 If the environment’s encryption model is the blocker, merely enabling features does not resolve that limitation.

C. Modify the data sources of App1 to make them compatible with Copilot The issue is not mainly about the app’s data sources. It is about the environment’s support and encryption configuration.

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 agent must deliver accurate and timely responses while customer data is spread across several systems:

ServiceNow

Dynamics 365 Finance

Dynamics 365 Supply Chain Management

Excel files in SharePoint Online

The most appropriate recommendation is Microsoft Power Platform connectors because they are the standard low-code integration mechanism for bringing together data and actions from multiple enterprise systems inside Microsoft Copilot Studio .

Why D is correct:

Connectors let the agent access data across different business systems

They reduce development effort compared with custom integration patterns

They help the agent ground responses on the latest data from connected sources

Why the other options are not the best fit:

A. Enable incremental indexing in Azure AI Search Useful in search-based architectures, but the core issue here is connecting multiple business systems into the agent solution.

B. Implement a model router for query handling A router helps distribute requests, but it does not solve enterprise data access and grounding across these systems.

C. Create custom prompts Prompting alone does not integrate the source systems or ensure current enterprise data access.

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.

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

use only approved connectors and services

are prevented from accessing sensitive data

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

Why B is correct:

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

limiting agents to approved connectors/services

preventing data from being exposed through unapproved or risky connector usage

Why the other options are not correct:

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

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

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