AB-620 Designing and Building Integrated AI Agent Solutions in Copilot Studio Questions and Answers

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

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

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

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

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 .

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.

Approval stage → Wait for a response and branch according to the decision; Information-collection stage → Wait for a response and capture the submitted inputs.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: An approval is a decision gate. The flow must pause until the reviewer responds, then branch to the appropriate approved, rejected, or other outcome path. Information collection also pauses, but its purpose is to capture supplied values and make them available to later actions in the same run. Sending a request or notification and continuing immediately would break both requirements because downstream processing could occur before the human response exists. The action should have a defined timeout and an escalation or cancellation path so a missing response does not leave the process suspended indefinitely. The flow should store the response, responder identity, timestamp, and any comments needed for audit. Sensitive information should not be requested through an inappropriate channel and should be protected in logs and variables. Testing must cover approval, rejection, corrected information, timeout, and unauthorized-responder cases. This produces a controlled human-in-the-loop design rather than a simple alert that has no effect on execution. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Create a human-in-the-loop agent flow.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Power Platform data policies are the preventive governance control for connectors, HTTP endpoints, knowledge sources, and combinations of data groups used by Copilot Studio agents. Administrators can classify or block connectors, restrict endpoint use, require authentication, and surface policy violations during authoring or publishing. This meets both enforcement and reporting requirements. Application Insights records runtime telemetry but does not prevent a maker from adding a disallowed connector. Security FAQs provide guidance only. Agent analytics can reveal behavior and usage trends but are detective, not an administrative guardrail. Data policies should be scoped deliberately at tenant or environment level and tested against representative agent configurations. When a violation occurs, Copilot Studio can block publishing and provide downloadable details identifying the policy conflict, enabling the administrator and maker to correct the design. Governance should also include least-privilege connections, environment segmentation, solution-based ALM, and review of exceptions; a broadly permissive policy followed by manual monitoring is not equivalent to enforcing the control at design and deployment time. Study Guide alignment: Plan and configure agent solutions > Plan an agent solution > Evaluate security and governance considerations.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Selecting Authenticate with Microsoft restricts the agent to signed-in organizational identities in the supported Microsoft channel and enables the agent to be shared with controlled users in the tenant. That meets the requirement for internal employees and enforced end-user authentication. No authentication or a public website would allow anyone with access to the link to converse with the agent and would prevent reliable organizational access control. A personal-account setting is not the enterprise identity model required here. Authentication and authorization are related but separate: after choosing Microsoft authentication, the owner must still share the agent only with the intended employees or groups and ensure connected knowledge and tools apply the user ' s permissions correctly. If the deployment uses a channel that requires manual Entra ID configuration, the appropriate manual authentication and sign-in requirement may be needed instead; however, among the supplied choices, Authenticate with Microsoft is the correct control. Test with authorized, unauthorized, and signed-out users before release, and review any DLP policy that mandates authentication. Study Guide alignment: Plan and configure agent solutions > Plan an agent solution > Plan identity strategy; Design agents for internal audiences.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The connector action ' s retry policy should be set to None when the business requirement explicitly says not to retry automatically. Otherwise, platform retries can repeat a non-idempotent operation or delay the controlled failure path. The notification action must then use Configure run after so it executes when the connector action fails or times out and can include the available error details. This combination directly addresses the three requirements: explicit failure and timeout handling, continuation into the notification branch, and no automatic retry. A scope can be valuable for grouping a try block and evaluating its aggregate result, but grouping alone does not disable retries or define the notification ' s run-after conditions. Increasing the timeout changes how long the action waits and can make recovery slower without handling the error. The flow should also end with a deliberate final status, avoid exposing secrets in the notification, and distinguish transient dependency errors from validation failures. If the external operation is non-idempotent, a correlation or idempotency key should be used to prevent duplicate effects when an administrator later resubmits the run manually. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Implement error handling in agent flows.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A separate custom prompt tool that merely requests an executive-summary structure does not, by itself, guarantee that the existing generative answers node and its configured knowledge sources remain in the response path. Prompt tools have their own inputs, knowledge configuration, model settings, and completion behavior. If the tool is invoked independently, it can generate correctly formatted text without using the sources selected for the topic ' s generative answer, which violates a stated requirement. The safer design is to keep the generative answers node and apply topic-specific custom instructions or prompt modification to that node, or explicitly pass its grounded output into a downstream formatting prompt with a controlled contract. Connector security remains enforced by the underlying connections and data policies; wording in a prompt cannot override those controls. Therefore, the proposed solution is incomplete and does not meet the goal as written. Testing should confirm not only the output format but also the sources used and the identity under which any connector retrieval occurred. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure advanced agent responses with custom prompts and custom knowledge sources.

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

1. Define success criteria and evaluation objectives; 2. Select evaluation methods and metrics aligned to the criteria; 3. Collect interaction data and evaluation signals; 4. Review results and identify improvement opportunities.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Evaluation starts with a definition of success because the business objective determines what should be measured. A policy agent might prioritize grounded accuracy and citations, while a transactional agent also needs tool-selection and completion measures. Once objectives and thresholds are defined, the team selects suitable methods and metrics, such as compare-meaning, exact match, keyword match, expected tool use, or a custom quality rubric. The test is then executed to collect responses, scores, resource usage, transcripts, and activity signals. Only after evidence exists should reviewers interpret the results, isolate weak scenarios, and prioritize changes. Choosing metrics before defining success risks optimizing an irrelevant score; reviewing before collecting consistent evidence encourages anecdotal conclusions. Improvement should be iterative: change the knowledge source, instructions, tool metadata, or expected outcome one at a time and rerun the same set. This sequence produces an auditable link between business intent, measurement design, observed performance, and the remediation decision. Study Guide alignment: Test and manage agents > Evaluate agent performance > Choose an evaluation method; Review test results.

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

Capture response → Use the action ' s response outputs in later steps; Continue the same run → Allow the action to wait for and return a response before continuing; Require a manual decision → Add a human approval action.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A human-in-the-loop flow must preserve execution state while it waits. The approval or information action pauses the current run and returns a response when the designated person acts; triggering a new flow would lose that direct continuation contract. The response outputs—decision, comments, supplied fields, responder, and timestamps as applicable—are then referenced by downstream conditions and actions. A human approval action provides the explicit decision gate required before processing continues. Sending a notification or message alone does not wait and cannot guarantee that the decision controls the flow. The designer should configure expiration, escalation, reassignment, and rejection paths so the run cannot remain suspended without governance. Responses should be validated before use, and sensitive values should be protected in variables and history. Test approval, rejection, timeout, duplicate response, and unauthorized response scenarios. These controls ensure that human oversight changes execution deterministically instead of acting as an informational side channel. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Create a human-in-the-loop agent flow.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A generative answers node inside the topic is the correct place to retrieve from configured knowledge sources for that specific conversational path. The node can use the user ' s message as input, search designated sources, and generate a grounded response from the retrieved content. Topic-level sources can override the broader agent-level set, which is useful when the topic must restrict itself to approved data. A custom prompt that merely instructs the model to use company information does not create or enforce a retrieval connection. Increasing the response limit affects length, not grounding. Analytics measures usage after the fact and cannot supply knowledge. Adding SharePoint only at agent level is unnecessarily narrow and would not satisfy the requirement for custom sources configured within the topic. The builder should enable Search only selected sources when strict scoping is required and turn off general knowledge if no ungrounded fallback is allowed. Testing should inspect both the answer and the resource details to confirm that the intended source supplied the evidence. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure generative answers node; Configure advanced agent responses with custom knowledge sources.

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