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

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.

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.

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.

In a proper ALM deployment for Microsoft Copilot Studio across development, staging, and production , you should package the agent in a way that is portable across environments while avoiding hardcoded endpoints, indexes, table targets, or credentials.

Here, Agent1 uses:

a Dataverse table: CustomerOrders

an Azure AI Search index: customer-knowledge

Because each environment has its own Dataverse tables and Azure AI Search index, the deployment package should not carry over the development environment’s live connections as fixed production settings. Instead, it should carry the agent and the references needed so the target environment can bind to its own production resources.

That is why the correct recommendation is:

Deployment package: Agent1 and references to the data sources

After deployment: Reconfigure the environment variables

Why this is correct:

Environment variables are the standard ALM-friendly way to externalize settings like:

endpoints

index names

table references

connection-related values

This supports secure handling of credentials and endpoints

It also helps minimize downtime , because production values can be switched cleanly after import without rebuilding the agent

Why the other choices are weaker:

Agent1 only would omit needed source references

The data sources only would not deploy the actual agent

Agent1 and the data source connections risks carrying environment-specific connection bindings

Agent1, the data sources, and the data source connections is too tightly coupled to the source environment and is not the best ALM design for secure cross-environment deployment

Reconfiguring only Dataverse or only Azure AI Search is incomplete because both can vary by environment

Reconfiguring Agent1 configuration is broader and less precise than using environment variables

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

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is A. Azure AI Search .

This scenario involves data coming from multiple sources:

Azure SQL database

flat files

APIs

logs

The requirement is to organize the data into a format that can be used as a knowledge source in Copilot Studio .

Why A is correct

Azure AI Search is the best answer because it is designed to ingest, index, and organize content from multiple heterogeneous data sources so that AI applications can retrieve and use relevant information effectively.

For Copilot and agent scenarios, Azure AI Search is especially useful because it supports:

unifying data from different sources

creating searchable indexes

enabling retrieval-based grounding

improving relevance for AI responses

From an AI business solutions perspective, when data is spread across structured and unstructured systems, Azure AI Search provides the retrieval layer that turns that fragmented data into a usable knowledge source.

It is much better suited than raw storage options because the question is not only about storing data. It is about organizing it for AI-driven access and use in Copilot Studio.

Why the other options are incorrect

B. Azure Data Lake Storage

Data Lake Storage is excellent for storing large volumes of raw and processed data, but by itself it does not provide the indexing and retrieval capabilities needed to make the content a strong knowledge source for Copilot Studio.

C. Azure Cosmos DB

Cosmos DB is a NoSQL operational database. It is not the primary service for consolidating and indexing multi-source business content into a knowledge source for Copilot Studio.

D. Azure Translator in Foundry Tools

Translator is for language translation, not for organizing business data into a knowledge source.

Expert reasoning

When the question asks how to make data from many sources usable as a knowledge source for an AI agent, think about the service that:

ingests

indexes

organizes

retrieves

That service is Azure AI Search .

So the correct choice is:

Answer: A

Custom knowledge sources → Must be uploaded to the agent; AI general knowledge → Must be disabled for the agent

The requirement says the solution must minimize the risk of generating inaccurate responses . In generative AI business solutions, the best way to reduce hallucinations or loosely grounded answers is to rely on approved, scoped, domain-specific knowledge rather than broad general knowledge.

That means the agent should use:

custom knowledge sources that are intentionally provided to the agent

AI general knowledge disabled , so the agent does not answer from broad open-ended model knowledge when enterprise-specific guidance is needed

In finance and operations scenarios, this is especially important because users may ask about:

internal business processes

financial controls

operational procedures

policy-specific guidance

company-configured ERP workflows

These are areas where inaccurate answers can create operational or compliance risk. Grounding the agent on uploaded custom sources provides a more controlled knowledge base.

Why custom knowledge sources must be uploaded

If the goal is in-app help and guidance for Dynamics 365 finance and operations apps, the safest and most reliable approach is to provide the agent with curated documentation such as:

internal process guides

approved SOPs

finance workflow documentation

policy documents

ERP-specific instructions

Uploading these custom knowledge sources ensures the agent answers from enterprise-approved material rather than from generic model knowledge.

From an AI governance perspective, this improves:

factual grounding

relevance

auditability

trustworthiness

alignment to company-specific processes

Why AI general knowledge must be disabled

General AI knowledge can be useful in broad assistant scenarios, but in a finance and operations help context it increases the risk that the agent may generate:

overly generic responses

answers not aligned to company policy

incorrect interpretations of internal process steps

content that sounds plausible but is not operationally correct

Because the question explicitly says to minimize the risk of inaccurate responses , the safer design is to disable general knowledge and constrain responses to approved custom sources.

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

The key issue is that the agent will run in a Canadian environment and use:

Dataverse data stored in Canada

a connector to Azure OpenAI in the United States

That means data may need to move across regions . Before deployment, the organization must make sure this cross-region use is explicitly allowed under the platform’s data movement and residency controls.

That makes C the correct answer.

Why C is correct:

It directly addresses the fact that the solution uses services in different geographic regions

It ensures the environment and its connector dependencies are configured to allow that movement in line with platform policy

It is the most specific action tied to data residency and data movement compliance before deployment

Why the other options are not correct:

A. Ensure that the data processed by Azure OpenAI is stored in the United States. This does not address whether the cross-region movement itself is permitted.

B. From the Microsoft Purview portal, validate the Data loss prevention settings. DLP helps govern connector usage and data exfiltration, but the question is specifically about data residency and cross-region data movement .

D. Migrate the tenant to the United States. This is unnecessary and does not align with the stated Canadian deployment requirement.

To improve performance → Move to a multi-agent architecture

To improve accuracy → Add a grounding data source

The current design uses a single agent and a single prompt to complete a series of tasks . That is often a bottleneck. When one agent is responsible for everything, it has to manage multiple steps, multiple reasoning modes, and multiple task transitions in one flow. This commonly leads to:

slower response times

task overload

incomplete outputs

reduced efficiency as complexity grows

Moving to a multi-agent architecture helps performance because tasks can be separated by function. For example:

one agent can handle task planning

another can retrieve domain knowledge

another can perform structured reasoning

another can prepare the final response

From an agentic AI systems perspective, decomposition improves throughput and execution quality. Instead of one overloaded agent trying to do everything, specialized agents handle narrower responsibilities. That often reduces latency in practical enterprise designs and improves the reliability of task completion.

This also addresses the symptom of incomplete results , because a multi-agent architecture can break a large workflow into smaller, controlled substeps.

Why “Add a grounding data source” improves accuracy

The agent struggles with domain-specific reasoning . That strongly suggests it lacks sufficient domain context during inference.

The best way to improve accuracy in this case is to add a grounding data source .

Grounding means giving the model access to trusted, relevant business knowledge at runtime, such as:

internal documentation

product specifications

policy manuals

knowledge bases

industry-specific reference data

This improves domain-specific reasoning because the model no longer relies only on general pretrained knowledge. Instead, it can anchor its responses in authoritative content.

From an AI business solutions standpoint, grounding is one of the most important mechanisms for improving:

factual relevance

domain accuracy

consistency

trustworthiness

explainability in enterprise contexts

When a model is inaccurate because it lacks business context, grounding is usually a better first fix than simply scaling model size.

Why the other actions are not the best fit

Add a prebuilt connector

A prebuilt connector helps with integration to systems and services, but it does not directly solve slow reasoning, incomplete output, or weak domain-specific reasoning unless the issue is specifically missing access to an external system. That is not the main problem described here.

Upgrade to a larger generative AI model

A larger model may sometimes improve reasoning quality, but it usually comes with higher cost and often slower response times , which works against the stated performance issue. It is not the best recommendation when the current agent is already slow.

Also, when domain-specific reasoning is the problem, grounding is usually more efficient and more controllable than simply choosing a larger model.

Expert reasoning shortcut

Use this exam logic:

Slow and overloaded single agent handling many tasks → move to multi-agent architecture

Weak domain-specific reasoning → add grounding data source

Need system integration → prebuilt connector

Need raw generative capability increase, but can accept more cost/latency → larger model

The key issue in this scenario is that the web app user interface changes frequently , which causes the automation to fail. The requirement also says the solution must minimize changes to the agent .

The best recommendation is Computer Use in Copilot Studio .

Why this is correct:

Computer Use is designed for UI-based automation where the agent interacts with applications much like a human would.

It is especially useful when a system does not provide a stable API or when the UI changes over time.

Compared with rigid selectors or brittle scripted automations, Computer Use is more resilient in dynamic interfaces.

This directly addresses the problem of frequent UI changes while reducing the need to constantly redesign or heavily modify the existing agent.

Why the other options are not the best fit:

A. conversation topics in Copilot Studio Topics help guide dialog and intent handling. They do not solve UI automation fragility caused by changing app screens.

B. an agent flow in Copilot Studio Agent flows help orchestrate logic and process steps, but they do not specifically solve the issue of unreliable UI interaction caused by layout changes.

D. custom models in Azure AI Studio Custom AI models are for specialized intelligence tasks, not for stabilizing web UI automation.

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 answers are B. Microsoft Copilot Studio and E. Customer engagement hub .

This question focuses on enabling a Dynamics 365 Contact Center agent to hand off a conversation to a live customer service representative . That requires both:

the tool used to build and configure the conversational agent

the service environment where live customer engagement and routing occur

Why B. Microsoft Copilot Studio is correct

Microsoft Copilot Studio is the platform used to build, configure, and manage the contact center agent experience. It enables you to define conversation flows, escalation logic, triggers, and handoff behavior.

In this case, the requirement is specifically that the agent must be able to transfer the conversation to a live representative. Copilot Studio is where that escalation or transfer behavior is designed as part of the agent experience.

Why E. Customer engagement hub is correct

The Customer engagement hub provides the operational environment for customer service interactions and live-agent engagement within Dynamics 365. Once the AI agent determines that escalation is required, the live representative needs an environment to receive and continue that engagement.

From a business solutions architecture perspective, this makes sense:

Copilot Studio defines the agent and transfer logic

Customer engagement hub supports the human service experience after transfer

Together, they satisfy the end-to-end requirement for AI-to-human handoff.

Why the other options are incorrect

A. Microsoft Foundry

Foundry supports AI model and agent development scenarios, but it is not the specific component needed for live-agent transfer in Dynamics 365 Contact Center.

C. Microsoft 365 Agents Toolkit

This is not the core component for enabling Dynamics 365 Contact Center handoff to a live service representative.

D. an Azure AI Bot Service skill

Bot skills can extend capabilities, but they are not the primary required components for enabling the standard transfer from a Dynamics 365 Contact Center agent to a live customer service representative.

Expert reasoning:

For Contact Center escalation questions, think in two layers:

agent authoring/orchestration → Microsoft Copilot Studio

human service environment / live representative experience → Customer engagement hub

So the correct choices are:

Answer: B, E

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is B. Microsoft Power Platform connectors .

In this scenario, the requirement is to enable Microsoft 365 Copilot to invoke external logic hosted in Azure services . That means Copilot needs a standardized way to call external systems, APIs, or service endpoints.

This is exactly what Microsoft Power Platform connectors are designed for.

Why this is correct:

Power Platform connectors provide a structured integration layer that allows Microsoft copilots and business solutions to interact with external services. When Azure-hosted logic is exposed through APIs, connectors can be used to make that logic callable from Copilot experiences.

This is important in AI-powered business solution architecture because copilots often need to do more than answer questions. They need to perform actions such as:

calling Azure Functions

interacting with Azure-hosted APIs

retrieving data from external business systems

triggering workflows

passing parameters into enterprise services

Connectors act as the operational bridge between the conversational interface and the external execution logic.

From an agentic AI business solutions standpoint, this is the preferred enterprise pattern because it provides:

reusability

governance

security

low-code extensibility

integration consistency across Microsoft business applications

Why the other options are incorrect:

A. Microsoft Copilot Studio skills

Skills are associated with extending agent capabilities, but they are not the primary answer when the requirement is specifically for Microsoft 365 Copilot to invoke Azure-hosted external logic. The practical integration mechanism in this case is the connector layer.

C. custom engine agents

Custom engine agents are used for more advanced orchestration scenarios where you bring your own backend agent runtime or external agent system. That is more complex than what the question asks. The question is not asking for a custom agent orchestration framework; it is asking how Microsoft 365 Copilot can invoke external Azure logic. Connectors are the more direct and appropriate solution.

Expert reasoning:

When a Microsoft exam question says:

Microsoft 365 Copilot

invoke external logic

hosted in Azure services

the safest and strongest answer is usually the integration mechanism that exposes actions cleanly to the Copilot environment. That mechanism is Microsoft Power Platform connectors .

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

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.