[GitLab201] GitLab 201 Tool Certification Exam
Preparation
**Question 1. Which GitLab visibility level allows any signed‑in user to view the project but
restricts push access?**
A) Private
B) Internal
C) Public
D) Confidential
Answer: B
Explanation: Internal projects are visible to any authenticated GitLab user, while Private limits
visibility to members and Public is open to anyone on the internet.
**Question 2. In a GitLab group hierarchy, which role inherits permissions from its parent group
to sub‑groups automatically?**
A) Guest
B) Reporter
C) Maintainer
D) Owner
Answer: D
Explanation: The Owner role at a parent group propagates full permissions to all sub‑groups,
ensuring consistent administrative control.
**Question 3. Which of the following best describes a “Scoped Label” in GitLab?**
A) A label that can only be used in one project
B) A label with a namespace prefix to define a specific workflow stage
C) A label that automatically assigns an issue to a milestone
D) A label that deletes itself after a set period
Answer: B
,[GitLab201] GitLab 201 Tool Certification Exam
Preparation
Explanation: Scoped labels use a prefix (e.g., `workflow::review`) to categorize issues and enable
automation on boards.
**Question 4. When creating an issue, which feature helps ensure that required fields are
always filled out?**
A) Issue Templates
B) Quick Actions
C) Epic Links
D) Snippets
Answer: A
Explanation: Issue templates provide a predefined structure, prompting users to supply
necessary information each time an issue is opened.
**Question 5. What is the primary purpose of the “Internal Note” in a GitLab issue comment?**
A) To notify all project members via email
B) To add a comment visible only to project members with at least Reporter role
C) To create a public discussion thread for external contributors
D) To automatically close the issue after 24 hours
Answer: B
Explanation: Internal notes are hidden from external users and only visible to members with
sufficient permissions, keeping sensitive information private.
**Question 6. Which action moves an issue from one project to another while preserving its
history?**
A) Promote to Epic
B) Transfer Issue
C) Duplicate Issue
,[GitLab201] GitLab 201 Tool Certification Exam
Preparation
Duplicate Issue
D) Archive Issue
Answer: B
Explanation: The “Transfer Issue” feature relocates the issue to a different project while
retaining comments, labels, and activity logs.
**Question 7. In GitLab boards, which column is automatically populated when an issue
receives the label `workflow::testing`?**
A) Todo
B) In Review
C) Testing
D) Done
Answer: C
Explanation: Scoped labels can be mapped to board columns; `workflow::testing` typically drives
issues into the “Testing” column.
**Question 8. Which Merge Request tab shows the list of jobs that ran for the MR’s pipeline?**
A) Changes
B) Commits
C) Pipelines
D) Reviews
Answer: C
Explanation: The Pipelines tab displays CI/CD job results associated with the current MR,
allowing reviewers to see build status.
**Question 9. What does adding the “Draft:” prefix to a Merge Request title accomplish?**
, [GitLab201] GitLab 201 Tool Certification Exam
Preparation
A) Enables automatic squashing of commits
B) Prevents the MR from being merged until the prefix is removed
C) Assigns the MR to the security team by default
D) Triggers a mandatory code‑owner approval rule
Answer: B
Explanation: Draft MRs are marked as work‑in‑progress; GitLab disables the “Merge” button
until the prefix is removed.
**Question 10. Which role is allowed to approve a Merge Request but not to push directly to
the target branch?**
A) Maintainer
B) Developer
C) Reporter
D) Guest
Answer: B
Explanation: Developers can review and approve MRs but lack direct push rights to protected
branches, supporting a review‑before‑merge workflow.
**Question 11. In GitLab’s approval rules, what does the “Code Owner” rule enforce?**
A) At least one maintainer must approve every MR
B) Only users listed in the CODEOWNERS file can approve certain files or directories
C) Every MR must receive three approvals from any role
D) The MR must pass a security scan before approval
Answer: B
Explanation: The Code Owner rule ties approval authority to the CODEOWNERS file, ensuring
domain experts review relevant changes.
Preparation
**Question 1. Which GitLab visibility level allows any signed‑in user to view the project but
restricts push access?**
A) Private
B) Internal
C) Public
D) Confidential
Answer: B
Explanation: Internal projects are visible to any authenticated GitLab user, while Private limits
visibility to members and Public is open to anyone on the internet.
**Question 2. In a GitLab group hierarchy, which role inherits permissions from its parent group
to sub‑groups automatically?**
A) Guest
B) Reporter
C) Maintainer
D) Owner
Answer: D
Explanation: The Owner role at a parent group propagates full permissions to all sub‑groups,
ensuring consistent administrative control.
**Question 3. Which of the following best describes a “Scoped Label” in GitLab?**
A) A label that can only be used in one project
B) A label with a namespace prefix to define a specific workflow stage
C) A label that automatically assigns an issue to a milestone
D) A label that deletes itself after a set period
Answer: B
,[GitLab201] GitLab 201 Tool Certification Exam
Preparation
Explanation: Scoped labels use a prefix (e.g., `workflow::review`) to categorize issues and enable
automation on boards.
**Question 4. When creating an issue, which feature helps ensure that required fields are
always filled out?**
A) Issue Templates
B) Quick Actions
C) Epic Links
D) Snippets
Answer: A
Explanation: Issue templates provide a predefined structure, prompting users to supply
necessary information each time an issue is opened.
**Question 5. What is the primary purpose of the “Internal Note” in a GitLab issue comment?**
A) To notify all project members via email
B) To add a comment visible only to project members with at least Reporter role
C) To create a public discussion thread for external contributors
D) To automatically close the issue after 24 hours
Answer: B
Explanation: Internal notes are hidden from external users and only visible to members with
sufficient permissions, keeping sensitive information private.
**Question 6. Which action moves an issue from one project to another while preserving its
history?**
A) Promote to Epic
B) Transfer Issue
C) Duplicate Issue
,[GitLab201] GitLab 201 Tool Certification Exam
Preparation
Duplicate Issue
D) Archive Issue
Answer: B
Explanation: The “Transfer Issue” feature relocates the issue to a different project while
retaining comments, labels, and activity logs.
**Question 7. In GitLab boards, which column is automatically populated when an issue
receives the label `workflow::testing`?**
A) Todo
B) In Review
C) Testing
D) Done
Answer: C
Explanation: Scoped labels can be mapped to board columns; `workflow::testing` typically drives
issues into the “Testing” column.
**Question 8. Which Merge Request tab shows the list of jobs that ran for the MR’s pipeline?**
A) Changes
B) Commits
C) Pipelines
D) Reviews
Answer: C
Explanation: The Pipelines tab displays CI/CD job results associated with the current MR,
allowing reviewers to see build status.
**Question 9. What does adding the “Draft:” prefix to a Merge Request title accomplish?**
, [GitLab201] GitLab 201 Tool Certification Exam
Preparation
A) Enables automatic squashing of commits
B) Prevents the MR from being merged until the prefix is removed
C) Assigns the MR to the security team by default
D) Triggers a mandatory code‑owner approval rule
Answer: B
Explanation: Draft MRs are marked as work‑in‑progress; GitLab disables the “Merge” button
until the prefix is removed.
**Question 10. Which role is allowed to approve a Merge Request but not to push directly to
the target branch?**
A) Maintainer
B) Developer
C) Reporter
D) Guest
Answer: B
Explanation: Developers can review and approve MRs but lack direct push rights to protected
branches, supporting a review‑before‑merge workflow.
**Question 11. In GitLab’s approval rules, what does the “Code Owner” rule enforce?**
A) At least one maintainer must approve every MR
B) Only users listed in the CODEOWNERS file can approve certain files or directories
C) Every MR must receive three approvals from any role
D) The MR must pass a security scan before approval
Answer: B
Explanation: The Code Owner rule ties approval authority to the CODEOWNERS file, ensuring
domain experts review relevant changes.
