Microsoft GH-100 GitHub Administration Exam Practice Test

Designingyour application to work within GitHub's rate limits

Using multiple tokens to bypass limits

Caching all API responses permanently

Ignoring secondary rate limits

helps organization administrators analyze and configure permissions to the least privilege required

helps developers improve and maintain the security and quality of code

helps enterprise administrators improve and maintain network security for their GitHub Enterprise Server instances

helps organization administrators manage security tokens

They guarantee no downtime during enterprise GitHub maintenance windows

They often include integrations with external services, reducing the need for custom code

Apps eliminate the need for GitHub Actions entirely

All apps come pre-approved by GitHub's internal security team

Execute scripts before and after a job

Dynamic scaling

Automatic updates to the operating system

GPU support

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.

Suits environments where all users need write access.

Improves collaboration by allowing users to modify content directly.

Increases efficiency in content creation and updates.

Enhances security by minimizing unintended modifications.

The user will automatically have the same role across all organizations.

The user's repository access and/or team membership needs to be managed separately for each organization.

The user will need to authorize credentials separately for each SAML-enabled organization.

The user will have different permission levels in each organization.

The user's profile information becomes private to non-organization members.

The user's personal repositories will become accessible to all organizations.

Remove the user from the team and re-add them

Check the user's permissions and rulesets applied to the branch

Raise a GitHub Support request for permissions issues

Revert the branch to an earlier state

Delete branch

Fetch

Push

Clone

To communicate corporate security and compliance policies for end users on a private repository.

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.

To prevent anyone from pushing to the repository without approval.

To define which open source packages are permitted for use as part of that repository.

GHES is hosted by GitHub and offers automatic scaling, while GHEC requires self-hosting.

GHEC offers data residency options in regions that GHES does not support.

GHES allows enterprises to have complete control over their hosting environment, including data storage and network security policies.

GHES users cannot integrate with external identity providers for authentication.

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".

It alerts the service provider (e.g., AWS, Stripe).

It immediately blocks the commit to protect the secret.

It deletes the secret from the repository automatically.

It notifies the admin via webhook.

GitHub provides configurable controls such as an audit log, SAML authentication, and enterprise rulesets.

GitHub disables all external collaboration features.

GitHub only allows those with repository owner (admin) permissions to write changes to repositories.

GitHub automatically encrypts user passwords in plaintext for quick access.

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 waits for manual triage of all CVEs.

It uses the dependency graph and Dependabot alerts to open PRs for patched versions.

It reads the GitHub Issues and automatically suggests fixes.

It compares your codebase to the GitHub Trending list.

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.

Revoke any exposed credentials immediately

Force push a commit removing the data

Open an issue to inform users

Delete the repository