Microsoft Designing and Building Integrated AI Agent Solutions in Copilot Studio AB-620 Exam Dumps: Updated Questions & Answers (August 2026)

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.

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.

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.

Support grounding from indexed data → Retrieve indexed content

Use existing access controls from the source system → Respect existing permissions

Support read-only operations → Prevent transactional updates

Microsoft 365 Copilot connectors index non-Microsoft enterprise content into Microsoft Graph for semantic grounding. They preserve source-level access controls so users receive only content they are authorized to access. Because the connector is configured as a knowledge source, its purpose is retrieval—not executing transactional updates. Microsoft Learn: Copilot connectors as knowledge sources

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 .

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.

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

Reusable governed components → Export or package them as a component collection; Environment-specific connections and secrets → Use connection references and environment variables; Automated staged approvals → Use an ALM pipeline.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Reusable authored assets should be packaged in a governed component collection so the same topics and prompts can be promoted and consumed without uncontrolled copying. Values that differ by environment must remain outside those authored assets: connection references bind connectors in the target environment, while environment variables supply endpoints, IDs, and other configuration; secret values should use the appropriate secret mechanism. A Power Platform pipeline then moves the solution through defined stages and can impose approvals and validation before production. Hard-coding configuration would make every promotion a source edit, and copying components between agents would create divergent versions. The collection and the solution still need explicit ownership and dependency management, because a shared component update can affect multiple agents. Before each stage, validate current variable values, connections, component versions, and target permissions. After deployment, publish and run the same evaluation set in the target environment so the team verifies not only package transport but also runtime behavior under target data and identity controls. Study Guide alignment: Test and manage agents > Implement application lifecycle management for agents in Copilot Studio > Add existing agents to a solution; Create and use environment variables; Implement Power Platform Pipelines.

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