Pass the Microsoft Certified: Dynamics 365 Sales AI Consultant Associate AB-620 Questions and answers with ExamsMirror

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.

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

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.

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

Repeated failures → Evidence of a recurring pattern; Response-quality information → The response partially matches the expected answer; Evaluation limitation → The specific underlying cause cannot be determined from the score alone.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Three failures on the same fixed interaction, with scores tightly clustered between 0.58 and 0.61, provide evidence of a repeatable problem rather than an isolated stochastic miss. The evaluator ' s reasoning directly supports the conclusion that the response only partially represents the expected answer. The run also shows that internal documentation was retrieved and no tools were involved, which narrows the diagnostic path toward the knowledge, instructions, retrieval quality, or expected-answer design. It does not, however, prove a single root cause. A score and short reasoning statement cannot tell whether the source document is incomplete, the wrong passage ranked highly, the question is ambiguous, the model omitted a key condition, or the expected response is too strict. The next step is to inspect the test transcript, retrieved sources, activity map, and expected answer, then change one factor and rerun the same case. This disciplined triage distinguishes what the evaluation demonstrates from what still requires investigation and prevents an unsupported causal conclusion. Study Guide alignment: Test and manage agents > Evaluate agent performance > Review test results.

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

Ordered Dev/Test/Prod deployment → Sequential stage progression; Detect missing references or variables → Deployment input validation; Unified stage and security management → Centralized pipeline configuration.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A Power Platform pipeline models the release path as ordered stages, so sequential progression is the control that enforces Dev-to-Test-to-Prod movement instead of allowing an arbitrary target. Deployment input validation checks required connection references, environment variables, and related deployment inputs before promotion begins, reducing failed or partially configured releases. Centralized pipeline configuration in the host environment provides one place to manage linked environments, stages, deployment rules, and security. Environment-specific packages or builder-defined settings would weaken repeatability and governance, while direct target selection would bypass the prescribed order. Managed solutions should be used in downstream environments so production customizations do not create unmanaged drift. The pipeline configuration should assign appropriate deployment roles, protect the host environment, and incorporate approvals or quality gates where required. A successful package check does not replace functional validation: the team should still run the agent ' s test set after deployment and confirm that connections, knowledge access, flows, and environment-specific values operate under target-environment identities. Study Guide alignment: Test and manage agents > Implement application lifecycle management for agents in Copilot Studio > Implement and extend Microsoft Power Platform Pipelines.

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

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: Applying custom instructions on the existing generative answers node at the topic level meets the scope requirement because only that topic ' s response behavior is changed. The node remains responsible for searching the configured knowledge sources, so grounding is preserved while the custom instruction imposes an executive-summary structure. Other topics continue using their own node or agent-level behavior. This is different from replacing the generative answers node with an independent prompt tool, which can sever the retrieval path. The topic should keep Search only selected sources configured when source restriction is required, and general knowledge should be disabled if the answer must be based exclusively on enterprise data. Connector authentication and data-policy enforcement remain platform controls and are not weakened by a formatting instruction. The instruction should specify a stable format—such as decision, key facts, risks, and next actions—without asking the model to disclose internal reasoning. Tests should verify both consistent formatting and correct source use under users with different permissions. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure advanced agent responses with custom prompts; Configure generative answers node.

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

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.

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

Sensitive value without republishing → Use a secret environment-variable type for runtime resolution; View but do not edit in Copilot Studio → Environment variables are read-only in Copilot Studio; Updated non-secret value used by the published agent → Republish the agent.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Secret environment variables are designed to resolve protected values, typically through Azure Key Vault, without embedding the secret in the agent definition. That makes them suitable when an administrator changes a sensitive value and runtime must obtain the current secret. Environment variables exposed to Copilot Studio are read-only there; administrators manage their definitions and current values through the Power Platform solution and environment controls, so a builder can inspect a reference without editing it on the topic canvas. For ordinary non-secret variables used by a published agent, a configuration change must be followed by republishing so the active runtime version consumes the updated value. Topic variables are conversation state and are not an ALM substitute for environment-specific configuration. Allowing every builder to edit environment variables from Copilot Studio would defeat separation of duties. The team should test the exact behavior for each variable type, because secret resolution and published configuration have different lifecycles, and should ensure target-environment service identities can read the referenced Key Vault secret. Study Guide alignment: Test and manage agents > Implement application lifecycle management for agents in Copilot Studio > Create and use environment variables.

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

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.