AB-620 Microsoft Designing and Building Integrated AI Agent Solutions in Copilot Studio Free Practice Exam Questions (2026 Updated)

A. Use a Microsoft Graph connector to index the partner’s travel advisory content. Microsoft 365 Copilot connectors—formerly called Microsoft Graph connectors—index non-Microsoft enterprise content into Microsoft Graph, making it available for semantic knowledge grounding and citations. Microsoft Learn: Copilot connectors

D. Add the internal policy documents as a knowledge source. The SharePoint PDFs and policy documents should be connected as agent knowledge so generative answers can retrieve and summarize the relevant content. This is scalable and avoids manually maintaining document-specific topics. Microsoft Learn: SharePoint knowledge sources

B violates the requirement to avoid manually authored Q & A topics. C could produce ungrounded responses from unapproved public sources and would not satisfy the airline’s accuracy, security, or compliance requirements.

B. Configure prompt instructions that include disclaimer text. Centralized prompt instructions apply the required disclaimer and behavioral controls consistently to generative responses. This avoids maintaining duplicate text in individual topics and reduces the risk of inconsistent compliance language. Microsoft confirms that prompt modifications can control response content, format, personality, and what the agent should or should not answer. Microsoft Learn: Prompt modification

C. Use Markdown syntax within response content. The scenario explicitly requires Markdown for formatting and states that HTML is unsupported. Markdown can provide headings, bold text, lists, and other structured presentation while remaining compatible with the target channels.

Options A and E duplicate disclaimer content across topics, creating unnecessary maintenance and inconsistent responses when the disclaimer changes. Option D violates the stated platform requirement because HTML must not be used.

Requirement

Implementation method

Let the agent decide when to run a tool based on user input.

Enable generative orchestration.

Run a specific agent flow at a defined step in a topic.

Add a tool node.

Use a connector action to retrieve data during a conversation.

Add a tool node.

Comprehensive and Detailed Explanation From [Microsoft AB-620 Study Guide]

Generative orchestration is appropriate when the agent must independently determine whether a tool is relevant to the user’s request. Copilot Studio evaluates the user’s message, conversation context, and the tool’s name, description, inputs, and outputs before deciding whether to invoke it. Microsoft documentation confirms that generative orchestration allows an agent to choose tools based on their descriptions and the current user query.

When an operation must occur at a predetermined point in an authored topic, the operation should instead be inserted explicitly by using an Add a tool node. Selecting an agent flow from that node ensures that the flow executes at that exact position in the topic rather than being selected autonomously by the orchestrator.

The same node type is used when calling a connector action. From the topic canvas, the author selects Add a tool , chooses Connector , and then selects and configures the required connector operation. Adaptive Cards present interactive information, while Question nodes collect user input; neither directly invokes flows or connectors.

Relevant study-guide area: Plan and configure agent solutions → Configure topics → Add agent flows to a topic and Add tools to a topic . See Orchestrate agent behavior with generative AI , Add tools to custom agents , and Use connectors in Copilot Studio agents .

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A Fabric Data Agent is the capability designed for questions that must be answered from governed analytical data. Fabrikam ' s backlog, SLA-risk, parts-shortage, and dispatch-delay measures already reside behind a Fabric semantic model, so delegating these requests to the data agent preserves the business definitions, relationships, and security applied in Fabric. The result can be returned in a structured form suitable for weekly operational review rather than being estimated from general model knowledge. A Foundry agent is already assigned to summarization and classification of long-form text; it is not the authoritative source for operational KPIs. An MCP server is appropriate when the user must perform a transaction, such as creating a parts request, but the question asks for performance information rather than an update. Azure AI Search supports document retrieval for policies and procedures, not calculation over the Fabric semantic model. The primary agent ' s description for the Fabric specialist should explicitly mention the supported metrics so generative orchestration consistently delegates those requests instead of attempting an unsupported generative answer. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate a Fabric data agent.

===============

A. Configure prompt modifications at the system level. Centralized instructions enforce the required tone, disclaimers, response boundaries, and refusal behavior consistently across generative responses. Microsoft documents that prompt modification can define an agent’s personality, response format, permitted subjects, and behavior when an answer is unavailable. This avoids inconsistent manual changes across individual topics. Microsoft: Prompt modification

D. Configure Power Platform DLP policies. DLP policies govern which connectors, knowledge sources, HTTP endpoints, and channels the agent may use. They should be configured and validated before publication because a policy violation can prevent the agent from being published. DLP also protects against unauthorized data movement between business and non-business connectors. Microsoft: Data policies for agents

Why the others are incorrect: B creates duplicated, inconsistent disclaimers. C incorrectly treats moderation as a web-channel setting; moderation is configured for generative behavior rather than enforced only by embedding settings. E applies safeguards after publication and assumes filters must be configured separately for every channel, which would not provide the required centralized governance.

Trace each answer to its source → Instruct the agent to cite sources in knowledge settings; Retrieve from the centralized index → Configure Azure AI Search as the grounding data source; Use an enterprise-approved foundation model → Select a model from the Foundry model catalog.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Each requirement is controlled by a different configuration layer. Source traceability is a presentation and grounding requirement, so citations must be enabled or explicitly required for knowledge-based responses. That allows users to inspect the material used to support a policy answer; it is not achieved merely by choosing a model. Centralized retrieval is provided by connecting the existing Azure AI Search vector index as the knowledge source. This preserves the curated index, semantic or vector retrieval behavior, and enterprise management of the policy corpus instead of copying documents into the agent. Model governance is handled in the prompt configuration by selecting the approved model from the Microsoft Foundry model catalog. Publishing does not automatically replace an unapproved model, and Azure AI Search does not enforce the foundation-model selection. Together, the three settings form a complete RAG path: Azure AI Search retrieves authoritative passages, the governed model produces the response, and citation settings expose provenance. The configuration should then be tested with representative policy questions to confirm that the response is grounded and that the cited source actually supports the answer. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure generative answers by using Azure AI Search with Foundry; Configure custom prompts to use the Foundry model catalog.

===============

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Fabrikam needs both reusable prompt behavior and explicit model governance. A reusable custom prompt template provides the stable summarization instructions, expected structure, and input/output contract that can be applied wherever summarization is required. Within that prompt ' s configuration, selecting the approved model from the Microsoft Foundry model catalog controls which model generates the output. These are separate controls: the template governs the task, while the model selection satisfies the approved-model requirement. Publishing only deploys the configuration already selected; it does not automatically choose or enforce an approved model. Citations are valuable for grounded policy answers but do not determine the model used for summarization. Azure AI Search is the retrieval system for indexed enterprise policy content and is not required merely to apply a long-form summarization template. The prompt should be tested with representative transcripts for completeness, classification accuracy, output schema, safety, and latency. Where Fabrikam already uses a connected Foundry agent for this specialist function, the prompt and model settings should remain owned by that component rather than being duplicated in the primary agent. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure custom prompts to use the Foundry model catalog.

===============

Policy questions → Delegate to a knowledge-focused agent; Metric requirements → Delegate to a data-access agent; Transaction requirements → Delegate to a tools-first agent.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The architecture should separate responsibilities according to the kind of work each specialist performs. Policy and procedure questions depend on retrieval from curated, indexed content and therefore belong with a knowledge-focused agent. Operational measures such as backlog, SLA exposure, and parts shortages require governed, current business data; a data-access specialist, represented in this case by the Fabric Data Agent, is the correct destination. Creating a parts request or changing a service-case status is different from answering a question: it is an authenticated transaction and should be delegated to a tools-first agent that can invoke approved MCP operations. Putting all three responsibilities into one agent would increase the number of competing tools and knowledge sources, weaken routing precision, and duplicate logic already owned by specialist teams. The selected pattern also matches Fabrikam ' s requirement that capabilities evolve independently. Clear names, descriptions, inputs, and outputs remain essential because generative orchestration uses that metadata to decide which connected agent to invoke. This division gives the primary agent a coordination role while each specialist retains its own knowledge, privileges, release lifecycle, and audit boundary. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Design multi-agent solutions in Copilot Studio.

===============

Prevent most builders from modifying shared assets → Share the component collection while controlling edit access; Reuse components without copying → Create a component collection and move the shared components into it; Limit use to the intended primary agent → Restrict the component collection to the primary agent.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A component collection is the correct reusable unit for the escalation topics, MCP definitions, and safety disclaimer. Moving those assets into one collection creates a maintained source that multiple agents can consume without copying and later diverging. Sharing the collection with teammates while controlling edit access separates use permission from modification permission, allowing agent authors to reference the assets while reserving changes for platform engineering. If a sensitive or tightly coupled collection must be usable only by one designated primary agent, the collection can be restricted accordingly. Exporting the primary agent and copying its components would recreate the duplication problem that Fabrikam is trying to eliminate, while restricting every collection to the primary agent would prevent the required cross-agent reuse. The collection should be versioned and tested after changes because a shared update can affect several consumers. Ownership, review, and release responsibilities should also be documented so that reuse does not become an uncontrolled dependency. This design provides consistency, centralized governance, and a smaller maintenance surface across the three agents. Study Guide alignment: Plan and configure agent solutions > Plan an agent solution > Plan reusable agent components.

===============

PartsOps per-user authentication → OAuth 2.0; WarrantyRules shared team credential → API key; Tool-selection context → Configure a server description that explains the MCP server ' s role.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The authentication choices must follow the identity requirements of each server. PartsOps performs attributable actions, including parts-request creation, so OAuth 2.0 is the appropriate mechanism for individual users to authorize access without sharing their credentials with the agent. That preserves user context and supports accountability for each transaction. WarrantyRules is explicitly read-only and uses a key shared by the agent team; it should therefore be configured with API-key authentication using the required header or query parameter. Applying the same authentication method to both servers would contradict the stated server designs. Authentication alone does not tell the orchestrator when a server is relevant. A concise, discriminating server description should identify PartsOps as the source for availability checks and parts-request creation and WarrantyRules as the source for warranty validation. Copilot Studio uses the names and descriptions of agents, topics, tools, and knowledge sources during generative orchestration. Accurate metadata reduces accidental calls, prevents the wrong server from handling a request, and makes the multi-agent plan more predictable during testing. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Configure MCP tools.

===============

Callable external summarization agent → Add an external agent of type Microsoft Foundry; Correct Foundry project and agent → Enter the Foundry project endpoint URL to create the connection.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The existing specialist should be connected as a Microsoft Foundry agent, not converted into indexed knowledge. A connected agent remains callable and can execute its own summarization and classification behavior when Operations Concierge delegates a matching request. During connection creation, Copilot Studio uses the Microsoft Foundry project endpoint URL to identify the project context and make the relevant agent available for selection. This is distinct from a model endpoint used directly by a custom prompt and from a knowledge-source connection used only for retrieval. Publishing the Copilot Studio agent is part of making a completed design available to users, but it is not the action that establishes the Foundry connection. Adding the Foundry output to an index would turn prior output into retrievable content and would not invoke the specialist on demand. The connected agent should receive a precise description covering long-form transcript summarization and classification, and the integration should be tested with representative inputs to confirm that delegation occurs, the correct Foundry agent runs, and the returned result is incorporated into the main conversation. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate a Foundry agent.

===============

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The first configuration check is the contract between the agent and the flow. Input and output parameter definitions must agree on name, data type, required status, and mapping. A flow can complete successfully yet return an empty value to the agent if the response field is not mapped to the declared output or if the agent expects a different type. Validating the parameter definitions therefore addresses the actual data-exchange requirement. Reviewing run history is useful for diagnosis, but it does not correct a mismatched contract by itself. Changing the trigger schema or adding Parse JSON might be necessary in a specific implementation, yet neither should be done before confirming what the caller sends and what the flow returns. Republishing cannot repair an incorrect mapping. The builder should test the flow directly with known values, inspect each action output, verify the final response action, and then test from the agent. Optional and null fields should be handled explicitly, and sensitive outputs should be minimized and protected in logs. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Add input and output parameters.

===============

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The Service Desk Agent must be both published and available for connections from other agents. Publishing establishes a runtime version that the primary agent can call; an unpublished draft is not a valid connected-agent target. On the Service Desk Agent, the setting that allows other agents to connect and use it must also be enabled. Microsoft additionally requires the connected agent to be in the same environment and the maker to own it or have it shared, but those conditions are not offered as choices. Replacing the agent with an MCP server would discard the existing agent ' s orchestration and ticket-routing logic. Adding it as a knowledge source would expose content for retrieval, not delegate an IT request to another agent. Publishing Operations Concierge alone does not satisfy the prerequisites of the target agent. After connection, the local description in Operations Concierge should clearly define when IT-specific work is delegated, because descriptions influence routing. Any later changes to the Service Desk Agent must be published before the main agent can use the updated version. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate an existing agent in Copilot Studio.

===============

Call the API during the conversation → Configure a REST action and call it from the topic; Run with authentication → Build an authenticated connection for the API; Make the response available at runtime → Store the API response in a topic variable.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The REST action is the executable component that issues the request when the topic reaches that node. An authenticated connection supplies the credential or token handling required by the endpoint; embedding secrets directly in a topic would be insecure and difficult to manage across environments. The returned JSON must then be assigned to a topic variable so downstream nodes can inspect fields, make decisions, format a response, or pass the value to another tool. Treating the API as indexed knowledge would be inappropriate because the requirement is a live runtime call, not search over a periodically indexed corpus. The builder should define the HTTP operation, endpoint, inputs, response schema, and output variable precisely. Authentication should use the narrowest appropriate identity model—user-delegated when actions must be attributable to the user, or maker/service credentials only when the business design permits shared access. Error and timeout paths should be explicit so malformed JSON, authorization failures, and unavailable services do not produce silent or misleading responses. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Add REST APIs to an agent.

===============

HTTP action → Endpoint and authentication; Data action → Table relationships and keys.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: An HTTP action must know where to send the request and how the destination authenticates it. The endpoint, method, headers, and authentication or connection details therefore belong to the HTTP action ' s configuration. A data action operates against structured records, so table relationships and key fields determine which entity and row are read or changed and how related data is resolved. Input mapping is important for both action types but does not replace these defining settings. Timeout and retry policy control resilience after an action has been configured; they do not identify the endpoint or the record relationship. The flow designer should also validate schemas, map outputs into clearly typed variables, and provide failure paths for authorization, not-found, timeout, and malformed-response conditions. Keys should be stable identifiers rather than display names, and connection permissions should follow least privilege. Testing with both valid and invalid records confirms that the data action targets the intended row and that the HTTP action cannot silently call an incorrect or unauthenticated endpoint. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Configure actions and connectors.

===============

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The agent needs a valid authenticated connection to the MCP server before it can discover and invoke the server ' s published tools. Copilot Studio supports the authentication methods exposed during MCP onboarding, including API key and OAuth 2.0. The choice must match the server: OAuth is appropriate for user-delegated authorization, while an API key is a shared secret mechanism. Publishing does not create credentials or make an unauthenticated server usable. A Power Platform connector used as real-time knowledge would serve a different retrieval pattern and would not replace the MCP tool contract. Generative answers also do not establish MCP connectivity; generative orchestration can select a tool only after that tool is correctly connected and described. The server and individual tools should have clear descriptions, typed inputs, and constrained permissions. Test the connection under the intended identity, confirm that only expected tools are visible, and implement error handling for consent, expired credentials, denied scopes, server unavailability, and invalid tool output. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Configure MCP tools.

===============

Requirement

Correct configuration

Make connector actions available for the agent to invoke.

Add the connector as a tool in the agent.

Handle authentication at the service level, not per user.

Create or reuse a connection for the connector.

Pass conversation context into the connector when called.

Map topic variables to the tool inputs.

Surface the connector’s returned data to the user.

Parse the JSON response and assign it to a topic variable.

Comprehensive and Detailed Explanation From [Microsoft AB-620 Study Guide]

Adding the approved connector as an agent tool exposes its defined REST operations to Copilot Studio. The tool can then be called explicitly from a topic or selected dynamically by generative orchestration, depending on its configuration.

A connector connection stores the authentication configuration required to call the underlying service. Among the provided choices, creating or reusing that connection is the correct service-authentication action. For strict service-level authentication, the tool must additionally be configured under Credentials to use with Maker-provided credentials . Creating a connection alone does not guarantee this behavior if the tool remains configured to use end-user credentials.

Topic variables containing conversation context—such as a customer identifier, ticket number, or requested operation—are mapped to the connector tool’s input parameters. This ensures the REST request receives values collected earlier in the conversation.

When the connector returns structured JSON, the relevant values must be parsed and stored in a topic variable. That variable can then be referenced in a message, adaptive card, or subsequent topic node to present the returned information to the user.

Relevant study-guide area: Integrate and extend agents in Copilot Studio → Add tools to agents → Add a tool by using an existing custom connector . See Use connectors in Copilot Studio agents and Add tools to custom agents .