
Exam GH-100: GitHub Administration is the GitHub certification for people who run GitHub Enterprise for a company: identity and access with SAML SSO, SCIM and Enterprise Managed Users, policies and rulesets, GitHub Advanced Security, Actions runners and secrets, the audit log, licensing and cost. The skills measured were significantly rewritten in July 2026, with new and reworded objectives, so check that your study material is current.
This guide follows the official Microsoft Learn study guide: five domains with weights and every objective, the deployment options to tell apart, a 5-week plan and 15 original scenario questions.
Quick facts (Microsoft Learn, November 2026)
| Item | Detail |
|---|---|
| Exam | GH-100: GitHub Administration (intermediate) |
| Skills measured | As of July 2026 (significant change) |
| Duration | 100 minutes, proctored through Pearson VUE |
| Passing score | 700 |
| Language | English |
| Validity | GitHub certifications are valid for 2 years; GitHub is moving to Microsoft's renewal process |
| Price | Based on the country where you take the exam |
Read the official GitHub Administration certification page and the GH-100 study guide. New to GitHub? Start with GH-900 GitHub Foundations.
Domains and weights
| Domain | Weight |
|---|---|
| Implement secure software development and compliance | 25–30% |
| Manage GitHub Actions | 20–25% |
| Manage GitHub identities and access | 15–20% |
| Administer GitHub Enterprise environment | 10–15% |
| Monitor and optimize GitHub usage | 10–15% |
1. Identities and access (15–20%)
- Managed users vs personal accounts; enforcing SAML SSO and 2FA; SCIM vs team synchronisation; choosing an identity provider; GitHub's authentication and authorisation model.
- Organisation and repository roles; enterprise teams; auditing access; settings, policies, rulesets and custom roles.
2. Enterprise environment (10–15%)
- What admins can fix vs what needs GitHub Support; support bundles and diagnostics; standards for workflows, branching, reviews and releases.
- Deployment options and licensing:
| Option | When it fits |
|---|---|
| GHEC with Enterprise Managed Users (EMU) | The company's identity provider owns every account; users can't act outside the enterprise |
| GHEC with data residency + EMU | Code and data must stay in a specific region, with managed identities |
| GHEC with personal accounts | Developers use their own GitHub accounts, linked through SAML SSO |
| GitHub Enterprise Server (GHES) | Self-hosted in your own data centre or cloud account |
3. Secure development and compliance (25–30%)
- Organisation and enterprise policies; security posture and data protection; audit logging and reporting.
- Vulnerability alerts, secret scanning and CodeQL code scanning; Dependabot and security advisories; a security response plan. See our GH-500 Advanced Security guide for depth.
- Personal access tokens (fine-grained vs classic); rate limits for PATs and GitHub Apps; GitHub Apps vs OAuth Apps; approving or denying apps by policy.
4. GitHub Actions (20–25%)
- Sharing actions and reusable workflows across the enterprise; organisation policies for which actions may run.
- Runner groups; GitHub-hosted vs self-hosted runners; IP allow lists and networking, including Azure private networking; runner performance troubleshooting.
- Secret scope and access; organisation and repository secrets; third-party vault integration. See the GH-200 Actions guide.
# Org-level policy pattern: reusable workflow called from any repo
# .github/workflows/ci.yml in an application repository
jobs:
build:
uses: my-org/platform-workflows/.github/workflows/node-ci.yml@v3
secrets: inherit
with:
node-version: "22"
5. Monitor and optimise (10–15%)
- Analysing the audit log and API usage; spotting adoption patterns and unused features.
- Usage reports for metered products (Actions minutes, storage, Copilot, Advanced Security); license and resource optimisation.
5-week study plan
| Week | Focus | Lab |
|---|---|---|
| 1 | Deployment options, licensing, enterprise vs org vs repo settings, support boundaries | Create an organisation; map every setting level |
| 2 | SAML SSO, SCIM, EMU, 2FA, roles, enterprise teams, rulesets | Protect main with a ruleset requiring reviews and status checks |
| 3 | Secret scanning, CodeQL, Dependabot, advisories, PATs, GitHub Apps vs OAuth Apps | Turn on code scanning and fix one Dependabot alert |
| 4 | Actions policies, reusable workflows, runner groups, self-hosted runners, secrets | Register a self-hosted runner in a runner group |
| 5 | Audit log, usage reports, cost optimisation; practice assessment | Query the audit log for permission changes; book the exam |
15 scenario questions with answers
These are original scenarios written for this guide, not exam questions.
1. A bank wants the identity provider to create, own and remove every GitHub account, with no personal accounts. Which option?
GitHub Enterprise Cloud with Enterprise Managed Users.
2. Source code must be stored in the EU. Which option?
GHEC with data residency (with EMU).
3. Leavers must lose GitHub access automatically when HR disables them. What do you configure?
SCIM provisioning from the identity provider.
4. Every repo in the org needs reviews and passing checks before merging to main. What scales best?
An organisation-level ruleset targeting the default branch.
5. A developer pushed a cloud access key. What should have blocked it?
Secret scanning with push protection.
6. You need to find SQL injection patterns in code on every pull request. What do you enable?
CodeQL code scanning.
7. A dependency has a known CVE. Which feature raises the alert and opens a fix PR?
Dependabot alerts and security updates.
8. An integration needs fine-grained, short-lived permissions on selected repos and acts as itself, not a user. GitHub App or OAuth App?
A GitHub App.
9. Only actions from GitHub and verified creators may run in the enterprise. Where do you set this?
The enterprise or organisation Actions policies (allowed actions).
10. Jobs must reach private resources in an Azure VNet without public endpoints. What do you use?
Azure private networking for GitHub-hosted runners (or self-hosted runners inside the VNet).
11. Only the payments team's repos may use the GPU self-hosted runners. What do you configure?
A runner group restricted to those repositories.
12. A secret should be shared by 20 repos but not the whole org. What do you do?
Create an organisation secret with access limited to the selected repositories.
13. Who changed a repository's visibility to public last week?
Search the audit log.
14. Actions minutes spending doubled this month. Where do you start?
The usage report for metered products, to find which repos and workflows drive it.
15. A GHES instance is failing and the admin can't fix it. What does GitHub Support need?
A support bundle (diagnostics) from the instance.
After GH-100
- Complete the GitHub track with GH-200, GH-300 and GH-500.
- Pair it with AZ-400 Azure DevOps Engineer.
- See live DevOps and platform jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches GitHub, CI/CD, DevSecOps and multi-cloud DevOps with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is exam GH-100?
GH-100: GitHub Administration, an intermediate exam for administrators of GitHub Enterprise Cloud and Server.
When did the GH-100 skills change?
The skills measured were significantly updated in July 2026, with new, removed and reworded objectives.
How long is GH-100 and what is the passing score?
100 minutes; a score of 700 or more is required to pass.
Which GH-100 domain has the most weight?
Implement secure software development and compliance, at 25–30%.
How long are GitHub certifications valid?
2 years. GitHub is moving to Microsoft's recertification process for renewals.
What is Enterprise Managed Users?
A GitHub Enterprise Cloud option where the company's identity provider creates, owns and removes every user account.



