Free GH-100 Exam Braindumps
GitHub Administration Questions 17–24 (page: 4)

Updated On: 9-Apr-2026

When comparing fine-grained Personal Access Tokens (PATs) with classic PATs, which of the following statements is accurate?

  1. Fine-grained PATs automatically renew while classic PATs require manual renewal.
  2. Fine-grained PATs permissions can be scoped to specific repositories.
  3. Classic PATs offer more permission controls than fine-grained PATs.
  4. Classic PATs can be restricted to specific organizations, but fine-grained PATs cannot.

Answer(s): B

Explanation:

Fine-grained personal access tokens let you scope permissions down to individual repositories, whereas classic PATs grant access across every repo the user can reach.



What is the new capability of GitHub's billing dashboard?

  1. Automatically removes unused users from billing
  2. Enables tracking of GitHub Copilot usage by user
  3. Allows self-service plan upgrades
  4. Offers real-time Slack alerts for billing

Answer(s): B

Explanation:

The revamped Billing&Licensing dashboard now includes a dedicated"Copilot" tab that shows per- user seat assignments, usage counts, and estimated costs for your organization's GitHub Copilot licenses, enabling you to track Copilot consumption by individual users.



What is a key characteristic of GitHub Enterprise Server (GHES) compared to GitHub Enterprise Cloud (GHEC)?

  1. GHES is hosted by GitHub and offers automatic scaling, while GHEC requires self-hosting.
  2. GHEC offers data residency options in regions that GHES does not support.
  3. GHES allows enterprises to have complete control over their hosting environment, including data storage and network security policies.
  4. GHES users cannot integrate with external identity providers for authentication.

Answer(s): C

Explanation:

GitHub Enterprise Server is a self-hosted product you install and manage on your own infrastructure - giving you full control over data storage, network security policies, and the underlying environment.



Your organization wants to reduce costs.
Which of the following actions should you take?

  1. Grant all users admin permissions
  2. Remove all outside collaborators
  3. Regularly audit for inactive users
  4. Disable SAML SSO for members

Answer(s): C

Explanation:

Regularly auditing for inactive (dormant) users lets you suspend or remove accounts that aren't consuming seats - freeing up licenses and directly lowering your per-user subscription costs.



How does metered billing work in GitHub Enterprise Cloud with Enterprise Managed Users (EMU)?

  1. Billing is based on number of total users in the enterprise
  2. Billing is based on owners and members of GitHub organizations
  3. Billing is based on total users in the enterprise that are not dormant
  4. Billing is based on the number of users created in Azure AD

Answer(s): A

Explanation:

Billing for GitHub Enterprise Cloud under metered (usage-based) billing is calculated by the total number of Enterprise Managed Users (and other license-consuming accounts) in your enterprise - each EMU consumes a seat and contributes to the monthly bill.



A team member is unable to push to a repository due to a 403-error related to branch protection.
What should the GitHub Enterprise administrator do first?

  1. Remove the user from the team and re-add them
  2. Check the user's permissions and rulesets applied to the branch
  3. Raise a GitHub Support request for permissions issues
  4. Revert the branch to an earlier state

Answer(s): B

Explanation:

The administrator should first review the user's repository role and the branch protection rules applied to that branch. A 403 error on push almost always indicates that the user either lacks the necessary write permissions or is not listed among the actors authorized by the branch protection settings.



Which of the following is true about outside collaborators in a GitHub organization?

  1. They are granted explicit access to specific repositories.
  2. They inherit organization-wide policies, such as SSO requirements.
  3. They have access to all private repositories by default.
  4. They appear in the organization's internal member list.

Answer(s): A

Explanation:

Outside collaborators aren't organization members; instead, they're granted explicit access - at read, write, or admin level - to only the repositories you choose.



Which of the following is a benefit of creating a new GitHub organization?

  1. Automatic inheritance of policies from other organizations.
  2. Reduced administrative overhead.
  3. Clear separation of reggs, projects, teams, billing, and organization-specific policies.
  4. Simplified collaboration across all organizations.

Answer(s): C

Explanation:

Creating a new organization gives you a dedicated container for your shared work, letting you isolate repositories, projects, teams, billing settings, and policy configurations on an organization-by- organization basis.



Viewing page 4 of 10
Viewing questions 25 - 32 out of 65 questions


Post your Comments and Discuss Microsoft GH-100 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!