GH-100 Practice Exam Questions with Answers GitHub Administration Certification

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.

Grant all users admin permissions

Remove all outside collaborators

Regularly audit for inactive users

Disable SAML SSO for members

GitHub Pages Settings.

GitHub Actions Logs.

Repository Settings > Manage Access.

Branch Protection Rules.

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

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.

Use environment variables to pass data directly to the reusable workflow.

Define inputs in the reusable workflow and pass values from the calling workflow.

Define the secrets in the caller repository and call the reusable workflow using the ‘secrets’ keyword.

Define the secrets in the reusable workflow's repository and reference the secret using the ‘secrets’ context.

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.

Execute scripts before and after a job

Dynamic scaling

Automatic updates to the operating system

GPU support

GitHub Apps always require two-factor authentication.

GitHub Apps can only be installed by organization owners.

GitHub Apps are limited to read-only access and cannot write to repositories.

GitHub Apps authenticate as an appwithfine-grained permissions, not as a user.

changes in permissions

B promoting users to administrators

pushes to repositories

changes to permissions of a GitHub App

cloning of repositories

Enterprise Managed Users can collaborate across both personal and enterprise repositories.

Personal Accounts are owned by users and can be used for both personal and professional work.

Personal Accounts provide stricter control over repositories and user activity.

Enterprise Managed Users require the organization to manage their own authentication server.

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.

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.