Microsoft AB-620 Practice Exam Questions & Answers

Explanation

This multiple-choice question asks for two actions to ensure every AI-generated response includes a disclaimer complying with security and governance policies. The available options are not provided in the question text.

Common approaches to adding disclaimers in Copilot Studio include:

<ul><li><strong>System Prompt Configuration:</strong> Adding disclaimer text to the system prompt or agent instructions</li><li><strong>Topic Flow Design:</strong> Implementing a disclaimer message node in conversation flows</li><li><strong>Post-Response Processing:</strong> Using a cloud flow to append disclaimers to all responses</li><li><strong>Message Template:</strong> Creating a custom response template that includes disclaimer text</li><li><strong>Generative Answer Settings:</strong> Configuring built-in disclaimer options for generative content</li></ul>

Explanation

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A generative answers node inside the topic is the correct place to retrieve from configured knowledge sources for that specific conversational path. The node can use the user's message as input, search designated sources, and generate a grounded response from the retrieved content. Topic-level sources can override the broader agent-level set, which is useful when the topic must restrict itself to approved data. A custom prompt that merely instructs the model to use company information does not create or enforce a retrieval connection. Increasing the response limit affects length, not grounding. Analytics measures usage after the fact and cannot supply knowledge. Adding SharePoint only at agent level is unnecessarily narrow and would not satisfy the requirement for custom sources configured within the topic. The builder should enable Search only selected sources when strict scoping is required and turn off general knowledge if no ungrounded fallback is allowed. Testing should inspect both the answer and the resource details to confirm that the intended source supplied the evidence. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure generative answers node; Configure advanced agent responses with custom knowledge sources.

Explanation

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Configure run after is the control that routes execution to an error-handling action when the external-service action fails, times out, is skipped, or reaches another selected status. By configuring the notification action to run after failure and timeout, the flow no longer terminates silently and can send a message containing sanitized error context. The handler can then set a deliberate flow status, record a correlation ID, and provide the operator with the failed action and remediation path. This design should be paired with an appropriate retry policy based on whether the external operation is safe to repeat. For non-idempotent writes, automatic retry may create duplicates and should generally be disabled or protected with an idempotency key. Error notifications must not include tokens, secrets, or unrestricted payloads. Testing should deliberately produce an authorization failure, timeout, and service error to prove that each status enters the handler and that the notification itself has a fallback if its connector is unavailable. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Implement error handling in agent flows.

Explanation

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The tenant administrator has already configured a Copilot connector that indexes the external system into Microsoft Graph. The agent should consume that approved enterprise knowledge source from its Knowledge configuration. This lets generative answers retrieve authorized indexed content without recreating the connector, uploading duplicate documents, or treating the source as a callable transaction. Copilot connectors are designed for enterprise search and knowledge grounding; the user's access is evaluated so that responses surface only content the user is permitted to see. A custom connector is appropriate when the agent must call an API or perform an operation, which the scenario explicitly excludes. Adding the connector as a tool would likewise shift the design from retrieval to invocation. Manual file upload would create a second, potentially stale copy and break the administrator-managed indexing lifecycle. After adding the source, the builder should provide a clear name and description, test representative questions, confirm citations or source attribution, and verify that restricted users cannot retrieve unauthorized material. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources > Connect to Copilot connectors.

Explanation

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The first configuration check is the contract between the agent and the flow. Input and output parameter definitions must agree on name, data type, required status, and mapping. A flow can complete successfully yet return an empty value to the agent if the response field is not mapped to the declared output or if the agent expects a different type. Validating the parameter definitions therefore addresses the actual data-exchange requirement. Reviewing run history is useful for diagnosis, but it does not correct a mismatched contract by itself. Changing the trigger schema or adding Parse JSON might be necessary in a specific implementation, yet neither should be done before confirming what the caller sends and what the flow returns. Republishing cannot repair an incorrect mapping. The builder should test the flow directly with known values, inspect each action output, verify the final response action, and then test from the agent. Optional and null fields should be handled explicitly, and sensitive outputs should be minimized and protected in logs. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Add input and output parameters.

Explanation

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.

Explanation

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.