AB-100 · LESSON 2

Design AI-powered business solutions25–30% · 3 topics

Learn to design AI and agents, design extensibility of AI solutions, and orchestrate configuration of prebuilt agents and apps.

2.1Design AI and agents for business solutions

Concept

Agent design decides the role (what to delegate), level of autonomy (whether people review), knowledge, tools, channels and multi-agent structure. Choose among Microsoft 365 Copilot declarative agents, Copilot Studio custom agents and Foundry agents.

How it works / steps

  1. Break down business steps and decide the split between agents and people
  2. Decide the autonomy level (suggest only, execute after approval, autonomous execution)
  3. Identify needed knowledge and tools
  4. Decide channels based on where users are (Teams, Microsoft 365 Copilot, web)
  5. Split into multiple agents when the role is large

Workplace example

In purchasing, the agent compares quotes autonomously, orders are executed after staff approval, and supplier evaluation is done by people.

Common confusions and exam tips

Mini quiz

Q1. You want a process that “detects unsubmitted expense reports at month-end and sends reminders to those people” to start automatically from a trigger. Which agent type applies?

  1. Task agent
  2. Prompt-and-response agent
  3. Autonomous agent
  4. Computer use agent
Show answer and explanation

Answer: C Autonomous agent

An agent that acts on its own from events or schedules is an autonomous agent. Designing permissions, approvals and monitoring is important. [Other options] Task agents act on user requests. Prompt-and-response agents only answer questions. Computer use is a means of operating UIs, not a type that starts automatically from triggers.

Q2. An agent only answers employees’ questions based on policies and performs no system operations. Which agent type applies?

  1. Prompt-and-response agent
  2. Task agent
  3. Autonomous agent
  4. Computer use agent
Show answer and explanation

Answer: A Prompt-and-response agent

A type specialized in answering questions. With no operations, permission design is relatively light. [Other options] Task agents involve system operations. Autonomous agents act from triggers. Computer use operates screens.

Reference links

2.2Design extensibility of AI solutions

Concept

Extensibility is designing AI solutions to connect to internal data and systems and expand their capabilities. Microsoft 365 Copilot is extended with Graph connectors (ingesting data) and API plugins (actions); Copilot Studio with connectors, MCP and OpenAPI.

How it works / steps

  1. Identify data and actions Copilot lacks
  2. Provide data via Graph connectors or knowledge, and actions via APIs, connectors or MCP
  3. Publish as reusable APIs (such as API Management) shared by multiple agents
  4. Design authentication and permissions (whether to run with the user’s credentials)
  5. Standardize common components and reuse them in future agents

Workplace example

Publish the project management system as an MCP server and use it from both the sales team’s Copilot Studio agent and the engineering team’s Foundry agent.

Common confusions and exam tips

Mini quiz

Q1. You want to automate entering order information into a partner portal that has no API. Which design option is appropriate?

  1. Connect directly to the partner’s database and build a flow that writes order information
  2. Operate the screens with Copilot Studio computer use and add confirmation steps
  3. Have a Copilot Studio agent explain the screen steps and let staff enter data by hand
  4. Use the HTTP connector in a Power Automate cloud flow to send order data directly to the portal
Show answer and explanation

Answer: B Operate the screens with Copilot Studio computer use and add confirmation steps

When there is no API, computer use is an option. Add confirmation steps to guard against misoperation. [Other options] There is no API, so HTTP sends are impossible. Direct connection to the partner’s database is not permitted. Explaining steps is not automation.

Q2. You want to provide tools from multiple internal systems to agents in a standard way and reuse them in other agents. Which design is appropriate?

  1. Provide tools with Model Context Protocol (MCP) and connect from Copilot Studio
  2. Build a Power Automate flow per system and call it individually from each agent
  3. Create a custom connector per system and configure it individually in each agent
  4. Write each system’s API specification in the agent instructions and have it call them directly
Show answer and explanation

Answer: A Provide tools with Model Context Protocol (MCP) and connect from Copilot Studio

Standardizing tools with MCP allows reuse across multiple agents. [Other options] Individually configured custom connectors or flows are not a standard way to share. Writing specifications in instructions is neither safe nor reusable.

Reference links

2.3Orchestrate configuration of prebuilt agents and apps

Orchestrate configuration for prebuilt agents and apps

Concept

Dynamics 365 and Microsoft 365 include prebuilt Copilot features and agents for sales, customer service, finance, supply chain and more. Enable and configure them, prepare data connections, permissions and business rules, and extend with Copilot Studio as needed.

How it works / steps

  1. Check available prebuilt agents and prerequisites (licenses, data)
  2. Enable features in the admin center and decide target roles
  3. Prepare quality and permissions of Dataverse and Dynamics 365 data
  4. Configure instructions, rules and knowledge to fit the business
  5. Extend missing parts with Copilot Studio and measure the effect

Workplace example

Enable case summaries and email drafts in Dynamics 365 Customer Service, improve knowledge articles and measure the change in handling time.

Common confusions and exam tips

Mini quiz

Q1. You want Dynamics 365 Sales Copilot to handle your company-specific product category names and industry terms correctly. Which design is appropriate?

  1. Replace product catalog names in Dynamics 365 Sales with generic names
  2. Tell salespeople to ask Copilot using generic terms
  3. Design business terms and customizations used by Copilot
  4. Distribute a glossary document to salespeople by email without using Copilot instructions
Show answer and explanation

Answer: C Design business terms and customizations used by Copilot

Defining business terms and customizations reflects company-specific context. [Other options] Replacing names loses business terminology. Asking in generic terms does not make Copilot understand your terms. Distributing documents is not reflected in Copilot.

Q2. You want Copilot in Dynamics 365 Customer Service to answer based on your product manuals and FAQs. Which design is most appropriate?

  1. Distribute product manual PDFs to agents and have them cross-check Copilot’s answers
  2. Configure knowledge articles and internal information sources as knowledge sources
  3. Disable Copilot and have agents search manuals and answer by hand
  4. Have agents paste the relevant parts of manuals into Copilot for every inquiry
Show answer and explanation

Answer: B Configure knowledge articles and internal information sources as knowledge sources

Customer Service Copilot can suggest answers grounded in information sources such as knowledge articles. Manage source quality and updates. [Other options] Pasting each time is laborious and causes gaps. Distributing and cross-checking does not ground Copilot. Disabling does not use Copilot.

Reference links

Lessons are written by this site based on public information and do not guarantee exam content. Product specifications change, so check the latest information at the reference links.

Notes (unofficial, original questions, no pass guarantee)