Microsoft • GH-100
Certifies ability to optimize and manage a healthy GitHub environment, covering repository management, workflow optimization, and efficient collaboration.
Questions
447
Duration
100 minutes
Passing Score
700/1000
Difficulty
IntermediateLast Updated
Jan 2026
The GitHub Administration certification (GH-100) validates a candidate's ability to optimize and manage a healthy GitHub environment at the enterprise level. The exam covers the full spectrum of GitHub Enterprise administration, including configuring user identities and authentication, managing access and permissions, enabling secure software development, automating workflows with GitHub Actions, and managing GitHub Packages. Administered by Microsoft via Pearson VUE but maintained by GitHub, this certification demonstrates mastery of both GitHub Enterprise Cloud (GHEC) and GitHub Enterprise Server (GHES) environments.
The certification is valid for two years from the date of passing and is recognized across the industry as a benchmark for professionals responsible for administering GitHub at scale. It encompasses practical knowledge of SAML SSO, SCIM provisioning, role-based access control, Dependabot, CodeQL scanning, self-hosted runner configuration, and audit log management — skills increasingly demanded in regulated, enterprise-grade software development environments.
This certification is designed for system administrators, DevOps engineers, application administrators, IT professionals, and technology managers with intermediate-level experience in GitHub Enterprise Administration. Ideal candidates are those who manage GitHub Enterprise environments on a day-to-day basis, configure organizational policies and security settings, support developer workflows, and ensure compliance within their organizations.
Professionals working in roles such as GitHub Enterprise administrator, platform engineer, DevOps engineer, or cloud infrastructure manager will find this certification most relevant. It is suited for those who have hands-on experience with GitHub's enterprise features but want a formal credential to validate their expertise and advance into senior administration or architecture roles.
There are no formal prerequisites required to sit for the GH-100 exam. However, Microsoft and GitHub recommend intermediate-level experience with GitHub Enterprise Administration before attempting the exam. Candidates should be comfortable navigating GitHub Enterprise Cloud and/or GitHub Enterprise Server, configuring organization and enterprise-level settings, and managing user access.
Practical familiarity with identity providers (such as Azure AD or Okta), SAML SSO, SCIM protocols, GitHub Actions runner management, and security features like Dependabot and code scanning is strongly recommended. Candidates who have previously earned the GitHub Foundations certification or have equivalent hands-on experience will be well-positioned to succeed.
The GH-100 exam is administered through Pearson VUE and must be taken under proctored conditions. Candidates have 100 minutes to complete the assessment. The exam may include interactive components in addition to traditional question types. The passing score is 700 out of 1000. The exam is currently offered in English only.
The exam is scored across seven domains with defined percentage weights. If a candidate fails, they may retake the exam 24 hours after the first attempt; subsequent retake waiting periods vary per Microsoft's retake policy. An official practice assessment is available on Microsoft Learn to help candidates familiarize themselves with the question style, wording, and difficulty level. An exam sandbox (GHCertDemo.starttest.com) is also available to experience the exam interface before test day.
The GitHub Administration certification is directly applicable to roles such as GitHub Enterprise Administrator, Platform Engineer, DevOps Engineer, Site Reliability Engineer, and Technology Manager. As GitHub Enterprise adoption grows across regulated industries and large enterprises, professionals who can manage secure, compliant, and scalable GitHub environments are in high demand. The certification signals readiness to own enterprise-wide GitHub strategy, including identity federation, policy governance, and CI/CD infrastructure.
According to the 2025 Pearson VUE Value of IT Certification report, 32% of certified professionals received salary increases after earning a certification, and 82% gained confidence to pursue new career opportunities. GitHub administrators in the United States can expect competitive compensation in the range of $120,000–$180,000 USD annually, varying by seniority, geographic location, and the complexity of the environments they manage. Compared to general DevOps certifications, the GH-100 is highly specific to GitHub's ecosystem, making it a strong differentiator for professionals in organizations standardized on GitHub Enterprise.
5 sample questions with correct answers and explanations. Start a practice session to test yourself across all 447 questions.
1. ProvisioningAutomation Corporation wants to automate employee onboarding and offboarding processes with their GitHub Enterprise deployment. They need immediate access provisioning for new hires and automatic access revocation when employees leave. Which GitHub Enterprise feature provides this complete lifecycle automation?
Explanation
Enterprise Managed Users (EMU) provides complete user lifecycle automation where the identity provider creates GitHub accounts for new employees, manages profile information and access permissions, and automatically deactivates accounts when employees leave the organization. This automation integrates with existing HR and onboarding systems to ensure immediate access provisioning and secure offboarding without manual GitHub account management.
2. EventManagement Inc wants to create a Git workflow where feature branches must be up-to-date with main before they can be merged, and they want to maintain a linear history. What merge strategy should they enforce?
Explanation
Requiring rebase before merging ensures feature branches are up-to-date with main and creates a linear history. The workflow would be: rebase feature branch onto main, then fast-forward merge (or merge with --ff-only). This prevents merge commits and creates a clean, linear history that's easier to follow.
3. MobileGaming Corp wants to connect their local Git repository to GitHub so they can backup their code and collaborate with remote team members. After creating a repository on GitHub, what do they need to set up for authentication?
Explanation
GitHub requires SSH keys for command-line Git operations. You generate an SSH key pair on your local machine and add the public key to your GitHub account settings. This provides secure authentication without needing to enter passwords for every Git operation. GitHub no longer accepts password authentication for Git operations from the command line.
4. VideoStream Entertainment processes large video files in their GitHub Actions workflows and frequently encounters timeout issues with their current runner setup. Their video processing jobs often require 4-6 hours to complete. What solution should they implement to handle these long-running processes?
Explanation
Self-hosted runners with custom timeout configurations are the best solution for VideoStream's long-running video processing workflows. GitHub-hosted runners have maximum timeout limits that cannot be extended beyond their built-in constraints, typically 6 hours for GitHub Actions. Self-hosted runners allow VideoStream to configure longer timeouts or even run jobs without timeout limits, and they can be equipped with the necessary computing resources for video processing. While splitting into parallel jobs might help in some cases, video processing often requires sequential operations that cannot be easily parallelized.
5. InsightMonitoring Corporation wants to track repository activity, contributor engagement, and project health metrics across their development teams. Which GitHub feature should they use to analyze repository performance?
Explanation
Repository Insights provide comprehensive analytics including contributor activity, commit frequency, traffic patterns, code frequency changes, and dependency information. These insights enable data-driven decisions about project health, team performance, and resource allocation. Issues track specific problems, pull requests show code review activity, and audit logs focus on security and administrative actions, but Insights provide the holistic view needed for performance monitoring.
One-time access to this exam