Microsoft GitHub Administration GH-100 Exam Dumps: Updated Questions & Answers (October 2025)

Enterprise policies and organization policies are independent, with organization policies taking precedence for repositories within the organization.

Enterprise policies configure mandatory settings for organizations.

Enterprise policies apply only to public repositories, while organization policies apply to public, internal, and private repositories.

Enterprise policies can block specific actions, while organization policies can only enable or disable actions entirely.

Contact GitHub Support to remove the secret from all forks and clones of the repository.

Revoke and/or rotate the secret to render it unusable, then assess whether history rewriting is necessary.

Rewrite the repository history using git filter-repo or BFG Repo-Cleaner to remove the secret from all commits.

Delete the repository and create a new one to ensure the secret is no longer accessible.

Outside collaborators for all repositories.

Organization-specific teams with custom policies.

Enterprise-level teams with inherited enterprise policies.

Assigning admin permissions to all team members.

changes in permissions

B promoting users to administrators

pushes to repositories

changes to permissions of a GitHub App

cloning of repositories

EMUs are fully controlled by an IdP and cannot log in with personal credentials

EMUs can only be created using email invites

EMUs are managed in GitHub and use GitHub authentication

EMUs are only available for GitHub Enterprise Server

Allow organization owners to administer the setting at the organization level.

Allow people who have access to private and internal repositories to fork these repositories.

Allow specific people or teams to fork private and internal repositories.

Disallow repository owners from administering the setting at the repository level.

Disallow forking of private and internal repositories.

The non-partner identity provider integrations can utilize OIDC for authentication.

The non-partner identity provider integrations require manual configuration of SAML 2.0 details.

The partner identity provider integrations support fewer GitHub-supported authentication methods.

The partner identity provider integrations rely on the partner to support the application on the partner IdP.

Personal Access Tokens (PATs)

GitHub App Installation Access Tokens

Device Tokens

OAuth tokens

Group SCIM requires less initial configuration than Team Sync.

Team Sync supports more identity providers than Group SCIM.

Team Syncprovides more automated user deprovisioningthan Group SCIM.

Group SCIM enablescentralized user and group management through the IdP.

Automatic inheritance of policies from other organizations.

Reduced administrative overhead.

Clear separation of reggs, projects, teams, billing, and organization-specific policies.

Simplified collaboration across all organizations.