Extend Agent Capabilities with Integrations CERTIFIED-GITLAB-DUO-AI-ASSOCIATE Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A development team wants the GitLab Duo agent to be able to create merge requests in a self-hosted GitLab instance and also post comments to a Slack channel. Both systems have APIs. What is the most efficient way to enable these capabilities?

   • AWrite a custom script that calls both APIs and have the agent execute the script via a single MCP server.
   • BUse GitLab Duo's built-in merge request creation and add Slack as a native integration.
   • CConfigure two MCP servers: one that wraps the GitLab API and another that wraps the Slack API, then register both in GitLab Duo.
   • DAsk the agent to use its built-in web search to find the APIs and call them directly.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   What is the purpose of managing MCP tools in GitLab Duo?

   • ATo uninstall the MCP servers from their hosting environment.
   • BTo rewrite the source code of the external tools for better performance.
   • CTo control which external tools the agent can use, ensuring a focused and secure set of capabilities.
   • DTo create backups of the data stored in the external tools.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   How does a user typically invoke an MCP tool during a conversation with the GitLab Duo agent?

   • ABy restarting the GitLab Duo agent to load the new tool.
   • BBy manually copying data from the external tool and pasting it into the chat.
   • CBy writing a script in the chat that directly calls the external tool's API.
   • DBy asking the agent in natural language to perform a task that requires the tool.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A team has configured an MCP server for a code-review tool. The server starts successfully, but the GitLab Duo agent reports that no tools are available from it. The server logs show it is listening on port 8080. Which configuration detail is most likely causing the issue?

   • AThe MCP server URL in GitLab Duo points to http://localhost:8080 instead of the server's actual hostname or IP.
   • BThe MCP server was configured with a bearer token that is too short.
   • CThe team enabled too many tools on the MCP server, exceeding GitLab Duo's per-server limit.
   • DThe MCP server uses JSON-RPC over HTTP, which GitLab Duo does not support for MCP.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   Which action is an example of 'organizing' MCP tools in GitLab Duo?

   • ADeleting the external tool's repository from GitLab.
   • BUpgrading the MCP server to a newer version.
   • CChanging the authentication token for the external service.
   • DGrouping related tools into logical categories for easier discovery and use.
   Reveal Solution Discussion Select an answer first