Microsoft GH-100 Exam Questions 2025

Microsoft GH-100

The GH-100: GitHub Administration (beta) certification exam validates your ability to run and maintain a healthy, secure, efficient GitHub Enterprise environment. It measures skills in repository and workflow architecture, user management and identity, permissions, security/compliance, and GitHub Actions orchestration.

Who Should Take This Exam?

This is aimed at people who manage or administer GitHub environments in organizations (especially enterprises). Typical candidate profiles include:

• System administrators or platform engineers responsible for GitHub Enterprise
• DevOps or SRE engineers who manage collaboration workflows and CI/CD
• Application administrators or tool engineers supporting developers
• Security / compliance engineers involved in securing repos, policies, audit logs
• IT professionals who maintain integration, access, and governance of GitHub across multiple teams

Experience level: Intermediate to advanced in GitHub, DevOps, identity & access management, and familiarity with enterprise contexts.

Prerequisites and Recommendations

Official prerequisites:

• None formally stated. Because the exam is in beta, there’s no formal eligibility requirement.
• You must schedule via Microsoft / Pearson VUE and take it within the permitted window.

Recommended background (practical):

• Hands-on experience with GitHub (both cloud and enterprise) — repositories, branches, pull requests, Actions, permissions
• Knowledge of identity systems (SAML SSO, SCIM, 2FA)
• Exposure to enterprise-scale governance (audit logs, license management, access policies)
• Understanding of CI/CD, automation, security, and compliance as applied to GitHub
• Prior credentials in DevOps, cloud, or security can help (not required)

Exam Objectives and Domains

The GH-100 exam assesses performance in the following domains (with approximate weightings):

1. Support GitHub Enterprise for users and stakeholders (~15 %)
2. Manage user identities and authentication (~20 %)
3. Describe GitHub deployment, distribution, licensing (~5 %)
4. Manage access and permissions (~20 %)
5. Enable secure software development & ensure compliance (~15 %)
6. Manage GitHub Actions (~20 %)
7. Manage GitHub Packages (~5 %)

Objective Details by Domain

Domain I: Support GitHub Enterprise for users and stakeholders

• Determine what issues should be escalated to GitHub Support vs handled internally
• Generate support bundles / diagnostics
• Monitor usage patterns, feature adoption, most active teams/repos
• Recommend best practices for developer workflows (branching models, review rules, code owners)
• Understand how to use GitHub APIs/Marketplace for enhancements

Domain II: Manage user identities and authentication

• Enable and enforce SAML SSO (single organization vs enterprise-wide)
• Configure 2FA
• Understand identity provider choices and SCIM provisioning
• Model team sync, membership relationships, and role inheritance
• Handle authorization logic in enterprise / org / team contexts

Domain III: Describe GitHub deployment, distribution, licensing

• Distinguish between GitHub Enterprise Server, GitHub Enterprise Cloud, and GitHub AE
• Explain licensing models (seat licenses, actions minutes, storage)
• Analyze license usage, billing and metered resources
• Understand how GitHub is hosted, distributed, and supported

Domain IV: Manage access and permissions

• Model organization structure (single vs multiple orgs) and trade-offs
• Assign scopes, default permissions, team vs member roles
• Enforce least privilege at repository, team, and org levels
• Use organization policies and enterprise policies
• Understand outside collaborators vs internal members

Domain V: Enable secure software development & ensure compliance

• Security features in GitHub: secret scanning, code scanning, dependency graph
• Audit log usage (via REST / GraphQL APIs)
• Scrub sensitive data from git history / contact support when needed
• Define security / compliance policies for repository and enterprise
• Coordinate security incident response, policy enforcement, and reporting

Domain VI: Manage GitHub Actions

• Distribute shared workflows, templates, reusable components
• Control access to actions, enforce usage policies
• Configure self-hosted vs GitHub-hosted runners
• Manage encrypted secrets at org / repo levels and integrate vaults
• Monitor/maintain, troubleshoot runners & workflows

Domain VII: Manage GitHub Packages

• Understand supported package types and usage in workflows
• Publish, share, and consume packages
• Integrate packages with CI/CD pipelines
• Understand differences between packages and GitHub Releases

What Changed in This Version?

Because GH-100 is currently in beta, many “changes” are not from a prior full version but reflect the exam’s design:

• It emphasizes enterprise-scale governance, identity, and operations rather than just basic repo features
• More weight on Actions management, permissions, and security/compliance
• Packaging is included as a lighter domain
• Some topics (like basic Git workflows) are likely assumed knowledge, with more depth required in managing scale, audit, and enterprise constraints

Registration and Scheduling

• Buy / register GH-100 via the Microsoft / GitHub certification portal
• Schedule exam through Pearson VUE (in-person) or online proctoring (if available in your region)
• You must take the exam within the valid window (especially while in beta)
• Book your slot in advance (at least 24 hours before)

Pricing and Vouchers

• As a beta exam, Microsoft has offered discounted pricing for early takers (e.g., up to 80% off for first 300 candidates)
• After beta period, full pricing will apply (regionally adjusted)
• Microsoft typically offers discounts for students, academic, and sometimes for early adopters
• Organizations (employers, training partners) may have voucher programs or bulk licensing deals

Policies You Should Know

• Beta exam results are not instantaneous; they may take weeks after the beta period ends
• Exam availability is limited during beta (not all regions)
• Rescheduling/cancellation rules follow Pearson VUE standard windows
• Valid government-issued ID required at test time
• Name used for registration must match ID
• During beta, certain exam policies (scoring, retakes) may differ

Scoring and Results

• After beta period, scores will be released (not instant)
• Scoring uses a standard scale (exact scale not fully disclosed)
• Partial credit is unlikely (questions are multiple choice)
• You receive a report showing domain-level performance
• Passing criteria will be set once beta is complete

Exam Day and Test Experience

• On-site test center: standard check-in, identity verification, proctor oversight
• Online proctoring (if available): room scan, webcam / mic checks, environment rules
• Allowed items: only permitted materials (no personal devices, notes, etc.)
• Breaks: may or may not be allowed (depending on exam mode)
• Interface tips: flag difficult questions, navigate back to review, manage time across domains
• Time allocation: with 100+ questions, aim for ~1–2 minutes per question, factoring in review

Study Plan and Preparation

Beginner plan (~10 weeks)

• Weeks 1–2: Review GitHub enterprise architecture, Git basics, identity management
• Weeks 3–4: Dive into user identities, SSO, SCIM, 2FA, provisioning
• Weeks 5–6: Study permissions, org / team structures, policies, access models
• Weeks 7–8: Focus on GitHub Actions (runners, workflows, secrets), audit, security tooling
• Week 9: Learn licensing, package management, billing, deployment models
• Week 10: Two full mock exams, review weak domains, memorization of policies

Experienced candidate plan (~5–6 weeks)

• Week 1: Gap analysis against domains
• Weeks 2–3: Deep dive into identity, permissions, and Actions governance
• Week 4: Run full-length mock exam and assess weak areas
• Week 5: Reinforce security/compliance, audit, package topics
• Week 6: Final review, quick scenario drills, restful sleep before exam

Certification Validity and Renewal

• Expected validity: 2 years (like many Microsoft / GitHub certifications)
• Renewal likely requires continuing education / recertification exams
• You’ll need to maintain familiarity with GitHub product updates, new features, and governance best practices
• Microsoft may require periodic retakes or updates through new exam versions

Career Outcomes

Actual compensation depends strongly on location, experience, and bonuses/equity.

Related or Next-Step Certifications

• GH-200: GitHub Actions — deeper specialization in automation, pipelines, and workflow orchestration
• GH-900: GitHub Foundations — foundational certification, good for those earlier in their GitHub journey
• Microsoft DevOps / Azure Certifications (AZ-400, etc.) — if your workflow spans Azure + GitHub
• Security / compliance certs (e.g. Microsoft security credentials) — to deepen the security side once GH-100 is done

How This Exam Compares to Similar Certifications

• Compared to GH-900 (Foundations): GH-100 is more advanced, focusing on governance, identity, enterprise features, and operations rather than basic Git workflow.
• Compared to DevOps or Azure exams (e.g. AZ-400): GH-100 is narrower (GitHub focused) but deeper in version control, permissions, actions, and compliance. It complements broader DevOps certs rather than overlapping fully.