GH-200 study plan

Your step-by-step plan

1. Map the reweighted blueprint and book a date

   Day 1

   Read the current GH-200 objectives, noting the January 2026 reweighting so older notes do not mislead you. Author and manage workflows and Manage GitHub Actions for the enterprise are the two heaviest domains and account for roughly half the marks between them, so plan the deepest study there. Book a provisional date now: a fixed date turns open-ended study into a plan and is the strongest predictor of actually sitting.

2. Build the core decision trees

   Week 1

   Before drilling any domain, build the splits the whole exam rests on: the trigger tree (schedule, workflow_dispatch, repository_dispatch, push, pull_request), the data-passing split (GITHUB_ENV, GITHUB_OUTPUT, artifacts, on.workflow_call.outputs), the reuse split (reusable workflow, composite action, starter workflow), and the action-type tree (composite, JavaScript, Docker). Use the recall prompts in this guide: cover the answer, choose the mechanism from the constraint, then reveal. If you cannot pick from the requirement alone, you do not own it yet.

3. Go deep on authoring and enterprise management (Domains 1 and 4)

   Weeks 1 to 3

   These two carry the most marks, so they get the most time. Drill workflow structure with needs and if, matrix expansion with include and exclude and fail-fast, and the workflow_call contract for inputs, secrets and outputs. For enterprise, fix the runner targeting array rule, the secret-scoping ladder, runner groups, and limits such as the four-level reusable workflow nesting depth. Practise on scenario questions and read the worked explanation on every one, including the ones you got right, watching for the named constraint that picks the answer.

4. Drill consuming, troubleshooting and action authoring (Domains 2 and 3)

   Weeks 3 to 4

   Practise inferring a trigger from run-history evidence and reading a failed step's exit-code line to trace the real cause. Fix artifact retention behaviour, the disable-versus-delete contrast, and matrix re-runs. For action authoring, lock the action-type decision tree, action.yml inputs, outputs and defaults, GITHUB_OUTPUT for step outputs, and tag-based versioning. Do the composite-versus-reusable-workflow and JavaScript-versus-Docker calls by hand until the constraint alone decides them.

5. Cover security and optimisation and its traps (Domain 5)

   Week 4

   This domain is smaller but its thread runs through every other domain. Drill the top-level permissions block and least-privilege GITHUB_TOKEN scoping, OpenID Connect federation to remove long-lived cloud secrets, pinning third-party actions to a full commit SHA, and environment protections including the wait timer and required reviewers. For cost, fix restore-keys cache warming, retention-days clamping, and concurrency. Practise rejecting the option that works but grants too much access.

6. Drill weak domains, then space the review

   Week 5

   Use your per-domain accuracy to attack the two domains dragging you down, not to re-read what you already know. Then space it: revisit each domain's recall prompts after a few days and again a week later. Spacing roughly doubles what sticks compared with cramming, and it is the cheapest gain available before the exam.

7. Sit a timed mock and calibrate

   Weeks 5 to 6

   Take at least one full timed mock under exam conditions to rehearse pacing and the flag-and-return habit across the whole question set in the time allowed. Treat the score as a per-domain readiness signal, not a single number, and review every missed question, naming the constraint you misread and re-reading the relevant YAML key, before you book or sit.

Frequently asked questions

Keep studying GH-200

• GitHub Actions Certification (GH-200): What to Expecttopical
• How to pass GitHub Actions (GH-200): study guidefull study guide
• GH-200 cheat sheetone-page reference
• GH-200 practice questionsworked answers