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

Requirement

Implementation method

Let the agent decide when to run a tool based on user input.

Enable generative orchestration.

Run a specific agent flow at a defined step in a topic.

Add a tool node.

Use a connector action to retrieve data during a conversation.

Add a tool node.

Comprehensive and Detailed Explanation From [Microsoft AB-620 Study Guide]

Generative orchestration is appropriate when the agent must independently determine whether a tool is relevant to the user’s request. Copilot Studio evaluates the user’s message, conversation context, and the tool’s name, description, inputs, and outputs before deciding whether to invoke it. Microsoft documentation confirms that generative orchestration allows an agent to choose tools based on their descriptions and the current user query.

When an operation must occur at a predetermined point in an authored topic, the operation should instead be inserted explicitly by using an Add a tool node. Selecting an agent flow from that node ensures that the flow executes at that exact position in the topic rather than being selected autonomously by the orchestrator.

The same node type is used when calling a connector action. From the topic canvas, the author selects Add a tool , chooses Connector , and then selects and configures the required connector operation. Adaptive Cards present interactive information, while Question nodes collect user input; neither directly invokes flows or connectors.

Relevant study-guide area: Plan and configure agent solutions → Configure topics → Add agent flows to a topic and Add tools to a topic . See Orchestrate agent behavior with generative AI , Add tools to custom agents , and Use connectors in Copilot Studio agents .

A. Use a Microsoft Graph connector to index the partner’s travel advisory content. Microsoft 365 Copilot connectors—formerly called Microsoft Graph connectors—index non-Microsoft enterprise content into Microsoft Graph, making it available for semantic knowledge grounding and citations. Microsoft Learn: Copilot connectors

D. Add the internal policy documents as a knowledge source. The SharePoint PDFs and policy documents should be connected as agent knowledge so generative answers can retrieve and summarize the relevant content. This is scalable and avoids manually maintaining document-specific topics. Microsoft Learn: SharePoint knowledge sources

B violates the requirement to avoid manually authored Q & A topics. C could produce ungrounded responses from unapproved public sources and would not satisfy the airline’s accuracy, security, or compliance requirements.

A. Configure prompt modifications at the system level. Centralized instructions enforce the required tone, disclaimers, response boundaries, and refusal behavior consistently across generative responses. Microsoft documents that prompt modification can define an agent’s personality, response format, permitted subjects, and behavior when an answer is unavailable. This avoids inconsistent manual changes across individual topics. Microsoft: Prompt modification

D. Configure Power Platform DLP policies. DLP policies govern which connectors, knowledge sources, HTTP endpoints, and channels the agent may use. They should be configured and validated before publication because a policy violation can prevent the agent from being published. DLP also protects against unauthorized data movement between business and non-business connectors. Microsoft: Data policies for agents

Why the others are incorrect: B creates duplicated, inconsistent disclaimers. C incorrectly treats moderation as a web-channel setting; moderation is configured for generative behavior rather than enforced only by embedding settings. E applies safeguards after publication and assumes filters must be configured separately for every channel, which would not provide the required centralized governance.

PartsOps per-user authentication → OAuth 2.0; WarrantyRules shared team credential → API key; Tool-selection context → Configure a server description that explains the MCP server ' s role.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The authentication choices must follow the identity requirements of each server. PartsOps performs attributable actions, including parts-request creation, so OAuth 2.0 is the appropriate mechanism for individual users to authorize access without sharing their credentials with the agent. That preserves user context and supports accountability for each transaction. WarrantyRules is explicitly read-only and uses a key shared by the agent team; it should therefore be configured with API-key authentication using the required header or query parameter. Applying the same authentication method to both servers would contradict the stated server designs. Authentication alone does not tell the orchestrator when a server is relevant. A concise, discriminating server description should identify PartsOps as the source for availability checks and parts-request creation and WarrantyRules as the source for warranty validation. Copilot Studio uses the names and descriptions of agents, topics, tools, and knowledge sources during generative orchestration. Accurate metadata reduces accidental calls, prevents the wrong server from handling a request, and makes the multi-agent plan more predictable during testing. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Configure MCP tools.

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

Trace each answer to its source → Instruct the agent to cite sources in knowledge settings; Retrieve from the centralized index → Configure Azure AI Search as the grounding data source; Use an enterprise-approved foundation model → Select a model from the Foundry model catalog.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Each requirement is controlled by a different configuration layer. Source traceability is a presentation and grounding requirement, so citations must be enabled or explicitly required for knowledge-based responses. That allows users to inspect the material used to support a policy answer; it is not achieved merely by choosing a model. Centralized retrieval is provided by connecting the existing Azure AI Search vector index as the knowledge source. This preserves the curated index, semantic or vector retrieval behavior, and enterprise management of the policy corpus instead of copying documents into the agent. Model governance is handled in the prompt configuration by selecting the approved model from the Microsoft Foundry model catalog. Publishing does not automatically replace an unapproved model, and Azure AI Search does not enforce the foundation-model selection. Together, the three settings form a complete RAG path: Azure AI Search retrieves authoritative passages, the governed model produces the response, and citation settings expose provenance. The configuration should then be tested with representative policy questions to confirm that the response is grounded and that the cited source actually supports the answer. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure generative answers by using Azure AI Search with Foundry; Configure custom prompts to use the Foundry model catalog.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Fabrikam needs both reusable prompt behavior and explicit model governance. A reusable custom prompt template provides the stable summarization instructions, expected structure, and input/output contract that can be applied wherever summarization is required. Within that prompt ' s configuration, selecting the approved model from the Microsoft Foundry model catalog controls which model generates the output. These are separate controls: the template governs the task, while the model selection satisfies the approved-model requirement. Publishing only deploys the configuration already selected; it does not automatically choose or enforce an approved model. Citations are valuable for grounded policy answers but do not determine the model used for summarization. Azure AI Search is the retrieval system for indexed enterprise policy content and is not required merely to apply a long-form summarization template. The prompt should be tested with representative transcripts for completeness, classification accuracy, output schema, safety, and latency. Where Fabrikam already uses a connected Foundry agent for this specialist function, the prompt and model settings should remain owned by that component rather than being duplicated in the primary agent. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure custom prompts to use the Foundry model catalog.

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

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The partner capability is described as an agent available only through a standardized agent-to-agent endpoint. That is the defining use case for an Agent2Agent connection. In Copilot Studio, the primary agent is configured with the external agent ' s A2A message endpoint and the applicable authentication details, after which orchestration can delegate shipment-tracking requests to it. An MCP server exposes tools or resources rather than an independently orchestrated partner agent, so option C changes the integration contract. An indexed knowledge source is also unsuitable because shipment status is dynamic and the requirement is delegation, not retrieval from a copied corpus. Generative responses in the primary agent would have no authoritative live shipment source and would violate the defined architecture. The A2A description should identify shipment tracking precisely so that it does not compete with unrelated agents or tools. Because external-agent support can be preview functionality, Fabrikam should also validate regional availability, authentication, error behavior, latency, and governance before production use. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Create a multi-agent solution by using A2A protocol.

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