Microsoft AB-620 Practice Test Questions Answers

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The Ask with Adaptive Card node is the interactive topic element that waits for a card submission and stores the user ' s responses as variables. The card must contain input controls with unique identifiers and an Action.Submit button so the host returns the collected values to Copilot Studio. A Message node can display a card, but it is not the correct choice when the topic must collect and bind structured input in one step. Action.Execute is not consistently supported across Copilot Studio channels; Microsoft documents host-specific schema limits, and the default web chat does not support that action. Using the latest schema indiscriminately can therefore break portability. The card should target the lowest schema version required by every intended channel, validate required fields, and provide clear labels and error messages. After submission, the topic variables should be typed and checked before they are passed to tools or flows. Testing is required in each production channel because rendering and supported Adaptive Card features differ between Teams, web chat, and customer-service hosts. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure adaptive cards; Manage variables.

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

Requirement

Correct configuration

Users must be able to trace each answer back to its source.

Instruct the agent to cite sources in the knowledge settings.

The agent retrieves information from a centralized data index.

Configure Azure AI Search as the grounding data source.

Responses are generated by an enterprise-approved foundation model.

Deploy a model in Foundry to an agent and connect it to Copilot Studio.

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

Source citations provide traceability by connecting generated statements to the enterprise content used for grounding. Therefore, the agent’s knowledge instructions should require citations. For Azure AI Search, this also requires a usable URL in the search index. Copilot Studio interprets metadata_storage_path, or another field containing a complete URL, as the citation target. Consequently, instructions alone cannot produce functional links if the index does not expose a valid source URL.

Azure AI Search should be configured as the grounding source because it provides centralized, indexed retrieval for enterprise content. During a conversation, the user’s query is submitted to the configured search index, relevant passages are retrieved, and those passages become the grounding context for the generated response. Uploading documents directly to Copilot Studio would create a separate Dataverse-backed knowledge source and would bypass the required centralized index.

To satisfy organizational model governance, the approved foundation model must be deployed through Microsoft Foundry and associated with a Foundry agent that is connected to Copilot Studio. This ensures generation uses the approved model deployment rather than an unrelated default model.

Relevant study-guide area: Integrate and extend agents in Copilot Studio → Integrate agents with Azure → Configure generative answers by using Azure AI Search with Foundry . See Add Azure AI Search as a knowledge source and Connect to a Microsoft Foundry agent .

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 .

Create a new agent flow artifact in the environment.

Configure the invocation trigger that allows the agent to call the agent flow.

Configure the actions that implement the required behavior.

Validate the agent flow behavior with representative test runs.

Make the agent flow available for agent usage.

An agent flow must first exist in the target environment before its trigger or processing logic can be configured. The invocation trigger is then configured so Copilot Studio can initiate the flow during a conversation. For an agent-callable flow, this is typically the When an agent calls the flow trigger. The flow should also return any required results through the corresponding response action.

After establishing the trigger, the author adds the actions that implement the required business process, such as retrieving records, calling connectors, applying conditions, or updating enterprise systems. Representative test runs should then be performed to confirm that inputs are accepted correctly, actions execute successfully, errors are handled appropriately, and expected outputs are returned to the agent.

Once the flow has been verified, it can be published and made available to the agent as a tool. Exposing an incomplete or unverified flow prematurely could cause conversation failures or incorrect tool results.

Relevant study-guide area: Plan and configure agent solutions → Create and monitor agent flows in Copilot Studio → Create an agent flow . See Create an agent flow as a tool and Call an agent flow from 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.

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