AB-100: Agentic AI Business Solutions Architect › Practice Assessment for Exam AB-100: Agentic AI Business Solutions Architect › Question #26624
Single Choice Moderate

Q

A company has multiple Microsoft Copilot Studio agents that create and update service desk tickets by calling an internal ITSM API.

The same ticketing actions must be shared across all agents, and the API schema changes frequently.

You need to define the ticketing actions once and have updates automatically apply to all the agents.

What should you do?

ID: #26624 Practice Assessment for Exam AB-100: Agentic AI Business Solutions Architect 8 views
Question Info
#26624Q ID
ModerateDifficulty
Practice Assessment for Exam AB-100: Agentic AI Business Solutions ArchitectTopic
Start Quiz on This Topic
 Your Answer

Choose the Best Option

Click any option to instantly check if you're correct.

  • A Add REST API calls directly inside agent topics. ✔ ✖
  • B Use the computer use tool to automate the ITSM web interface. ✔ ✖
  • C Create a separate API plugin for each agent and republish each agent when schemas change. ✔ ✖
  • D Connect each agent to an Model Context Protocol (MCP) server that publishes the ticketing tools. ✔ ✖
Correct Answer

Explanation

Objective:

2.2 Design extensibility of AI solutions

What This Item Tests:

Design agent extensibility with Model Context Protocol in Copilot Studio

Additional Reading:

Extend your agent with Model Context Protocol

Integrate agent tools by using MCP

Integrate MCP Tools with Azure AI Agents - Introduction

Rationale:

MCP enables the centralized definition and hosting of tool schemas that can be shared across multiple Copilot Studio agents. When the API changes, updates are made once on the MCP server and automatically reflected in all connected agents. Per-agent plugins, embedded REST calls, and UI automation do not provide centralized, reusable tool management.

 Continue Practice
Previous Question Next Question
 Share

Share This Question

Challenge a friend or share with your study group.

 More from This Topic

Related MCQ Questions

A company has two production agents: One is built in Microsoft Copilot Studio, and the other is built in Microsoft Foundry. Both agents send telemetry to the same Azure Monitor Application Insights resource. U... A company has a multi-agent solution built in Microsoft Foundry. The solution grounds responses in internal HR documents and uses agent tools to call internal and external systems. Security testing shows that ... A company uses Microsoft Dynamics 365 Sales with a custom model-driven app that sellers use instead of the standard Sales Hub app. The sellers cannot open the Copilot immersive experience from the custom app n... A company uses an agent built in Microsoft Foundry that retrieves internal content and invokes tools to perform actions. Security testing shows that prompt injection attacks can trigger unauthorized tool calls... A company has a Microsoft Copilot Studio agent grounded in a Microsoft SharePoint Online knowledge source. After adding new knowledge documents and updating the agent instructions, responses to the same user q... A company has a customer service agent built in Microsoft Foundry that calls an Azure OpenAI model and a knowledge API. Telemetry and online evaluation scores are sent to Azure Monitor Application Insights. Us... A company has a Microsoft Copilot Studio agent that performs browser-based automation against a legacy web app by using the Computer Use tool. When multiple users trigger the automation simultaneously, some ru... A company has a Microsoft Copilot Studio agent that generates a daily incident summary from a user-provided transcript and incident data stored in a Microsoft Dataverse table. The response must always be forma... A company has a Microsoft Copilot Studio agent that uses Azure OpenAI to generate responses and retrieves grounding data from Microsoft Dataverse. Multiple users can modify the agent's configurations, includin... A company uses Microsoft Dynamics 365 Supply Chain Management with customizations developed in Microsoft Visual Studio and stored in Azure Repos. Deployable packages are published to the Lifecycle Services (LCS...