Description
For learners studying for GitHub Administration
What you'll learn
Practice pack content
Domain 1 - Manage GitHub identities and access
Domain 2 – Administer GitHub Enterprise environment
Domain 3 – Implement secure software development and compliance
Domain 4 – Manage GitHub Actions
Domain 5 – Monitor and optimize GitHub usage
Final Exam Simulators
Exam Study Guide
Interactive Flashcards
Try 3 GitHub Administration GH-100 practice questions
Choose an answer, explore the explanation, and see why the other options are less suitable. Three short scenarios. No sign-in required.
1. Requiring corporate sign-in for repositories
An organization uses GitHub Enterprise Cloud with members' existing personal GitHub accounts. Security requires employees to authenticate through the corporate identity provider whenever they access the organization's private repositories, without replacing those accounts. Which GitHub identity configuration directly enforces that requirement?
Answer and full explanation
Correct answer: D — Enforce SAML single sign-on for organization resource access.
Why D is correct
SAML single sign-on (SSO) lets an organization on GitHub Enterprise Cloud require its members to authenticate through a corporate identity provider to access organization resources. Members can continue to use their existing personal GitHub accounts, which are linked to identities at the provider. The scenario specifically calls for enforcing corporate authentication when accessing private repositories, rather than provisioning accounts or assigning teams. Enforcing SAML SSO addresses that sign-in requirement for organization members. Administrators should test their identity-provider configuration and plan enforcement carefully to avoid disrupting legitimate access.
Why the other options are less suitable
- A — Team synchronization: Team synchronization can map identity-provider groups to GitHub teams and keep membership aligned. It does not independently impose the required SAML authentication step for organization resources.
- B — SCIM provisioning: SCIM helps automate identity and membership lifecycle operations when supported in the configured deployment. Provisioning is different from requiring each organization member to authenticate through the identity provider to access repositories.
- C — Two-factor authentication: Two-factor authentication adds a security check to GitHub account sign-in. It does not, by itself, require authentication through the organization’s corporate identity provider.
Key takeaway: SAML SSO governs identity-provider authentication for organization access; SCIM and team synchronization address different lifecycle and membership needs.
Read two more sample questions
2. Applying consistent merge requirements
An enterprise security team manages several private repositories within one GitHub organization. Selected repositories must require pull request reviews and passing CI status checks before changes reach their default branches, and administrators want to maintain this requirement centrally. Which GitHub feature most directly meets that need?
Answer and full explanation
Correct answer: C — An organization-level branch ruleset targeting the selected repositories.
Why C is correct
Organization rulesets let administrators define branch restrictions once and apply them to multiple targeted repositories. An organization-level branch ruleset can target the default branches of selected repositories and require pull requests and passing status checks. Its active enforcement setting makes those requirements effective for matching branches. Managing one organization ruleset avoids having to maintain equivalent settings independently in every repository. Repository-specific rules can add restrictions, but they cannot make the centrally applied organization rules less restrictive.
Why the other options are less suitable
- A — CODEOWNERS: A CODEOWNERS file identifies suggested or required code owners when combined with suitable branch protections. It does not by itself centrally enforce the complete cross-repository merge policy and required CI checks.
- B — Separate branch protection rules: Branch protection rules can enforce reviews and status checks in an individual repository. Configuring them independently does not satisfy the requirement for one centrally managed organization policy.
- D — Workflow comments: A workflow can report build results or post comments on pull requests. Posting comments alone does not create the required branch-level merge restrictions across the targeted repositories.
Key takeaway: Use organization rulesets to enforce branch policies across targeted repositories; status-check workflows alone do not enforce the merge gate.
3. Sharing an Actions secret with two repositories
A GitHub Enterprise organization has deployment workflows in two approved private repositories. An administrator wants to maintain a single encrypted API token centrally and prevent all other organization repositories from receiving that token during workflow runs. How should the administrator configure access to the credential?
Answer and full explanation
Correct answer: A — An organization Actions secret restricted to selected repositories.
Why A is correct
GitHub Actions supports encrypted secrets at the organization level for reuse by permitted repositories. An organization owner can set a secret's repository access policy to selected repositories. Choosing the two approved private repositories keeps the token centrally managed without exposing it to every repository in the organization. Workflows in authorized repositories can reference the secret within GitHub's applicable access rules. Administrators should also minimize the token's privileges and rotate it according to their credential policy.
Why the other options are less suitable
- B — Repository-level secret: A repository secret is scoped to the repository in which it is configured. Creating it in one project does not automatically make it available to other repositories in the organization.
- C — Actions variable: Variables can store non-sensitive configuration, but they are not the encrypted credential store. A sensitive API token should use an appropriate secret mechanism rather than a plaintext variable.
- D — All private repositories: An organization secret available to every private repository provides broader access than required. The scenario explicitly restricts the credential to two approved repositories, so selected-repository access is more suitable.
Key takeaway: Organization-level Actions secrets can be centrally managed and restricted to selected repositories.
Preview complete
You have tried all three samples
Review the explanations or try the samples again. This short preview covers only a small part of the exam objectives.
Your sample score resets when this page reloads.
Your practice pack includes
More ways to make each study session count
Focus on a topic, practise under a time limit, or return to the supporting resources before your next attempt.
Domain-based practice
Timed practice sets
Study guide
Flashcards
Requirements
- The official GH-100 guide expects experience administering GitHub Enterprise environments, including identity management, repository permissions, organization governance, GitHub Actions and features supporting secure software development.
- Combine question practice with GitHub documentation and authorized exercises. Explore SAML SSO configurations, organization rulesets, Actions secret permissions, audit logs and runner management when identifying gaps in your knowledge.
- You will need an internet-connected device, a current web browser and an ExamsDigest account to access this online practice product and review your study work.
Know the exam you’re studying for
These details describe GitHub’s official GitHub Administration GH-100 exam.
What our students say
“I was having trouble understanding some of the GitHub Enterprise administration topics, especially SAML SSO and organization permissions. The ExamsDigest practice exams helped me identify what I needed to review, and the explanations made everything much clearer.”
Thomas Reynolds
✓ Verified Review
“The questions covered situations I could actually see happening at work, particularly around repository security, rulesets, and access management. I liked that the explanations showed why the other answers were wrong instead of just giving me the correct option.”
Natalie Brooks
✓ Verified Review
“I've been working with GitHub for a while, but GH-100 covers quite a few administrative features I hadn't used before. The ExamsDigest practice questions helped me find those gaps and understand topics like GitHub Actions security and enterprise policies.”
Eric Harrison
✓ Verified Review
Your questions, answered.
Which GitHub Administration exam does this practice target?
These questions target GitHub Administration certification exam GH-100, using the official skills measured as of July 2026. The outline covers identity management, enterprise administration, secure development, GitHub Actions and usage optimization. Before purchasing, compare the product’s stated topics, included resources and access terms with the official GH-100 guide. Certification objectives can change, so verify the version applicable to your scheduled examination.
Who is GitHub Administration GH-100 practice suitable for?
GH-100 is intended for system administrators, application administrators, developers, DevOps engineers and IT professionals with intermediate GitHub Enterprise experience. Familiarity with GitHub Enterprise Cloud or Server, identity providers, repository permissions and organization policies is particularly helpful. The guide also expects experience with GitHub Actions and secure software development features. Candidates with limited administrative experience should combine practice questions with foundational study and authorized hands-on work.
How should I combine practice questions with administrative experience?
Use practice questions alongside GitHub documentation and exercises in organizations or repositories you are authorized to administer. Compare SAML SSO with SCIM, examine organization rulesets, review Actions secrets and inspect audit information. These activities help you connect examination terminology to actual administration decisions. They are independent study suggestions and do not imply that enterprise subscriptions, hosted laboratories or administrative access are included with the practice pack.
What should I do after answering a GH-100 question incorrectly?
Identify which administrative requirement your selected option failed to meet. For example, distinguish SAML authentication from SCIM provisioning, centralized rulesets from repository-level branch protection, or organization secrets from repository variables. Review all four explanations and revisit the corresponding official documentation before trying another scenario. Focus on understanding permissions, scope and security consequences rather than memorizing answer letters. Practice scores cannot guarantee an official passing result.
Does this preview reproduce the official GH-100 examination format?
No. The preview contains three independently written questions, each with four answer choices and one correct answer. GitHub’s official examination is proctored and may include interactive components or other question formats. Microsoft’s examination guidance does not disclose the exact question-type mix beforehand. The official exam sandbox is available for exploring the testing interface. This preview should not be treated as a full examination simulation or a representation of every paid-pack feature.
Does completing this practice earn the GitHub Administration certification?
No. Purchasing or completing independent practice questions does not award the GitHub Administration credential. Earning certification requires passing the official GH-100 exam and satisfying the applicable certification requirements. GitHub currently describes its certifications as valid for two years while transitioning to Microsoft’s recertification process. Practice access and official exam registration are separate activities. Check the product’s stated terms for any voucher arrangements rather than assuming an exam booking is included.
30-day conditional refund policy
Eligible requests must be made within 30 calendar days, with no more than 20% of any included simulator completed. The purchase must not already be refunded or under a payment dispute or chargeback. Other provisions apply; mandatory consumer rights remain unaffected.
Useful links for your preparation
