Microsoft · GH-100
GitHub Administration (GH-100) Practice Tests
Certifies ability to optimize and manage a healthy GitHub environment, covering repository management, workflow optimization, and efficient collaboration.
Exam Details
Practice Questions
447
≈ 8 practice exams
Duration
100 minutes
Passing Score
700/1000
Difficulty
IntermediateLast Updated
Jan 2026
Topics Covered
Support GitHub Enterprise for users and key stakeholdersManage user identities and GitHub authenticationGitHub deployment, distribution, and licensingManage access and permissions based on membershipEnable secure software development and ensure complianceManage GitHub Actions
GitHub Administration (GH-100) Practice Exam Preparation
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 Microsoft 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.
Exam Domain Breakdown
Support GitHub Enterprise for users and key stakeholders9%
Manage user identities and GitHub authentication11%
Describe how GitHub is deployed, distributed, and licensed9%
Manage access and permissions based on membership18%
Enable secure software development and ensure compliance36%
Manage GitHub Actions16%
Manage GitHub Packages5%
Exam Overview
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.
Who Should Take This Exam
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.
Prerequisites
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.
Exam Format
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.
Skills Measured
- 1.Domain 1: Support GitHub Enterprise for users and key stakeholders (9%) — Covers distinguishing administrator-resolvable issues from GitHub Support tickets, generating support bundles and diagnostics, recommending developer workflow standards (branching, code review, CI/CD strategy), using GitHub APIs to extend admin capabilities, and evaluating GitHub Marketplace apps and actions.
- 2.Domain 2: Manage user identities and GitHub authentication (11%) — Covers enabling and enforcing SAML SSO for single and multiple organizations, requiring two-factor authentication, selecting and configuring identity providers, understanding SCIM provisioning with Azure AD and Okta, and contrasting team synchronization with SCIM.
- 3.Domain 3: Describe how GitHub is deployed, distributed, and licensed (9%) — Covers contrasting GitHub Enterprise Cloud, GitHub Enterprise Server, and GitHub AE capabilities; describing billing models for seat licenses, GitHub Actions minutes, and GitHub Packages storage; and locating license usage statistics.
- 4.Domain 4: Manage access and permissions based on membership (18%) — Covers defining GitHub organizations and teams, contrasting single vs. multiple organization deployments, describing role-based permissions (organization members, owners, billing managers, outside collaborators), applying least-privilege principles, and configuring enterprise and organization policies.
- 5.Domain 5: Enable secure software development and ensure compliance (36%) — Covers GitHub's security posture support, scrubbing sensitive data from repositories, audit log APIs (REST and GraphQL), security policies, dependency vulnerability management with Dependabot, CodeQL-based automated code scanning, secret scanning, security advisories, supported access tokens, GitHub Apps vs. OAuth Apps, and enterprise managed users (EMUs).
- 6.Domain 6: Manage GitHub Actions (16%) — Covers distributing reusable actions and workflow templates across the enterprise, configuring organizational use policies for Actions, managing GitHub-hosted and self-hosted runners (including IP allow lists, proxies, labels, and groups), monitoring and troubleshooting runners, and managing encrypted secrets at repository and organization levels.
- 7.Domain 7: Manage GitHub Packages (5%) — Covers supported package registries, accessing and sharing packages, integrating GitHub Packages into workflows with GitHub Actions or other CI/CD tools, and differentiating GitHub Packages from releases.
Study Tips
- Start with the official GH-100 Study Guide on Microsoft Learn (aka.ms/GH100-StudyGuide), which maps every exam domain with specific sub-topics and bullet points — use it as a checklist to track your preparation progress.
- Take the free official Practice Assessment on Microsoft Learn before scheduling your exam; it mirrors the actual question style and difficulty, and helps identify knowledge gaps across all seven domains.
- Use the GitHub Certification exam sandbox at GHCertDemo.starttest.com to get comfortable with the interactive question types before exam day, since the GH-100 may include lab-style components beyond standard multiple-choice.
- Build hands-on experience in a GitHub Enterprise trial environment: practice configuring SAML SSO with a test identity provider, setting up SCIM, creating self-hosted runners, and enabling Dependabot and code scanning on real repositories.
- Pay special attention to Domain 5 (Enable secure software development and ensure compliance), which carries the highest weight at 36%. Focus on the differences between GitHub Apps, OAuth Apps, and PATs; the audit log REST and GraphQL APIs; and the full Dependabot/CodeQL/secret scanning feature set.
- Review the official GitHub Docs for GitHub Enterprise Cloud and GitHub Enterprise Server side-by-side to understand feature parity differences — exam questions frequently test your ability to distinguish GHEC, GHES, and GHAE capabilities.
- Study the GitHub Actions runner management documentation thoroughly, including the security implications of self-hosted runners on public repositories, IP allow list configurations, and runner group access controls, as Domain 6 accounts for 16% of the exam.
Career Benefits
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.
Sample Questions
5 sample questions with answers and explanations. The full bank has 447 questions, enough for 8 full-length practice exams.
Preview — answers shown1. FashionTech Ltd wants to enforce a policy where all commit messages must include a ticket number from their project management system. Which Git hook would be most appropriate for this validation?
Apre-push
Bpre-commit
Cpost-commit
Dcommit-msg
Explanation
The commit-msg hook is triggered after the user enters a commit message but before the commit is finalized. This hook receives the commit message as input and can validate it, reject commits with improper messages, or even modify the message. This is perfect for enforcing commit message standards like requiring ticket numbers.
2. InsuranceCorp Inc wants to implement a Git workflow where no code can be pushed directly to main branch - all changes must go through pull requests with required reviews. What GitHub feature enforces this policy?
AIssue templates
BRepository templates
CBranch protection rules
DGitHub Actions
Explanation
GitHub branch protection rules can enforce policies like requiring pull request reviews before merging, preventing direct pushes to protected branches, requiring status checks to pass, and requiring branches to be up-to-date before merging. These rules provide automated enforcement of code review and quality gate policies.
3. ComplianceReporting Solutions needs to export audit log data for external compliance auditing and long-term archival. What methods can they use to access and export comprehensive audit information?
AEmail GitHub Support to request audit information
BManual screenshots of audit events in the web interface
CAudit data cannot be exported from GitHub
DUse GitHub's REST API, GraphQL API, and web interface export capabilities to programmatically access and export audit data in CSV or JSON formats
Explanation
GitHub provides multiple methods for accessing audit data including REST API for comprehensive event data, GraphQL API for structured queries, and web interface export in CSV or JSON formats. These programmatic approaches enable automated audit data collection, integration with compliance management systems, and long-term archival for regulatory requirements. API access provides more comprehensive and searchable data than manual methods.
4. RetailChain Inc has discovered that their last commit introduced a critical bug in production. They want to create a new commit that undoes the changes from the problematic commit while preserving the project history. Which command should they use?
Agit revert HEAD
Bgit undo HEAD
Cgit delete HEAD
Dgit reset --hard HEAD~1
Explanation
The git revert HEAD command creates a new commit that undoes the changes introduced by the specified commit. Unlike git reset, which rewrites history, git revert is safe for shared repositories because it preserves the existing history while adding a new commit that reverses the problematic changes. This is the preferred approach for fixing issues in commits that have already been shared.
5. MobileApps Inc wants to understand the basic Git workflow. They have a working directory with modified files and want to create a checkpoint (commit). What is the correct sequence of steps in the Git workflow?
AStaging Area → Working Directory → Repository
BWorking Directory → Staging Area → Repository
CRepository → Staging Area → Working Directory
DWorking Directory → Repository → Staging Area
Explanation
The correct Git workflow is: Working Directory → Staging Area → Repository. First, you modify files in your working directory. Then you add specific files to the staging area using git add (this is like preparing files for a checkpoint). Finally, you commit the staged files to the repository using git commit (this creates the actual checkpoint). The staging area acts as an intermediate step that lets you carefully choose which changes to include in each commit.
More Microsoft Practice Exams
Microsoft 365 Certified: Endpoint Administrator Associate (MD-102)
MD-102 · 723 questions
Microsoft Certified: Fabric Data Engineer Associate (DP-700)
DP-700 · 819 questions
GitHub Actions (GH-200)
GH-200 · 310 questions
GitHub Advanced Security (GH-500)
GH-500 · 299 questions
GitHub Copilot (GH-300)
GH-300 · 352 questions
Microsoft Certified: Identity and Access Administrator Associate (SC-300)
SC-300 · 489 questions
$17.99
One-time access to this exam
447 questions (8 practice exams' worth)
Unlimited timed exam simulations
Yours forever — no subscription
Detailed explanations
Free preview stays available