GH-200 study guide: GitHub Actions exam domains, plan and common mistakes
Written and reviewed by the DevOpsCode Lab Team. Last updated 19 November 2026.
GH-200 is the GitHub Actions certification exam. It checks that you can write and debug workflows, build and publish your own actions, manage Actions across an organization or enterprise, and keep your automation secure and efficient.
What the exam tests
Many questions show a short piece of workflow YAML or describe a pipeline requirement and ask what it does, why it fails or which keyword fixes it. Others ask where to set a policy, how to share a runner with some repositories only, or how to reach a cloud without long-lived secrets. You need to read workflow syntax fluently and know where each setting lives at repository, organization and enterprise level.
Domains and how much each counts
| Domain | Weight | What to be able to do | Questions in our bank |
|---|---|---|---|
| Author and manage workflows | 24% | Triggers and event filters, jobs, steps and dependencies with needs, contexts and expressions, matrix strategies, environment variables, reusable workflows, concurrency | 69 |
| Consume and troubleshoot workflows | 19% | Read workflow logs, enable debug logging, re-run jobs, use artifacts and caches, find run results and status badges, diagnose failing triggers and conditions | 55 |
| Author and maintain actions | 19% | JavaScript, Docker container and composite actions; the action.yml metadata file with inputs, outputs and runs; versioning with tags and releases; publishing to GitHub Marketplace | 55 |
| Manage GitHub Actions for the enterprise | 24% | Organization and enterprise policies for allowed actions, GitHub-hosted versus self-hosted runners, runner groups and labels, sharing actions and workflows internally, usage and billing controls | 70 |
| Secure and optimize automation | 14% | Secrets at repository, environment and organization level, GITHUB_TOKEN permissions, OIDC to cloud providers, pinning actions to a commit SHA, environment protection rules, caching for speed | 41 |
Authoring workflows and enterprise management are the two largest domains. Developers often underestimate the enterprise domain.
Exam format
Our practice tests use 60 questions in 100 minutes with a 70% pass mark, so you get used to a full sitting at a realistic pace. The live exam is made up mainly of multiple-choice questions, some with more than one correct answer. Check the official GitHub certification page for the current format, price and objectives before you book.
Who should take it
- Developers who maintain CI workflows for their repositories.
- DevOps and platform engineers who run self-hosted runners or set Actions policy for an organization.
- Engineers moving to GitHub Actions from Jenkins, Azure Pipelines or GitLab CI.
If you have only edited existing workflows, plan time to write an action and configure an organization from scratch.
A 4-week study plan
| Week | Focus | Practice |
|---|---|---|
| 1 | Workflow authoring: on triggers and filters, jobs and needs, if conditions, contexts, expressions, matrix, reusable workflows, concurrency | Take the free questions, then one full test as a baseline; practice mode on authoring workflows |
| 2 | Troubleshooting and actions: debug logging, artifacts versus caches, action.yml, JavaScript, Docker and composite actions, versioning | Domain quizzes on both domains; build one composite action and one JavaScript action |
| 3 | Enterprise management: allowed actions policies, runner groups, self-hosted runner setup and labels, internal sharing, usage limits | Domain quiz on enterprise management; review every wrong answer with its explanation |
| 4 | Security and full exams: secrets scopes, GITHUB_TOKEN permissions, OIDC, SHA pinning, environments | Two full timed tests, then the mistakes quiz; book when you score 80%+ twice |
A free personal account and a test organization are enough for most labs. Register one self-hosted runner to see how labels and runner groups behave.
Topics people often get wrong
- Artifacts versus caches. Artifacts keep files produced by a run, such as build output or test reports, and share them between jobs. Caches store dependencies, keyed by a hash, to speed up later runs. A cache is not a reliable way to pass build output.
- Reusable workflows versus composite actions. A reusable workflow is called at the job level with uses under jobs and can contain several jobs. A composite action bundles steps and runs inside a single job.
- Events from GITHUB_TOKEN. Pushes or other events made with GITHUB_TOKEN do not start new workflow runs, apart from workflow_dispatch and repository_dispatch. Use a GitHub App token or a personal access token when a chained run is needed.
- Secret precedence. When a secret with the same name exists at several levels, the environment secret wins over the repository secret, which wins over the organization secret.
- pull_request versus pull_request_target. pull_request_target runs in the context of the base repository with access to secrets, so checking out and running code from a fork there is a security risk.
- Docker container actions. They run only on Linux runners. Use a JavaScript or composite action when the action must work on Windows and macOS runners too.
How to use the practice tests
Start with the free GH-200 questions to see the style. Then take one full timed test in exam mode for a baseline and look at the score by domain. Spend most of your time in the two weakest domains with domain quizzes, and finish with the mistakes quiz before each new full test. The readiness number tells you when your recent scores hold above the pass mark across all domains.
Frequently asked questions
How hard is GH-200? It is an intermediate exam. Engineers who write workflows every week often need three to four weeks of practice, mostly on enterprise settings and actions authoring.
Do I need GitHub Foundations first? No. There is no prerequisite, but Foundations covers the repository and organization basics that GH-200 assumes.
Are these the real exam questions? No. Every question is written by us for the published study guide. We never use leaked or recalled exam content.
DevOpsCode Lab is not affiliated with or endorsed by GitHub. Exam names are trademarks of their owners. Check the official GitHub exam page for the current price, format and objectives before you book.