SaveMyCert
Log in
5 of 5 free questions left today·for 30 a day
GH-200 mock exams

Free GH-200 mock exams

Full-length GitHub Actions rehearsals: 60 questions in 100 minutes, drawn to the official domain weights and scored on the same scale as the real exam. Pass mark 700 / 1000.

Questions
60
~1.7 min each
Time limit
100 min
server-timed
Pass mark
700
on a 100–1000 scale
Papers
3
retake any of them
Create an account, then unlock Pro to sit a mock exam
Attempts are timed, saved and scored — you need somewhere to keep them.
GH-200 Mock Exam 1
60 questions · 100 min
New
Not attempted yet
GH-200 Mock Exam 2
60 questions · 100 min
New
Not attempted yet
GH-200 Mock Exam 3
60 questions · 100 min
New
Not attempted yet

What's in a GH-200 mock paper

Each paper draws its questions per domain in the same proportions GitHub publishes for the real GH-200 — so a mock that goes badly in one domain is telling you something a randomly-drawn quiz couldn't.

Questions drawn per exam domain in a GH-200 mock paper
DomainOfficial weightQuestions drawnShare of paper
Author and manage workflows24%1423%
Consume and troubleshoot workflows19%1220%
Author and maintain actions18%1118%
Manage GitHub Actions for the enterprise24%1423%
Secure and optimize automation15%915%
Total100%60100%

What a GH-200 paper is shaped like

Which way this particular paper applies pressure.

The clock

At roughly 1.7 minutes a question, the pacing is comfortable but not generous. You can afford to think on a hard question, and you cannot afford to do it twice. Most candidates finish with time for a second pass if they keep the first pass moving.

The weighting

Author and manage workflows is the largest domain at 24%, but with 5 domains in play no single one decides the result. A mock score here is usually a fair reflection of overall coverage rather than a verdict on one topic.

The standard

The pass mark is 700 on the 100–1000 scale. Because scaling adjusts for the difficulty of the particular set you were served, there is no fixed number of questions that guarantees it — which is exactly why a single mock result means less than a consistent one.

Pacing a GH-200 paper

Where you need to be on the clock, quarter by quarter.

Checkpoints for a full-length GH-200 paper
CheckpointElapsedBe at questionQuestions left
First quarter25 min1545
Halfway50 min3030
Three quarters75 min4515
Time called100 min600

What trips people up on a GH-200 mock

GH-200 is a syntax exam as much as a concepts exam. Many questions show a short workflow or action file and ask what it does, why it fails or which line fixes it. Candidates who have only read about Actions recognise every keyword and still miss these, because the trap is in the detail: an expression evaluated at the wrong time, an output written to the wrong file, a job that silently skips because of how needs and if combine. Practise reading YAML slowly and predicting the run before you look at the options.

The wrong options are real Actions features in the wrong place. GITHUB_ENV or GITHUB_OUTPUT, an artifact or a cache, env or vars or secrets, a reusable workflow or a composite action or a starter workflow — each one is the right answer to a different question. When you review a miss, name what the option you chose is actually for; that habit closes most of the gap.

Enterprise management and workflow authoring carry the most weight between them, and the enterprise side is where hands-on experience runs out for many people: runner groups, self-hosted runner networking, organization policies for which actions may run, and secrets scoped to organizations, repositories and environments. If you have only used Actions in a personal repository, give this domain deliberate time.

Security questions reward precise permission thinking. Know what GITHUB_TOKEN can and cannot do and how to narrow it, when OIDC replaces stored cloud credentials, why pinning third-party actions to a full commit SHA matters, and how script injection gets into a run step. These are rules you can learn exactly, which makes them some of the most dependable marks on the paper.

Several objectives follow recent platform changes — runner images, immutable actions, artifact attestations. Revise them from the current documentation; an answer that was right two years ago is a common reason for a confident miss.

Before you sit a GH-200 mock

How to sit a mock examThe method that applies to any full-length paper: one sitting, flag and move, and how to read the result afterwards.Should you book yet?Check your mock scores, coverage and consistency against the signals that actually predict a pass before you pay the exam fee.GH-200 practice questionsNot ready for the clock yet? Drill 379 questions by domain, with every option explained.GH-200 revision notes9 lessons across every domain — where a failed mock sends you back to.GH-200 cheat sheetEvery key fact on one page, for the last few days before the exam.GH-200 flashcardsThe same facts one at a time with the answer hidden — for the recall gaps a mock exposes.GitHub Actions (GH-200) exam overviewExam facts, who it is for, cost and how it fits alongside the other certifications.

GH-200 mock exams: your questions

60 questions in 100 minutes. Every mock exam here matches that format exactly, and is weighted across the domains the same way the real GH-200 is.

Source

Exam structure, domain weights and scoring on this page come from the official GH-200 exam guide.