Free Microsoft AB-620 Practice Exam with Questions & Answers | Set: 3

Ground answers from enterprise data → Add a Copilot connector knowledge source for indexed content; Invoke standardized callable functions → Connect to an MCP server and add its tools; Write an authenticated update → Add a Power Platform connector tool and call it from a topic.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: These requirements represent three different integration contracts. Indexed enterprise content is a retrieval problem, so a Copilot connector knowledge source should ground the generated answer in Microsoft Graph-indexed information while honoring the user ' s permissions. Callable functions published through the standardized Model Context Protocol belong behind an MCP server connection; once added, the agent can discover and invoke the server ' s tools. A write operation during a conversation is a transactional tool call. A Power Platform connector action invoked from the topic supplies the authenticated operation and exposes defined inputs and outputs. Dataverse tables can be used as knowledge, but that choice does not satisfy the broader indexed-enterprise requirement stated here. Likewise, using MCP for every requirement would blur read-only grounding and system updates, increasing the security and orchestration surface. Separating knowledge from actions also improves observability: retrieval sources can be evaluated for grounding quality, while tool calls can be audited for inputs, identity, outcome, and errors. Descriptions and parameter metadata should make each capability ' s scope unambiguous to the orchestrator. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources; Add tools to agents.

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

Fixed prepared interactions → Use a curated prompt list; Predefined baseline → Compare against predefined expected outcomes; Repeatable comparison → Use a consistent scoring evaluation matrix.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A curated prompt list creates the controlled input population required for repeatability. Predefined expected outcomes establish what a correct or acceptable response should contain, which lets the evaluator judge performance against a baseline rather than against a reviewer ' s memory. A stable scoring matrix ensures that repeated runs are interpreted under the same thresholds and dimensions. Live conversations and post-rollout feedback can enrich the test inventory, but they cannot replace a fixed regression set because the questions, users, and context change. Publishing status confirms deployment, not response quality. General impressions are similarly unsuitable for consistent comparison. The team should select the scoring method according to the response type: semantic comparison for valid paraphrases, exact match for immutable values, keyword checks for mandatory phrases, and custom criteria for compliance or domain quality. Versioning the prompt list, expected answers, rubric, agent version, and knowledge snapshot is essential; otherwise a changed test set can be mistaken for a change in agent performance. Study Guide alignment: Test and manage agents > Evaluate agent performance > Create a test set; Choose an evaluation method.

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

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.

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