Free GitHub GH-100 Administration practice questions

10 free GitHub GH-100 Administration practice questions with the correct answer and a full explanation for each, taken from the CertStash pack of 65 questions. Work through them, then open each answer to check your reasoning.

Get all 65 questions (US$39) · Download these 10 as a PDF

Question 1

You have subscribed to GitHub Premium Support, and you need to submit a support ticket. GitHub Premium Support can help you with:

  1. writing scripts.
  2. installing GitHub Enterprise Server.
  3. setting up hardware.
  4. integrating with third-party applications.
Show answer and explanation

Correct answer: B. installing GitHub Enterprise Server.

GitHub Premium Support provides assistance with GitHub Enterprise Server installation and configuration, which is an enterprise-level service offering. Writing scripts, setting up hardware, and third-party integrations fall outside the scope of GitHub's support services, as these are customer responsibilities or handled through other channels like community forums or marketplace integrations.

Why the other options are wrong

  • A. GitHub Premium Support does not provide script writing services.
  • C. Hardware setup is the responsibility of the customer and their infrastructure team.
  • D. Third-party application integration support is typically handled through documentation and community resources, not premium support.

Question 2

You need to contact GitHub Premium Support.

What are valid reasons for submitting a support ticket? (Each answer presents a complete solution.

Choose two.)

  1. license renewal
  2. hardware setup issues or errors
  3. business impact from security issues within your organization
  4. outages on GitHub.com affecting core Git functionality
Show answer and explanation

Correct answer: C, D

C. business impact from security issues within your organization D. outages on GitHub.com affecting core Git functionality GitHub Premium Support is designed to address business-critical issues, including security vulnerabilities that impact organizational operations and outages affecting core Git functionality on GitHub.com. License renewal is an administrative matter handled through billing channels, not support tickets, and hardware setup issues are outside GitHub's purview as a cloud service provider.

Why the other options are wrong

  • A. License renewal is handled through billing and account management, not support tickets.
  • B. Hardware setup issues are the customer's responsibility and not within GitHub's support scope.

Question 3

Which of the following is a key benefit of using GitHub Marketplace Apps in an enterprise?

  1. They guarantee no downtime during enterprise GitHub maintenance windows
  2. They often include integrations with external services, reducing the need for custom code
  3. Apps eliminate the need for GitHub Actions entirely
  4. All apps come pre-approved by GitHub's internal security team
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 tools, allowing enterprises to extend GitHub's functionality without developing custom code. This reduces development time and maintenance overhead. The other options misrepresent the capabilities: apps cannot guarantee no downtime, do not eliminate GitHub Actions, and are not automatically pre-approved by GitHub's security team, users must review and authorize them.

Why the other options are wrong

  • A. Marketplace apps cannot guarantee no downtime during GitHub maintenance windows.
  • C. GitHub Actions and Marketplace Apps serve different purposes; apps do not eliminate the need for Actions.
  • D. While GitHub reviews apps in the marketplace, they are not all pre-approved; users must evaluate and authorize them.

Question 4

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?

  1. ssh -p 122 adming@ghe.avocado.corp — 'ghe-support-bundle -o' > suppor-undle.tgz
  2. ssh -p 122 adming@ghe.avocado.corp, 'ghe-diagnostics' > support-bundle.tgz
  3. curl -u admin https://ghe.avocado.corp/diagnostics/support-bundle.tgz -o
  4. ssh -p 122 adming@ghe.avocado.corp — 'ghe-config generate-support-bundle' > support-bundle.tgz
Show answer and explanation

Correct answer: A. ssh -p 122 adming@ghe.avocado.corp — 'ghe-support-bundle -o' > suppor-undle.tgz

The correct command to generate a support bundle on GitHub Enterprise Server is `gh-upport-bundle`, executed via SSH on port 122 to the admin user. This command captures diagnostic information needed for troubleshooting. The other options reference no-xistent commands or incorrect procedures: `ghe-diagnostics` does not create a support bundle, curl cannot be used for this function, and `ghe-config generate-support-bundle` is not a valid command.

Why the other options are wrong

  • B. The `ghe-diagnostics` command does not generate a support bundle.
  • C. Support bundles cannot be generated via curl HTTP requests.
  • D. The command `ghe-config generate-support-bundle` does not exist in GitHub Enterprise Server.

Question 5

What do you need to successfully generate a support bundle on a GitHub Enterprise Server?

  1. Approval from GitHub Support
  2. A custom GitHub Action in the root repo
  3. Administrator SSH access to the appliance
  4. A GitHub App with read:org permissions
Show answer and explanation

Correct answer: C. Administrator SSH access to the appliance

Generating a support bundle on GitHub Enterprise Server requires administrator SSH access to the appliance, as the `ghe-support-bundle` command runs on the server itself with elevated privileges. GitHub Support approval is not required beforehand, custom GitHub Actions are not involved, and GitHub Apps with specific permissions are not needed for this local administrative task.

Why the other options are wrong

  • A. GitHub Support approval is not required to generate a support bundle locally.
  • B. Custom GitHub Actions are not used in the support bundle generation process.
  • D. GitHub Apps with read:org permissions are not needed for support bundle generation.

Question 6

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?

  1. Enterprise Managed Users can collaborate across both personal and enterprise repositories.
  2. Personal Accounts are owned by users and can be used for both personal and professional work.
  3. Personal Accounts provide stricter control over repositories and user activity.
  4. Enterprise Managed Users require the organization to manage their own authentication server.
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, offering flexibility in how they are utilized. Enterprise Managed Users, by contrast, are owned and managed by the enterprise organization, limiting collaboration outside the enterprise context. Personal Accounts do not provide stricter control, and Enterprise Managed Users do not require organizations to manage their own authentication servers.

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 less control over activity compared to Enterprise Managed Users, which are centrally managed.
  • D. Enterprise Managed Users do not require organizations to manage their own authentication servers; they work with existing identity providers.

Question 7

Which THREE of the following accurately describe how the SCIM protocol enhances user management in GitHub Enterprise Cloud? (Choose three.)

  1. SCIM synchronizes changes to user attributes from the identity provider to GitHub.
  2. SCIM deactivates GitHub accounts when users are deleted from the identity provider.
  3. SCIM automatically deletes organization repositories when administrators are removed.
  4. SCIM automates user provisioning when new users are added to the identity provider.
  5. SCIM generates authentication tokens for accessing GitHub's REST API.
  6. SCIM configures repository permissions based on user roles within the organization.
Show answer and explanation

Correct answer: A, B, D

A. SCIM synchronizes changes to user attributes from the identity provider to GitHub. B. SCIM deactivates GitHub accounts when users are deleted from the identity provider. D. 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 added to the identity provider, and deactivates GitHub accounts when users are removed from the identity provider. SCIM does not automatically delete repositories, is not involved in generating authentication tokens, and does not configure repository permissions directly.

Why the other options are wrong

  • C. SCIM does not automatically delete organization repositories when administrators are removed.
  • E. SCIM does not generate authentication tokens; this is handled through separate OAuth or token management systems.
  • F. SCIM handles user provisioning and attribute synchronization, not repository permission configuration.

Question 8

When comparing a partner identity provider integration with a non-partner identity management solution for GitHub Enterprise Managed Users, which statement is Correct?

  1. The non-partner identity provider integrations can utilize OIDC for authentication.
  2. The non-partner identity provider integrations require manual configuration of SAML 2.0 details.
  3. The partner identity provider integrations support fewer GitHub-supported authentication methods.
  4. The partner identity provider integrations rely on the partner to support the application on the partner IdP.
Show answer and explanation

Correct answer: B. The non-partner identity provider integrations require manual configuration of SAML 2.0 details.

Non-partner identity provider integrations require manual configuration of SAML 2.0 details, as they lack pre-built integration pathways that partner identity providers offer. Partner integrations are typically pre-configured and supported directly by the partner, reducing manual setup. Non-partner integrations can still support multiple authentication methods, partner integrations support the same or more GitHub authentication methods, and partner support responsibility lies with the partner organization.

Why the other options are wrong

  • A. Non-partner identity providers typically do not support OIDC; manual SAML 2.0 configuration is required.
  • C. Partner identity provider integrations support the same or more authentication methods, not fewer.
  • D. While partners support their integrations, this is not the distinguishing characteristic between partner and non-partner integrations.

Question 9

When comparing Group SCIM to Team Sync for identity management in GitHub Enterprise, which statement is Correct?

  1. Group SCIM requires less initial configuration than Team Sync.
  2. Team Sync supports more identity providers than Group SCIM.
  3. Team Sync provides more automated user deprovisioning than Group SCIM.
  4. Group SCIM enables centralized user and group management through the IdP.
Show answer and explanation

Correct answer: D. Group SCIM enables centralized user and group management through the IdP.

Group SCIM (System for Cross-domain Identity Management) is a standards-based protocol that enables centralized user and group management through an identity provider. It automates provisioning and deprovisioning of users and groups at the enterprise level, allowing the IdP to be the single source of truth for identity management across GitHub Enterprise. This is the primary advantage of SCIM over Team Sync, which requires more manual coordination.

Why the other options are wrong

  • A. Group SCIM actually requires more initial configuration than Team Sync, as it involves setting up SCIM endpoints and synchronization rules.
  • B. Team Sync does not support more identity providers; both solutions work with major IdPs, but SCIM is the more comprehensive standard.
  • C. Group SCIM provides more automated user deprovisioning through the IdP, not Team Sync, which relies on manual team management.

Question 10

Why is a GitHub App preferred over a PAT for machine authentication?

  1. GitHub Apps are required to pass SAML assertions
  2. GitHub Apps have time-limited installation tokens with scoped access
  3. PATs cannot be used in GitHub Actions
  4. PATs support fewer GitHub APIs than Apps
Show answer and explanation

Correct answer: B. GitHub Apps have time-limited installation tokens with scoped access

GitHub Apps generate time-limited installation tokens that automatically expire and can be scoped to specific permissions and repositories. This is superior to Personal Access Tokens (PATs), which are long-lived and represent the user rather than the application. The scoped, time-limited nature of GitHub App tokens provides better security for machine-to-machine authentication and aligns with the principle of least privilege.

Why the other options are wrong

  • A. SAML assertions are handled at the authentication layer and are not a distinguishing factor between GitHub Apps and PATs.
  • C. PATs can be and are used in GitHub Actions; this is not a limitation of PATs.
  • D. Both GitHub Apps and PATs support comprehensive GitHub APIs; this is not a meaningful distinction.

That was 10 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.

Get the full pack