Q01 - Question
Woodgrove Bank wants its IT service desk agent in Copilot Studio to submit requests to an internal IT service management API. No prebuilt connector exists for this API. The organization also plans to use the same API integration in Power Automate and Power Apps. What should you use?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. A REST API tool created in Copilot Studio from an OpenAPI v2 specification
- B. A connector added to the agent as a knowledge source
- C. A custom connector that exposes the API through OpenAPI, added to the agent as a connector tool
- D. A prebuilt standard connector selected from the connector gallery
C is correct.
Explanation: A custom connector exposes an organization API through OpenAPI. You can reuse it across Copilot Studio, Power Automate, Power Apps, and Azure Logic Apps, which meets the reuse requirement.
A is incorrect: A REST API tool is created in Copilot Studio for a single use case when no connector exists. It is also preview-only and not intended for production use.
B is incorrect: A connector used as a knowledge source queries live data to ground responses. It does not let the agent submit requests in an external system.
D is incorrect: No prebuilt connector exists for this internal API.
Q02 - Question
A developer at Woodgrove Bank creates a custom connector for the CMDB API. Another maker must add this custom connector as a tool to the IT service desk agent in Copilot Studio. What should you do before the maker adds the tool?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. Share the custom connector with the maker by using Can view or Can edit permission in the Power Apps maker portal
- B. Share the connection with the maker by using Can use + share permission in Power Apps Connections
- C. Recreate the CMDB integration as a REST API tool in the agent
- D. Assign Power Fx formulas to all inputs of the connector action
A is correct.
Explanation: Share a custom connector with the intended makers by using Can view or Can edit permission in the Power Apps maker portal before they add it as a tool.
B is incorrect: Sharing a connection with Can use + share permission lets other makers manage and test that connection. It does not share the custom connector itself.
C is incorrect: A REST API tool is for cases where no connector exists. It is also preview-only and not suitable for production use.
D is incorrect: Input configuration defines how values are supplied to the action. It does not give the maker access to the custom connector.
Q03 - Question
In a Woodgrove Bank escalation conversation, the agent must retrieve a CMDB configuration record at a specific step every time. The call must use fixed parameter values. The team does not want the generative orchestrator to decide whether to call the action. What should you configure?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. An agent-level connector tool with a more detailed description
- B. The CMDB connector as a knowledge source for the agent
- C. Connector tool inputs set to dynamically fill with AI
- D. A topic-level call to the connector action from a topic node
D is correct.
Explanation: Topic-level connector calls give deterministic control over when the action runs and which parameters it uses. Use a topic node when execution must be predictable.
A is incorrect: Agent-level tools are selected by generative orchestration. A better description improves selection, but the orchestrator still decides when to invoke the tool.
B is incorrect: A connector used as a knowledge source grounds responses with live data. It does not provide deterministic action execution at a specific step.
C is incorrect: Inputs that dynamically fill with AI do not meet the requirement for fixed parameter values.
Q04 - Question
Woodgrove Bank adds a connector tool that looks up employee IT profiles. Each employee has an account in the target system. Each employee must see only the data that their own account permits. Which credential mode should you use for the connector tool?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. Maker-provided credentials
- B. User-provided credentials
- C. A REST API tool with the None authentication option
- D. A connection shared with all employees by using Can use + share permission
B is correct.
Explanation: User-provided credentials are the default mode. Each user signs in at first tool use, and the agent acts with that user's permissions. Use this mode when data access must be scoped to each user.
A is incorrect: Maker-provided credentials use one shared identity for all users. This suits a common data scope, not per-user access, and it requires an authenticated channel.
C is incorrect: None authentication sends calls without a user identity. It cannot scope data to each employee's permissions.
D is incorrect: Can use + share permission on a connection lets other makers manage and test it. It does not scope data access for each end user.
Q05 - Question
You create a REST API tool in Copilot Studio from an OpenAPI specification. The target API requires an API key that is sent in a request header named x-api-key. You select API key authentication. Which two settings must you configure? Each correct answer presents part of the solution.
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Multi-select
- A. The actual parameter name that the API expects
- B. The identity provider client credentials and token endpoint
- C. Header as the parameter location
- D. A connection shared with other makers by using Can use + share permission
A and C are correct.
Explanation: API key authentication for a REST API tool requires a display label, the actual parameter name, and a location of Header or Query. For this API, set the parameter name to x-api-key and set the location to Header.
B is incorrect: Identity provider credentials and endpoint configuration are required for OAuth 2.0, not for API key authentication.
D is incorrect: Sharing a connection with Can use + share permission applies to connector tool connections in Power Apps. It is not part of API key configuration for a REST API tool.
Q06 - Question
Adatum Corporation has a customer service agent in Copilot Studio. The team wants to add a tool that the AI orchestrator can select automatically during any conversation. The team doesn't need the tool to run at a fixed step in a specific topic. Where should the team add the tool?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. Add the tool inside one topic by using Add node and then Add a tool.
- B. Add a Send HTTP request node to each topic that might need the tool.
- C. Add the tool at the agent level.
- D. Call an agent flow from a condition node in a single topic.
C is correct.
Explanation: The evidence states that tools added at the agent level are selected by the AI orchestrator automatically during any conversation. Use this approach when the tool doesn't need to run at a specific, controlled point in a topic.
A is incorrect: A tool added inside a topic runs at a specific point on the topic canvas. It isn't selected by the orchestrator across all conversations.
B is incorrect: The Send HTTP request node is an ad-hoc REST API call within a topic. It runs where you place it and doesn't let the orchestrator select it during any conversation.
D is incorrect: Calling an agent flow from a topic runs the flow at that step in that topic only. It doesn't meet the requirement for orchestrator selection across conversations.
Q07 - Question
A maker adds a connector tool to a topic in Copilot Studio. The connector reads records from a business system. Each user must only get data that their own permissions allow. Which authentication option should the maker configure for the connector tool?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. Maker-provided authentication, so the tool runs with the maker's identity.
- B. End-user authentication.
- C. Store the maker's credentials in an environment variable and reference it in the connector tool.
- D. Replace the connector tool with a Send HTTP request node that uses a single static API key.
B is correct.
Explanation: The evidence states that end-user authentication uses each user's permissions when the connector tool runs. This meets the requirement that users only get data their own permissions allow.
A is incorrect: Maker-provided authentication uses a shared maker identity for all users. It also requires an authenticated channel.
C is incorrect: This approach still uses one shared identity for every user. It doesn't apply each user's permissions.
D is incorrect: A single static API key is one shared credential, not each user's permissions. The HTTP request node is also intended for cases where no connector exists.
Q08 - Question
A maker wants to call an existing agent flow from a topic by using Add a tool. The flow doesn't appear in the tool picker in Copilot Studio. Which two conditions could cause this issue? Each correct answer presents a complete solution. Select two.
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Multiple choice
- A. The flow doesn't use the When an agent calls the flow trigger.
- B. The Asynchronous response toggle in the Respond to the agent action is set to Off.
- C. The flow includes actions after the Respond to the agent action.
- D. The flow isn't a solution flow.
A and D are correct.
Explanation: The evidence states that the "When an agent calls the flow" trigger makes a flow callable from a topic or the agent orchestrator. A flow without this trigger doesn't appear in the tool picker. The flow must also be a solution flow to appear in Copilot Studio.
B is incorrect: Setting Asynchronous response to Off is a requirement. It makes the topic wait for the flow outputs before it continues.
C is incorrect: Actions after the Respond to the agent action are allowed. They run asynchronously after the topic receives its outputs.
Q09 - Question
A customer-facing topic uses a Send HTTP request node to call a carrier tracking API. When the API is unavailable, the conversation stops without a useful message. The maker wants the topic to show a clear fallback message and not expose raw error details. What should the maker configure?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. Keep the default Raise an error mode so the system On Error topic handles the failure.
- B. Increase the Request timeout value so the request doesn't fail.
- C. Change the body option to Raw content so errors are returned as text in the chat.
- D. Select Continue on error, save the status code and error response to topic variables, and add a condition that checks the status code.
D is correct.
Explanation: The evidence states that configuring "Continue on error" lets the topic continue after the node. You save the HTTP status code and error response to variables, such as Topic.StatusCode and Topic.ErrorResponse, and then add a condition. A value of 200 shows the result, and other values route to a fallback message.
A is incorrect: "Raise an error" triggers the system On Error topic and stops the current flow. This might be acceptable for internal agents, but not for a customer-facing topic.
B is incorrect: A longer Request timeout can help when an API responds slowly under load. It doesn't handle an API that is unavailable or a tracking number that doesn't exist.
C is incorrect: Raw content controls the request body format sent to the API. It doesn't handle failed responses, and showing raw error details in the chat isn't the goal.
Q10 - Question
A maker configures a Send HTTP request node with a GET request to a carrier tracking API. The request succeeds. The maker now needs a message node to show the shipment status field from the JSON response. What should the maker do?
Domain: Integrate and extend agents in Copilot Studio (40–45%) Type: Single choice
- A. Set Response data type to From Sample Data, use Get schema from sample JSON with a sample response, save the response to Topic.TrackingResponse, and reference Topic.TrackingResponse.status.
- B. Change the method to POST and select JSON Content for the request body.
- C. Add a Content-Type: application/json header to the request.
- D. Move the request into an agent flow and return the status by using the Respond to the agent action.
A is correct.
Explanation: The evidence states that you must define the response shape so Copilot Studio can expose the response fields as variables. You paste a sample JSON response from the API documentation, confirm the schema, and save the response to a variable. Then use Power Fx dot notation, such as Topic.TrackingResponse.status.
B is incorrect: Retrieving shipment status uses GET with No Content. Changing the method and body doesn't define the response schema.
C is incorrect: The Content-Type header tells the API how to parse a request body. It doesn't expose response fields as topic variables.
D is incorrect: An agent flow is for multi-step workflows or reusable logic. This integration is a single request in one topic, so the HTTP request node response schema is enough.