Microsoft GH-100 Online Practice Questions and Exam Preparation

Microsoft GH-100 Online Questions & Answers

• Question 1:

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

  A. Group SCIM requires less initial configuration than Team Sync.
  B. Team Sync supports more identity providers than Group SCIM.
  C. Team Syncprovides more automated user deprovisioningthan Group SCIM.
  D. Group SCIM enablescentralized user and group management through the IdP.
  D. Group SCIM enablescentralized user and group management through the IdP.

  ---

  Explanation

  Group SCIM 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 Team Sync only mirrors IdP group membership into existing GitHub teams.

• Question 2:

  What distinguishes Enterprise Managed Users (EMUs) from standard GitHub accounts?

  A. EMUs are fully controlled by an IdP and cannot log in with personal credentials
  B. EMUs can only be created using email invites
  C. EMUs are managed in GitHub and use GitHub authentication
  D. EMUs are only available for GitHub Enterprise Server
  A. EMUs are fully controlled by an IdP and cannot log in with personal credentials

  ---

  Explanation

  EMU accounts are provisioned and authenticated exclusively through your identity provider - users sign in via the IdP and cannot use or manage GitHub-native credentials.

• Question 3:

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

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

  ---

  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.

• Question 4:

  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?

  A. Enterprise Managed Users can collaborate across both personal and enterprise repositories.
  B. Personal Accounts are owned by users and can be used for both personal and professional work.
  C. Personal Accounts provide stricter control over repositories and user activity.
  D. Enterprise Managed Users require the organization to manage their own authentication server.
  B. Personal Accounts are owned by users and can be used for both personal and professional work.

  ---

  Explanation

  Personal Accounts are owned and controlled by individual users and can serve both their personal projects and professional work, whereas Enterprise Managed Users exist solely within the enterprise context and cannot be used for personal repositories.

• Question 5:

  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. Remove the user from the team and re-add them
  B. Check the user's permissions and rulesets applied to the branch
  C. Raise a GitHub Support request for permissions issues
  D. Revert the branch to an earlier state
  B. Check the user's permissions and rulesets applied to the branch

  ---

  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.

• Question 6:

  Your organization is implementing team synchronization. Which of the following should you prioritize during the setup process?

  A. Disabling the audit log stream
  B. Setting an infrequent sync schedule to reduce performance impact
  C. Allowing manual updates to team memberships
  D. Clearly define how identity provider groups will align with GitHub teams and roles
  D. Clearly define how identity provider groups will align with GitHub teams and roles

  ---

  Explanation

  Before you enable team synchronization, you should clearly define how groups in your identity provider will map to GitHub teams and roles - ensuring that when the sync runs, users land in the correct teams with the right permissions.

• Question 7:

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

  A. Automatically removes unused users from billing
  B. Enables tracking of GitHub Copilot usage byuser
  C. Allows self-service plan upgrades
  D. Offers real-time Slack alerts for billing
  B. Enables tracking of GitHub Copilot usage byuser

  ---

  Explanation

  The revamped Billing and 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.

• Question 8:

  Your enterprise has multiple organizations, and you want to ensure consistent security policies across all teams. Which feature should you use?

  A. Outside collaborators for all repositories.
  B. Organization-specific teams with custom policies.
  C. Enterprise-level teams with inherited enterprise policies.
  D. Assigning admin permissions to all team members.
  C. Enterprise-level teams with inherited enterprise policies.

  ---

  Explanation

  By using enterprise-level teams with inherited enterprise policies, you can group members across all your organizations and enforce the same security settings globally - ensuring every team abides by the enterprise's mandatory policies.

• Question 9:

  Why would someone choose to configure a security policy?

  A. To communicate corporate security and compliance policies for end users on a private repository.
  B. To provide information on an open source repository for open source collaborators and researchers that may need to report and disclose sensitive security findings to maintainers securely.
  C. To prevent anyone from pushing to the repository without approval.
  D. To define which open source packages are permitted for use as part of that repository.
  B. To provide information on an open source repository for open source collaborators and researchers that may need to report and disclose sensitive security findings to maintainers securely.

  ---

  Explanation

  A security policy (the SECURITY.md file) lets maintainers of an open source repository provide clear, private instructions for collaborators and external researchers on how to report and disclose security vulnerabilities responsibly.

• Question 10:

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

  A. Grant all users admin permissions
  B. Remove all outside collaborators
  C. Regularly audit for inactive users
  D. Disable SAML SSO for members
  C. Regularly audit for inactive users

  ---

  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.