GitLab Certifications

Like GitHub, GitLab runs its own certification program rather than routing through a neutral body like the CNCF or the Linux Foundation — a family of Associate-level exams delivered through GitLab's own learning platform, each one checking product-specific fluency in one slice of GitLab rather than a discipline in the abstract. Of that family, the one that matters most to this course is the GitLab Certified CI/CD Associate — the direct counterpart to the GitLab CI/CD tool page and the CI/CD pipelines lesson it sits under. This page profiles that exam, names the rest of the family for completeness, and spends real time on the question the content brief for this page actually asks: how much of what this credential tests is CI/CD knowledge in general, versus GitLab's product specifically. The honest answer is not close, and knowing why matters more than any single logistics fact below.

What GitLab Certifications are, and who runs them

☺ Like you're 10: Multiple-choice, online, and — unlike almost everything else on this course's certification shelf — historically free to sit.

GitLab has run its own certification program since 2021, delivered through what the company has variously branded GitLab University and GitLab Learn — its own e-learning platform, not a third-party testing vendor like Pearson VUE or PSI. Every exam in the family is knowledge-based: multiple-choice questions checked online, with no hands-on lab component and no live pipeline graded on its end state. That puts it in the same format family as the Terraform Associate and the GitHub Actions cert, and firmly on the opposite side of the format line from the CKA, which is 100% performance-based against real clusters.

The genuinely unusual detail, and the one worth leading with: GitLab's certification exams have historically been offered free of charge, positioned by the company as an extension of the same open, low-friction ethos behind its open-source roots — a real point of difference from every other credential profiled on this course's shelf, all of which charge somewhere between roughly $99 and $445. Delivery has also historically leaned lighter-touch than a proctored professional exam: reports from candidates describe an unproctored, largely honor-system format rather than a webcam-and-ID-check session. Treat both of those as facts to verify, not facts to plan a study schedule around blindly — see the warning box further down for exactly why.

↗ GitLab official certifications page

The Associate family — and why the CI/CD one is the one to know

☺ Like you're 10: There's more than one badge, each one aimed at a different job — this page goes deep on exactly one of them.

GitLab's Associate-level exams are organized by role rather than stacked as one long ladder — you pick the one that matches what you actually do with the platform, not a mandatory first step. As generally named across GitLab's own program materials:

• GitLab Certified Associate — the platform-wide baseline: Git fundamentals, the GitLab flow branching model, issues and merge requests, and basic navigation of the product as a whole. The closest thing this family has to an entry point, though it is not a hard prerequisite for the others.
• GitLab Certified CI/CD Associate — pipelines specifically: .gitlab-ci.yml, GitLab Runner, variables and environments, and the built-in security scanning templates. Profiled in full below, and the one this page and the CI/CD pipelines / GitLab CI/CD lessons exist to prepare you for.
• GitLab Certified Security Associate — vulnerability management, the built-in scanners, and compliance features, aimed closer at a security- or DevSecOps-leaning role than a delivery-focused one. Named here for completeness, not covered in depth.
• GitLab Certified Project Management Associate — issues, boards, milestones, and epics as a planning tool rather than a delivery pipeline. Also named for completeness only.

Above the Associate tier, GitLab has also offered higher-level Professional and implementation-partner credentials aimed at consultants and trainers rather than individual practitioners — out of scope for a working DevOps engineer and not covered here.

The CI/CD Associate exam, in full

☺ Like you're 10: This is the one that actually tests pipeline skills — not "have you used GitLab," but "do you know exactly how its pipelines work."

Reconstructed from GitLab's own published exam scope and the product surface it necessarily draws from — treat the grouping as directional and re-check the current exam guide before you sit it, the same caveat that applies to every knowledge-based vendor exam on this shelf:

• Pipeline configuration fundamentals — .gitlab-ci.yml anatomy: stages, per-job stage:, the modern rules keyword versus the older only/except it replaced, and needs as the mechanism that turns a strict waterfall into a DAG. Full syntax depth lives on the GitLab CI/CD page.
• GitLab Runner and execution — what a runner is versus what GitLab itself does, runner scope (shared, group, project), tags: matching as the reason a job sits at "pending" forever, and the three executors — shell, docker, kubernetes — and when each is the right call.
• Variables, secrets, and environments — CI/CD variables, what "masked" and "protected" actually guarantee (and don't), and environment: as the object deployment tracking and approvals attach to.
• Merge request pipelines and merge trains — the difference between a branch pipeline and an MR pipeline that runs against the merge result, the classic duplicate-pipeline trap a missing workflow: rules block causes, and merge trains as GitLab's answer to queuing several approved changes safely.
• Built-in security scanning — recognizing the six scanning categories (SAST, DAST, dependency, container, secret, and IaC scanning) and that they're added via include: - template:, not installed as separate third-party tools the way they would be on Jenkins.
• Auto DevOps — GitLab's zero-configuration pipeline template, which detects a project's language via buildpacks and automatically builds, tests, scans, and deploys it without a hand-written .gitlab-ci.yml at all. It has no equivalent taught elsewhere on this course's certification shelf, because it has no equivalent outside GitLab specifically — which is exactly the kind of fact this page exists to flag.

# exam-relevant vocabulary in eleven lines — every keyword here is GitLab's own name for a generic idea
workflow:
  rules:
    - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'   # avoids the classic duplicate-pipeline trap
    - if: '$CI_COMMIT_BRANCH == "main"'

deploy-prod:
  stage: deploy
  needs: ["test-job"]              # DAG edge — GitLab's name for "start as soon as the thing I need finishes"
  environment: { name: production }  # approvals and deployment history attach HERE, not inline in the job
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'
      when: manual                 # the human gate, GitLab's way

Generic CI/CD skill versus GitLab-product-specific knowledge

☺ Like you're 10: Passing this exam proves you know GitLab's own screens and keywords cold — it does not, by itself, prove you understand CI/CD as an idea. Those are two different things, and this exam is almost entirely the first one.

This is the question the content brief for this page asks directly, and it's worth being blunt about: a candidate can pass the CI/CD Associate exam by memorizing GitLab's specific keywords and screens without ever having internalized why staged pipelines, artifact promotion, and deployment gating exist as ideas — and, in the other direction, a candidate who deeply understands CI/CD as a discipline from years on Jenkins or CircleCI can still fail this exam cold if they've never actually opened GitLab, because none of that portable knowledge tells you that rules replaced only/except, or that approvals live on the environment: object instead of inline in the job. The exam is testing the right half of the diagram below, not the left.

The table below makes the split concrete, row by row, using facts already established on CI/CD pipelines and the GitLab CI/CD page — not new claims invented for this comparison.

How this maps onto the course

☺ Like you're 10: One tool page does most of the heavy lifting here; a couple of deep-dive pages round out the security-flavored corners.

Exam logistics — verify these yourself before you register

☺ Like you're 10: More than most certs on this site, this one changes its own name and shape from time to time — read the current page, not this one, before you commit.

Where it sits, and who should take it

☺ Like you're 10: Free and fast if your team already runs on GitLab. Not a substitute for a hands-on or vendor-neutral credential if that's the gap you're actually trying to close.

Set against the rest of this course's certification shelf, the CI/CD Associate is the cheapest and lowest-friction credential covered anywhere here — genuinely free, historically unproctored, and narrowly scoped to one product. That makes it closer in spirit to the GitHub Actions certification than to the CKA or the AWS DevOps Engineer – Professional, both of which cost real money and assume real production hours behind you.

Take it if: your team runs delivery on GitLab specifically, you want a fast, no-cost credential formalizing product knowledge you already use daily, or you're the person other engineers already ask "why is this pipeline stuck at pending" and want that informally recognized skill externally checked. Take the platform-wide GitLab Certified Associate first if: you're newer to GitLab as a whole and want the broader baseline before narrowing into CI/CD specifically — though it isn't a hard prerequisite. Look elsewhere if: your actual gap is CI/CD or delivery thinking in general rather than one vendor's screens — the CI/CD pipelines lesson and the Terraform Associate or CKA transfer to more employers than any single-vendor badge will; or if your team doesn't run GitLab at all, in which case this credential has close to zero signal value regardless of how well you'd score on it.