AI Agent Builder Associate · 40% of the exam

Integrate and extend agents in Copilot Studio: free practice questions

5 sample questions from our 16-question bank for this domain — answers and explanations included. These are the same scenario-based style as the real Microsoft exam.

1. A Copilot Studio agent needs to retrieve live inventory data from an external REST API that requires a Bearer token in the Authorization header. The API has an OpenAPI 3.0 specification file available. What is the MOST efficient way to integrate this API into the agent?

  • A. Create a custom connector by importing the OpenAPI specification file, configure the connector's security definition to use OAuth 2.0 Bearer token authentication, and then add the connector as an action in the agent.✓ Correct
  • B. Write a Power Automate cloud flow that calls the HTTP action, pass the Bearer token as a hardcoded string in the flow, and invoke the flow from the agent.
  • C. Use the built-in Azure API Management action in Copilot Studio to proxy the REST API call without any connector configuration.
  • D. Copy the API endpoint URL directly into the agent's knowledge sources section and enable live web crawling to retrieve inventory data.
Explanation

Option A is correct because Copilot Studio supports importing OpenAPI specification files to auto-generate custom connectors, and the security definition in the spec maps directly to supported authentication schemes including OAuth 2.0 Bearer tokens — making this the fastest, most maintainable path. Option B would work functionally but hardcoding a Bearer token in a flow is a security anti-pattern and is far less efficient than using a connector with proper auth configuration. Option C is incorrect because Copilot Studio does not have a native 'Azure API Management action' that proxies arbitrary REST calls without connector setup. Option D is incorrect because the knowledge sources section is designed for document/FAQ-style retrieval, not live transactional API calls that require authentication headers.

2. Your organization's Copilot Studio agent needs to query a large semantic dataset stored in a Microsoft Fabric Lakehouse. The agent must retrieve contextually relevant rows based on natural language queries rather than exact keyword matches. Which Fabric feature should you configure as the agent's data integration endpoint?

  • A. A Fabric Data Pipeline that exports Lakehouse data to a SharePoint list, which the agent then indexes as a knowledge source.
  • B. A Fabric Real-Time Intelligence KQL queryset, called directly via a custom connector using a hardcoded KQL query string.
  • C. A Fabric AI Skill (OneLake AI Skill), which exposes Lakehouse data for natural language querying and can be connected to the agent as a knowledge source.✓ Correct
  • D. A Fabric Notebook that runs on a scheduled basis and writes results to Dataverse, which the agent queries through a Power Automate flow.
Explanation

Option C is correct. Microsoft Fabric's AI Skill (also referred to as OneLake AI Skill) is specifically designed to enable natural language querying over structured data in a Fabric Lakehouse or Warehouse. Copilot Studio supports connecting to a Fabric AI Skill as a knowledge source, enabling semantic retrieval without requiring exact keyword matches. Option A is incorrect because exporting to a SharePoint list introduces data staleness, loses semantic indexing, and is an unnecessarily complex pipeline for what Fabric AI Skill handles natively. Option B is incorrect because a KQL queryset requires a predefined, hardcoded query and cannot dynamically interpret natural language to generate queries — it would not satisfy the 'natural language' requirement. Option D is incorrect because the scheduled Notebook approach introduces latency, requires Dataverse licensing, and does not provide real-time or on-demand natural language querying of the Lakehouse data.

3. You are integrating a Copilot Studio agent with a Model Context Protocol (MCP) server that exposes several tools. During configuration, you notice the MCP server requires the agent to authenticate using an API key passed as a custom header. Which steps are required to correctly configure this MCP server connection in Copilot Studio? (Select TWO.)

  • A. In the agent's MCP server connection settings, select 'API Key' as the authentication type and specify the header name and secret value.✓ Correct
  • B. Register the MCP server as an Azure AD application and assign the agent's managed identity the 'MCP.ReadWrite' role before connecting.
  • C. Provide the MCP server's endpoint URL (the server manifest URL) when adding the MCP server as a tool source in the agent settings.✓ Correct
  • D. Export the MCP server's tool definitions as an OpenAPI 3.0 YAML file and import it as a custom connector instead, since Copilot Studio cannot natively connect to MCP servers.
  • E. Enable the 'Allow agent to call unauthenticated MCP servers' tenant-level setting in the Power Platform admin center to bypass API key validation.
  • F. Store the API key in Azure Key Vault and reference it using a Key Vault secret name in the Copilot Studio MCP connection configuration.
Explanation

Options A and C are correct. To connect a Copilot Studio agent to an MCP server: (1) you must supply the MCP server's endpoint/manifest URL so that Copilot Studio can discover the available tools — this is the primary identifier for the server connection; and (2) you must configure the appropriate authentication for that server, which for API key auth means selecting 'API Key' and specifying the header name and key value in the connection settings. Option B is incorrect because MCP server connections do not require Azure AD app registration or a special 'MCP.ReadWrite' role; this conflates Azure resource permissions with MCP authentication. Option D is incorrect because Copilot Studio does natively support MCP server connections as a first-class integration; there is no need to export and re-import as an OpenAPI custom connector. Option E is incorrect because there is no 'Allow agent to call unauthenticated MCP servers' tenant toggle in the Power Platform admin center; this is a fabricated setting. Option F is a plausible future pattern, but currently Copilot Studio's MCP connection settings accept the key value directly in the connection configuration rather than by referencing an Azure Key Vault secret name.

4. An architect is designing a Copilot Studio agent solution that integrates with Azure AI Foundry to leverage a custom fine-tuned language model. The agent must pass conversation history and retrieved document context from a SharePoint knowledge source to the Foundry model, and the Foundry model's response must be post-processed by a Power Automate flow before being shown to the user. Which statement BEST describes the correct integration architecture for this scenario?

  • A. Configure the agent to use Azure AI Foundry as a 'Generative Answers' knowledge source, which will automatically pass conversation history, retrieved documents, and route the response through Power Automate.
  • B. In Copilot Studio, add the Azure AI Foundry agent/model as a connected AI model in the agent's AI capabilities settings. Use a Generative Answers node to retrieve SharePoint context, pass both the context and conversation history as inputs to an action that calls the Foundry model, then chain a Power Automate flow action to post-process the output before the final Send Message node.✓ Correct
  • C. Deploy the fine-tuned model as an Azure OpenAI deployment and replace the agent's default language model with it in the tenant-level AI model settings in the Power Platform admin center, bypassing the need for an explicit Foundry connection.
  • D. Use a single Power Automate flow that calls both the SharePoint search API and the Azure AI Foundry REST API in sequence, returns the final processed response to the agent, and configure the agent to display the flow's output — eliminating the need for any Copilot Studio AI nodes.
Explanation

Option B is correct and reflects the proper layered architecture: (1) a Generative Answers node retrieves relevant SharePoint documents as grounding context; (2) an action node invokes the Azure AI Foundry-connected model with both conversation history and the retrieved context as explicit inputs; (3) a subsequent Power Automate flow action post-processes the Foundry model's output; and (4) the Send Message node presents the final result. This uses each component for its designed purpose. Option A is incorrect because Azure AI Foundry is not configured as a 'knowledge source' in Copilot Studio — knowledge sources are data stores (SharePoint, websites, files), not AI models. Foundry models are connected as AI model capabilities or called via actions. Additionally, Generative Answers does not automatically route through Power Automate. Option C is incorrect because swapping the tenant-level default AI model in Power Platform admin center applies globally and does not support per-agent fine-tuned model targeting via Foundry. Azure OpenAI deployments used this way do not automatically inherit Foundry-specific features. Option D is incorrect because while technically achievable, routing all AI inference through a single Power Automate flow bypasses Copilot Studio's native orchestration capabilities, conversation context management, and topic logic — it is an anti-pattern that creates an unmaintainable, brittle solution and does not leverage the platform's strengths.

5. A developer is building a multi-agent solution in which a Copilot Studio orchestrator agent delegates financial analysis tasks to a specialized sub-agent. The sub-agent must return a strictly structured JSON response containing specific fields (e.g., 'riskScore', 'recommendation', 'confidence') that the orchestrator will parse programmatically. Which combination of features should the developer use to guarantee the sub-agent's output adheres to the required schema? (Select TWO.)

  • A. Configure the sub-agent's generative AI response node to use 'Structured Outputs' mode and provide a JSON schema that enforces the required fields.✓ Correct
  • B. Add a SharePoint list as a knowledge source on the sub-agent and define column names that match the required JSON field names.
  • C. In the orchestrator agent, use a Condition node to check if each required field exists in the sub-agent's response and trigger a re-prompt if any field is missing.✓ Correct
  • D. Set the sub-agent's response format to 'plain text' and instruct the orchestrator to use regex parsing to extract field values from the prose response.
  • E. Use a Power Automate flow as the final step in the sub-agent's topic to serialize the output variables into a JSON object with the required schema before returning to the orchestrator.
  • F. Enable the 'strict mode' setting on the sub-agent's Azure OpenAI model connection to automatically coerce all outputs to valid JSON.
Explanation

Options A and C are correct. Structured Outputs (Option A) is the primary mechanism for enforcing JSON schema compliance on a generative AI node's output — by providing a schema, the model is constrained to produce only valid, schema-conformant JSON, eliminating missing or extra fields. Option C provides a runtime safety net: even with Structured Outputs, a defensive Condition node in the orchestrator that validates field presence and re-prompts on failure is a best-practice error-handling pattern for multi-agent reliability. Option B is incorrect because SharePoint list columns have no connection to JSON output schema enforcement; they are a knowledge source feature, not an output formatting mechanism. Option D is incorrect because plain text with regex parsing is fragile, unmaintainable, and the direct opposite of using structured outputs — it introduces parsing errors and defeats the purpose of reliable agent-to-agent communication. Option E is partially viable but sub-optimal: using a Power Automate flow solely to serialize output adds unnecessary latency and complexity when Structured Outputs already handles this within the agent node itself. Option F is incorrect because 'strict mode' in this context (as described) is not an actual Copilot Studio setting; Azure OpenAI's 'strict' mode for function calling is configured at the API level, not as a Copilot Studio agent connection toggle.

11 more questions in this domain

Practice the full bank with instant grading, flashcards, and a timed mock exam.

Start practicing free
Integrate and extend agents in Copilot Studio — Free AI Agent Builder Associate Practice Questions | DataCertPrep — Certification Prep