microsoft gh-100 practice test

GitHub Administration

Last exam update: Nov 18 ,2025
Page 1 out of 5. Viewing questions 1-15 out of 65

Question 1

You have subscribed to GitHub Premium Support, and you need to submit a support ticket. GitHub
Premium Support can help you with:

  • A. writing scripts.
  • B. installing GitHub Enterprise Server.
  • C. setting up hardware.
  • D. integrating with third-party applications.
Mark Question:
Answer:

B


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.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 2

You need to contact GitHub Premium Support. What are valid reasons for submitting a support
ticket? (Each answer presents a complete solution. Choose two.)

  • A. license renewal
  • B. hardware setup issues or errors
  • C. business impact from security issues within your organization
  • D. outages on GitHub.com affecting core Git functionality
Mark Question:
Answer:

C, D


Explanation:
Business-impact security issues (for example, a critical vulnerability affecting your organization) are
classified as High-priority tickets and are covered under your Premium Support SLA.
Outages on GitHub.com that disrupt core Git or web application functionality trigger Urgent-priority
responses under Premium Support’s SLA.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 3

Which of the following is a key benefit of using GitHub Marketplace Apps in an enterprise?

  • A. They guarantee no downtime during enterprise GitHub maintenance windows
  • B. They often include integrations with external services, reducing the need for custom code
  • C. Apps eliminate the need for GitHub Actions entirely
  • D. All apps come pre-approved by GitHub's internal security team
Mark Question:
Answer:

B


Explanation:
GitHub Marketplace Apps come with built-in integrations to external services - so you can plug in
things like CI servers, code-quality scanners, or deployment tools without writing and maintaining
custom connectors.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 4

You need to create a support bundle for your GitHub Enterprise Server instance with the hostname
ghe.avocado.corp. What command should you use to create a support bundle?

  • A. ssh -p 122 [email protected] -- 'ghe-support-bundle -o' > support-bundle.tgz
  • B. ssh -p 122 [email protected] – 'ghe-diagnostics' > support-bundle.tgz
  • C. curl -u admin https://ghe.avocado.corp/diagnostics/support-bundle.tgz -o
  • D. ssh -p 122 [email protected] -- 'ghe-config generate-support-bundle' > support- bundle.tgz
Mark Question:
Answer:

A


Explanation:
Run the ghe-support-bundle command over SSH on your appliance and redirect its output to a file.
For example:
ssh -p 122 [email protected] -- 'ghe-support-bundle -o' > support-bundle.tgz
This invokes the built-in support-bundle utility on your GitHub Enterprise Server instance and
captures the resulting archive locally.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 5

What do you need to successfully generate a support bundle on a GitHub Enterprise Server?

  • A. Approval from GitHub Support
  • B. A custom GitHub Action in the root repo
  • C. Administrator SSH access to the appliance
  • D. A GitHub App with read:org permissions
Mark Question:
Answer:

C


Explanation:
You must have administrator-level SSH access to the GitHub Enterprise Server appliance so you can
run the ghe-support-bundle command over SSH and capture the bundle locally.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 6

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.
Mark Question:
Answer:

B


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.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 7

Which THREE of the following accurately describe how the SCIM protocol enhances user
management in GitHub Enterprise Cloud? (Choose three.)

  • A. SCIM synchronizes changes to user attributes from the identity provider to GitHub.
  • B. SCIM deactivates GitHub accounts when users are deleted from the identity provider.
  • C. SCIM automatically deletes organization repositories when administrators are removed.
  • D. SCIM automates user provisioning when new users are added to the identity provider.
  • E. SCIM generates authentication tokens for accessing GitHub's REST API.
  • F. SCIM configures repository permissions based on user roles within the organization.
Mark Question:
Answer:

A, B


Explanation:
SCIM automatically updates a user’s account on GitHub whenever their profile attributes change in
the identity provider.
When a user is removed or deactivated in the IdP, SCIM deactivates (soft-deprovisions) their GitHub
account and disables access.
SCIM provisions new GitHub Enterprise Cloud accounts automatically when users are added in the
identity provider.

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
F
50%
Discussions
vote your answer:
A
B
C
D
E
F
0 / 1000

Question 8

When comparing a partner identity provider integration with a non-partner identity management
solution for GitHub Enterprise Managed Users, which statement is Correct?

  • A. The non-partner identity provider integrations can utilize OIDC for authentication.
  • B. The non-partner identity provider integrations require manual configuration of SAML 2.0 details.
  • C. The partner identity provider integrations support fewer GitHub-supported authentication methods.
  • D. The partner identity provider integrations rely on the partner to support the application on the partner IdP.
Mark Question:
Answer:

B


Explanation:
Non-partner identity provider integrations require you to enter SAML 2.0 configuration details by
hand - such as the Sign-on URL, Issuer, and X.509 certificate - whereas partner IdPs supply a pre-
configured application integration.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 9

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 Sync provides more automated user deprovisioning than Group SCIM.
  • D. Group SCIM enables centralized user and group management through the IdP.
Mark Question:
Answer:

D


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.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 10

Why is a GitHub App preferred over a PAT for machine authentication?

  • A. GitHub Apps are required to pass SAML assertions
  • B. GitHub Apps have time-limited installation tokens with scoped access
  • C. PATs cannot be used in GitHub Actions
  • D. PATs support fewer GitHub APIs than Apps
Mark Question:
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.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 11

You are planning GitHub account management for a healthcare organization with strict compliance
requirements. Which THREE of the following statements accurately describe GitHub Enterprise
Managed Users (EMU) accounts? (Choose three.)

  • A. EMU accounts can be used for both personal and enterprise repositories.
  • B. EMU accounts are managed through an identity provider such as Azure AD.
  • C. EMU accounts allow users to create and manage their own credentials.
  • D. EMU accounts restrict users to enterprise-related activities only
  • E. EMU accounts are created and managed by individual users.
  • F. EMU accounts are owned by the organization and cannot be unlinked.
Mark Question:
Answer:

B, D, F


Explanation:
Enterprise Managed User accounts are provisioned and authenticated exclusively through your
identity provider (for example, Azure AD), so the IdP handles their creation, attribute updates, and
deprovisioning.
Managed user accounts cannot create public content or interact with repositories outside your
enterprise; they’re confined to private and internal repos within the enterprise.
EMU accounts are owned and controlled by the enterprise (via the IdP) and cannot be converted into
or unlinked as personal accounts outside that enterprise.

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
F
50%
Discussions
vote your answer:
A
B
C
D
E
F
0 / 1000

Question 12

A GitHub Enterprise administrator is planning to implement SAML SSO across their company. Which
of the following correctly distinguishes enterprise-wide SAML SSO from organization-level SAML
SSO?

  • A. Enterprise-wide SAML SSO requires less initial administrative overhead than organization-level implementation.
  • B. Enterprise-wide SAML SSO allows different organizations to use different authentication methods.
  • C. Enterprise-wide SAML SSO immediately removes users who fail to authenticate via the IdP.
  • D. Enterprise-wide SAML SSO ensures users authenticate through the same IdP across all organizations.
Mark Question:
Answer:

D


Explanation:
Enterprise-wide SAML SSO enforces a single IdP across all member organizations—its configuration
overrides any per-organization SAML settings, so everyone must authenticate through the same
provider.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 13

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
Mark Question:
Answer:

A


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.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 14

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
Mark Question:
Answer:

D


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.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 15

What makes GitHub Apps a more secure choice for automation over OAuth Apps?

  • A. GitHub Apps always require two-factor authentication.
  • B. GitHub Apps can only be installed by organization owners.
  • C. GitHub Apps are limited to read-only access and cannot write to repositories.
  • D. GitHub Apps authenticate as an app with fine-grained permissions, not as a user.
Mark Question:
Answer:

D


Explanation:
GitHub Apps authenticate as themselves with fine-grained, installation-scoped permissions and
short-lived tokens - rather than inheriting a user’s broad OAuth scopes - minimizing blast radius and
aligning with least-privilege principles.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000
To page 2