Microsoft AB-100 Agentic AI Business Solutions Architect Exam Practice Test

The requirement is to make sure the data ingested by the agent is clean and suitable for the intended use , which is producing monthly sentiment insights to guide product development and marketing .

The best answer is C. Identify and address biased data.

Why C is correct:

For sentiment analysis and reporting, biased data can distort conclusions and produce misleading recommendations

Data preparation should include checking for skew, unfair representation, missing segments, and other quality issues that affect downstream decisions

This aligns with responsible AI and sound analytics practice

Why the other options are not correct:

A. Ensure that the size of the database does not exceed 100 GB is unrelated to data quality or suitability

B. Translate the data into a single language might help in some implementations, but it is not universally required and is not the primary data-quality action here

D. Sort the database by customer last name has no relevance to model readiness or report quality

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answer is C. Implement version control for all the AI system components .

This question is not only about model approval. It is about creating a deployment process that allows the organization to:

review every release before production

compare current and prior versions

evaluate the impact of changes

improve business continuity if a deployment introduces risk

That makes version control for all AI system components the strongest answer.

Why C is correct

The requirement says the security and compliance team must have access to prior versions to determine exposures introduced by each release. That means the organization must be able to track, compare, and potentially roll back not just the model itself, but the broader AI solution over time.

In real enterprise AI deployments, “AI system components” usually include:

models

prompts

orchestration logic

configuration files

policies

connectors

inference code

evaluation assets

deployment definitions

If only the model is versioned, the team may miss exposure introduced by surrounding components. For example:

a prompt change could create unsafe outputs

a policy/configuration change could expose sensitive data

an orchestration update could alter transaction behavior

a connector change could affect compliance boundaries

That is why full AI system version control is the best answer. It gives security and compliance teams complete visibility into what changed across releases.

It also enhances business continuity because version control supports:

rollback to known-good versions

change auditing

release comparison

traceability

controlled recovery from faulty deployments

From an agentic AI business solutions perspective, this is the most robust governance pattern because AI outcomes are rarely determined by the model alone. They are determined by the entire solution stack.

Why the other options are less appropriate

A. Create a central model registry that uses version history

A model registry is useful, and version history helps, but this option is too narrow. The question asks about evaluating the impact of each deployment and enhancing business continuity. In enterprise AI systems, impact is often caused by more than just the model artifact. A model registry does not necessarily capture all surrounding components that affect production behavior.

B. Establish a promotion process by using a quality gate

A quality gate is valuable for approval workflows, but it does not by itself satisfy the need for deep access to prior versions across the system. It controls promotion, but it does not fully provide historical traceability and rollback coverage for all AI system components.

D. Track model retirement schedules to prevent service disruptions

This may support lifecycle planning, but it does not address the core requirement of comparing releases, reviewing prior versions, and evaluating exposure introduced by each deployment.

Expert reasoning

This question combines three ideas:

security/compliance review

access to prior versions

business continuity

When those appear together, the strongest answer is typically the one that provides end-to-end traceability and rollback across the whole solution , not just a single artifact.

That is why version control for all AI system components is the best recommendation.

So the correct choice is:

Answer: C

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

To validate prompt engineering for Microsoft Copilot Studio agents , the goal is to confirm that the agent responds correctly even when users ask the same thing in different ways, and to measure whether the responses are actually useful and correct.

For the prompt validation technique , the correct choice is Use prompts that have varied phrasing . This is a core best practice because real users do not ask questions in one fixed form. They may use different wording, sentence structure, synonyms, or levels of detail. Testing with varied phrasing checks whether the prompt design is robust and whether the agent can still produce the right response across natural language variation.

For the metric , the correct choice is Response relevance and accuracy . Since the requirement is to ensure responses are accurate and contextually relevant , this is the most appropriate measure. It directly evaluates whether the output answers the user’s need correctly and in the right context.

Why the other options are not correct:

Exclude domain-specific terminology from the prompts is not a best practice in business AI solutions. In many enterprise scenarios, domain-specific terms are essential for accuracy.

Use only simple, one-word prompts does not reflect real-world usage and would weaken testing coverage.

The number of words generated per response does not tell you whether the response is correct or contextually appropriate.

The response generation time is a performance metric, not the best metric for validating prompt 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 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

Vendor overdue invoices and outstanding balances → AI Summaries with Copilot

Review overdue invoices and payment history faster → Collections coordinator summary

This question combines two different finance-process needs inside Dynamics 365 Finance :

The first requirement is in the accounts payable / vendor context. Staff need AI-driven details to quickly understand overdue vendor invoices and outstanding balances. The best fit is AI Summaries with Copilot , because this feature is intended to surface concise, contextual summaries that help users understand finance records faster without manually opening and reviewing every transaction.

The second requirement is in the customer debt recovery / collections context. Staff need to reduce the time spent reviewing overdue invoices and payment history . The best match here is Collections coordinator summary , because it is specifically aligned to collections work and helps users quickly review the customer’s collections status, invoice aging, and payment-related context.

Why the other options are less suitable:

Agent management is administrative and not the feature that provides invoice/balance insights.

The Account Reconciliation agent is more focused on reconciliation tasks than on these specific AP and collections-review needs.

The supplier Communication agent is oriented toward supplier interaction/communication, not primarily summarizing overdue invoice and balance insight for internal review.

Analyze demand plans with Copilot is unrelated to overdue invoices or payment-history review.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

This question is about improving prompt quality so a Microsoft Copilot Studio agent gives consistent and accurate answers.

For the first prompt, “help the customer as best you can” is too vague. It does not tell the model exactly what task to perform, what boundaries to follow, or what kind of response is expected. The correct improvement is to rewrite the prompt with clear and task-specific instructions . Clear prompts reduce ambiguity and make agent behavior more predictable and repeatable.

For the second prompt, the agent is retrieving product information from a knowledge base . To keep answers accurate and grounded, the best practice is to use responses with only reference sources and limit the response scope . That ensures the model stays tied to approved knowledge and does not invent unsupported product details.

Why the other options are not correct:

Add filler words to make the prompt sound more natural and conversational does not improve accuracy or consistency.

Keep the prompt vague to enable model flexibility increases inconsistency.

Add several open-ended questions to give the model broader context can make responses less focused.

Remove the knowledge source so that the model responds freely with general product information would reduce reliability and increase hallucination risk.

Comprehensive and Detailed Explanation From Agentic AI Business Solutions Topics:

The correct answers are A. the reduced average case resolution time and D. increased employee productivity .

This question is asking for measurable business drivers for a ROAI analysis of a Copilot Studio and Power Platform solution used by operational teams.

For ROAI, the strongest business drivers are those that are:

directly attributable to the AI solution

operationally measurable

tied to business outcomes

relevant across teams

Why A is correct

Reduced average case resolution time is a strong measurable driver because it reflects a direct operational improvement in customer service and support workflows.

This metric can be quantified clearly by comparing:

baseline resolution time before AI

resolution time after deployment

That makes it ideal for ROAI because faster case resolution often leads to:

lower service cost

higher throughput

better customer experience

more efficient staffing

Why D is correct

Increased employee productivity is another core ROAI driver because AI solutions in sales, marketing, and customer service are often deployed specifically to reduce manual work and improve output per employee.

This can be measured through indicators such as:

more tasks completed per agent or employee

reduced manual effort

increased throughput

faster response cycles

more time spent on higher-value work

From an AI business solutions perspective, productivity improvement is one of the most common and valid drivers in ROAI analysis.

Why the other options are incorrect

B. market capitalization

This is too broad and influenced by many external factors. It is not a practical direct business driver for evaluating the specific impact of one AI business solution.

C. economic market predictability

This is not a direct business driver created by the solution and is too external to the organization’s operational AI ROI calculation.

E. brand awareness

Brand awareness can matter strategically, but it is less directly attributable and less operationally measurable than resolution time and productivity for this kind of internal business solution.

Expert reasoning

For ROAI questions, prefer metrics that are:

operational

attributable

measurable before and after deployment

That leads to:

reduced average case resolution time

increased employee productivity

So the correct choices are:

Answer: A, D

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.

If a Copilot Studio agent that uses Dataverse is returning poor or irrelevant results, the most likely issue is weak or inconsistent grounding data.

The best corrective action is C. Verify and cleanse the Dataverse data.

Why C is correct:

Grounded AI quality depends heavily on source data quality

Incomplete, inconsistent, duplicated, outdated, or badly structured Dataverse records will lead to poor answers

Cleansing and validating the data improves both relevance and reliability without requiring unnecessary model changes

Why the other options are not correct:

A. Use an adaptive card in Agent1 Adaptive cards improve UI interaction, not grounding quality.

B. Add example user inputs to the training data of Agent1 This may help intent handling, but the issue here is inaccurate grounding from Dataverse.

D. Retrain Agent1 Copilot Studio grounding problems are usually solved by improving source data, not retraining the agent.

Enforces deployment to only approved Azure regions → Azure Policy; Provides continuous compliance verification → Microsoft Defender for Cloud

Why Azure Policy is correct

The requirement is to enforce that Azure OpenAI resources can be deployed only in approved Azure regions .

That is exactly what Azure Policy is designed to do. Azure Policy allows organizations to create and assign rules that govern resource deployment and configuration. For regional restrictions, you can define a policy that permits deployments only in allowed locations and denies deployments elsewhere.

From an AI business solutions and cloud governance perspective, Azure Policy is the right preventive control because it acts at deployment time. It helps enforce organizational standards before noncompliant resources are created.

Typical policy use cases include:

restricting allowed Azure regions

enforcing approved SKUs

requiring tags

limiting resource types

ensuring security configuration standards

This is especially important for AI deployments where geography may affect:

regulatory compliance

data residency

internal governance

customer contract obligations

Why Microsoft Defender for Cloud is correct

The second requirement is to provide continuous compliance verification of the resources.

That points to Microsoft Defender for Cloud .

Defender for Cloud continuously assesses Azure resources against security and compliance standards. It provides visibility into resource posture, identifies misconfigurations, and tracks compliance status over time.

This makes it well suited for ongoing verification because it supports:

continuous assessment

compliance dashboards

security posture monitoring

recommendations for remediation

regulatory standard mapping

In enterprise AI deployments, this is critical because governance is not only about blocking bad deployments. It is also about continuously validating that deployed resources remain compliant as environments evolve.

Why the other options are incorrect

Azure Monitor

Azure Monitor is used for telemetry, logging, metrics, and observability. It is not the primary service for enforcing allowed regions or for formal continuous compliance governance.

Microsoft Purview

Microsoft Purview focuses on data governance, data cataloging, classification, and compliance across data estates. It is not the main control for Azure resource deployment region enforcement.

Microsoft Sentinel

Microsoft Sentinel is a SIEM/SOAR platform for security analytics and threat detection. It is not the service used to enforce deployment locations, and it is not the primary tool for continuous Azure resource compliance verification.

Azure Policy for continuous verification

Azure Policy does provide compliance views, but in this question, the stronger mapping for continuous compliance verification is Microsoft Defender for Cloud , which is specifically designed for continuous security posture and compliance assessment across resources.

Expert reasoning

Use this exam pattern:

Prevent or restrict how Azure resources are deployed → Azure Policy

Continuously assess and verify cloud compliance posture → Microsoft Defender for Cloud

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.