GitHub · GH-100
Certifies ability to optimize and manage a healthy GitHub environment, covering repository management, workflow optimization, and efficient collaboration.
Practice Questions
447
≈ 5 practice exams
Duration
100 minutes
Passing Score
700/1000
Difficulty
IntermediateLast Updated
Jan 2026
Use this GH-100 practice exam to prepare for GitHub Administration (GH-100) with realistic questions, detailed explanations, and focused study modes. The practice bank includes 447 questions for GitHub GH-100, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to recurring topics such as Support GitHub Enterprise for users and key stakeholders, Manage user identities and GitHub authentication, GitHub deployment, distribution, and licensing, Manage access and permissions based on membership, and Enable secure software development and ensure compliance. Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
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 answers and explanations. The full bank has 447 questions, enough for 5 full-length practice exams.
Preview — answers shown1. DevTeam Corp is merging a feature branch into main, but Git opens an editor asking for a commit message. What is Git trying to create?
Explanation
Git is creating a merge commit, which is a special commit that combines the histories of two branches. When you merge branches that have diverged (both have new commits), Git creates a merge commit to join them together. The editor opens so you can provide a message describing what was merged, though Git usually provides a default message.
2. DataCorp wants to see the history of all commits in their project to understand what changes were made over time. Which command will show them a detailed log of all commits?
Explanation
The git log command displays the commit history, showing commit IDs, authors, dates, and commit messages. This gives developers a complete timeline of all changes made to the project. git history and git list are not valid Git commands, while git show displays details about a specific commit rather than the complete history.
3. StartupTeam Ltd has a repository on GitHub that their colleague has updated. They want to download the latest changes to their local repository. Which command should they use?
Explanation
The git pull command downloads changes from the remote repository and automatically merges them into your current branch. This is equivalent to running git fetch (which downloads changes) followed by git merge (which integrates them). This keeps your local repository synchronized with the remote repository.
4. TransportApp Inc wants to automatically format their code and run linting before each push to ensure code quality. Which Git hook is most appropriate for this automated check?
Explanation
The pre-push hook runs before git push completes, making it ideal for comprehensive checks like code formatting, linting, and running tests. This prevents pushing code that doesn't meet quality standards. Pre-commit is good for quick checks, but pre-push allows for more thorough validation since it runs less frequently.
5. FinTech Solutions has multiple stashed changes and wants to see what they have stashed before applying any of them. Which command shows their stash history?
Explanation
The git stash list command displays all stashed changes with their identifiers (stash@{0}, stash@{1}, etc.) and the branch they were created on. This helps you identify which stash contains the work you want to restore, especially when you have multiple stashes saved.
$17.99
One-time access to this exam