Publish Custom Agents and Flows CERTIFIED-GITLAB-DUO-AI-ASSOCIATE Practice Questions (Page 2)

Questions 6–10

1. 6foundation · medium

   What is the default visibility for a newly created custom flow in a private GitLab project?

   • AHidden, accessible only to the instance administrator
   • BPrivate, accessible only to project members
   • CInternal, accessible to all logged-in users
   • DPublic, accessible to all GitLab users
   Reveal Solution Discussion Select an answer first
2. 7foundation · medium

   What is the first step in publishing a custom flow for GitLab Duo?

   • ARequest approval from the GitLab administrator
   • BDefine the flow's steps and logic in a configuration file
   • CCreate a new GitLab group for the flow
   • DCompile the flow into a binary executable
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   An organization wants to publish a custom agent that is only accessible to members of the 'Engineering' group. They also want to ensure that the agent's source code is not visible to users outside the group. What visibility setting should they choose for the agent?

   • APublic
   • BPrivate
   • CInternal
   • DRestricted
   Reveal Solution Discussion Select an answer first
5. 9foundation · medium

   Which setting controls who can access a published custom agent in GitLab Duo?

   • AThe agent's response language
   • BVisibility level of the project where the agent is defined
   • CThe agent's name and description
   • DThe number of versions published
   Reveal Solution Discussion Select an answer first
6. 10foundation · medium

   How are custom flows typically integrated with GitLab Duo after they are published?

   • ABy referencing the flow in GitLab Duo chat or automation settings
   • BBy installing a separate plugin in the GitLab web interface
   • CBy adding the flow to the GitLab CI/CD pipeline as a job
   • DBy exporting the flow to an external workflow engine
   Reveal Solution Discussion Select an answer first