GH-100
Free GH-100 practice questions
10 questions from our GH-100 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Manage GitHub identities and access
A company wants every developer account to be created, named and deactivated by its identity provider, and developers must not be able to create public repositories or contribute to repositories outside the company. Which GitHub Enterprise Cloud model meets these requirements?
- APersonal accounts with organization-level SAML SSO, SCIM invitations and required 2FA
- BPersonal accounts with team synchronization linking IdP groups to teams
- CPersonal accounts with SAML single sign-on enforced at the enterprise level
- DEnterprise Managed Users, with accounts provisioned from the IdP through SCIM Correct answer
Answer and explanation: Enterprise Managed Users gives the IdP full control of account lifecycle and usernames, and managed users cannot create public content or collaborate outside the enterprise. SAML SSO on personal accounts only gates access to enterprise resources; the developer still owns the account and can work anywhere on GitHub.com. Team synchronization manages team membership, not account creation, and required 2FA adds an authentication factor without restricting where the account contributes.
Question 2 of 10, Manage GitHub identities and access
An enterprise on GitHub Enterprise Cloud with personal accounts has twelve organizations, and each organization owner has configured SAML differently. Security wants one IdP configuration to apply to all current and future organizations. What should the enterprise owner do?
- AConfigure SAML SSO once on the enterprise account, which supersedes organization-level SAML settings Correct answer
- BEnable SCIM provisioning in each organization so the IdP controls all twelve organizations centrally
- CAsk each organization owner to point their SAML settings at the same IdP application and certificate
- DRequire two-factor authentication at the enterprise level so that every organization inherits the policy
Answer and explanation: Enterprise-level SAML SSO applies to every organization in the enterprise, including ones created later, and replaces any organization-level SAML configuration. Repointing each organization at the same IdP still leaves twelve separate configurations that can drift. SCIM depends on SAML being set up and handles provisioning, not authentication, and a 2FA requirement does not centralize identity provider configuration.
Question 3 of 10, Administer GitHub Enterprise environment
A GitHub Enterprise Server administrator opens a ticket about intermittent failures, and GitHub Support asks for logs from the appliance. Which command sends the required data directly to GitHub Support from the instance?
- Aghe-config-apply -u
- Bghe-diagnostics -u
- Cghe-repl-status -u
- Dghe-support-bundle -u Correct answer
Answer and explanation: ghe-support-bundle collects the logs and configuration that Support needs, and the upload option sends it straight to GitHub Enterprise Support. ghe-diagnostics produces a smaller diagnostics summary rather than the log bundle, ghe-repl-status reports high availability replication health, and ghe-config-apply applies configuration changes rather than collecting data.
Question 4 of 10, Administer GitHub Enterprise environment
A company standard requires that production releases come only from a release branch, after QA approval, with a tag created by automation. Which combination enforces this?
- AA RELEASES.md file describing the process and a weekly review of new tags by the release manager
- BIncrease the CPU and memory of the European appliance so that it processes clones faster
- CAdd a geo-replication replica in Asia so that Git reads are served locally Correct answer
- DMaking all developers outside collaborators so only owners can create release tags manually
Answer and explanation: Rulesets restrict who can push to release branches and create tags, and an environment with required reviewers gates the production deployment on QA approval. Documentation and reviews after the fact do not enforce anything, checks on main do not cover releases, and converting developers to collaborators is disruptive and misdirected.
Question 5 of 10, Implement secure software development and compliance
A developer needs a token for a script that reads issues from three repositories in one organization. Security wants the token to be limited to those repositories and to read-only issue access, with an expiration date. Which token should be used?
- AThe GITHUB_TOKEN of a workflow run, copied into the script's configuration file
- BA fine-grained PAT limited to the three repositories with read-only Issues permission Correct answer
- CAn SSH deploy key added to each of the three repositories with write access disabled for safety
- DA personal access token (classic) with the repo scope and an expiration date of 30 days
Answer and explanation: Fine-grained PATs are restricted to one resource owner, chosen repositories and specific permissions such as read-only Issues, and they have an expiration. A classic token with repo scope grants broad access to all repositories the user can reach. Deploy keys provide Git access rather than issue API access, and a GITHUB_TOKEN expires when its job ends and must not be copied out.
Question 6 of 10, Implement secure software development and compliance
Compliance requires that GitHub Enterprise Cloud audit events be retained for seven years in the company's SIEM. Which approach meets this with the LEAST ongoing effort?
- ARely on the audit log in the enterprise settings, which retains events for as long as needed
- BStream the enterprise audit log to a supported destination such as Splunk or Azure Event Hubs Correct answer
- CExport the enterprise audit log as JSON every month and upload the files to the SIEM manually
- DWrite a scheduled workflow that queries the audit log API every five minutes and forwards results
Answer and explanation: Audit log streaming continuously sends audit and Git events to destinations such as Splunk, Azure Event Hubs, Azure Blob Storage, Amazon S3, Google Cloud Storage or Datadog, where retention is controlled by the customer. Manual exports and polling workflows add effort and risk gaps. The built-in audit log has a limited retention period, so it cannot satisfy a seven-year requirement on its own.
Question 7 of 10, Implement secure software development and compliance
A security lead wants to enable Dependabot alerts, secret scanning with push protection and CodeQL default setup across hundreds of repositories, and have new repositories receive the same settings automatically. What is the MOST efficient approach?
- AApply an organization security configuration to all repositories and set it as the default for new repositories Correct answer
- BUse a scheduled workflow that calls the REST API to toggle each feature on every repository once per day
- CAdd a dependabot.yml file and a CodeQL workflow file to every repository through an automated pull request
- DAsk repository admins to enable the features from each repository's settings and track progress in a spreadsheet
Answer and explanation: Security configurations group security settings, can be applied to many repositories at once, and can be set as the default for new repositories. A scheduled API script and manual enablement add work and drift. A dependabot.yml configures version updates rather than alerts, and committing workflow files sets up advanced CodeQL rather than default setup and does not cover secret scanning.
Question 8 of 10, Manage GitHub Actions
An enterprise wants workflows to use only actions created by GitHub, actions from verified Marketplace creators, and actions in its own enterprise repositories. Where should this be enforced?
- AA required reusable workflow that scans each job for actions from unapproved publishers
- BA ruleset on every repository that blocks commits to workflow files referencing unapproved actions
- CAn enterprise Actions policy allowing enterprise actions plus selected non-enterprise actions Correct answer
- DThe dependency review action, configured to fail when a workflow adds a new action
Answer and explanation: The enterprise Actions policy can permit enterprise actions plus actions created by GitHub and verified creators, and it is enforced when workflows run. A ruleset that inspects workflow contents, a scanning workflow and dependency review are indirect checks that can be bypassed or produce noise, instead of controlling which actions can execute.
Question 9 of 10, Manage GitHub Actions
An enterprise wants to stop repository admins from registering their own self-hosted runners, so that runners are managed only at organization or enterprise level. What should be configured?
- AA ruleset that blocks commits containing self-hosted runner configuration scripts
- BAn IP allow list that blocks connections from unregistered runner hosts
- CAn organization secret that stores the only valid runner registration token
- DThe enterprise Actions policy disabling repository-level self-hosted runners Correct answer
Answer and explanation: An enterprise policy can disable repository-level self-hosted runners across organizations, so only organization or enterprise admins manage runners. Rulesets do not see runner registration, IP allow lists do not distinguish runner registration level, and registration tokens are generated on demand rather than stored as a single secret.
Question 10 of 10, Monitor and optimize GitHub usage
Developers report that GitHub Copilot suggestions do not appear in their IDEs only when connected to the corporate network. Other GitHub features work. Who should resolve this, and how?
- AGitHub Support, by allow-listing the company's IP ranges for Copilot on GitHub's side
- BEach developer, by turning off two-factor authentication on their GitHub account
- CThe enterprise owner, by switching the enterprise to Enterprise Managed Users
- DThe company's administrators, by allowing Copilot endpoints through the proxy Correct answer
Answer and explanation: A failure only on the corporate network points to network controls, so administrators should allow the required Copilot endpoints and configure proxy settings. GitHub does not allow-list customer networks for Copilot, disabling 2FA is unrelated and unsafe, and changing account model does not affect network access.