AB-100 Practice Questions

Verified Answer : =

Monitors AI app and agents for compliance → Microsoft Purview

Monitors performance metrics and operational health → Azure Monitor

For an Azure-based AI solution using Azure OpenAI models , the best Azure-native monitoring design is to separate:

operational and performance monitoring

compliance and governance monitoring

For performance metrics and operational health , the correct choice is Azure Monitor . It is the standard Azure-native service for collecting telemetry, tracking service health, monitoring metrics, analyzing logs, and alerting on runtime issues. This is the best fit for model and application operational monitoring with minimal development effort.

For monitoring AI apps and agents for compliance , the correct choice is Microsoft Purview . Purview is designed for compliance, governance, data protection, and policy-based oversight across data and AI-related assets. It aligns best with the requirement to monitor AI applications and agents from a compliance perspective.

Why the other options are not the best fit:

Azure API Management is for API exposure, management, and security, not primary compliance or operational monitoring.

Azure Policy is used to enforce and assess Azure resource compliance, but it is not the main tool for monitoring AI apps and agents in the broader compliance/governance sense asked here.

Azure Stream Analytics is for streaming data processing, not this monitoring scenario.

Microsoft Defender is focused on security threat detection and posture, not overall AI compliance monitoring.

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.  

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

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

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.

Agent 1 = NLU

Agent 2 = NLU and NLU+

https://learn.microsoft.com/en-us/microsoft-copilot-studio/nlu-overview

Agent1 must support simple and short phrases for a given topic . That is the classic use case for NLU in Copilot Studio. NLU is designed for standard intent recognition where users enter brief, predictable utterances tied to a topic.

This makes NLU the best fit for:

narrow topic triggering

short phrase matching

standard, non-generative agent behavior

Why Agent2 = NLU+

Agent2 must integrate with Microsoft Dynamics 365 Contact Center voice channel . For that scenario, NLU+ is the correct recommendation among the listed standard models.

NLU+ extends the standard NLU approach and is the model aligned to scenarios that need stronger language understanding support in more advanced enterprise channel integrations such as voice experiences. Since the requirement explicitly says:

use a standard model

do not use generative orchestration

NLU+ fits better than Azure OpenAI or other generative options.

For Microsoft Copilot Studio ALM across development, test, and production , the right approach is to package the app components properly and use controlled deployment in production.

A.  

D.  

Why the other options are not correct:

B.  

Move the agents between environments by using data export and import is not the recommended ALM approach for Copilot Studio components.

C.  

Manually rebuild the agents in each environment creates inconsistency and increases effort and risk.

E.  

Deploy unmanaged solutions to production would allow easier direct modification, which conflicts with the requirement to prevent direct editing in production.