Microsoft Updated AB-620 Exam Questions and Answers by sienna-rose

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.

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 .

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The approved solution preserves the reusable prompt template and changes the model configuration that actually executes it. Applying the established template retains the required tone, structure, and repeatable instruction set. Selecting an approved model in the prompt configuration ensures that prompt-driven responses are produced by a model permitted under the organization ' s governance policy. An instruction that tells the model to use an approved model cannot control the underlying runtime; model selection is a platform configuration, not a behavior the model can enforce on itself. Citations address provenance, not model approval. Azure AI Search supplies grounding data but also does not choose the foundation model. Publishing is necessary to expose completed changes to users, yet it does not automatically substitute a compliant model. The team should also test the prompt against representative inputs after changing models, because output quality, formatting adherence, latency, and token behavior can vary across models even when the prompt remains identical. Governance records should capture the selected model, prompt version, owner, and validation evidence. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure custom prompts to use the Foundry model catalog.

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

Authentication → Add the required authentication headers; Retrieve data → Set the HTTP method to GET; Structured reusable response → Select a JSON/Record response type, define the schema, and save the response to a topic variable.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The Send HTTP request node must express the API contract directly. If the service expects a token or key in a header, the required header is added using a protected variable or connection-derived value rather than hard-coded secret text. GET is the correct method for retrieving status without changing the external resource; PATCH would imply a partial update. Selecting a structured JSON or Record response type and defining its schema allows Copilot Studio to type the returned fields. Saving that response to a topic variable makes values available for conditions, formatting, adaptive cards, or later tool calls. The schema must reflect optional fields, arrays, and nested records accurately; otherwise valid responses can be rejected or fields can appear empty. The topic also needs branches for non-success status codes, timeouts, invalid JSON, and authentication failure. Where a reusable connector or REST tool already exists, that managed abstraction may be preferable to embedding HTTP details in multiple topics, but the node configuration shown is correct for the stated direct-request requirement. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure advanced agent responses with API and Send HTTP requests.

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