Practice Free AB-620 Designing and Building Integrated AI Agent Solutions in Copilot Studio Exam Questions Answers With Explanation

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.

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

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.

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

Support grounding from indexed data ? Retrieve indexed content

Use existing access controls from the source system ? Respect existing permissions

Support read-only operations ? Prevent transactional updates

Microsoft 365 Copilot connectors index non-Microsoft enterprise content into Microsoft Graph for semantic grounding. They preserve source-level access controls so users receive only content they are authorized to access. Because the connector is configured as a knowledge source, its purpose is retrieval—not executing transactional updates. Microsoft Learn: Copilot connectors as knowledge sources

Call an external API ? Make an HTTPS request

Retrieve stored data from a supported internal data source ? Add a standard connector

Send a Teams message ? Add a standard connector

The HTTP action is appropriate for calling an external REST API directly. Supported internal systems should be accessed through their available Power Platform connectors. The Microsoft Teams connector is also a standard connector and provides actions such as Post message in a chat or channel . Because selections may be reused, Add a standard connector applies to both the internal-data and Teams requirements.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Computer use is the Copilot Studio capability for operating a website or desktop application ' s graphical interface when an API is unavailable. Enabling it gives the agent a UI automation tool driven through the supported machine execution context. During testing, the builder can open the computer-use activity or remote session from the agent ' s activity view to observe steps, inspect logs, and understand failures in real time. Adding a desktop flow is a different deterministic automation technology and is not required by the stated computer-use design. Publishing alone does not provision the UI automation or its machine. A custom connector cannot automate screen controls when the application exposes no API. The tool should be configured with narrowly scoped instructions, a healthy supported machine, protected credentials, and human confirmation for sensitive actions. Because computer-use behavior is probabilistic and visual interfaces change, the team should test alternate screen states, pop-ups, timing, and recovery, then monitor production sessions under strict access and retention controls. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Configure and monitor computer use for an 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: Terminating immediately on error makes the failure explicit to the runtime but does not send the required notification. The solution therefore still allows an operator-facing silent failure even though the run status is marked failed. A proper pattern uses Configure run after to enter a notification or catch scope on failure and timeout, collects safe diagnostic details, sends the administrative alert, and only then terminates with the intended status. If notification delivery fails, a secondary monitoring or logging path should still preserve the incident. The error message should include a run or correlation identifier, the failed action, and a concise remediation hint without exposing credentials or sensitive business data. Retry behavior should be configured separately according to idempotency and service characteristics. The proposed immediate termination satisfies neither the communication requirement nor controlled recovery, so the answer is No. Tests should force each expected failure state and confirm both notification delivery and final run status. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Implement error handling in agent flows.

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

Avoid indexing business records ? Retrieve data without indexing; Preserve source-system controls ? Use existing permissions; Access current data at runtime ? Use a real-time Power Platform connector.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Power Platform real-time knowledge connectors query the source system when the agent needs an answer. Microsoft indexes metadata needed to understand the available tables and fields, but the business records themselves are not copied into a separate content index. Because the request is executed through the established connection, the source system ' s permissions remain part of the access decision. This is materially different from a Copilot connector, which indexes external content into Microsoft Graph, and from Azure AI Search, which relies on a maintained search index. The real-time pattern is best when current operational records and source-enforced access are more important than broad document search. The connection must be governed with the same Power Platform data policies that apply to actions, and authentication should reflect whether access is user-delegated or provided by a service identity. Testing under users with different permissions is essential to confirm that the agent cannot return records a user could not access directly and that changes in the source appear without an indexing delay. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources > Connect to Microsoft Power Platform connectors.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The test passed because the score of 0.92 exceeds the configured threshold of 0.80 and the evaluation method recognizes semantic equivalence. The actual answer conveys the same policy meaning as the expected response even though the wording is different, so an exact textual match is unnecessary. The recorded knowledge source is RefundPolicy_KB, which is the expected grounding path; confirming that source behavior is therefore appropriate. No tool was expected or invoked, so investigating tool configuration would add noise rather than address a defect. A score below 1.00 is not itself a failure, and rewriting the expected answer to mirror every valid paraphrase would undermine a meaning-based evaluation. The result can be accepted while still being retained as regression evidence. Reviewers should confirm that the cited or retrieved policy content supports the non-refund statement and that the chosen threshold reflects the business risk. For fixed codes or legally prescribed phrases, exact match might be preferable, but this natural-language policy answer is correctly evaluated by semantic similarity. Study Guide alignment: Test and manage agents > Evaluate agent performance > Review test results.

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

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.

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

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.

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.

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 .

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.