Free Microsoft AB-620 Practice Exam with Questions & Answers | Set: 2

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 partner capability is described as an agent available only through a standardized agent-to-agent endpoint. That is the defining use case for an Agent2Agent connection. In Copilot Studio, the primary agent is configured with the external agent ' s A2A message endpoint and the applicable authentication details, after which orchestration can delegate shipment-tracking requests to it. An MCP server exposes tools or resources rather than an independently orchestrated partner agent, so option C changes the integration contract. An indexed knowledge source is also unsuitable because shipment status is dynamic and the requirement is delegation, not retrieval from a copied corpus. Generative responses in the primary agent would have no authoritative live shipment source and would violate the defined architecture. The A2A description should identify shipment tracking precisely so that it does not compete with unrelated agents or tools. Because external-agent support can be preview functionality, Fabrikam should also validate regional availability, authentication, error behavior, latency, and governance before production use. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Create a multi-agent solution by using A2A protocol.

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

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.

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

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.

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

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.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Removing the generative answers node eliminates the component that searches the configured knowledge sources and produces the grounded topic response. A standalone custom prompt can format or transform supplied input, but it does not automatically inherit the topic ' s selected knowledge sources or reproduce the node ' s retrieval behavior. The resulting answer could therefore have the requested executive-summary style while failing the grounding requirement. The correct design retains the generative answers node and applies topic-scoped custom instructions to its response, or captures the grounded output in a variable and sends that content through a carefully configured formatting prompt. General knowledge should remain disabled when the topic must use only approved enterprise sources. Connector security and data policies continue to govern the actual source connections and cannot be replaced by prompt text. The proposed removal is consequently not a valid solution. Validation should inspect the retrieved sources, generated answer, final format, and behavior when no authorized source returns relevant content. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure generative answers node; Configure advanced agent responses with custom prompts.

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

Interact with the legacy UI → Enable the Computer use tool; Supported execution → Use a platform-hosted execution environment; Observe execution → Monitor run details in the agent runtime/activity view.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Computer use is specifically designed for websites and Windows desktop applications that lack a suitable API. It operates the interface through a virtual mouse and keyboard, allowing the agent to select controls and enter values on screen. The automation must be associated with a supported hosted or configured machine environment; enabling the tool alone does not supply an execution computer. Run and activity details provide the observation surface for testing how the model navigated the interface, where it paused, and why it failed. A custom connector would be preferable if a stable API existed, but the scenario explicitly rules that out. UI automation is inherently sensitive to layout, timing, pop-ups, and application changes, so the tool instructions should be narrow and the test set should cover common visual states. Credentials must be stored through supported credential management rather than typed into instructions. Destructive or high-impact operations should include confirmation or human supervision, and verbose logging should be protected because it can capture operational data shown on screen. 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: 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.

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

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.

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

Use the user ' s message → Select Activity.Text as the input; Query only designated data → Turn on Search only selected sources and choose the approved sources; Restrict to enterprise data → Turn off Allow the AI to use its own general knowledge.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Activity.Text is the system variable containing the current user ' s utterance, so it is the appropriate query input for the generative answers node. Search only selected sources changes the node from the default broad agent-level search to an explicit source set for that topic. Turning off the option that permits the model to use its own general knowledge closes the ungrounded fallback path and ensures the response depends on approved enterprise content. Generative orchestration at the agent level does not itself guarantee that this particular node searches only designated sources. The selected sources replace, rather than supplement, the agent-level list for the node, and there is no automatic fallback to other knowledge if they return no answer. That behavior is desirable for strict policy boundaries but should be reflected in a clear no-answer or escalation response. Testing should inspect source use, verify authorization trimming under different users, and include questions for which the approved source contains no relevant material to ensure the agent does not invent an answer. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure generative answers node.

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