Pass the Microsoft GitHub Administrator GH-100 Questions and answers with ValidTests

Enterprise-wide SAML SSO requires less initial administrative overhead than organization-level implementation.

Enterprise-wide SAML SSO allows different organizations to use different authentication methods.

Enterprise-wide SAML SSO immediately removes users who fail to authenticate via the IdP.

Enterprise-wide SAML SSO ensures users authenticate through the same IdP across all organizations.

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.

SCIM synchronizes changes to user attributes from the identity provider to GitHub.

SCIM deactivates GitHub accounts when users are deleted from the identity provider.

SCIM automatically deletes organization repositories when administrators are removed.

SCIM automates user provisioning when new users are added to the identity provider.

SCIM generates authentication tokens for accessing GitHub's REST API.

SCIM configures repository permissions based on user roles within the organization.

It configures scheduling, package ecosystems, and target directories for update checks.

It lists commit SHAs to exclude from automatic pull requests.

It enables GitHub to scan for secrets in dependency files.

It encrypts dependency versions before storing them in the repo.

Machine accounts are required for webhook delivery.

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.

GitHub Apps are limited to a single repository.

Machine accounts are easier to audit than GitHub Apps.

Each API action made with the token generates a separate audit log entry

Only the first repository accessed is recorded

GitHub creates a ZIP archive of all token activity

The audit log stores only the token name and not its actions

Allows custom pattern definitions for internal secret formats.

Disables any code that contains a secret.

Rewrites history to remove secrets.

Revokes GitHub access tokens automatically.

Disabling the audit log stream

Setting an infrequent sync schedule to reduce performance impact

Allowing manual updates to team memberships

Clearly define how identity provider groups will align with GitHub teams and roles

Use GitHub's meta API to configure access.

Add a label to the runner group.

Configure repository access in the runner group settings.

Configure the Actions Policies to "Only selected repositories".