Intermediate GitHub Actions experience
RecommendedHands-on experience creating workflows, automating tasks and managing CI/CD pipelines with GitHub Actions.

Validates knowledge of authoring and troubleshooting workflows, building custom actions, managing Actions across an enterprise and securing pipelines.
GH-200 tests practical knowledge of GitHub Actions: workflow syntax and triggers, debugging failed runs, writing your own actions, governing runners and secrets across an organization, and securing pipelines. Build real workflows as you study, read the Actions documentation alongside the official learning path, and use the free practice assessment to find gaps.
Example scenario: A test job should run on Linux, Windows and macOS with two Node versions each, but only on pull requests to main. How would you set up the trigger and the matrix?
Example scenario: A matrix build passes on Linux but fails on Windows at a shell step. What would you check in the logs, and how would you rerun only the failing job?
Example scenario: Only the payments team's repositories may deploy from a self-hosted runner inside the company network. How would you restrict that runner?
Example scenario: A deploy workflow stores a long-lived cloud access key as a repository secret. How would you replace it?
Official GH-200 study guide · Skills measured as of January 2026
Choose one answer, or select every correct option when the question says how many to pick.
A workflow should start only when a pull request targets the main branch. Which trigger does this?
B. The pull_request event with a branches filter runs only for pull requests into main. A push trigger ignores pull requests.
Move items into the right places on screen, such as matching terms to their meaning.
Match each workflow keyword to what it controls.
runs-on → the runner that executes the job; needs → which jobs must finish first; permissions → what the GITHUB_TOKEN may do; concurrency → how many runs in a group can happen at once.
Sign in to Microsoft Learn with a personal Microsoft account, then schedule through Pearson VUE. Exams booked with a work or school account are lost if you leave that organization.
Take the free practice assessment to see where you stand, then work through the domains while building workflows in your own repository.
Most candidates spend 20–40 hours. Plan for the low end if you already write Actions workflows; add time if you are new to Actions or have not worked with reusable workflows, custom actions or enterprise governance.
The official learning path covers every domain. Read the GitHub Actions documentation alongside it, because candidates say the docs fill gaps on syntax and Docker actions.
Practise at organization level A free GitHub organization lets you try runner groups, organization secrets and Actions policies, which make up a large share of the exam.
Take the free official assessment first and last. Add a paid set if you want full-length timed exams with explanations.
Use the checklist for your delivery route.
A candidate who scored 904 found the workflow questions easy but struggled with GitHub Enterprise questions, having no enterprise experience. Practise organization and runner settings if your job does not cover them.
Passers say the Microsoft Learn modules alone were not enough and recommend reading the GitHub Actions docs section by section, especially Docker actions and workflow syntax details.
Wrong answers are not penalized, so answer every question and flag uncertain ones for review. Candidates found multi-select questions, where every correct option is needed, the hardest to be sure of.