GitLab Certified Fundamentals Associate

Last checked November 10, 2026 against the official GitLab exam page.

1. Question 1Essential GitLab Functions

   A top-level group named Platform has a subgroup named Payments that contains several projects. A developer is added to Platform with the Maintainer role. What access does the developer get in Payments?

   1. ANo access to Payments until the developer is also invited to the subgroup separately
   2. BGuest access only, because subgroups cap any inherited role at the Guest level
   3. COwner rights over Payments, because a parent group Maintainer always gains ownership of every subgroup
   4. DMaintainer access to the projects in Payments, inherited from the parent group membership
   Show answer and explanationHide answer

   Correct answer: D

   Group memberships are inherited by subgroups and the projects inside them, so the developer keeps Maintainer access in Payments. The other options are wrong because no separate invitation is needed, Maintainer does not turn into Owner, and inherited roles are not capped at Guest.

2. Question 2GitLab CI/CD Functions

   A pipeline defines three stages: build, test, and deploy. The build stage has a job named compile, the test stage has jobs named unit and lint, and the deploy stage has a job named publish. In what order does GitLab run them by default?

   1. AAll four jobs start at the same time because the stages keyword only labels jobs and does not control order
   2. BThe compile job runs first, then unit and lint run in parallel, and publish waits for them to succeed
   3. CThe unit and lint jobs run first, then compile, and publish runs last to prepare the environment
   4. Dpublish runs first to reserve the environment, then compile, and then unit and lint in sequence
   Show answer and explanationHide answer

   Correct answer: B

   Stages run in the order they are listed, and jobs inside one stage run in parallel. A later stage starts only after the jobs of the earlier stage succeed, so compile goes first and publish goes last. The other options ignore stage order or reverse it.

3. Question 3GitLab Overview

   A team wants every merge request to trigger automatic builds and tests, so that a broken change is found within minutes of being pushed. Which practice does this describe?

   1. AContinuous deployment, where every change that passes the tests is released to production automatically
   2. BContinuous delivery, where a person approves each change before it is released to production
   3. CIssue tracking, where each new change is logged as a ticket and assigned to a reviewer for triage
   4. DContinuous integration, where changes merge often and each one is automatically built and tested
   Show answer and explanationHide answer

   Correct answer: D

   Continuous integration means changes are merged often and each one is built and tested automatically, which is what this team wants. Continuous deployment and continuous delivery are about releasing to production, and issue tracking does not run builds or tests.

4. Question 4GitLab Security Functions

   Which scanner type inspects source code for security weaknesses without running the application?

   1. ADAST, which sends requests to a running application and observes how it responds
   2. BContainer scanning, which checks the packages inside a built image against known vulnerabilities
   3. CSAST, static application security testing, which analyzes source code without running it
   4. DLicense compliance, which checks the open-source licenses used by project dependencies
   Show answer and explanationHide answer

   Correct answer: C

   SAST, or static application security testing, analyzes source code without executing the application. DAST tests a running application, container scanning checks image contents, and license compliance checks licenses rather than security weaknesses.

5. Question 5GitLab Agile Planning

   What is the main purpose of labels on issues and merge requests in GitLab?

   1. ATo categorize items so they can be filtered, searched, and shown as lists on issue boards
   2. BTo give a user Maintainer permissions on a project without changing group membership
   3. CTo store the binary files that a pipeline produces so that they can be downloaded later
   4. DTo set a hard deadline that automatically publishes a release when the date is reached
   Show answer and explanationHide answer

   Correct answer: A

   Labels categorize issues and merge requests, and they drive filtering, searching and board lists. Artifacts, permissions and release deadlines are handled by other features, so those options do not describe labels.