Question 55 — AB-620 Practice Exam 5
A maker wants to add a prebuilt Microsoft MCP connector to a Copilot Studio agent and does not have a custom server URL. What workflow should the maker use? (Select one answer)
Open New tool, enter a server name and URL, authorize the endpoint, and publish the agent
Open New tool, enter a server description, configure Streamable HTTP, and select the Microsoft service
Open Model Context Protocol, create a custom endpoint, enter Microsoft-managed connection details, and authorize it
Open Model Context Protocol from Add a tool, select the prebuilt connector, authorize the connection, and select Add and configure
Correct answers
Open Model Context Protocol from Add a tool, select the prebuilt connector, authorize the connection, and select Add and configure
Explanations
Correct:
Open Model Context Protocol from Add a tool, select the prebuilt connector, authorize the connection, and select Add and configure
Prebuilt Microsoft MCP connectors are selected from the MCP catalog. The maker authorizes the connection and then adds and configures the connector. Microsoft manages the endpoint details, so the maker does not need to supply a custom server URL or server description.
Wrong:
Open New tool, enter a server name and URL, authorize the endpoint, and publish the agent
Entering custom server details is part of custom MCP server onboarding rather than the catalog workflow for a prebuilt Microsoft connector.
Open New tool, enter a server description, configure Streamable HTTP, and select the Microsoft service
A maker does not manually configure an endpoint or server description when adding a prebuilt Microsoft MCP connector. Those connection details are managed by Microsoft.
Open Model Context Protocol, create a custom endpoint, enter Microsoft-managed connection details, and authorize it
A prebuilt connector does not require the maker to create or enter a custom endpoint. The connector supplies the endpoint configuration automatically.