GitLab CI/CD Specialist
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
The GitLab CI/CD Specialist credential is aimed at engineers who build, operate, and troubleshoot delivery pipelines on GitLab rather than at general GitLab users. It targets DevOps engineers, platform and SRE staff, release engineers, and developers who own a project's .gitlab-ci.yml end to end - people expected to design pipeline structure, choose runners and executors, manage variables and secrets, and diagnose failures under time pressure. This independent study page organises preparation around six areas: pipeline configuration and authoring; runners, executors, and the job execution environment; variables, secrets, and protected configuration; pipeline efficiency through caching, artifacts, and parallelism; job orchestration with rules, needs, stages, and triggers; and security, compliance, and troubleshooting. Preparation should be hands-on. Stand up a project, write pipelines with multiple stages and needs-based DAGs, register and tag your own runner, move secrets into masked and protected variables, and deliberately break things - expired artifacts, failing cache keys, rules that silently skip jobs - then read the job logs until the cause is obvious. Pair that practice with the official GitLab CI/CD documentation and the .gitlab-ci.yml reference, and rehearse reading pipeline graphs and job traces quickly. Important caveat: the official certification page returned a 404 when this page was compiled, so exam format, length, passing score, fee, retake policy, and validity are not published here. Treat the domain list as provisional and confirm current details with GitLab before booking.
What you'll study
About GitLab CI/CD Specialist preparation
What is the exam format?
Not confirmed. The official GitLab CI/CD Specialist certification page returned a 404 when this page was last compiled, so question count, question types, duration, and delivery method are unknown and deliberately left blank here. Check GitLab's certification pages directly for the current format before you schedule anything.
How much does it cost, and how long is the certification valid?
Unknown from available sources. Fee, validity period, and any recertification requirement could not be verified because the certification page was unavailable. Do not budget or plan around figures from older blog posts or third-party training sites, which may describe a previous version of the programme.
How hard is it, and how long should I study?
No published difficulty data exists. Realistically, candidates who already maintain production GitLab pipelines need less time than those who only run pre-built templates. Focus study on the areas where you have the least hands-on exposure - usually runner configuration, caching behaviour, and rules versus only/except semantics - rather than rereading basics you already use daily.
Can I retake it if I fail?
The retake policy could not be confirmed because the official certification page was unavailable at retrieval. GitLab's certification terms govern waiting periods and any retake fees. Verify with GitLab before assuming a free or immediate second attempt.
In what order should I study the six domains?
Start with pipeline configuration and authoring, since every other domain assumes you can read a .gitlab-ci.yml fluently. Then take runners and the execution environment, followed by variables and secrets. Efficiency topics - caching, artifacts, parallelism - make most sense after that. Finish with orchestration (rules, needs, triggers) and troubleshooting, which draw on everything before them.
What do candidates most often get wrong?
Common trouble spots: assuming cache is guaranteed to restore, confusing artifacts with cache, misjudging how rules interacts with pipeline types, forgetting that protected variables are unavailable on unprotected branches, and not understanding how runner tags and tags: matching affect scheduling. Practise reproducing each of these failures so you can recognise the symptom in job logs.
Do I need to know GitLab administration, not just CI/CD?
The provisional domains centre on pipeline behaviour: authoring, runners and executors, variables and secrets, efficiency, orchestration, and security plus troubleshooting. Broad instance administration is not the focus, but runner registration, executor choice, and protected configuration touch administrative territory, so some familiarity with project and group settings helps.
Is this page affiliated with GitLab?
No. This is independent study material and makes no claim of official affiliation, endorsement, or partnership with GitLab. It is written from general practice and the public documentation, not from any official exam blueprint. Always treat GitLab's own documentation and certification pages as the authoritative source for exam facts.
How should I prepare practically?
Build a real project pipeline: multiple stages, a needs-based DAG, a registered runner with tags, masked and protected variables, and artifacts passed between jobs. Then break it deliberately - expire artifacts early, change cache keys, add a rule that skips a job - and diagnose each failure from the logs. Reading job traces quickly is the single most transferable skill.