A comprehensive study repository for the GH-100: GitHub Administration certification exam. This repository provides structured study notes, hands-on labs, practice questions, mock exams, cheatsheets, and quick-reference materials aligned to the official six-domain exam blueprint.
Last Updated: March 2026 Exam Version Covered: GH-100 (as of Q1 2026 — official objectives) If you notice outdated content, please open an issue or submit a PR. Blueprint source of truth used in this repo: the Microsoft Learn GH-100 certification page, verified on March 18, 2026.
| Field | Details |
|---|---|
| Exam Code | GH-100 |
| Full Name | GitHub Administration |
| Delivery | Online proctored (Pearson VUE) |
| Question Format | Multiple choice, multiple select |
| Duration | 120 minutes |
| Passing Score | 750 / 1000 |
| Language | English |
| Prerequisite Knowledge | GitHub fundamentals, basic Linux/CLI, networking concepts |
| Content Version | Q1 2026 |
The GH-100 exam is designed for:
- GitHub Enterprise administrators managing GHEC or GHES deployments
- DevOps/Platform engineers responsible for GitHub infrastructure
- Security engineers implementing GitHub Advanced Security
- IT administrators migrating organizations to GitHub Enterprise
- Team leads managing organization-wide GitHub policies
Recommended experience: 6-12 months hands-on experience administering GitHub at the organization or enterprise level.
Before studying for GH-100, you should be comfortable with:
- Creating and managing GitHub repositories, branches, and pull requests
- Basic Git commands (clone, push, pull, merge, rebase)
- GitHub organization concepts (teams, members, repositories)
- Basic Linux command line and shell scripting
- Fundamental networking (DNS, HTTP/HTTPS, firewalls)
- Authentication concepts (SSO, SAML, OAuth, tokens)
GH_100_Cert_Prep/
├── README.md # This file
├── QUICK-REFERENCE.md # Printable cheat sheet for all domains
├── CONTRIBUTING.md # How to contribute to this repo
├── LICENSE # MIT License
├── .gitignore
├── .editorconfig
│
├── exam-metadata/
│ ├── gh-100-exam-objectives.md # Complete domain/objective breakdown
│ ├── domain-weights.md # Visual weight distribution + study time
│ └── key-terms-glossary.md # 50+ GitHub Administration definitions
│
├── docs/
│ ├── domain-1-enterprise-support.md
│ ├── domain-2-identity-authentication.md
│ ├── domain-3-deployment-licensing.md
│ ├── domain-4-access-permissions.md
│ ├── domain-5-security-compliance.md # HEAVIEST (36%) — most comprehensive
│ └── domain-6-github-actions.md
│
├── demos/
│ ├── 01-enterprise-setup/README.md
│ ├── 02-identity-sso-setup/README.md
│ ├── 03-deployment-options/README.md
│ ├── 04-access-permissions/README.md
│ ├── 05-security-compliance/README.md
│ └── 06-github-actions/README.md
│
├── labs/
│ ├── 01-enterprise-support.md
│ ├── 02-identity-authentication.md
│ ├── 03-deployment-licensing.md
│ ├── 04-access-permissions.md
│ ├── 05-security-compliance.md
│ ├── 06-github-actions.md
│ └── README.md
│
├── cheatsheets/
│ ├── domain-1-enterprise-support.md
│ ├── domain-2-identity-authentication.md
│ ├── domain-3-deployment-licensing.md
│ ├── domain-4-access-permissions.md
│ ├── domain-5-security-compliance.md
│ └── domain-6-github-actions.md
│
├── practice-questions/
│ ├── domain-1-enterprise-support.md
│ ├── domain-2-identity-authentication.md
│ ├── domain-3-deployment-licensing.md
│ ├── domain-4-access-permissions.md
│ ├── domain-5-security-compliance.md
│ ├── domain-6-github-actions.md
│ └── README.md
│
├── mocks/
│ ├── full-mock-exam-01.md
│ └── answer-keys/
│ └── mock-exam-01-answers.md
│
├── .github/
│ ├── SECURITY.md
│ ├── dependabot.yml
│ ├── pull_request_template.md
│ ├── ISSUE_TEMPLATE/
│ └── workflows/
│ ├── link-check.yml
│ └── lab-verification.yml
│
├── LAB-VERIFICATION.md # Fork-only lab workflow guide
├── lab-submissions/ # Evidence files for forked lab PRs
│ └── TEMPLATE.md
│
└── scripts/
├── README.md
└── lab/
└── verify-pr.sh
| Domain | Title | Weight | Priority |
|---|---|---|---|
| Domain 1 | Support GitHub Enterprise for users and key stakeholders | 9% | Medium |
| Domain 2 | Manage user identities and GitHub authentication | 11% | Medium-High |
| Domain 3 | Describe how GitHub is deployed, distributed, and licensed | 9% | Medium |
| Domain 4 | Manage access and permissions based on membership | 18% | High |
| Domain 5 | Enable secure software development and ensure compliance | 36% | Critical |
| Domain 6 | Manage GitHub Actions | 16% | High |
Domain 5 is worth more than a third of the exam. Prioritize your study time accordingly.
- Read
exam-metadata/gh-100-exam-objectives.mdto understand scope - Review
exam-metadata/key-terms-glossary.mdto build vocabulary - Complete Domain 3 study notes (deployment/licensing — good foundation)
- Complete Domain 1 study notes (enterprise support)
- Complete Domain 2 study notes (identity and authentication)
- Complete Domain 4 study notes (access and permissions)
- Run Demo Lab 02 (SSO/SAML setup) and Demo Lab 04 (permissions)
- Complete Domain 5 study notes — read twice
- Run Demo Lab 05 (security policies)
- Focus on: Dependabot, secret scanning, code scanning, branch protections, rulesets, GHAS
- Complete Domain 6 study notes (GitHub Actions)
- Run Demo Lab 06 (Actions management)
- Take practice questions for all domains
- Review
QUICK-REFERENCE.mddaily
- Start with exam metadata — understand what the exam tests before diving into content
- Read domain docs in weight order — Domain 5, then 4, then 6, then 2, then 1 and 3
- Do the labs — use
labs/plus the linkeddemos/assets for hands-on practice - Use the cheatsheets — review one cheatsheet after each domain study session
- Answer practice questions — use the dedicated
practice-questions/directory by domain - Take a mock exam — use
mocks/full-mock-exam-01.mdfor timed review - Use the quick reference — print or bookmark
QUICK-REFERENCE.mdfor last-minute review
The Actions-based lab verification flow is designed to work only in a fork of this repository.
- The upstream repo is the shared study source.
- Lab verification is for your own sandbox, training cohort fork, or internal classroom copy.
- The verification workflow checks whether the repository itself is a fork and exits early in the upstream repo.
- Fork this repository to your own GitHub account or training organization.
- Enable Actions in the fork if GitHub prompts you to do so.
- Open a lab issue in the fork using the
GH-100 Lab Exerciseissue form. - Create a branch for your lab work and complete the exercise in the fork.
- Add a submission file under
lab-submissions/<lab-id>/usinglab-submissions/TEMPLATE.md. - Open a pull request in the fork using the built-in PR template.
- Fill in the PR metadata:
Lab-ID: <official-lab-id>Issue: #<number>Validation-Evidence: <value>
- Wait for the
GH-100 Lab Verificationworkflow to validate the PR structure and evidence.
domain-1-enterprise-supportdomain-2-identity-authenticationdomain-3-deployment-licensingdomain-4-access-permissionsdomain-5-security-compliancedomain-6-github-actions
- the repo is a fork
- the PR body includes the required
Lab-ID,Issue, andValidation-Evidencefields - a markdown evidence file was added or changed under the correct
lab-submissions/<lab-id>/folder - the submission file includes the required sections:
## Summary## Commands## Screenshots or Artifacts## Outcome
- the submission includes domain-appropriate evidence keywords or changed files
- live enterprise or organization settings outside the repo
- SAML, SCIM, EMU, or GHES administration performed in external systems
- audit log streaming delivery to third-party services
- UI-only changes without screenshots or exported evidence
For those steps, include screenshots, command output, JSON exports, or reviewer notes in the submission file and PR.
This repo is aligned to the 6 official GH-100 domains shown on the Microsoft Learn certification page:
- Domain 1: Support GitHub Enterprise for users and key stakeholders — 9%
- Domain 2: Manage user identities and GitHub authentication — 11%
- Domain 3: Describe how GitHub is deployed, distributed, and licensed — 9%
- Domain 4: Manage access and permissions based on membership — 18%
- Domain 5: Enable secure software development and ensure compliance — 36%
- Domain 6: Manage GitHub Actions — 16%
Coverage matrix:
exam-metadata/official-domain-coverage-matrix.md
Fork-only lab verification framework:
LAB-VERIFICATION.md
- GitHub's UI changes frequently. Always cross-reference with the official GitHub Docs. If something in this repo conflicts with current docs, docs win.
- Terminology matters. The exam uses GitHub's exact terms. Know the difference between "organization" and "enterprise," between "repository ruleset" and "branch protection rule."
- GHEC vs GHES distinctions are heavily tested. Many features are only available on one platform. Make a comparison table for yourself.
- EMU (Enterprise Managed Users) is a major topic in Domain 2 and Domain 4. Understand what it restricts and enables.
- Domain 5 has scenario-based questions. You will be given a security requirement and asked which GitHub feature satisfies it. Learn the use case for every security feature.
- For Actions (Domain 6), focus on the administrative controls — policies, runner groups, required workflows — not workflow authoring syntax.
- GitHub Docs
- GitHub Enterprise Cloud Documentation
- GitHub Enterprise Server Documentation
- GitHub Advanced Security
- GitHub Certifications
- Microsoft Learn GH-100 Certification Page
- GitHub Skills
- GitHub Blog
See CONTRIBUTING.md for guidelines on submitting corrections, new practice questions, or lab improvements.
This repository is licensed under the MIT License. Study materials are community-contributed and not affiliated with or endorsed by GitHub, Inc.
Note: GitHub and GitHub Enterprise are trademarks of GitHub, Inc. This repository is an independent study resource.