Microsoft Designing and Building Integrated AI Agent Solutions in Copilot Studio AB-620 Exam Questions

Answer : A, E

A custom prompt provides a reusable instruction template that controls how the model performs a specific task. The template can define tone, output structure, formatting, constraints, examples, and fallback behavior. It can then be added as an agent-level tool, called from a topic, or used within an agent flow. This makes option A the correct mechanism for applying consistent instructions wherever the structured response is generated.

The prompt's model is configured separately in the prompt editor. The builder selects the required enterprise-approved model from the Model field or connects an approved deployment from the Microsoft Foundry model catalog. After that model is selected for the custom prompt, every execution of that prompt uses the selected model, making option E correct.

Publishing does not automatically select an appropriate Foundry model; the model must be explicitly configured. Azure AI Search controls retrieval and grounding, not model selection. Citations provide source traceability but do not limit execution to approved models. Defining instructions independently in individual topics would duplicate configuration and weaken consistency.

Answer : A

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.

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

Answer : C

Comprehensive and Detailed 150 to 250 words of Explanation From [Microsoft AB-620 study guide]: Azure AI Search must be configured as the authoritative retrieval source, with ungrounded or general-knowledge responses disabled. In the retrieval-augmented generation process, Copilot Studio first reformulates the user's question, searches the connected vector index, and supplies relevant results to the Microsoft Foundry-hosted model for response generation. Requiring grounding prevents the model from answering solely from its pretrained knowledge when Azure AI Search returns no sufficiently relevant content. In that situation, the agent should return no generated answer and follow its configured fallback or escalation behavior. Selecting a Foundry model alone does not enforce grounding because model selection controls the generation layer, not the retrieval requirement. Citations provide traceability but likewise do not prevent an unsupported answer. Uploading duplicate documents would introduce another knowledge store and undermine Azure AI Search as the controlled enterprise index. The Azure AI Search connection should identify the intended vector index and use semantic ranking where appropriate. Testing should confirm that valid queries return supported answers and citations, while out-of-scope queries produce no ungrounded response. Study Guide alignment: Integrate and extend agents in Copilot Studio Connect to Azure AI Search; Integrate agents with Azure Configure generative answers by using Azure AI Search with Foundry.

Answer : A

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.

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

Answer : C, E

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

First, create a custom solution in the development environment and add the existing agent by selecting Add existing Agent Agent. The solution acts as the application lifecycle management package that contains the agent and its dependent components. Required objects such as agent flows, environment variables, connection references, and custom connectors should also be included when applicable.

After the agent and its dependencies are included, export the solution from the development environment. Microsoft's documented procedure starts from the list of unmanaged solutions and exports the solution containing the agent. During the export process, the maker can select the appropriate package type. Production deployments commonly use a managed export, but the source development solution remains unmanaged; it does not need to be converted before export.

Removing topics directly from the solution is specifically discouraged because changing or removing agent components outside the standard Copilot Studio authoring interface can cause export or import failures. Publishing the agent to a channel is also unrelated to creating a solution package. After the solution is imported into production, the imported agent must be configured, tested, and published in that environment.

Relevant study-guide area: Test and manage agents Implement application lifecycle management for agents in Copilot Studio Create a solution and add existing agents to a solution. See Export and import agents using solutions.

Answer : B

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A Fabric Data Agent is the capability designed for questions that must be answered from governed analytical data. Fabrikam's backlog, SLA-risk, parts-shortage, and dispatch-delay measures already reside behind a Fabric semantic model, so delegating these requests to the data agent preserves the business definitions, relationships, and security applied in Fabric. The result can be returned in a structured form suitable for weekly operational review rather than being estimated from general model knowledge. A Foundry agent is already assigned to summarization and classification of long-form text; it is not the authoritative source for operational KPIs. An MCP server is appropriate when the user must perform a transaction, such as creating a parts request, but the question asks for performance information rather than an update. Azure AI Search supports document retrieval for policies and procedures, not calculation over the Fabric semantic model. The primary agent's description for the Fabric specialist should explicitly mention the supported metrics so generative orchestration consistently delegates those requests instead of attempting an unsupported generative answer. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate a Fabric data agent.

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

Answer : A, D

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.