GH-100 試験問題と解答 - 模擬練習 - 練習問題・模擬試験

Question No : 1
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

正解:
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.

Question No : 2
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.

正解:
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 No : 3
What is the new capability of GitHub's billing dashboard?

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

正解:
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.

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

A.Fine-grained PATs automatically renew while classic PATs require manual renewal.
B.Fine-grained PATs permissions can be scoped to specific repositories.
C.Classic PATs offer more permission controls than fine-grained PATs.
D.Classic PATs can be restricted to specific organizations, but fine-grained PATs cannot.

正解:
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.

Question No : 5
Why would a GitHub App be favored over a machine account for automation tasks?

A.Machine accounts are required for webhook delivery.
B.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.
C.GitHub Apps are limited to a single repository.
D.Machine accounts are easier to audit than GitHub Apps.

正解:
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.

Question No : 6
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.

正解:
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.

Question No : 7
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

正解:
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 No : 8
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

正解:
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 No : 9
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 Id
D.Enterprise-wide SAML SSO ensures users authenticate through the same IdP across all organizations.

正解:
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.

Question No : 10
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 A
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.

正解:
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.

Question No : 11
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

正解:
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.

Question No : 12
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 SCI
C.Team Sync provides more automated user deprovisioning than Group SCI
D.Group SCIM enables centralized user and group management through the Id

正解:
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 No : 13
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 Id

正解:
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.

Question No : 14
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 AP
F.SCIM configures repository permissions based on user roles within the organization.

正解:
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.

Question No : 15
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.

正解:
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.

Microsoft GH-100 問題練習