GitLab PM Associate study guide
GitLab PM Associate · Work through your exam, one topic at a time.
The GitLab PM Associate credential is presented here as a study target for people who plan, track, and report on work inside GitLab. This page is an independent preparation resource. It is not affiliated with, endorsed by, or operated by GitLab, and it does not reproduce any official exam content. The material is organized around four domains of equal weight: GitLab platform fundamentals, planning and project management, source code and collaboration workflows, and CI/CD and delivery visibility. Topics on this exam: GitLab platform fundamentals, Planning and project management, Source code and collaboration workflows, and CI/CD and delivery visibility. The GitLab PM Associate study guide has 4 sections and about 1,716 words.
01GitLab Platform Fundamentals
This domain tests how you navigate GitLab as a DevSecOps platform: how projects sit inside namespaces, how visibility changes who can see them, and how role-based permissions control actions. The exam expects you to choose the least-privileged role that still lets a person do the job. A project path is namespace/project ; a group can contain subgroups, and a project inherits membership from its parent group. Visibility is Private (members only), Internal (any signed-in user), or Public (anyone).
419 words, about 2 min02Planning and Project Management
This domain tests how GitLab turns work into trackable items: issues, labels, milestones, boards, epics, and iterations. The exam focuses on choosing the right planning object and configuring it so status rolls up correctly. An issue is the unit of work. It carries a title, description, assignee(s), labels, milestone, due date, weight, and comments.
419 words, about 2 min03Source Code and Collaboration Workflows
This domain tests the everyday Git and GitLab flow: branching, commits, merge requests, review, approvals, and merging. The exam expects you to know which setting controls which behavior and how a change moves from a branch to the default branch. A branch is a movable pointer to commits. A feature branch isolates work; the default branch (often main ) is the integration branch.
428 words, about 2 min04CI/CD and Delivery Visibility
This domain tests how GitLab runs pipelines and how teams see delivery performance. You need to read .gitlab-ci.yml , understand job ordering and rules, and interpret deployment and DORA-style metrics. A pipeline contains stages; jobs in the same stage run in parallel, and stages run sequentially by default. needs: creates a directed acyclic graph so a job can start before its stage completes.
450 words, about 2 min