[Dec-2025] Dumps Practice Exam Questions Study Guide for the GH-100 Exam
GH-100 Dumps with Practice Exam Questions Answers
Microsoft GH-100 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 10
Which GitHub feature is responsible for tracking dependencies and known vulnerabilities in those dependencies from an advisory database?
- A. Security Policy
- B. Repository Insights
- C. CodeQL
- D. Dependency Graph
Answer: D
Explanation:
The Dependency Graph continuously analyzes your repository's manifest and lock files to build an inventory of direct and transitive dependencies and flags any that match entries in the GitHub Advisory Database, surfacing known vulnerabilities.
NEW QUESTION # 11
What benefit does GitHub Advanced Security provide?
- A. helps developers improve and maintain the security and quality of code
- B. helps organization administrators analyze and configure permissions to the least privilege required
- C. helps enterprise administrators improve and maintain network security for their GitHub Enterprise Server instances
- D. helps organization administrators manage security tokens
Answer: A
Explanation:
GitHub Advanced Security equips developers with built-in code scanning (CodeQL), secret scanning, dependency review, and other AppSec tools - helping them find, fix, and prevent security vulnerabilities while maintaining code quality.
NEW QUESTION # 12
An organization wants to share a single API key required for their Actions workflows. They need to restrict its use to only a subset of repositories. Where should they configure the secrets to minimize maintenance?
- A. Organization secrets
- B. Environment secrets
- C. Development environment secrets
- D. Repository secrets
Answer: A
Explanation:
By defining the API key as an organization secret, you centralize management and can grant access only to the subset of repositories you choose - eliminating per-repo duplication while enforcing the desired scope.
NEW QUESTION # 13
Which product's usage is not included in GitHub Enterprise Cloud's monthly metered billing report?
- A. GitHub Actions minutes
- B. GitHub Packages storage
- C. GitHub Discussions engagement
- D. Git LFS bandwidth
Answer: C
Explanation:
GitHubDiscussions engagement isn't a metered product and doesn't appear in the "Product billing" list, so its usage isn't included in the monthly metered billing report.
NEW QUESTION # 14
Which Git operation is not included in the Git activity audit log?
- A. Delete branch
- B. Push
- C. Fetch
- D. Clone
Answer: A
Explanation:
Delete branch operations aren't tracked as Git-activity events; the Git activity audit log only records Git events such as clone, fetch (pull), and push.
NEW QUESTION # 15
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?
- A. Revert the branch to an earlier state
- B. Remove the user from the team and re-add them
- C. Check the user's permissions and rulesets applied to the branch
- D. Raise a GitHub Support request for permissions issues
Answer: C
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.
NEW QUESTION # 16
How does GitHub handle secrets found via secret scanning in a public repository?
- A. It alerts the service provider (e.g., AWS, Stripe).
- B. It notifies the admin via webhook.
- C. It immediately blocks the commit to protect the secret.
- D. It deletes the secret from the repository automatically.
Answer: A
Explanation:
When secret scanning detects a supported credential in a public repository, GitHub notifies the issuing service provider so they can revoke or rotate the exposed secret.
NEW QUESTION # 17
Why would a GitHub App be favored over a machine account for automation tasks?
- A. 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.
- B. GitHub Apps are limited to a single repository.
- C. Machine accounts are easier to audit than GitHub Apps.
- D. Machine accounts are required for webhook delivery.
Answer: A
Explanation:
GitHub Apps authenticate with short-lived installation tokens scoped to fine-grained permissions and, when owned by a GitHub Enterprise Cloud organization, enjoy a higher rate limit (15,000 requests/hour) compared to a machine account's personal access token.
NEW QUESTION # 18
How does metered billing work in GitHub Enterprise Cloud with Enterprise Managed Users (EMU)?
- A. Billing is based on owners and members of GitHub organizations
- B. Billing is based on the number of users created in Azure AD
- C. Billing is based on total users in the enterprise that are not dormant
- D. Billing is based on number of total users in the enterprise
Answer: D
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.
NEW QUESTION # 19
You have subscribed to GitHub Premium Support, and you need to submit a support ticket. GitHub Premium Support can help you with:
- A. integrating with third-party applications.
- B. writing scripts.
- C. setting up hardware.
- D. installing GitHub Enterprise Server.
Answer: D
Explanation:
GitHub Premium Support includes assistance with installing and using GitHub Enterprise Server, ensuring your deployment is configured correctly and any installation issues are resolved.
NEW QUESTION # 20
Your organization wants to reduce costs. Which of the following actions should you take?
- A. Remove all outside collaborators
- B. Disable SAML SSO for members
- C. Regularly audit for inactive users
- D. Grant all users admin permissions
Answer: 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.
NEW QUESTION # 21
Why is a GitHub App preferred over a PAT for machine authentication?
- A. PATs support fewer GitHub APIs than Apps
- B. GitHub Apps have time-limited installation tokens with scoped access
- C. GitHub Apps are required to pass SAML assertions
- D. PATs cannot be used in GitHub Actions
Answer: B
Explanation:
GitHub Apps issue short-lived installation tokens that you scope to only the permissions and repositories your automation needs, reducing blast radius and automatically rotating credentials.
NEW QUESTION # 22
When comparing Group SCIM to Team Sync for identity management in GitHub Enterprise, which statement is Correct?
- A. Team Sync provides more automated user deprovisioning than Group SCIM.
- B. Group SCIM enables centralized user and group management through the IdP.
- C. Group SCIM requires less initial configuration than Team Sync.
- D. Team Sync supports more identity providers than Group SCIM.
Answer: B
Explanation:
GroupSCIM lets you manage both user accounts and group memberships centrally in your identity provider - automatically provisioning, updating, and deprovisioning users and groups in GitHub - whereas TeamSync only mirrors IdP group membership into existing GitHub teams.
NEW QUESTION # 23
In a GitHub repository using Dependabot, which of the following best describes the purpose of the .github/dependabot.yml file?
- A. It encrypts dependency versions before storing them in the repo.
- B. It enables GitHub to scan for secrets in dependency files.
- C. It configures scheduling, package ecosystems, and target directories for update checks.
- D. It lists commit SHAs to exclude from automatic pull requests.
Answer: C
Explanation:
The .github/dependabot.yml file defines Dependabot's package-ecosystem, the directories to inspect, and the update schedule (daily/weekly/monthly), controlling when and where Dependabot checks for new versions.
NEW QUESTION # 24
You are an administrator and need to enforce a policy on forking private and internal repositories. Which options are available for configuring the policy at the enterprise level? (Each answer presents a complete solution. Choose three.)
- A. Allow organization owners to administer the setting at the organization level.
- B. Allow specific people or teams to fork private and internal repositories.
- C. Disallow repository owners from administering the setting at the repository level.
- D. Allow people who have access to private and internal repositories to fork these repositories.
- E. Disallow forking of private and internal repositories.
Answer: A,D,E
Explanation:
You can configure the enterprise policy toallow organization owners to administer the forking setting at the organization level, giving them control over how repos fork within their orgs.
You can choose toallow any user who already has access to a private or internal repo to fork it.
You can also set the policy tonever allow forkingof private or internal repositories across all organizations.
NEW QUESTION # 25
......
Free GitHub Administrator GH-100 Exam Question: https://prep4sure.real4dumps.com/GH-100-prep4sure-exam.html
