GH-100 Sample Questions Answers

writing scripts.

installing GitHub Enterprise Server.

setting up hardware.

integrating with third-party applications.

Enterprise Managed Users can collaborate across both personal and enterprise repositories.

Personal Accounts are owned by users and can be used for both personal and professional work.

Personal Accounts provide stricter control over repositories and user activity.

Enterprise Managed Users require the organization to manage their own authentication server.

Allow organization owners to administer the setting at the organization level.

Allow people who have access to private and internal repositories to fork these repositories.

Allow specific people or teams to fork private and internal repositories.

Disallow repository owners from administering the setting at the repository level.

Disallow forking of private and internal repositories.

It creates a pull request to update the direct dependency to a version that resolves the vulnerability.

It opens a pull request to update the affected package directly, regardless of version compatibility.

It automatically removes the package from the repository.

It sends an email to the repository owner but does not alter code.

It waits for manual triage of all CVEs.

It uses the dependency graph and Dependabot alerts to open PRs for patched versions.

It reads the GitHub Issues and automatically suggests fixes.

It compares your codebase to the GitHub Trending list.

Number of workflows defined in .github/workflows/

Number of contributors to the repository Explanation:Incorrect. Contributor count does not impact billing for Actions

Total number of repositories using Actions

Operating system used in the runner environment

Only organization-level rulesets are enforced over repository-level ones

All applicable rulesets will be evaluated, and their combined rules enforced

Only the most recently created ruleset will be enforced

Rulesets will override each other, leading to unpredictable behavior

GitHub Apps always require two-factor authentication.

GitHub Apps can only be installed by organization owners.

GitHub Apps are limited to read-only access and cannot write to repositories.

GitHub Apps authenticate as an appwithfine-grained permissions, not as a user.

Remove the user from the team and re-add them

Check the user's permissions and rulesets applied to the branch

Raise a GitHub Support request for permissions issues

Revert the branch to an earlier state

GHES is hosted by GitHub and offers automatic scaling, while GHEC requires self-hosting.

GHEC offers data residency options in regions that GHES does not support.

GHES allows enterprises to have complete control over their hosting environment, including data storage and network security policies.

GHES users cannot integrate with external identity providers for authentication.

Automatically removes unused users from billing

Enables tracking of GitHub Copilot usage byuser

Allows self-service plan upgrades

Offers real-time Slack alerts for billing

They guarantee no downtime during enterprise GitHub maintenance windows

They often include integrations with external services, reducing the need for custom code

Apps eliminate the need for GitHub Actions entirely

All apps come pre-approved by GitHub's internal security team

Group SCIM requires less initial configuration than Team Sync.

Team Sync supports more identity providers than Group SCIM.

Team Syncprovides more automated user deprovisioningthan Group SCIM.

Group SCIM enablescentralized user and group management through the IdP.

Allows custom pattern definitions for internal secret formats.

Disables any code that contains a secret.

Rewrites history to remove secrets.

Revokes GitHub access tokens automatically.

It alerts the service provider (e.g., AWS, Stripe).

It immediately blocks the commit to protect the secret.

It deletes the secret from the repository automatically.

It notifies the admin via webhook.

Fine-grained PATs automatically renew while classic PATs require manual renewal.

Fine-grained PATs permissions can be scoped to specific repositories.

Classic PATs offer more permission controls than fine-grained PATs.

Classic PATs can be restricted to specific organizations, but fine-grained PATs cannot.