AB-620 Exam Dumps - Designing and Building Integrated AI Agent Solutions in Copilot Studio

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.

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

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.

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

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.

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

1. Open the Solutions area in Copilot Studio; 2. Define the solution name and publisher; 3. Save the solution container.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Solution creation begins in the Solutions area because that is the Copilot Studio entry point to the Power Platform solution explorer. The maker then supplies the solution name and publisher. The publisher is not cosmetic: it determines the customization prefix and forms part of the ownership and naming strategy for components that will move through ALM. Saving creates the solution container, after which agents, flows, connection references, environment-variable definitions, prompts, and other dependent assets can be added. Reviewing the solution details page can follow creation but is not one of the required creation steps in this three-action sequence. A custom solution is preferable to relying on the default solution for controlled export, source management, and pipeline deployment. Before export, the team should use dependency checks to ensure all assets required by the agent are included and should avoid including unrelated components. Downstream releases normally import a managed build of the solution, while development remains unmanaged so authorized makers can continue editing. Study Guide alignment: Test and manage agents > Implement application lifecycle management for agents in Copilot Studio > Create a solution.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A predefined test set with expected outcomes is the only option that satisfies consistency, grounding comparison, and repeatable regression analysis. The fixed prompts ensure that each version receives the same inputs. Verified expected responses provide the baseline against which meaning, quality, keywords, or exact output can be scored. Rerunning the same set produces comparable results over time, allowing the team to calculate whether a knowledge-base change improved or degraded performance. The manual test pane is valuable for interactive debugging and inspecting the activity map, but it does not provide the same controlled batch or historical comparison. Channel usage metrics describe adoption and operational behavior, not response correctness. Transcript keyword searches can reveal patterns after deployment but do not establish a golden answer or a controlled experiment. The evaluation method should match the content: compare-meaning for legitimate paraphrases, exact match for fixed values, keyword match for required terms, or a custom rubric for domain-specific quality. Results should be retained or exported when a longer audit history is required. Study Guide alignment: Test and manage agents > Evaluate agent performance > Create a test set; Choose an evaluation method; Review test results.

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

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.

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

Call the API during the conversation → Configure a REST action and call it from the topic; Run with authentication → Build an authenticated connection for the API; Make the response available at runtime → Store the API response in a topic variable.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The REST action is the executable component that issues the request when the topic reaches that node. An authenticated connection supplies the credential or token handling required by the endpoint; embedding secrets directly in a topic would be insecure and difficult to manage across environments. The returned JSON must then be assigned to a topic variable so downstream nodes can inspect fields, make decisions, format a response, or pass the value to another tool. Treating the API as indexed knowledge would be inappropriate because the requirement is a live runtime call, not search over a periodically indexed corpus. The builder should define the HTTP operation, endpoint, inputs, response schema, and output variable precisely. Authentication should use the narrowest appropriate identity model—user-delegated when actions must be attributable to the user, or maker/service credentials only when the business design permits shared access. Error and timeout paths should be explicit so malformed JSON, authorization failures, and unavailable services do not produce silent or misleading responses. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Add REST APIs to an agent.

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