16 free GitHub GH-100 Administration practice questions from the CertStash pack of 65, each with the correct answer and a full explanation. The rule is the same for every exam: ten free on the product page, 16 free here, all 65 in the pack, and each step includes the one before it.
Get all 65 questions (US$39) · Download the first 10 as a PDF
Question 1
When comparing fine-grained Personal Access Tokens (PATs) with classic PATs, which of the following statements is accurate?
Show answer and explanation
Correct answer: B. Fine-grained PATs permissions can be scoped to specific repositories.
Fine-grained Personal Access Tokens offer repository-level permission scoping, allowing developers to restrict token access to specific repositories rather than granting broad access across all repositories. This is a key security improvement over classic PATs, which can only be scoped to broad permission categories without repository-level granularity.
Why the other options are wrong
- A. Neither fine-grained nor classic PATs automatically renew; both require manual renewal or expiration management.
- C. Fine-grained PATs provide more granular permission controls than classic PATs, not fewer.
- D. Fine-grained PATs can be restricted to specific repositories and organizations; classic PATs cannot be restricted to specific repositories.
Question 2
What is the new capability of GitHub's billing dashboard?
Show answer and explanation
Correct answer: B. Enables tracking of GitHub Copilot usage by user
GitHub's billing dashboard includes the capability to track GitHub Copilot usage metrics by individual user, enabling organizations to monitor AI tool consumption and manage costs associated with Copilot licenses effectively.
Why the other options are wrong
- A. The billing dashboard does not automatically remove unused users; this requires manual action by administrators.
- C. While plan management exists, self-service upgrades are not the primary new billing dashboard capability.
- D. The billing dashboard does not provide real-time Slack alert integration for billing overages.
Question 3
What is a key characteristic of GitHub Enterprise Server (GHES) compared to GitHub Enterprise Cloud (GHEC)?
Show answer and explanation
Correct answer: C. GHES allows enterprises to have complete control over their hosting environment, including data storage and network security policies.
GitHub Enterprise Server is a self-hosted solution that allows enterprises complete control over their hosting environment, including decisions about data storage locations, network security policies, infrastructure management, and compliance requirements specific to their organization.
Why the other options are wrong
- A. This statement is reversed: GHEC is GitHub-hosted with automatic scaling, while GHES requires self-hosting.
- B. GHEC offers data residency options, not GHES; GHES hosting is determined by the enterprise's own infrastructure.
- D. GHES fully supports integration with external identity providers such as SAML, LDAP, and OAuth for authentication.
Question 4
You have subscribed to GitHub Premium Support, and you need to submit a support ticket. GitHub Premium Support can help you with:
Show answer and explanation
Correct answer: B. installing GitHub Enterprise Server.
GitHub Premium Support provides assistance with GitHub Enterprise Server installation, configuration, and deployment issues. Installing GitHub Enterprise Server is a core support function that requires specialized knowledge of the platform's infrastructure requirements and setup procedures.
Why the other options are wrong
- A. Writing scripts is a development task outside the scope of GitHub's support services.
- C. Setting up hardware is a customer infrastructure responsibility, not a GitHub support function.
- D. While GitHub supports integrations, third-party application integration issues are typically handled by the third-party vendor or through documentation rather than Premium Support.
Question 5
You need to contact GitHub Premium Support. What are valid reasons for submitting a support ticket? (Each answer presents a complete solution. Choose two.)
Show answer and explanation
Correct answer: C, D. business impact from security issues within your organization; outages on GitHub.com affecting core Git functionality
GitHub Premium Support is designed for urgent business-impacting issues. Security vulnerabilities that affect your organization's operations and outages impacting core Git functionality on GitHub.com are both critical issues requiring immediate escalated support. These represent genuine business continuity threats that warrant premium support intervention.
Why the other options are wrong
- A. License renewal is an administrative billing matter handled through account management, not a support ticket reason.
- B. Hardware setup issues are the customer's infrastructure responsibility and fall outside GitHub's support scope.
Question 6
Which of the following is a key benefit of using GitHub Marketplace Apps in an enterprise?
Show answer and explanation
Correct answer: B. They often include integrations with external services, reducing the need for custom code
GitHub Marketplace Apps provide pre-built integrations with external services and platforms, eliminating the need for organizations to develop custom code for common workflows and tool connections. This reduces development overhead and accelerates deployment of enterprise functionality.
Why the other options are wrong
- A. Marketplace Apps cannot guarantee no downtime during GitHub maintenance windows as they are separate applications dependent on GitHub's infrastructure.
- C. GitHub Actions and Marketplace Apps serve different purposes; apps provide integrations while Actions provide workflow automation, and neither eliminates the need for the other.
- D. Apps in the Marketplace undergo security review but are not universally pre-approved; users must evaluate app security and permissions for their specific needs.
Question 7
You need to create a support bundle for your GitHub Enterprise Server instance with the hostname ghe.avocado.corp. What command should you use to create a support bundle?
Show answer and explanation
Correct answer: A. ssh -p 122 adming@ghe.avocado.corp -- 'ghe-support-bundle -o' > support-bundle.tgz
The correct command uses SSH on port 122 (the standard management port for GitHub Enterprise Server) to connect to the admin user and execute the ghe-support-bundle command with the output redirection flag (-o) to save the bundle as a tarball file. This is the official method for generating diagnostic bundles from a GitHub Enterprise appliance.
Why the other options are wrong
- B. The ghe-diagnostics command generates diagnostic information but is not the correct command for creating a support bundle.
- C. Using curl with HTTPS to retrieve a support bundle endpoint is not a valid GitHub Enterprise support bundle generation method.
- D. The ghe-config command is used for configuration management, not for generating support bundles.
Question 8
What do you need to successfully generate a support bundle on a GitHub Enterprise Server?
Show answer and explanation
Correct answer: C. Administrator SSH access to the appliance
Generating a support bundle on GitHub Enterprise Server requires administrator-level SSH access to the appliance. This elevated access is necessary to execute the diagnostic commands and access sensitive system information included in the support bundle.
Why the other options are wrong
- A. GitHub Support approval is not required to generate a support bundle; it is a self-service administrative function performed before contacting support.
- B. GitHub Actions in a repository have no role in generating appliance-level support bundles.
- D. GitHub App permissions are irrelevant to generating support bundles, which require direct SSH access to the appliance infrastructure.
Question 9
A financial services company is evaluating GitHub account types. Which of the following is a key distinction between GitHub Enterprise Managed Users and Personal Accounts?
Show answer and explanation
Correct answer: B. Personal Accounts are owned by users and can be used for both personal and professional work.
Personal Accounts are owned and controlled by individual users and can be used for both personal projects and professional work. This is the fundamental distinction that differentiates Personal Accounts from Enterprise Managed Users, which are provisioned and controlled by the enterprise organization.
Why the other options are wrong
- A. Enterprise Managed Users are restricted to enterprise repositories and cannot freely collaborate across personal repositories.
- C. Personal Accounts provide user autonomy, not stricter control; Enterprise Managed Users provide stricter organizational control.
- D. Enterprise Managed Users require the identity provider to manage authentication, but the organization does not need to operate their own authentication server.
Question 10
Which THREE of the following accurately describe how the SCIM protocol enhances user management in GitHub Enterprise Cloud? (Choose three.)
Show answer and explanation
Correct answer: A, B, D. SCIM synchronizes changes to user attributes from the identity provider to GitHub; SCIM deactivates GitHub accounts when users are deleted from the identity provider; SCIM automates user provisioning when new users are added to the identity provider.
SCIM (System for Cross-domain Identity Management) synchronizes user attributes from the identity provider to GitHub, automatically provisions new users when they are added to the identity provider, and deactivates GitHub accounts when users are removed from the identity provider. These three capabilities automate the entire user lifecycle, reducing manual administrative overhead.
Why the other options are wrong
- C. SCIM manages user accounts and group memberships, not repository deletion policies.
- E. SCIM does not generate authentication tokens; that functionality is provided by GitHub's authentication and authorization systems.
- F. SCIM manages user provisioning and group membership but does not configure granular repository permissions directly.
What people say about the full GH-100 pack 5.0 from 4
Thank you so much for your high-effective GH-100 exam questions! GH-100 exam is an important exam for me and I had cleared it with your help.
This was my first try, but I passed my GH-100 GitHub Administration exam successfully. The dumps from Cert Stash were so accurate that I passed with confidence. Thanks very much!
I am your loyal customer, perfect GitHub Administrator as before.
Question 11
Which of the following actions can a user with Write permissions perform in a GitHub repository?
Show answer and explanation
Correct answer: B. Push code to non-protected branches.
Users with Write permissions can push code to non-protected branches, allowing them to contribute code to the repository. Write permissions do not extend to managing repository settings, configuring branch protection rules, or deleting repositories, these require higher permission levels.
Why the other options are wrong
- A. Managing repository settings such as labels and GitHub Pages requires Admin or Maintain permissions, not Write.
- C. Configuring branch protection rules requires Admin or Maintain permissions, not Write.
- D. Deleting a repository requires Admin permissions, well above Write level.
Question 12
You are managing a repository in your organization's GitHub account. A team member asks you to confirm who has access to the repository and their permission levels. Which tool should you use to review and manage repository access?
Show answer and explanation
Correct answer: C. Repository Settings > Manage Access.
Repository Settings > Manage Access is the dedicated tool in GitHub for reviewing and managing who has access to a repository and their specific permission levels. This interface displays collaborators, teams, and their assigned roles (pull, push, admin, maintain, triage). GitHub Pages Settings controls static site deployment, GitHub Actions Logs tracks workflow executions, and Branch Protection Rules manage branch-level restrictions, none of these tools are designed for managing overall repository access and permissions.
Why the other options are wrong
- A. GitHub Pages Settings is used for configuring static site hosting, not for managing repository access.
- B. GitHub Actions Logs display workflow execution details and history, not repository access permissions.
- D. Branch Protection Rules enforce restrictions on specific branches, not manage overall repository access.
Question 13
Which of the following is the responsibility of an Organization Owner in GitHub? (Choose three.)
Show answer and explanation
Correct answer: A, B, C. View and manage organization billing information; Create repositories without approval from other members; Manage organization settings, such as configuration and default permissions.
Organization Owners have responsibility for viewing and managing billing information, creating repositories without needing approval from other members, and managing organization settings including configuration and default permissions. These are core ownership privileges that grant comprehensive control over the organization.
Why the other options are wrong
- D. Organization Owners have implicit access to repositories as part of their ownership role; they are not restricted to only explicitly granted access by team maintainers.
Question 14
Why would a GitHub App be favored over a machine account for automation tasks?
Show answer and explanation
Correct answer: B. GitHub Apps provide a higher rate limit ceiling than using a personal access token on a machine account, when they use an install token and are owned by a GitHub Enterprise Cloud licensed enterprise.
GitHub Apps using installation tokens provide higher rate limits compared to personal access tokens on machine accounts, particularly when the GitHub App is owned by a GitHub Enterprise Cloud licensed enterprise. This higher rate ceiling enables more efficient automation and reduces the risk of hitting rate limits during intensive operations.
Why the other options are wrong
- A. Webhook delivery does not require machine accounts and is not a distinguishing factor for GitHub Apps.
- C. GitHub Apps can be installed at the enterprise, organization, or repository level; they are not limited to single repositories.
- D. GitHub Apps provide better auditability than machine accounts due to their distinct identity and permission logging capabilities.
Question 15
Your organization wants to reduce costs. Which of the following actions should you take?
Show answer and explanation
Correct answer: C. Regularly audit for inactive users
Regularly auditing for inactive users directly reduces costs by identifying accounts that are no longer in use and can be removed, eliminating unnecessary licensing fees. This is a proactive cost management practice that doesn't compromise security or functionality.
Why the other options are wrong
- A. Granting all users admin permissions increases security risks and doesn't reduce costs.
- B. Removing outside collaborators may impact business relationships and project needs rather than addressing systemic cost issues.
- D. Disabling SAML SSO increases security risks and complexity rather than reducing costs.
Question 16
You are planning GitHub account management for a healthcare organization with strict compliance requirements. Which THREE of the following statements accurately describe GitHub Enterprise Managed Users (EMU) accounts? (Choose three.)
Show answer and explanation
Correct answer: B, D, F. EMU accounts are managed through an identity provider such as Azure AD; EMU accounts restrict users to enterprise-related activities only; EMU accounts are owned by the organization and cannot be unlinked.
EMU accounts are managed centrally through an identity provider like Azure AD (B), are owned and controlled by the organization rather than individual users and cannot be unlinked (F), and are restricted to enterprise-related activities only (D). EMUs cannot be used for personal repositories, users cannot create their own credentials, and accounts are created by the IdP-organization integration, not by individual users.
Why the other options are wrong
- A. EMU accounts are restricted to enterprise repositories only, not personal repositories.
- C. EMU users cannot manage their own credentials; all credential management is handled by the IdP.
- E. EMU accounts are created and managed by the organization through the IdP, not by individual users.
That was 16 of 65.
The full GitHub GH-100 Administration pack has all 65 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. US$39, paid once, with free monthly updates and a pass-or-your-money-back guarantee.
Not ready yet? Get the first 32 free as one PDF by email. Get the Half Pack →