Connect External Tools via the Model Context Protocol (MCP) CERTIFIED-GITLAB-DUO-AI-ASSOCIATE Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A company wants to use GitLab Duo to interact with multiple external services: a project management tool, a monitoring system, and a documentation wiki. They want a unified way to connect all three without writing custom code for each. What is the primary benefit of using MCP in this scenario?

   • AMCP automatically migrates all external data into GitLab's native storage.
   • BMCP eliminates the need for any external tools by embedding their functionality directly into GitLab Duo.
   • CMCP provides a standardized protocol so GitLab Duo can interact with all three services through their respective MCP servers.
   • DMCP replaces the need for APIs by using a proprietary data format.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   What is a key security best practice when connecting external tools via MCP?

   • AUse the same API key for all MCP servers to simplify management
   • BDisable authentication for MCP servers to avoid configuration complexity
   • CStore authentication tokens securely and use scoped permissions
   • DGrant MCP servers full access to all GitLab projects
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   What is the primary purpose of the Model Context Protocol (MCP) in the context of GitLab Duo?

   • ATo create a new programming language for building GitLab extensions.
   • BTo provide a standardized way for AI assistants to access and interact with external tools and data sources.
   • CTo encrypt all data transmitted between GitLab and its users.
   • DTo replace GitLab's CI/CD pipeline with a new AI-driven automation engine.
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A development team wants to let GitLab Duo Chat query their internal incident-management system to fetch recent incident statuses during merge-request discussions. The incident system exposes a REST API but has no existing MCP server. The team has already installed the GitLab Duo CLI and configured the MCP client. What should the team do to enable this integration?

   • AConfigure GitLab Duo Chat to call the REST API directly by adding the API endpoint to the GitLab configuration file.
   • BInstall the incident system's API client as a plugin directly into the GitLab Duo CLI.
   • CBuild a custom MCP server that wraps the REST API, register it with the MCP client, and configure the server's access token with read-only permissions.
   • DAsk the incident system vendor to expose a GraphQL endpoint, then use GitLab Duo's built-in GraphQL connector.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   An organization is deploying an MCP server that connects GitLab Duo to a sensitive internal service. The server will run on a shared host. The security team mandates that the server's configuration, including credentials, must not be readable by other processes on the host. Which approach should be used?

   • AEmbed the credentials in the GitLab Duo client configuration so the server does not need to store them.
   • BPlace the credentials in the MCP server's configuration file and set the file permissions to 644.
   • CUse environment variables in the shell script that starts the MCP server.
   • DStore credentials in a secrets manager and have the MCP server retrieve them at runtime via an authenticated API.
   Reveal Solution Discussion Select an answer first